2010/1/25 Jeff Pohlmeyer <yetanothergeek_at_gmail.com>:
> On Mon, Jan 25, 2010 at 8:15 AM, ErrolLeRoux wrote:
>
>
>> Where can I get more info on the configure script - In the manual??
>
> "./configure --help" is a good place to start.
>
> In particular, you'll probably want to specify the correct
> --host= and --target= and --build=  options, and make sure
> the cross-compiler, etc. is in your $PATH.

--target is only needed if you're building a compiler or something
like that (which produces object code targeted at the specified
architecture).

--build is automatically guessed (and normally correct).

So, --host is likely the only one that's needed.

--host might be something like mipsel-linux-uclibc with the compiler
being named mipsel-linux-uclibc-gcc and other tools being named
similarly. Some toolchains have a different naming scheme, though,
but I think if you just use the prefix of the compiler in --host=
you'll probably be OK.

You could also try something like:

$ CC=/path/to/cross-compiler/mips-gcc ./configure ...

if --host=... doesn't work by itself.

>> I don't want to mess up the OpenSUSE binaries.
>
> Of course it is always a good idea to NOT be root when compiling
> anything, especially when you're in uncharted waters!

Yes, if you're compiling as a normal user, there's no way you can
overwrite the system binaries, unless the permissions on the system
binaries are really messed up already.

-- 
Michael Wood <esiotrot_at_gmail.com>
Cape Town, South Africa
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html