From: "Diego 'Flameeyes' Pettenò" <flameeyes@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: [crda PATCH 0/5] Makefile improvement and fixes
Date: Mon, 01 Dec 2008 11:30:44 +0100 [thread overview]
Message-ID: <20081201103016.18024.80454.stgit@localhost> (raw)
I've been asked by a colleague Gentoo developer (Tony Vroon) to look
at a build failure with parallel make[1] in crda, and I decided to
take a closer look to the Makefile.
With these patches applied, --as-needed build works, as well as
parallel make, the dependencies are properly handle so that changing a
file will only rebuild the correct one, and it's as parallel as
feasible with no recursive make.
HTH,
Diego
[1] http://bugs.gentoo.org/show_bug.cgi?id=3D249181
---
Diego E. 'Flameeyes' Petten=C3=B2 (5):
Ignore built files.
Don't use recursive make for verify target.
Make it possible to switch gcrypt/openssl via knob.
Fix dependencies for parallel make and others.
Fix building with --as-needed LD flag.
.gitignore | 2 ++
Makefile | 33 +++++++++++++++++++++------------
2 files changed, 23 insertions(+), 12 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2008-12-01 10:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 10:30 Diego 'Flameeyes' Pettenò [this message]
2008-12-01 10:30 ` [crda PATCH 1/5] Fix building with --as-needed LD flag Diego 'Flameeyes' Pettenò
2008-12-01 10:30 ` [crda PATCH 2/5] Fix dependencies for parallel make and others Diego 'Flameeyes' Pettenò
2008-12-01 10:31 ` [crda PATCH 3/5] Make it possible to switch gcrypt/openssl via knob Diego 'Flameeyes' Pettenò
2008-12-01 10:31 ` [crda PATCH 4/5] Don't use recursive make for verify target Diego 'Flameeyes' Pettenò
2008-12-01 10:31 ` [crda PATCH 5/5] Ignore built files Diego 'Flameeyes' Pettenò
2008-12-01 22:35 ` [crda PATCH 0/5] Makefile improvement and fixes Luis R. Rodriguez
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=20081201103016.18024.80454.stgit@localhost \
--to=flameeyes@gmail.com \
--cc=linux-wireless@vger.kernel.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.