Re: Confusion on 'specs' file in m68k-aout cross compiler build...

[Doug Evans <dje at transmeta dot com>]

Brendan J Simon writes:
 > > $ rm ./specs
 > > $ gcc -v
 > > Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.2/specs
 > > gcc version 2.95.2 20000220 (Debian GNU/Linux)
 > > $ touch specs
 > > $ gcc -v
 > > Reading specs from ./specs
 > > gcc version 2.95.2 20000220 (Debian GNU/Linux)
 > 
 > This definately looks weird to me.  Why would "touch" cause gcc to look in a different
 > place for the specs file ?

All he's done is create a file (an empty file) that didn't already exist.
The purpose is to see if gcc is looking in the current directory for
`specs' (without being told to :-).  It is, and that is wrong.

 > What directory were you in when you ran "touch" ?  If the
 > file does not exist then touch will create an empty file.  "touch -c" will touch the
 > file if it exists but will not create a new file if it does not exist.

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