On 4/13/06, Dave Murphy <[EMAIL PROTECTED]> wrote: > Daniel Jacobowitz wrote: > > On Thu, Apr 13, 2006 at 03:49:43PM +0100, Dave Murphy wrote: > > > >> Hi, > >> > >> I've been having some odd problems with relocation of 4.x toolchains - > >> i.e. when a toolchain is configured, built and installed with one prefix > >> but later moved to another location. The binaries appear to be checking > >> something in the old location before reading from the new path. > >> > > > > How did you configure the toolchain? Which was the configured install > > directory and which was the relocated install directory? > > > Sorry, meant to include this with the mail. > > > $ arm-elf-gcc -v > Using built-in specs. > Target: arm-elf > Configured with: ../../gcc-4.1.0/configure --enable-languages=c,c++ > --with-cpu=arm7tdmi --enable-interwork --enable-multilib --with-gcc > --with-gnu-ld --with-gnu-as --with-stabs --disable-shared > --disable-threads --disable-win32-registry --disable-nls --disable-debug > --disable-libmudflap --disable-libssp --target=arm-elf --with-newlib > --prefix=e:/devkitPro/devkitARM > Thread model: single > gcc version 4.1.0 (devkitARM release 18) > > configured install directory was e:/devkitPro/devkitARM, relocated to > c:/devkitARM > > This was built with mingw ( gcc 3.4.2 ) & minsys.
Maybe you could do a gcc -v hello.c and see what all it is looking for and where it is searching for. > > > Dave > > >
