From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14996] Too many directories in BR2_EXTERNAL causes hang during make
Date: Fri, 16 Sep 2022 17:56:11 +0000 [thread overview]
Message-ID: <bug-14996-163-LPmbkaGNwk@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14996-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14996
--- Comment #4 from Yann E. MORIN <yann.morin.1998@free.fr> ---
David, All,
To be noted: on my machine, in the directory I was using, I was limited
to using just 2446 br2-external trees, otherwise, make would whine with:
- with 2447:
make: execvp: /bin/sh: Argument list too long
- with 2248 and above:
-bash: /usr/bin/make: Argument list too long
Yes, note how 2446 succeeds, 2447 has a special error, and 2448 and above
have another error... Meh...
But still, 2446 br2-external trees is clearly way more than was ever
expected when the feature was added... back in 2016!
Regards,
Yann E. MORIN.
--
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:[~2022-09-16 17:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 13:58 [Buildroot] [Bug 14996] New: Too many directories in BR2_EXTERNAL causes hang during make bugzilla
2022-09-16 16:16 ` [Buildroot] [Bug 14996] " bugzilla
2022-09-16 16:53 ` bugzilla
2022-09-16 17:39 ` bugzilla
2022-09-16 17:56 ` bugzilla [this message]
2022-09-16 18:40 ` bugzilla
2022-09-16 18:45 ` bugzilla
2022-09-16 19:19 ` bugzilla
2022-09-17 6:54 ` bugzilla
2022-09-17 7:36 ` bugzilla
2022-09-19 17:27 ` bugzilla
2022-09-19 21:06 ` bugzilla
2022-09-20 19:58 ` bugzilla
2022-09-20 20:00 ` bugzilla
2023-01-07 20:11 ` 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-14996-163-LPmbkaGNwk@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.