[MacPorts] #58935: go @1.13: build fails on 10.9 and less
MacPorts
noreply at macports.org
Tue Oct 8 02:08:17 UTC 2019
#58935: go @1.13: build fails on 10.9 and less
---------------------+-------------------------------
Reporter: kencu | Owner: ci42
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords: lion mountainlion
Port: go |
---------------------+-------------------------------
Comment (by Ionic):
Good, that seems to work:
{{{
% nm -arch x86_64 $(port work legacy-
support)/destroot/opt/local/lib/libMacportsLegacySupport.dylib | grep -i
fdopendir
0000000000002aa5 T _fdopendir
0000000000002bb1 T _fdopendir$INODE64
% nm -arch i386 $(port work legacy-
support)/destroot/opt/local/lib/libMacportsLegacySupport.dylib | grep -i
fdopendir
00002a55 T _fdopendir
00002c6f T _fdopendir$INODE64$UNIX2003
00002b62 T _fdopendir$UNIX2003
}}}
This stuff still seems very fragile...
Ken, you do have access to ppc machines, right?
I'd like to see the output of
{{{
% nm -arch ppc /usr/lib/system/libsystem_c.dylib | grep opendir
% nm -arch ppc64 /usr/lib/system/libsystem_c.dylib | grep opendir
}}}
on a 10.5, 10.6, and, if possible, also a 10.4 machine.
I need to know how to tweak that stuff for `ppc` and `ppc64`.
10.4 is interesting because the first UNIX-certified version was 10.5 as
far as I remember, so I suspect that 10.4 won't have $UNIX2003-postfixed
symbols. In that case, I'd like to make the `fdopendir` implementation
10.5+ only.
--
Ticket URL: <https://trac.macports.org/ticket/58935#comment:14>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list