This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: configure issue during make of avr-elf

Ian Lance Taylor wrote:
Joel Sherrill <> writes:

Configuring in avr-elf/libgcc
configure: loading cache ./config.cache
configure: error: `CC' has changed since the previous run:

The change is that these options are new:

-nostdinc -B/home/cain/avr-tools/gcc/avr-elf/newlib/ -isystem /home/cain/avr-tools/gcc/avr-elf/newlib/targ-include -isystem /home/cain/src/gcc-svn/trunk/newlib/libc/include -B/home/cain/avr-tools/gcc/avr-elf/libgloss/avr -L/home/cain/avr-tools/gcc/avr-elf/libgloss/libnosys -L/home/cain/src/gcc-svn/trunk/libgloss/avr

These options are added by the top level configure script when newlib
and libgloss are present in the source tree and --with-newlib was passed
to configure.

This is what I would expect to happen if the student changed the source
tree by adding the newlib and libgloss directories and did a new build
without completely removing the old build.  I don't see how it could
possibly happen when doing a build in a fresh empty directory.  If it is
happening in a fresh empty directory, it might help to send the complete
output of make, to see why libgcc is being configured twice.

Josh, can you point Ian to where you put all your build logs?

Thanks Ian.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]