From: Tim Deegan <tim@xen.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: Juergen Gross <juergen.gross@ts.fujitsu.com>,
xen-devel <xen-devel@lists.xen.org>,
Yuriy Logvinov <hackroute@mail.ru>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: compiling error "xen-unstable.hg"
Date: Thu, 2 Aug 2012 11:53:16 +0100 [thread overview]
Message-ID: <20120802105316.GC11437@ocelot.phlegethon.org> (raw)
In-Reply-To: <5016539D020000780009134A@nat28.tlf.novell.com>
At 08:27 +0100 on 30 Jul (1343636877), Jan Beulich wrote:
> > We might do better to switch to '$(CC) --version | head -1', which seems
> > to provide something sensible on all the gcc and clang binaries I have
> > handy.
>
> The question is how relevant that string is in the first place:
> My cross compilers, for example, get invoked through a shell
> scripts that's named gccx. Invoking that with --version
> reproduces the shell script name (which the script forces as
> the argv[0] of the exec-ed "real" gcc):
>
> gccx (GCC) 4.7.1
>
> which isn't the case for -v:
>
> gcc version 4.7.1 (GCC)
Sigh.
> So as long as no deeper meaning is implied from the string by
> anyone (there's nothing in-tree that I'm aware of), I think
> that's at least as good a change as adding LC_ALL=C (of
> which I'm not really certain whether it would be fully reliable
> in all possible cases).
I'm not aware of anyone/anything that relies on that string except for
human consumption. I'll submit a patch to change to --version.
Cheers,
Tim.
prev parent reply other threads:[~2012-08-02 10:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 7:24 compiling error "xen-unstable.hg" hackroute
2012-07-27 7:56 ` Jan Beulich
2012-07-27 8:33 ` Ian Campbell
[not found] ` <1343380597.380868008@f116.mail.ru>
2012-07-27 9:25 ` Ian Campbell
[not found] ` <1343382308.59310320@f318.mail.ru>
2012-07-27 9:54 ` Ian Campbell
[not found] ` <1343380992.326297641@f89.mail.ru>
2012-07-27 10:14 ` Jan Beulich
2012-07-27 10:25 ` Ian Campbell
2012-07-27 10:38 ` Jan Beulich
2012-07-27 10:58 ` Juergen Gross
2012-07-27 20:29 ` Tim Deegan
2012-07-30 7:27 ` Jan Beulich
2012-08-02 10:53 ` Tim Deegan [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=20120802105316.GC11437@ocelot.phlegethon.org \
--to=tim@xen.org \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=hackroute@mail.ru \
--cc=juergen.gross@ts.fujitsu.com \
--cc=xen-devel@lists.xen.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 NNTP newsgroup(s).