Danny Backx wrote: > > I always forget exactly how to force "configure" to do the right thing, > but you might want to try this : > % setenv CC arm-wince-cegcc-gcc > % setenv AR arm-wince-cegcc-ar > % setenv RANLIB arm-wince-cegcc-ranlib > % ./configure --target=arm-wince-cegcc > % make >
For a library, it's --host that matters. Think of it as the host where the code you're compiling is going to run. --target is only makes sense in the context of a cross compiler or cross debugger (or a cross anything else). Eg: Compiling gcc with '--host=xxx --target=yyy' means that the code (the compiler) is going to run on host xxx, and is going to produce code for target yyy. You can then go further like: --build=bbb --host=xxx --target=yyy : that is, I want to build a compiler that runs on host xxx, but I'm going to build it on a bbb machine, and I want that compiler to cross-compile code for target yyy. > This build libjpeg flawlessly on my system. > > Note that there's no -fPIC in the compiler command line, I don't think > you can/should use that for ARM. > It's not about ARM. Currently, -fPIC is only implemented for elf targets. As you can see, the linker was complaining about a GOT, which is elf specific. Cheers, Pedro Alves ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Cegcc-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cegcc-devel
