This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/42947] multilib and startup files paths differ on sh4 with -m4 and without -m4 where -m4 is default multilib
- From: "kyle at farnsworthtech dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 09 Aug 2013 21:46:20 +0000
- Subject: [Bug target/42947] multilib and startup files paths differ on sh4 with -m4 and without -m4 where -m4 is default multilib
- Auto-submitted: auto-generated
- References: <bug-42947-4 at http dot gcc dot gnu dot org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42947
Kyle Farnsworth <kyle at farnsworthtech dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kyle at farnsworthtech dot com
--- Comment #1 from Kyle Farnsworth <kyle at farnsworthtech dot com> ---
I encountered this same issue. When I added the -print-sysroot option to see
what gcc was thinking was the sysroot setting it revealed this:
WITH -m4 option:
$ sh4-oe-linux-gcc -ml -m4 --sysroot=sysroots/sh775x-oe-linux -print-sysroot
sysroots/sh775x-oe-linux/m4
WITHOUT -m4 option:
$ sh4-oe-linux-gcc -ml --sysroot=sysroots/sh775x-oe-linux -print-sysroot
sysroots/sh775x-oe-linux
It appears some arguments are getting mangled and somehow the m4 option is
concatinated to the end of the sysroot.
My workaround was to add symlink sysroots/sh775x-oe-linux/m4 to point to "./".
$ sh4-oe-linux-gcc --version
sh4-oe-linux-gcc (GCC) 4.7.2