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] toolchain/wrapper: fix building without glibc
Date: Wed, 25 Jan 2017 22:31:30 +0100	[thread overview]
Message-ID: <87bmuug72l.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20161231225649.x6lp2l6oavetrbth@sapphire.tkos.co.il> (Baruch Siach's message of "Sun, 1 Jan 2017 00:56:50 +0200")

>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:

 > Hi Marcin,
 > On Sat, Dec 31, 2016 at 04:30:17PM +0100, Marcin Chojnacki wrote:
 >> toolchain-wrapper.c now uses program_invocation_short_name, which is
 >> a glibc specific extension. This causes build to fail when using a
 >> system with libc different than glibc (musl, BSD libc, etc.)
 >> 
 >> This change makes toolchain-wrapper.c portable, by setting it's value
 >> to getprogname() when __GLIBC__ is not defined, and thus makes running
 >> buildroot possible on glibc-less systems.

 > getprogname() is BSD specific[1]. None of the major Linux libcs (glibc, 
 > uclibc-ng, musl) provide it.

 > [1] https://www.freebsd.org/cgi/man.cgi?query=getprogname&sektion=3

Out of interest, what system are you trying to use Buildroot on? A BSD
variant? I would imagine a number of other things breaking on !Linux
systems.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2017-01-25 21:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-31 15:30 [Buildroot] [PATCH 1/1] toolchain/wrapper: fix building without glibc Marcin Chojnacki
2016-12-31 22:56 ` Baruch Siach
2017-01-25 21:31   ` 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=87bmuug72l.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