universal_cflags in 10.5 cause linking issue

[gzjjgod@…]

If we use the default configure.universal_cflags to build universal binary in Mac OS X 10.5, error like

ld: library not found for -lcrt1.10.5.o

will happend. See also  http://lists.apple.com/archives/Xcode-users/2007/Oct/msg00686.html

This patch fixed this by adding "-mmacosx-version-min=10.4" into default configure.universal_cflags.

[gzjjgod@…]

patch to portconfigure.tcl

[wsiegrist@…]

Not an infrastructure issue. Sending to jmpp for reclassification.

[eridius@…]

We target the 10.5 SDK if it exists now, so is this problem still valid?

[gzjjgod@…]

No, if -isysroot /Developer/SDKs/MacOSX10.5.sdk is used, such linking problem will not happen.

[afb@…]

Replying to eridius@macports.org:

We target the 10.5 SDK if it exists now, so is this problem still valid?

Only if cross-developing, which isn't supported. (or if 10.5 SDK is missing, which isn't either)

[mdickens@…]

At least in MacPorts 1.6.0, this ticket no longer seems to be an issue.

Ticket #11267 provides a tarball that (at least in my testing) allows for python25 +universal, +framework, +universal+framework, or just plain; for both 10.4 (using the 10.4SDK for +universal) and 10.5 (using the 10.5SDK for +universal); all combinations of variants seem to work correctly. While the resulting binaries using +universal are for "i386" and "ppc", it would not be difficult to add variants to do "ppc64" and "x86_64" (though, of course, 64-bit apps are not well-tested on OSX just yet).

[toby@…]

Milestone MacPorts base bugs deleted