Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] bash: fix linking for static builds with uClibc toolchains
Date: Wed, 22 Oct 2014 10:41:17 +0100	[thread overview]
Message-ID: <54477BBD.8010907@imgtec.com> (raw)
In-Reply-To: <54477A59.1050000@mind.be>

Dear Arnout Vandecappelle,

On 10/22/2014 10:35 AM, Arnout Vandecappelle wrote:
> On 22/10/14 11:17, Vicente Olivert Riera wrote:
>> Dear Arnout Vandecappelle,
>>
>> On 10/21/2014 09:50 PM, Arnout Vandecappelle wrote:
>>>    Also, does musl allow redefining getenv?
>>
>> Well, I did a test with a static build using the musl toolchain and it worked
>> fine. So, yes, it seems that musl is ok with the getenv redefinition.
>
>   Perhaps it's a good idea to mention this analysis explicitly in comments.
> Something like:
>
> # bash wants to redefine the getenv() function. To check whether this is
> # possible, AC_TRY_RUN is used which is not possible in cross-compilation.
> # On uClibc, redefining getenv is not possible; on glibc and musl it is.
>
>
>   Regards,
>   Arnout
>
> [snip]
>

Done: http://patchwork.ozlabs.org/patch/401979/

Best regards,
-- 
Vicente Olivert Riera
Graduate Software Engineer, MIPS Processor IP
Imagination Technologies Limited
t: +44 (0)113 2429814
www.imgtec.com

      reply	other threads:[~2014-10-22  9:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21 13:21 [Buildroot] [PATCH] bash: fix linking for static builds with uClibc toolchains Vicente Olivert Riera
2014-10-21 20:50 ` Arnout Vandecappelle
2014-10-22  9:17   ` Vicente Olivert Riera
2014-10-22  9:35     ` Arnout Vandecappelle
2014-10-22  9:41       ` Vicente Olivert Riera [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=54477BBD.8010907@imgtec.com \
    --to=vincent.riera@imgtec.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