Comments on: Missing Link

By: Daniel Jalkut

Daniel Jalkut — Fri, 23 Feb 2007 20:39:15 +0000

Mike: I wish I had more concrete instructions for how to get around all the niggling problems, but to be honest what I ended up doing was just going through and painstakingly figuring out the failures one at a time, and sometimes rather crudely hacking around the failures.

I believe the failure you’re seeing there is based on a problem where the System path is getting searched for libraries, instead of fetching all libraries from the SDK path. You need to go through and eradicate all references to “/usr/local/lib” for instance. Maybe taking out that -rpath argument would do the trick.

But then you have to look in those .la arguments and make sure THEY don’t list any / relative libraries in their dependencies.

There is probably a “right way” to fix it but that’s how I would pursue it if you just need to hack out a solution.

By: Mike Laster

Mike Laster — Fri, 23 Feb 2007 20:28:15 +0000

I ran into the *exact* same problem you did trying to build a Universal version of Subversion. What change did you make to make this problem go away?

I followed the instructions on TN2137:

CFLAGS=”-O -g -isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc” LDFLAGS=”-arch i386 -arch ppc” ./configure
make

and I get a link error:

cd subversion/libsvn_ra_dav && /bin/sh /tmp/subversion-1.4.3/libtool –tag=CC –silent –mode=link gcc -O -g -isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc -arch i386 -arch ppc -L/tmp/subversion-1.4.3/apr-util/xml/expat/lib -rpath /usr/local/lib -o libsvn_ra_dav-1.la commit.lo fetch.lo file_revs.lo log.lo merge.lo options.lo props.lo replay.lo session.lo util.lo ../../subversion/libsvn_delta/libsvn_delta-1.la ../../subversion/libsvn_subr/libsvn_subr-1.la /tmp/subversion-1.4.3/apr-util/libaprutil-0.la /tmp/subversion-1.4.3/apr-util/xml/expat/lib/libexpat.la -liconv /tmp/subversion-1.4.3/apr/libapr-0.la -lresolv -lpthread /tmp/subversion-1.4.3/neon/src/libneon.la -framework Security -framework CoreFoundation -framework CoreServices -lz
libtool: link: warning: `/usr/lib/gcc/powerpc-apple-darwin8/4.0.1/../../..//libiconv.la’ seems to be moved
libtool: link: warning: `/usr/lib/gcc/powerpc-apple-darwin8/4.0.1/../../..//libiconv.la’ seems to be moved
libtool: link: warning: `/usr/lib/gcc/powerpc-apple-darwin8/4.0.1/../../..//libiconv.la’ seems to be moved
ld: Undefined symbols:
_acl_copy_ext_native referenced from CarbonCore expected to be defined in libSystem
_acl_copy_int_native referenced from CarbonCore expected to be defined in libSystem
_task_name_for_pid referenced from CarbonCore expected to be defined in libSystem
/usr/bin/libtool: internal link edit command failed
lipo: can’t figure out the architecture type of: /var/tmp//ccFJj5J0.out

By: Scott Stevenson

Scott Stevenson — Wed, 03 Jan 2007 02:07:52 +0000

I did a whole blog post about a Rails migration error only to have Dominik Wagner point out to me that the variable name was wrong. It was, like, ten lines of code.

I win.

By: Mike Zornek

Mike Zornek — Tue, 02 Jan 2007 23:10:30 +0000

I feel for ya.

Just last night I narrowed a core data relationship bug down to it’s there when I deploy but not during regular development (even if I use the release config).

At first I though I was getting a different result from the xcode command line than the GUI but then I eventually found a bad model in svn. Schema 6 at some point was edited and was in the repo but my my ~/Projects/Billable folder. This by the way took about 3 hours to really understand.

Don’t sweat it! :-)

By: Chucky

Chucky — Tue, 02 Jan 2007 21:41:30 +0000

“You can’t expect ld to prefix full-path specifications with the SDK path.”

I wish someone had let me know this before my wedding night.

By: Daniel Jalkut

Daniel Jalkut — Tue, 02 Jan 2007 20:56:36 +0000

Heh, thanks for saying so, rentzsch :) I replied to somebody off-line comment, saying that I figure mistakes go with this profession, and are also educational in their own way.

By: rentzsch

rentzsch — Tue, 02 Jan 2007 20:51:49 +0000

I link-blogged this, but I’ll also put it here for better locality of reference:

I love this entry. It’s the common case than I find “here’s a bug!” + later “oh it’s not a bug, here’s the story”-style postings more valuable than straight-up “publishing-what-I-know” pieces.

Bottom-line: I like trigger-happy blog entries penned by smart guys like you when they enumerate solution attempts, and provide an interesting back story.