building gdb with newer clangs on 10.7 and Xcode <4.4

[Gagan Sidhu]

from what i can see, the issue isn’t with the nodejs.  

but you enjoy dwelling on things like nodejs22 having issues and claiming it applies in general, which is false.

your last response needs no further comment.

you relish a role you haven’t proven you can fulfil. simple as that. 

Thanks,
Gagan
> On Dec 25, 2024, at 11:50 AM, Ken Cunningham <ken.cunningham.webuse at gmail.com> wrote:
> 
> You've been here a few months, and you still know very little.
> 
> Have some humility. Ask for help rather than think everything has been broken until you came along.
> 
> And -- fix all those broken nodejs ports -- all the ones you pushed are broken, I understand, and I don't have time to fix them.
> 
> K
> 
> 
> 
>> On Dec 25, 2024, at 10:44 AM, Gagan Sidhu <broly at mac.com> wrote:
>> 
>> i just gave the log of the problem, so i don’t see how you can ask that.
>> 
>> i don’t appreciate your attitude sometimes. and you wonder why people don’t want to stick around.
>> 
>> READ 
>> 
>> Thanks,
>> Gagan
>> 
>>> On Dec 25, 2024, at 11:17 AM, Ken Cunningham <ken.cunningham.webuse at gmail.com> wrote:
>>> 
>>> 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.
>>>>> 
>>>>> 
>>>> 
>> 
> 

Thanks,
Gagan