Bug 45503 - "make distclean" Does Not Remove All Local Configuration Data
Summary: "make distclean" Does Not Remove All Local Configuration Data
Status: RESOLVED DUPLICATE of bug 25470
Alias: None
Product: gcc
Classification: Unclassified
Component: other (show other bugs)
Version: 4.5.1
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-02 17:53 UTC by Tom Browder
Modified: 2017-07-24 18:10 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Browder 2010-09-02 17:53:18 UTC
After an aborted or clean build in a directory outside the gcc source tree, "make distclean" is supposed to remove all configuration information.  However, that is not the case for at least one target (pdf).  Using gcc-4.5.1 in my build directory (as a bash user):

$ cd gcc_build
$ ../gcc-4.5.1/configure
... # nothing unusual
$ make pdf
... # nothing unusual except pdf target seems to
    # result in LOTs of extra compilation

Come back the next day

$ export CC=/usr/local/bin/gcc-4.5.1
$ cd gcc_build
$ make distclean
$ ls -aCF
./  ../  fixincludes/
$ ../gcc-5.5.1/configure
... # nothing unusual
$ make pdf
make[1]: Entering directory `/usr/local/src/gcc_build'
make[2]: Entering directory `/usr/local/src/gcc_build'
make[2]: Leaving directory `/usr/local/src/gcc_build'
Configuring in ./fixincludes
configure: loading cache ./config.cache
configure: error: `CC' has changed since the previous run:
configure:   former value:  `gcc'
configure:   current value: `/usr/local/bin/gcc-4.5.1'
configure: error: in `/usr/local/src/gcc_build/fixincludes':
configure: error: changes in the environment can compromise the build
configure: error: run `make distclean' and/or `rm ./config.cache' and start over
make[1]: *** [configure-fixincludes] Error 1
make[1]: Leaving directory `/usr/local/src/gcc_build'
make: *** [do-pdf] Error 2
Comment 1 Eric Gallager 2017-07-24 18:10:38 UTC
Duplicate of bug 25470 which was itself fixed.

*** This bug has been marked as a duplicate of bug 25470 ***