All of lore.kernel.org
 help / color / mirror / Atom feed
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:39:34 +0000	[thread overview]
Message-ID: <bug-14996-163-eipqn2hpSQ@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 #3 from Yann E. MORIN <yann.morin.1998@free.fr> ---
David, All,

Here's how I prepared the test br2-external trees:

$ for i in $(seq 1 1000); do
    mkdir -p br2-external-${i}/configs
    touch br2-external-${i}/{Config.in,external.mk}
    echo "name: BR_TEST_${i}" >br2-external-${i}/external.desc
    touch br2-external-${i}/configs/foo{,_${i}}_defconfig
done

So, I get minimal br2-external trees, each with two defconfigs:
one that is present in all br2external trees, and one that is
specific to each tree.

And here is exactly how I tested that:

$ make --version
GNU Make 4.2.1

$ for ext in 1 10 100 1000; do time make BR2_EXTERNAL="$(for i in $(seq 1
${ext}); do echo $(pwd)/br2-external-${i}; done)" list-defconfigs >/dev/null;
done 2>&1 |grep real
real    0m0.179s
real    0m0.245s
real    0m1.299s
real    0m18.277s

What version of make are you using? How many br2-external trees do you have?

However, please do note that indeed, it was never envisioned that more than a
few
br2-external trees be used simultaneously. But that it feels like it got stuck
is
still not a nice behaviour...

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

  parent reply	other threads:[~2022-09-16 17:39 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 [this message]
2022-09-16 17:56 ` bugzilla
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-eipqn2hpSQ@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.