Cross compile error question: i686 to powerpc--linux-gnu
Thu Oct 18 10:14:00 GMT 2001
"M. R. Brown" wrote:
> It's a Good Thing as long as you know how to "opt-out" of certain
> compilerisms by using gcc's extensive options. I'd suggest anyone
> seriously working with gcc read it's info pages, particulary the node
> "Invoking GCC". Especially read up on target-specific options.
And that is my question...how do I "opt-out" of these things when building?
There seems to be a lot of problems caused by this right now, and I'm basically
doing it for some functionality I don't need.
So, my base question is, can I set come configuration options to get gcc to
compile and behave as a bare-bones, text-in/text-out compiler that generates
target assembly code? Then, can I also get a linker that makes me have to
specify what I need in order to link?
Because, for the purpose of what I'm doing, I don't NEED threaded support.
I don't NEED shared library support. I'm compiling this on a box, and putting
the code in an embedded system for which I will be writing libraries (including
base C functionality). All it needs to do is give me assembly code which I can
run the linker on myself.
Now, my problems with getting the linker working...that's a separate issue
(which I'm assuming at this point is a configuration screw-up on my part). :)
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to firstname.lastname@example.org
More information about the crossgcc