attica fails to build on Tiger

[roberto@…]

When updating today, attica failed to build. I have attached the complete log.

[ryandesign (Ryan Carsten Schmidt)]

The relevant lines in the log are:

ld: warning can't open dynamic library: /Developer/SDKs/MacOSX10.4u.sdk/opt/local/lib/libz.1.dylib referenced from: /opt/local/libexec/qt4-mac/lib/QtCore.framework/QtCore (checking for undefined symbols may be affected) (No such file or directory, errno = 2)
ld: warning can't open dynamic library: /Developer/SDKs/MacOSX10.4u.sdk/opt/local/lib/libssl.0.9.8.dylib referenced from: /opt/local/libexec/qt4-mac/lib/QtNetwork.framework/QtNetwork (checking for undefined symbols may be affected) (No such file or directory, errno = 2)
ld: warning can't open dynamic library: /Developer/SDKs/MacOSX10.4u.sdk/opt/local/lib/libcrypto.0.9.8.dylib referenced from: /opt/local/libexec/qt4-mac/lib/QtNetwork.framework/QtNetwork (checking for undefined symbols may be affected) (No such file or directory, errno = 2)

It means the link flags -lz -lssl -lcrypto are missing.

This problem is unique to using a Mac OS X SDK on Tiger; with Leopard and later Xcode figures this out for you. In this case there's not even really a reason to be using an SDK since we're building on i386 for i386. But cmake seems to decide that it should always use the SDK when on Tiger, thus causing this problem. We could work around it by either telling cmake to not use the SDK, or by adding the required -l flags.

[nerdling (Jeremy Lavergne)]

So this wasn't a result of qt4-mac referencing non-existant paths? It sounds like we're overriding qt4-mac...

[nerdling (Jeremy Lavergne)]

Untested patch using additional LD flags when compiled on Tiger, r68174.

[cenci@…]

Replying to snc@…:

Untested patch using additional LD flags when compiled on Tiger, r68174.

Patch has a typo: crytpo -> crypto
Tested on Macports 1.9.0 Tiger 10.4.11 XCode 2.5
I reopen the ticket, I don't know if I did the right thing, first time aroun

[nerdling (Jeremy Lavergne)]

Typo fixed in r69085. Let me know if it works aside from the typo … ;-)