This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/43531] [4.5 Regression] host files being used during cross compilation
- From: "rwild at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 7 Apr 2010 05:38:16 -0000
- Subject: [Bug bootstrap/43531] [4.5 Regression] host files being used during cross compilation
- References: <bug-43531-9565@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #23 from rwild at gcc dot gnu dot org 2010-04-07 05:38 -------
(In reply to comment #21)
> (In reply to comment #20)
> > Is this fixed now?
> The hard-breakdown due is gone, but now I am observing another bug:
[...]
> Note the
> -I../../gcc//users/rtems/src/toolchains/gcc-trunk/BUILD/h8300-rtems4.11/h8300h/libgcc
In what way is that a bug (honest question)? Does it cause any wrong
semantics or not? The path should point nowhere AFAICS.
This particular command line argument was expanded from gcc/Makefile.in
INCLUDES = ... -I$(srcdir)/$(@D) ...
with $(srcdir) being ../../gcc and the $(@D) the dirname of $@ which is
/users/rtems/src/toolchains/gcc-trunk/BUILD/h8300-rtems4.11/h8300h/libgcc
in this case. That $@ is absolute comes from the fact that this rule is
invoked from the libgcc/Makefile:gcc-extra-parts rule which sets
T=`$(PWD_COMMAND)`.
That all then looks weird for this rule where the target has an absolute
name, but seems harmless to me otherwise.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43531