Issue #25 resolved

rev e4a7447a9251 doesn't build - MYUtilities signedness & needs to link Security.framework

Nicholas Riley
created an issue

I'm using the current MYUtilities (r252c13061ee5). I ran into a couple of issues trying to compile Murky, one with signedness (patch attached) and one with a missing framework.

{{{ Ld /Users/nicholas/src/murky/build/Debug/Murky.app/Contents/MacOS/Murky normal i386 mkdir /Users/nicholas/src/murky/build/Debug/Murky.app/Contents/MacOS cd /Users/nicholas/src/murky setenv MACOSX_DEPLOYMENT_TARGET 10.5 /Developer/usr/bin/gcc-4.2 -arch i386 -isysroot /Developer/SDKs/MacOSX10.5.sdk -L/Users/nicholas/src/murky/build/Debug -F/Users/nicholas/src/murky/build/Debug -filelist /Users/nicholas/src/murky/build/Murky.build/Debug/Murky.build/Objects-normal/i386/Murky.LinkFileList -mmacosx-version-min=10.5 -framework Cocoa -licucore -o /Users/nicholas/src/murky/build/Debug/Murky.app/Contents/MacOS/Murky Undefined symbols: "_SecCopyErrorMessageString", referenced from: _MYErrorName in MYErrorUtils.o ld: symbol(s) not found collect2: ld returned 1 exit status }}}

Comments (7)

  1. Jens Alfke repo owner

    Sorry about that — I had updated MYUtilities at the same time as Murky, but accidentally pushed MYUtilities to the wrong server. I've got the new revision up on bitbucket now.

  2. Peter Hosey

    So, I take it you're not going to pull the change to add Security.framework, since you've already fixed the error by conditionalizing the code that required it?

    If that's the case, I'll just strip the change from my repositories.

  3. Log in to comment