I've been attempting to explain that I think that doing universal builds with configure scripts (without muniversal) works on standard macports by accident. It is actually broken, but works just because the MacOSX sdk provides i386 headers and because CPPFLAGS didn't contain the -arch flag.
I'm now trying a case where the accident can't happen because the iOS sdk doesn't have the i386 headers and I have to use the -arch flag with the preprocessor.....so, the bug is being exposed for the first time. BTW: I could be wrong about this...I'll be the first to admit that my knowledge of this codebase is limited, and I'm therefore naive about it. I'm figuring it out in pieces as I go along, but learning a large batch of scripts in a alien language takes time. I'm just stating my theory that I've derived from working through the problems and going through the code. So, feel free to tell me I'm full of it. Also, the whole purpose of my investing weeks of engineering time into this project is to make iOS cross compiling a supported configuration. -James On Feb 3, 2011, at 5:19 PM, Toby Peterson wrote: > On Feb 3, 2011, at 11:54 AM, James Gregurich wrote: > >> I think that I'll change the expat port to use muniversal. >> >> >> >> Is this reasonable? > > Not really a reasonable change for the mainline expat, since it's not > necessary for supported configurations (i386, x86_64). If you do make the > change locally, I'm not sure it would work. Often, configure scripts want to > run commands on the build machine. Obviously, building only for armv6 would > not work in that situation. > > - Toby _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
