From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] RFC: musl: Fix gettext support
Date: Mon, 01 Feb 2016 17:11:57 +0100 [thread overview]
Message-ID: <87mvrkcsvm.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1454194293-17572-1-git-send-email-bernd.kuhls@t-online.de> (Bernd Kuhls's message of "Sat, 30 Jan 2016 23:51:33 +0100")
>>>>> "Bernd" == Bernd Kuhls <bernd.kuhls@t-online.de> writes:
> The issue is discussed here:
> http://thread.gmane.org/gmane.comp.lib.uclibc.buildroot/127196
> I consider this patch an ugly hack but I could compile ~900 packages
> without a gettext-related error, so I put this patch up for discussion.
> Fixes
> http://autobuild.buildroot.net/results/911/9115ddb411ec15eb8bfa1d4f03a804f48e77ff76/
> and many similar errors
> To test use the defconfig mentioned above, then
> make clean
> make dos2unix (build will succeed either with or without this patch)
> make clean
> make gettext
> make dos2unix (build fails because gettext replaced musl's libintl.h)
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
Hi,
I now spent some quality time (!) with gettext.m4 and figured out what
we really going on here with musl and libintl.h, and I've pushed a
simpler / more complete patch fixing the issue.
I have therefore marked this patch as superseeded.
I've also reverted the madplay fix now that it is handled globally in
TARGET_CONFIGURE_ARGS.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2016-02-01 16:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 22:51 [Buildroot] [PATCH 1/1] RFC: musl: Fix gettext support Bernd Kuhls
2016-01-31 7:33 ` Thomas Petazzoni
2016-01-31 7:49 ` Bernd Kuhls
2016-01-31 20:17 ` Bernd Kuhls
2016-02-01 16:11 ` Peter Korsgaard [this message]
2016-02-01 17:45 ` Bernd Kuhls
2016-02-01 21:05 ` Bernd Kuhls
2016-02-01 22:42 ` Peter Korsgaard
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=87mvrkcsvm.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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.