From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Pedro Aguilar <paguilar@paguilar.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 1/1] package/guile: Guile 3.0.7 requires libiconv.
Date: Sun, 6 Feb 2022 10:30:40 +0100 [thread overview]
Message-ID: <20220206103040.1704ef40@windsurf> (raw)
In-Reply-To: <20220206084334.1900252-1-paguilar@paguilar.org>
On Sun, 6 Feb 2022 09:43:34 +0100
Pedro Aguilar <paguilar@paguilar.org> wrote:
> This fixes the error reported in the daily results.
>
> Signed-off-by: Pedro Aguilar <paguilar@paguilar.org>
libiconv is normally needed only on toolchains that don't have
BR2_ENABLE_LOCALE. But the build failure of guile happens with glibc
toolchains, so it doesn't make much sense.
Are you sure that your analysis of the problem is correct? Could you
provide some more details?
Thanks a lot!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-02-06 9:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-06 8:43 [Buildroot] [PATCH v1 1/1] package/guile: Guile 3.0.7 requires libiconv Pedro Aguilar
2022-02-06 8:48 ` Giulio Benetti
2022-02-06 8:54 ` Giulio Benetti
2022-02-06 9:30 ` Thomas Petazzoni via buildroot [this message]
2022-02-08 9:19 ` Pedro Aguilar
2022-02-08 11:47 ` Giulio Benetti
2022-02-08 12:02 ` Giulio Benetti
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=20220206103040.1704ef40@windsurf \
--to=buildroot@buildroot.org \
--cc=paguilar@paguilar.org \
--cc=thomas.petazzoni@bootlin.com \
/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