From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Revert of 406cd0fee12ad99ba6d6f7d55f743cc4c6697955
Date: Thu, 19 Nov 2009 16:40:28 +0100 [thread overview]
Message-ID: <20091119154028.GS919@mx.loc> (raw)
In-Reply-To: <20091118123012.GD2919@mx.loc>
On Wed, Nov 18, 2009 at 01:30:12PM +0100, Bernhard Reutner-Fischer wrote:
>On Wed, Nov 18, 2009 at 12:44:39PM +0100, Leon Woestenberg wrote:
>>Hello Bernhard,
>>
>>On Wed, Nov 18, 2009 at 12:41 PM, Bernhard Reutner-Fischer
>><rep.dot.nop@gmail.com> wrote:
>>> On Wed, Nov 18, 2009 at 11:34:28AM +0100, Koen Kooi wrote:
>>>>Hi,
>>>>
>>>>Since 406cd0fee12ad99ba6d6f7d55f743cc4c6697955 broke all
>>>>glibc-internal-iconv builds and I'm too lazy/stupid to fix it
>>>>properly for uclibc I reverted this commit.
>>>
>>> for unpatched uClibc you could just
>>> TARGET_CPPFLAGS += -D_Exit=_exit
>>>
>>Thanks, and what's the patched uClibc alternative (and where's the
>>patch)? It defines _Exit()?
>
>I suggest to just #define it to _exit, yes.
>(glibc has it as weak alias but i'd prefer to get away with a define),
>like:
>
>_Exit(): define to _exit()
OTOH someone may want to override it locally, so to play safe let's
follow suite:
http://git.uclibc.org/uClibc/commit/?h=0_9_30&id=e4adfdc4128c5909adeefecdaf870e30172922a9
next prev parent reply other threads:[~2009-11-19 15:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 10:34 Revert of 406cd0fee12ad99ba6d6f7d55f743cc4c6697955 Koen Kooi
2009-11-18 11:41 ` Bernhard Reutner-Fischer
2009-11-18 11:44 ` Leon Woestenberg
2009-11-18 12:30 ` Bernhard Reutner-Fischer
2009-11-18 22:10 ` Henning Heinold
2009-11-19 15:40 ` Bernhard Reutner-Fischer [this message]
2010-01-23 10:02 ` Holger Hans Peter Freyther
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=20091119154028.GS919@mx.loc \
--to=rep.dot.nop@gmail.com \
--cc=openembedded-devel@lists.openembedded.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 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.