Compiling x264 for i386?

Autotooled configure scripts have special command-line arguments build and host that they use to configure cross-compilation. Some old configure scripts attempt to figure out they are cross-compiling by inspecting the output of the compiler, but telling the configure script explicitly is much saner and more robust See here for example. Or this question (Oh, and the immediate reason for the "Unknown option" errors you're seeing is that environment-variable overrides go before the name of the script on the sh command line, not after it.It's not make where variable definitions can be given on the make command line itself.

).

Autotooled configure scripts have special command-line arguments --build and --host that they use to configure cross-compilation. Some old configure scripts attempt to figure out they are cross-compiling by inspecting the output of the compiler, but telling the configure script explicitly is much saner and more robust. See here, for example.

Or this question. (Oh, and the immediate reason for the "Unknown option" errors you're seeing is that environment-variable overrides go before the name of the script on the sh command line, not after it. It's not make, where variable definitions can be given on the make command line itself.).

Configure has been taking options this way for a long time now. – Per Johansson Aug 25 at 15:21 Oh. Well, apparently the one the OP is using doesn't.(I'm extrapolating its behavior from the wording of the error messages he quoted).

– Henning Makholm Aug 25 at 15:23 Yes, you're right. And not all configure scripts are autoconf anyway. – Per Johansson Aug 25 at 21:20 So if I use .

/configure --host=i386-apple-darwin10 it says "no working C Compiler found", is there any way to print a list of valid hosts? – user293895 Aug 27 at 1:51.

If you have an x86-64 gcc you can supply the "-m32" to ask it to compile a 32-bit binary. So you should be able to use configure like this: . /configure CFLAGS="-m32" If however that doesn't work it may be a bug in the autotooling and the CFLAGS are getting overwritten.An alternative you can try: make CFLAGS="-m32" The problem with the latter is that you have to remember to do this, otherwise you'll end up with linking issues with some object files built for different architectures.

You may also need LDFLAGS="-m32" to get the linking done right. – Zan Lynx Aug 25 at 15:33.

As per Apple's recommendations at developer.apple.com/library/mac/#documen... try: . /configure make CFLAGS="-arch i386" LDFLAGS="-arch i386" If that doesn't work add the -isysroot flags as well (but 10.6 or 10.7 rather than 10.4u).

Unfortunately this doesn't work, it just throws up a lot of errors – user293895 Aug 28 at 1:42.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.