From: Matthew Wilcox <matthew@wil.cx>
To: David Ronis <ronis@ronispc.chem.mcgill.ca>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.23.1->2.6.23.8 breaks root Makefile
Date: Mon, 19 Nov 2007 09:34:38 -0700 [thread overview]
Message-ID: <20071119163437.GD12494@parisc-linux.org> (raw)
In-Reply-To: <1195489140.21337.10.camel@ronispc.chem.mcgill.ca>
On Mon, Nov 19, 2007 at 11:19:00AM -0500, David Ronis wrote:
> The current main Makefile incorrectly identified my ld as one that
> supports --build-id (it didn't). The problem is fixed by upgrading to
> the latest binutils, version 2.18, which does, but somehow I suspect
> that this wasn't what was intended. For what it's worth, I was running
> with slackware's binutils-2.17.50.0.17.
That's not something that the janitors are responsible for. Redirecting
to linux-kernel.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
parent reply other threads:[~2007-11-19 16:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1195489140.21337.10.camel@ronispc.chem.mcgill.ca>]
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=20071119163437.GD12494@parisc-linux.org \
--to=matthew@wil.cx \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ronis@ronispc.chem.mcgill.ca \
/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
all inboxes | Powered by JetHome®