From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15306] glibc build fails in Docker container
Date: Sun, 12 Mar 2023 17:36:14 +0000 [thread overview]
Message-ID: <bug-15306-163-kxFjFSNpaA@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15306-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15306
--- Comment #5 from Russ <russelljbrennan@gmail.com> ---
Yep sorry I didn't close the loop on this -- I was able to repro with upstream,
*but* I found that I could only repro when using a bind mount. I'm not sure
what the root cause is, but I assume it's an issue with the Docker bind
mounting mechanism.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-03-12 17:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 22:41 [Buildroot] [Bug 15306] New: glibc build fails bugzilla
2023-01-31 22:42 ` [Buildroot] [Bug 15306] glibc build fails in Docker container bugzilla
2023-02-12 18:15 ` bugzilla
2023-02-12 19:57 ` bugzilla
2023-02-13 0:43 ` bugzilla
2023-02-13 11:44 ` bugzilla
2023-03-12 15:17 ` bugzilla
2023-03-12 17:36 ` bugzilla [this message]
2023-03-12 19:38 ` bugzilla
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-15306-163-kxFjFSNpaA@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.