Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 23:42:07 +0100	[thread overview]
Message-ID: <87lh749hog.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <dtt4ocxf5l.ln2@ID-313208.user.individual.net> (Bernd Kuhls's message of "Mon, 01 Feb 2016 22:05:17 +0100")

>>>>> "Bernd" == Bernd Kuhls <bernd.kuhls@t-online.de> writes:

Hi,

 > Am Mon, 01 Feb 2016 17:11:57 +0100 schrieb Peter Korsgaard:
 >> 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.

 > Hi Peter,

 > there is still a problem left, binutils contains its own intl library 
 > with a GNU libintl.h, similar to the one provided by gettext. It changes 
 > function names in libbfd.so, this leads to a link error at least with 
 > dropwatch:

Thanks. The problem is really that the binutils build system runs
configure in the sub directories from make, and we only pass
TARGET_CONFIGURE_ARGS in the environment of the configure step and not
the make step.

I'll send a fix shortly.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2016-02-01 22:42 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
2016-02-01 17:45   ` Bernd Kuhls
2016-02-01 21:05   ` Bernd Kuhls
2016-02-01 22:42     ` Peter Korsgaard [this message]

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=87lh749hog.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox