From: Jan Engelhardt <jengelh@medozas.de>
To: gcc-help@gnu.org
Subject: Re: sparc64: -m64 implies -mlong-double-64
Date: Sat, 12 Dec 2009 01:01:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.01.0912120146240.10776@obet.zrqbmnf.qr> (raw)
In-Reply-To: <alpine.LSU.2.01.0912112319460.7623@obet.zrqbmnf.qr>
On Friday 2009-12-11 23:23, Jan Engelhardt wrote:
>
>I observe that -m64 throws an error on the given configuration:
>
>$ touch x.c
>$ gcc -m64 x.c
>x.c:1: error: -mlong-double-64 not allowed with -m64
Replying to myself and the archive:
The error can show up if one tries to use the sparc64-defaulting gcc
frontend with a sparc32-defaulting(sparc64-capable) cc1. Pointing the
gcc64 to the right cc1 using -B/appropriate/prefix solves it for me.
Background: Let /ch be a chroot environment with a gcc64. When calling
/ch/usr/bin/gcc, -B may be needed. Some distributions have cc1 in
usr/lib/gcc rather than usr/libexec/gcc. Where this is the case, the gcc
frontend seems to use a relative pathspec "../lib/gcc" (observed on
openSUSE gcc -v) so that -B is not strictly needed. But it turns out
Fedora uses an absolute pathspec "/usr/libexec/gcc".
prev parent reply other threads:[~2009-12-12 0:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-12 0:59 Jan Engelhardt
2009-12-12 1:01 ` Jan Engelhardt [this message]
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=alpine.LSU.2.01.0912120146240.10776@obet.zrqbmnf.qr \
--to=jengelh@medozas.de \
--cc=gcc-help@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).