public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kyle at farnsworthtech dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/42947] multilib and startup files paths differ on sh4 with -m4 and without -m4 where -m4 is default multilib
Date: Fri, 09 Aug 2013 21:46:00 -0000 [thread overview]
Message-ID: <bug-42947-4-czSNK6NeZv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-42947-4@http.gcc.gnu.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
next parent reply other threads:[~2013-08-09 21:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-42947-4@http.gcc.gnu.org/bugzilla/>
2013-08-09 21:46 ` kyle at farnsworthtech dot com [this message]
2013-08-11 9:36 ` olegendo at gcc dot gnu.org
2013-08-12 0:43 ` kkojima at gcc dot gnu.org
2013-08-20 9:05 ` ams at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-42947-4-czSNK6NeZv@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).