Building a cross-compiler

James Tebneff tebneff@gmail.com
Tue Jan 29 06:54:00 GMT 2008


On Jan 29, 2008 11:06 AM, Michael Witten <mfwitten@mit.edu> wrote:
>
> On 28 Jan 2008, at 6:44 PM, Wenton L. Davis wrote:
>
> > John Carter wrote:
> >>
> >> It's a _very_ dark art....
> > No kidding!!!!
>
> I disagree wholeheartedly.
>
> Creating a cross compiler _should_ be the easiest
> thing in the world, but the gcc is so backasswards
> that it can be troublesome.
>
> >> Some hints:...
> >>
> >> There is a nasty tangly dependency between binutils, libc and the
> >> compiler.
> >>
> >> Last time I did it, I found I had to have the binutils --prefix
> >> directory
> >> the same --prefix as the compiler.
>
> This is definitely the case; gcc is really just an
> interface to a bunch of different tools, so it needs
> to know where to find those tools.
>
> It would be nice if there were a configure directive
> to specify the location of binutils tools for greater
> flexibility. For now, just make --prefix the same for
> both.
>
> In any case, you're supposed to be able to put the
> binutils source subdirectories (gprof, opcodes,
> bintutils, ...) inside the top level of the gcc source
> code so that one configure invocation handles both; both
> source trees are actually 2 separate views of a larger
> tree.
>


Yes check out the documentation for a Combined build

http://gcc.gnu.org/simtest-howto.html

Regards

JT



More information about the Gcc-help mailing list