From: "Adam Kropelin" <akropel1@rochester.rr.com>
To: <linux-kernel@vger.kernel.org>
Cc: <sam@mars.ravnborg.org>
Subject: Parallel build not working since -test6?
Date: Wed, 26 Nov 2003 18:27:37 -0500 [thread overview]
Message-ID: <02d801c3b474$e09e42a0$02c8a8c0@steinman> (raw)
Lately I've noticed my kernel compilations taking longer than usual. Tonight
I finally realized the cause... Parallel building (i.e. make -jN) is no
longer working for me. I traced it back and the last kernel it worked in
was -test5. It ceased working in -test6.
Not to point fingers, but I do notice that the kbuild separate output
directory patch went into -test6...
Build environment details:
arch: i386
make: GNU Make version 3.79.1
gcc: gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)
output directory: default (i.e. source dir)
I can narrow it down to a -bk if that's useful or if someone has a patch to
back out the separate output dir kbuild changes I can give that a whirl...
--Adam
next reply other threads:[~2003-11-26 23:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 23:27 Adam Kropelin [this message]
2003-11-28 20:26 ` Parallel build not working since -test6? Sam Ravnborg
2003-11-29 1:47 ` Adam Kropelin
2003-11-29 2:47 ` Derek Foreman
2003-11-29 3:40 ` Adam Kropelin
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='02d801c3b474$e09e42a0$02c8a8c0@steinman' \
--to=akropel1@rochester.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@mars.ravnborg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).