Why is one compiler on 10.6 able to generate PPC binaries and not the other?
Mojca Miklavec
mojca at macports.org
Fri Mar 11 02:14:07 PST 2016
Hi,
A few more questions:
(1) If I want to target 10.5 from 10.6 I probably need libmacho and
libunwind as well? What about these lines from libcxxabi? Are they
most likely needed or not?
pre-build {
system "nm -g ${prefix}/lib/libmacho.a 2> /dev/null | grep
' \[DST\] ' | awk '{print \$3}' >
${worksrcpath}/unexported_symbols_macho"
system "nm -g ${prefix}/lib/libunwind.a 2> /dev/null |
grep ' \[DST\] ' | awk '{print \$3}' | grep -v '^__Unwind' >
${worksrcpath}/unexported_symbols_unwind"
system "cat ${worksrcpath}/unexported_symbols_macho
${worksrcpath}/unexported_symbols_unwind >
${worksrcpath}/unexported_symbols"
}
build.env-append \
EXTRA_LDFLAGS="${prefix}/lib/libmacho.a
${prefix}/lib/libunwind.a -unexported_symbols_list
${worksrcpath}/unexported_symbols"
(2) Installing libunwind +universal (with clang 3.4) fails with
"clang: error: unknown argument: '-fno-integrated-as'". If I remove
that flag from the Portfile it fails with
ld: absolute addressing (perhaps -mdynamic-no-pic) used in
_unwind_phase2 from ./UnwindLevel1.o not allowed in slidable image.
Use '-read_only_relocs suppress' to enable text relocs
and if I try to compile it with clang 3.7 it start installing gdbm
(most likely it tries to build clang 3.7 + universal) and fails.
If I don't need libunwind on 10.6 (for 10.5), then I'll skip it. If I
do, I need to find a workaround.
Thank you,
Mojca
More information about the macports-dev
mailing list