This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug other/45994] New: During 'make clean', some variables not propagating properly
- From: "phantall at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 12 Oct 2010 22:14:15 +0000
- Subject: [Bug other/45994] New: During 'make clean', some variables not propagating properly
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45994
Summary: During 'make clean', some variables not propagating
properly
Product: gcc
Version: 4.5.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: phantall@gmail.com
During a make clean, when it attempts to execute 'make clean' for
<target>/libgcc, the 'CC' variable is populated with 'CC_FOR_TARGET' which may
not be populated during a 'clean'. This cascades into another problem on a few
different lines in <target>/libgcc/Makefile. For example, on (or about) <gcc
build path>/sparcv9-sun-solaris2.10/libgcc/Makefile:199, the following line is
present:
version := $(shell $(CC) -dumpversion)
$(CC) typically populates this line with something of the form:
<gcc build path>/./gcc/xgcc -B<some path> -B<some other path> (and so on)
... when this Makefile is used. However, at the moment it's populating CC with
the empty string, which results in that 'version' line looking (in effect) like
this:
version := ($shell -B<some path> -B<some other path> <etc> -dumpversion)
... causing bash to exit with the error:
/bin/bash: -/: invalid option
(bash usage info below this line)
Temporary workaround is to enter the <target>/libgcc directory and manually
'make clean', or during
-Brian