Ryan Schmidt wrote:
Also, it would be more "universal" if it was to use the 10.4u SDK on
Leopard too, since then the generated binaries would work on Tiger in
addition. (currently it uses the 10.5 SDK if available)
Yes, but I understood that it was changed to use the 10.5 SDK on
Leopard because using the 10.4u SDK on Leopard was broken?
No, the usage of it was broken. It wasn't setting
MACOSX_DEPLOYMENT_TARGET (to use 10.4)
"ld: library not found for -lcrt1.10.5.o"
Changing to the 10.5 SDK made the problem "go away", since it would
work with M_D_T=10.5
--anders
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-dev
