From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13641] glibc on raspberrypi
Date: Mon, 22 Mar 2021 16:28:14 +0000 [thread overview]
Message-ID: <bug-13641-163-CxM2vgd6u4@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13641-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=13641
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yann.morin.1998 at free.fr
Status|NEW |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #1 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Julien,
I can not reproduce the error:
make raspberrypi_defconfig
make menuconfig
-> toolchain
-> C library
-> glibc
make
You need to provide more information, like the full build log.
Note : be sure to start the build from scratch when you change the C library,
see the manual: https://buildroot.org/manual.html#full-rebuild
Regards,
Yann E. MORIN.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2021-03-22 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 12:43 [Buildroot] [Bug 13641] New: glibc on raspberrypi bugzilla at busybox.net
2021-03-22 16:28 ` bugzilla at busybox.net [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=bug-13641-163-CxM2vgd6u4@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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