From: "Peter T. Breuer" <ptb@inv.it.uc3m.es>
To: "Kyle Moffett" <mrmacman_g4@mac.com>
Cc: "linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: .o.cmd files wanted, static analysis
Date: Fri, 16 Sep 2005 08:46:15 +0200 (MET DST) [thread overview]
Message-ID: <200509160646.j8G6kFg00923@inv.it.uc3m.es> (raw)
In-Reply-To: <0CF04ACB-C931-4016-B50C-233FEA7AC78C@mac.com> from "Kyle Moffett" at "Sep 15, 2005 08:08:40 pm"
"Also sprach Kyle Moffett:"
> On Sep 15, 2005, at 19:50:29, Peter T. Breuer wrote:
> > Does somebody out there have a pretty complete kernel compilation,
> > mainly all modules (though I don't care!), and could let me have
> > their .*.o.cmd files? In fact, just the FIRST LINE of them.
>
> doesn't "make allmodconfig" work for you? That should generate a
Thanks. I didn't know about allconfig. That sounds good.. But no,
it wouldn't exactly work for me just like that - I don't have space
to do the actual kernel compilation on any machine (nor time to do it,
since the fastest machine is my laptop at 1.13GHz, and that suffers from
overheating problems - the next fastest machine is a dual 550MHz, and I
will start that churning but space is tight everywhere and I am pretty
sure that there is no chance to get it to go to a finish as is).
> config with everything possible included as modules, and then you can
> compile that to generate .cmd files.
Has anyone already done it? I was hoping there was somebody running a
big compile every day in order to check consistency. Then I could
simply "borrow" their files!
Failing that, I'll try setting CC to something like FOO, and seeing if
I can generate the .o.cmd files without the compilation actually being
done. Hmmm ...
Peter
next prev parent reply other threads:[~2005-09-16 6:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 23:50 Peter T. Breuer
2005-09-16 0:08 ` Kyle Moffett
2005-09-16 6:46 ` Peter T. Breuer [this message]
[not found] <200509161502.17861.lion.vollnhals@web.de>
2005-09-16 18:39 ` Peter T. Breuer
[not found] <432B332F.8070808@tuxrocks.com>
2005-09-17 4:25 ` Peter T. Breuer
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=200509160646.j8G6kFg00923@inv.it.uc3m.es \
--to=ptb@inv.it.uc3m.es \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
/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®