From: Denys Vlasenko <vda.linux@googlemail.com>
To: Roland McGrath <roland@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
tony.luck@intel.com, Doug Chapman <dchapman@redhat.com>
Subject: Re: [PATCH] ia64 vDSO vs --build-id
Date: Fri, 19 Oct 2007 10:28:07 +0000 [thread overview]
Message-ID: <200710191128.08252.vda.linux@googlemail.com> (raw)
In-Reply-To: <20071018221108.638644D04E2@magilla.localdomain>
On Thursday 18 October 2007 23:11, Roland McGrath wrote:
> When gcc uses --build-id by default, the gate.lds.S linker script runs afoul
> of the new note section and produces a bad DSO image. This fixes it.
I wonder why we bother having --build-id.
--
vda
WARNING: multiple messages have this Message-ID (diff)
From: Denys Vlasenko <vda.linux@googlemail.com>
To: Roland McGrath <roland@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
tony.luck@intel.com, Doug Chapman <dchapman@redhat.com>
Subject: Re: [PATCH] ia64 vDSO vs --build-id
Date: Fri, 19 Oct 2007 11:28:07 +0100 [thread overview]
Message-ID: <200710191128.08252.vda.linux@googlemail.com> (raw)
In-Reply-To: <20071018221108.638644D04E2@magilla.localdomain>
On Thursday 18 October 2007 23:11, Roland McGrath wrote:
> When gcc uses --build-id by default, the gate.lds.S linker script runs afoul
> of the new note section and produces a bad DSO image. This fixes it.
I wonder why we bother having --build-id.
--
vda
next prev parent reply other threads:[~2007-10-19 10:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 22:11 [PATCH] ia64 vDSO vs --build-id Roland McGrath
2007-10-18 22:11 ` Roland McGrath
2007-10-19 10:28 ` Denys Vlasenko [this message]
2007-10-19 10:28 ` Denys Vlasenko
2007-10-25 16:08 ` Doug Chapman
2007-10-25 16:08 ` Doug Chapman
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=200710191128.08252.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=dchapman@redhat.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
--cc=tony.luck@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.