From: Christopher Faylor <christopher.faylor@timesys.com>
To: linux-kernel@vger.kernel.org, "Robb, Sam" <sam.robb@timesys.com>,
Sam Ravnborg <sam@ravnborg.org>,
zippel@linux-m68k.org, akpm@osdl.org,
Kyle McMartin <kyle@parisc-linux.org>
Subject: Re: [PATCH] kconfig: detect if -lintl is needed when linking conf,mconf
Date: Tue, 14 Feb 2006 11:13:19 -0500 [thread overview]
Message-ID: <20060214161319.GA17161@trixie.casa.cgf.cx> (raw)
In-Reply-To: <3D848382FB72E249812901444C6BDB1D03E051E7@exchange.timesys.com>
On Thu, Feb 09, 2006 at 12:24:12PM -0500, Robb, Sam wrote:
>Kyle McMartin <kyle@parisc-linux.org> wrote:
>>On Mon, Jan 30, 2006 at 01:26:47PM -0500, Robb, Sam wrote:
>>> This patch attempts to correct the problem by detecting whether or not
>>> NLS support requires linking with libintl.
>>
>>Sigh. Can everyone please stop assuming gcc can output to /dev/null? On
>>several platforms, ld tries to lseek in the output file, and fails if it
>>can't.
>
>Ouch. Out of curiosity - what is the reason for this behavior in ld?
Ouch, indeed.
I'd be interested in details on which platforms perform so lamely. When
I grep for lseek and its variants in the bfd and ld source code, the only
occurrences that I see are all working on object files - as I would expect.
-Chris Faylor
(one of the) binutils maintainers
next prev parent reply other threads:[~2006-02-14 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 17:24 Robb, Sam
2006-02-14 16:13 ` Christopher Faylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-30 18:26 Robb, Sam
2006-02-09 5:42 ` Kyle McMartin
2006-02-09 5:57 ` Andrew Morton
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=20060214161319.GA17161@trixie.casa.cgf.cx \
--to=christopher.faylor@timesys.com \
--cc=akpm@osdl.org \
--cc=kyle@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam.robb@timesys.com \
--cc=sam@ravnborg.org \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®