From: Andi Kleen <andi@firstfloor.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: markus at trippelsdorf dot de
<sourceware-bugzilla@sourceware.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>, Andrew Lutomirski <luto@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Andi Kleen <andi@firstfloor.org>
Subject: Re: [Bug gold/19197] gold trunk cannot build LInux kernel
Date: Fri, 6 Nov 2015 04:19:40 +0100 [thread overview]
Message-ID: <20151106031940.GF3533@two.firstfloor.org> (raw)
In-Reply-To: <CALCETrWpR-7H3x0XF9UFwNbMNgGUGddk0tST69hjncjZVVGYrQ@mail.gmail.com>
> I don't know the history here. hpa? Andi?
>
> Presumably we could strip the problematic -m argument from just the
> 32-bit things is we care.
I don't think it was intentional or there from the beginning, probably a bug
added somewhere on the way. Removing it seems fine.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2015-11-06 3:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-19197-6758@http.sourceware.org/bugzilla/>
[not found] ` <bug-19197-6758-9zxzEhVG3v@http.sourceware.org/bugzilla/>
2015-11-03 18:43 ` [Bug gold/19197] gold trunk cannot build LInux kernel Andy Lutomirski
2015-11-06 3:19 ` Andi Kleen [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=20151106031940.GF3533@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=sourceware-bugzilla@sourceware.org \
--cc=x86@kernel.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