Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/glibc: drop dependency of utilities on bash
Date: Mon, 9 Dec 2019 08:53:01 +0100	[thread overview]
Message-ID: <20191209085301.19cd9f52@windsurf.home> (raw)
In-Reply-To: <CAJ4jsaca+BnSWrQ5Zcd9h_6o5705oe0z9fAjBr7bN6g65+RE=w@mail.gmail.com>

Hello Carlos,

On Sun, 8 Dec 2019 22:38:52 -0300
Carlos Santos <unixmania@gmail.com> wrote:

> I'm working on a patch series to glibc but it requires ATORECONF,
> which fails because GLIBC_SUBDIR is set to "build" and there
> configure.ac is not there. I circumvented the problem by using
> 
> define GLIBC_AUTORECONF
>         cd $(@D) && $(AUTORECONF) || true
> endef
> 
> GLIBC_PRE_CONFIGURE_HOOKS = GLIBC_AUTORECONF
> 
> The "|| true" there is a kludge to ignore this error:
> 
> Use of uninitialized value $args[0] in split at
> /work/qemu_x86_64_glibc_eudev/host/bin/autoreconf line 493, <GEN2>

Hum, OK. Perhaps another way is to simply have your patch make its way
upstream, and wait until the next glibc release to really use it in
Buildroot. In the mean time, we can keep the post patch hook that you
have implemented and that was merged in Buildroot.

What is important is that at some point in the future, there will be an
upstream solution. We don't necessarily need to use it immediately in
Buildroot.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-12-09  7:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-03  0:14 [Buildroot] [PATCH] package/glibc: drop dependency of utilities on bash unixmania at gmail.com
2019-12-05 22:17 ` Thomas Petazzoni
2019-12-09  1:38   ` Carlos Santos
2019-12-09  7:53     ` Thomas Petazzoni [this message]
2019-12-09 11:41       ` Carlos Santos
2019-12-09 12:41         ` Thomas Petazzoni

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=20191209085301.19cd9f52@windsurf.home \
    --to=thomas.petazzoni@bootlin.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