building gdb with newer clangs on 10.7 and Xcode <4.4

[Ken Cunningham]

These scripts have worked perfectly for years. 

They work fine for me now, and on all the buildbots. 

Please explain or demonstrate exactly what problem you believe you are experiencing. The problem is most likely in your setup.

Ken


Sent from my iPhone

> On Dec 25, 2024, at 9:47 AM, Gagan Sidhu via macports-dev <macports-dev at lists.macports.org> wrote:
> 
> i think it’s an old and unneeded workaround for newer clangs. could someone look into this?
> 
> i know that it’s not needed for newer clangs and, if anything, will frustrate any potential users from staying with our package manager.
> 
> in my experience i’ve found this macro to be more of a hindrance than a positive. i would appreciate a resolution to improve our competitiveness in this space.
> 
> Thanks,
> Gagan
> 
>> On Dec 25, 2024, at 10:45 AM, Ryan Carsten Schmidt <ryandesign at macports.org> wrote:
>> 
>>> On Dec 25, 2024, at 11:40, Gagan Sidhu wrote:
>>> 
>>> it’s the scripts or macro check for xcrun are causing a problem:
>>>> 
>>>> vms-Mac-2:MacOS vm$ cat /opt/local/bin/clang++-mp-17
>>>> #!/bin/bash
>>>> 
>>>> if [ -x /usr/bin/xcrun ] ; then
>>>>  exec /usr/bin/xcrun /opt/local/libexec/llvm-17/bin/clang++ "${@}"
>>>> else
>>>>  exec /opt/local/libexec/llvm-17/bin/clang++ "${@}"
>>>> fi
>> 
>> Oh. I didn't know our clang was a wrapper script that did this.
>> 
>> 
>