From: Sam Ravnborg <sam@ravnborg.org>
To: Francis Moreau <francis.moro@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Kbuild: how to cleanly retrieve information compilation about the last build
Date: Sat, 16 Apr 2011 16:50:50 +0200 [thread overview]
Message-ID: <20110416145050.GA1124@merkur.ravnborg.org> (raw)
In-Reply-To: <BANLkTi=wdDsrV+ikoxLhnTpLhQTuVKW0mA@mail.gmail.com>
>
> BTW are the allowed flags documented somewhere ?
Some/most supported flags are documented in Dumentation/kbuild/kbuild.txt
> > If you on a regular basis need to pass flags on the command-line
> > then you likely are doing something odd as this is not the typical use.
> > So please reconsider what you are doing.
>
> Ok, if I'm doing something wrong, I'd like to be corrected.
>
> What's wrong with passing those flags for example:
>
> $ make ARCH=arm CROSS_COMPILE=arm-linux
>
> or
>
> $ make CC=distcc
>
> ?
Both examples are perfectly OK. From your previous posting it
looked like you passed flags that influenced how the kernel
was built (CCFLAGS) and it did not look like you had cross-compile
nor distcc in mind - hence my comment.
Sam
next prev parent reply other threads:[~2011-04-16 14:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 7:13 Francis Moreau
2011-04-16 8:05 ` Francis Moreau
2011-04-16 13:59 ` Sam Ravnborg
2011-04-16 14:04 ` Francis Moreau
2011-04-16 14:33 ` Valdis.Kletnieks
2011-04-16 14:45 ` Francis Moreau
2011-04-16 15:08 ` Valdis.Kletnieks
2011-04-16 15:47 ` Francis Moreau
2011-04-16 15:57 ` Francis Moreau
2011-04-16 19:46 ` Valdis.Kletnieks
2011-04-16 19:54 ` Francis Moreau
2011-04-16 14:50 ` Sam Ravnborg [this message]
2011-04-16 8:26 ` Américo Wang
2011-04-16 14:00 ` Francis Moreau
2011-04-17 4:57 ` Américo Wang
2011-04-17 10:27 ` Francis Moreau
2011-04-19 19:24 ` Jonathan Neuschäfer
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=20110416145050.GA1124@merkur.ravnborg.org \
--to=sam@ravnborg.org \
--cc=francis.moro@gmail.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®