building gdb with newer clangs on 10.7 and Xcode <4.4
Gagan Sidhu
broly at mac.com
Wed Dec 25 17:40:21 UTC 2024
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
>
lawg: https://pastebin.mozilla.org/B6Tww3Lp
if i edit this file to just leave the ‘else’ exec, then the gdb configuration process goes fine.
i didn’t create a bug ticket since i am not sure if these scripts are still supposed to be here, as i have noticed others previously discussing 17664:
https://lists.macports.org/pipermail/macports-users/2021-April/049896.html
https://macports-tickets.macosforge.narkive.com/8GOtVcmE/macports-55008-py27-cython-0-27-1-does-not-build-on-snow-leopard-mac-os-x-10-6-8-after-upgrading
Thanks,
Gagan
> On Dec 25, 2024, at 10:32 AM, Ryan Carsten Schmidt <ryandesign at macports.org> wrote:
>
> On Dec 25, 2024, at 11:13, Gagan Sidhu wrote:
>>
>> i noticed that when building with older xcodes (the ones that can build a lion kernel on lion), that the scripts for newer clangs in /opt/local/bin interfere with compiling gdb.
>
> Can you be more specific? Which scripts? How do they interfere? What error message? Is there a bug report URL?
>
>
More information about the macports-dev
mailing list