Re: GCC-4.0.2 on Cygwin

[Brian Rose <lists at brianrose dot net>]

Jim Tison wrote:
> Bleh ... this will teach me to post at midnight!
>
> --build is where you're running the configury/build process. That's 
> self-evident and defaults to the sane value.
>
> --host is where you want the language processor to *run*. If you don't 
> specify it, it will equal --build.
>
> --target is the architecture for which you want the language processor 
> to *emit* code.
>
> When --host == --build != --target, you'll build a normal cross compiler.
> When --host != --build != --target, you'll have a Canadian Cross.

So when I build binutils, I do it with the following commands...
(from a build directory)

$ ../../binutils-2.16.1/configure --target=m68k-elf --prefix=$HOME/rtems/tools
$ make && make install

So I look in the $HOME/rtems/tools directory and I see a bin and a m68k-elf 
directory. In bin I see the m68k-elf-* tools which have the correct target. 
But GCC seems to be looking in the m68k-elf/bin directory, where I have ar, 
as, etc which have the i686-pc-cygwin target. Having an i686-pc-cygwin 
target program in the m68k-elf directory doesn't make sense. Can somebody 
shed light on this?

Anyway, GCC is supposed to look in the prefix/bin directory for the tools. 
 GCC should also prepend the target to the filename to get the complete 
path  name of prefix/bin/target-tool, correct? If so, then something is 
broken because those files are present.

In any event, I can modify my build script to explicitly call the correct 
assembler and linker. I would like to solve this, because I don't think 
that this should be nessecary.

../../gcc-4.0.2/configure --target=m68k-elf --prefix=$HOME/rtems/tools 
--with-as=$HOME/rtems/tools/bin/m68k-elf-as.exe 
--with-ld=$HOME/rtems/tools/bin/m68k-elf-ld.exe



--

Brian

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com