On 25/05/14 13:28, Justin Cormack wrote:
> Another approach is to just teach buildrump.sh about more kinds of
> targets, eg evbarm-earmv7hf etc - mostly what we are trying to do is
> deal with the fact that we are not building the compiler. So add a
> (guessed if not specified) -m machine target and convert that to gcc
> flags. So ./buildrump.sh -m earmv5eb would build for that regardless
> of toolchain defaults (assuming the toolchain can build for that of
> course). I think for arm that would solve all the issues. For mips
> this wont entirely work as the machine names do not always encode the
> ABI, but another abi flag could be added so ./buildrump.sh -m mipsel
> -a n32 perhaps.
>
> If people then want to tweak with more specific flags thats another
> step, but at least you can force a cross build that works to the right
> platform. Alternatively we could not exactly match the netbsd names
> for eg mips and have buildrump specific ones.

Dunno, it sounds like a lot more work for us to provide some -m/-n 
grammar instead of just allowing to specify compiler flags.  It's also 
more work for the users, since they can't quite be sure if -m/-n params 
map to the compiler flags they know (and I do assume that anyone who 
wants to compile for earmv7hf knows what they're doing ;)

I'm not sure if there's a good answer for what an "ambiguous" compiler 
should produce with buildrump.sh.  Maybe the best thing to do is to 
remove magic like EXTRA_CFLAGS=-march=armv6k, throw an error, and ask 
that the user is more specific.

------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
rumpkernel-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rumpkernel-users

Reply via email to