MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Roland McGrath <roland@redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Sam Ravnborg <sam@ravnborg.org>, Andrew Morton <akpm@linux-foundation.org>,
       linux-kernel@vger.kernel.org, Dan Aloni <da-x@monatomic.org>,
       Bernhard Walle <bwalle@suse.de>
Subject: Re: [PATCH] Add ELF note with Linux version
In-Reply-To: Jeremy Fitzhardinge's message of  Friday, 14 September 2007 14:31:27 -0700 <46EAFDAF.8000809@goop.org>
References: <20070904150018.GA4357@suse.de>
	<46DFD825.2020109@goop.org>
	<20070913144228.2efcd5d9.akpm@linux-foundation.org>
	<20070913221340.GA29181@uranus.ravnborg.org>
	<46E9BD3D.4050102@goop.org>
	<20070914060805.GA32169@uranus.ravnborg.org>
	<46EAE534.5030900@goop.org>
	<20070914210738.GA5031@uranus.ravnborg.org>
	<46EAFDAF.8000809@goop.org>
Message-Id: <20070915013052.578554D0424@magilla.localdomain>
Date: Fri, 14 Sep 2007 18:30:52 -0700 (PDT)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 858
Lines: 19

> Yes, binutils can be pretty fragile with notes about.  In this case it
> seems to be a specific problem with build-id; I'm not really sure what
> build-id actually does.

The thing about the build ID section that brings up issues with linking is
that it is a SHF_ALLOC, SHT_NOTE section.  As you mentioned, this is a
general, straightforward, and well-defined thing in ELF.  But in practice,
there were not previously SHF_ALLOC note sections used with custom linker
scripts like the kernel's.  (They are used every day in normal executables
and DSOs, but those don't use custom linker scripts.)


Thanks,
Roland
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/