From: John R. <jr...@ce...> - 2013-09-22 15:43:50
|
On Sep 22, 2013, at 7:21 AM, Ronan Waide <wa...@gm...> wrote: > Hmm, seems there's more to it than that. It looks like any attempt to build for i386 (I tried setting a few different target/sdk combinations) results in a failure to locate libiconv during the build. Telling jhbuild to skip libiconv during bootstrap doesn't fix this; I'm guessing maybe telling jhbuild to skip libiconv in all circumstances may cause different problems, but I'll have another look at this once the current "native" build finishes. The i386 image in /usr/lib/libiconv.dylib is fine; it's the x86_64 one that's missing symbols. But we fixed glib to not notice a long time ago, and libiconv hasn't been in the modulesets since--so `skip libiconv` is a no-op. Since libiconv is definitely in all of the SDKs up through 10.8, it seems likely that something's misconfigured. What does `xcode-select -print-path` emit? > On a similar thread, I've tried building with Xcode 5, and jhbuild initially bombs out because it uses a nonexistent compiler; adding os.environ settings for CC and CXX to point to /usr/bin/cc and /usr/bin/c++ respectively gets the build going, but it throws a bunch of errors elsewhere that I've not yet looked into. I'll leave this to one side for the moment since I have a working build environment to play with on the 10.7 machine. I added the necessary patches for Xcode5 when the 10.9 dev preview came out, but I hadn't pushed them because it was subject to Apple's NDA. Thanks for reminding me that it's now released. I'll push them today. Regards, John Ralls |