From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] zlib: Fix build
Date: Sat, 18 Sep 2010 22:13:11 +0200 [thread overview]
Message-ID: <8739t66ca0.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1284812207-31798-3-git-send-email-llandwerlin@gmail.com> (llandwerlin@gmail.com's message of "Sat, 18 Sep 2010 14:16:46 +0200")
>>>>> "llandwerlin" == llandwerlin <llandwerlin@gmail.com> writes:
llandwerlin> From: Lionel Landwerlin <llandwerlin@gmail.com>
llandwerlin> Using "make -j $(N)" with N > 1 break zlib build.
In what way exactly? Zlib is a pretty common package and I've never
seen if breaking because of parallel builds.
In fact, testing on a big (24 core) machine I don't see it either:
tar jxf ~/zlib-1.2.5.tar.bz2
mv zlib-1.2.5{,-parallel}
tar jxf ~/zlib-1.2.5.tar.bz2
cd zlib-1.2.5-parallel ; ./configure --prefix=/usr --shared; \
make -j 100 all libz.a; cd ..
cd zlib-1.2.5 ; ./configure --prefix=/usr --shared; \
make all libz.a; cd ..
Gives the same result:
ls -la zlib-1.2.5*/libz.{a,so.1.2.5}
-rw-r--r-- 1 peko peko 133746 2010-09-18 22:00 zlib-1.2.5/libz.a
-rwxr-xr-x 1 peko peko 109995 2010-09-18 22:00 zlib-1.2.5/libz.so.1.2.5
-rw-r--r-- 1 peko peko 133746 2010-09-18 22:00 zlib-1.2.5-parallel/libz.a
-rwxr-xr-x 1 peko peko 109995 2010-09-18 22:00 zlib-1.2.5-parallel/libz.so.1.2.5
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2010-09-18 20:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-18 12:16 [Buildroot] [pull request] small fixes llandwerlin at gmail.com
2010-09-18 12:16 ` [Buildroot] [PATCH 1/3] package: drop special case for target-install with BR2_ENABLE_DEBUG llandwerlin at gmail.com
2010-09-18 12:54 ` Thomas Petazzoni
2010-09-18 12:16 ` [Buildroot] [PATCH 2/3] zlib: Fix build llandwerlin at gmail.com
2010-09-18 20:13 ` Peter Korsgaard [this message]
2010-09-18 20:48 ` Martin Banky
2010-09-18 20:59 ` Peter Korsgaard
2010-09-18 22:11 ` Lionel Landwerlin
2010-09-20 7:22 ` Peter Korsgaard
2010-09-18 12:16 ` [Buildroot] [PATCH 3/3] autotools: fix MESSAGE calls llandwerlin at gmail.com
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=8739t66ca0.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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