From: Jan Engelhardt <jengelh@linux01.gwdg.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] Compile kernel with -fwhole-program --combine
Date: Fri, 25 Aug 2006 11:51:28 +0200 (MEST) [thread overview]
Message-ID: <Pine.LNX.4.61.0608251149560.5613@yvahk01.tjqt.qr> (raw)
In-Reply-To: <1156499122.2984.36.camel@pmac.infradead.org>
>> That's what I meant. Assume I explicitly built read.o foo.o and bar.o.
>> If I then run the regular make, it will rerun gcc for read.c foo.c and
>> bar.c rather than using the already-created .o files for linking.
>
>You built something manually that wasn't needed, and then it wasn't
>used. Is there a problem here?
Although I cannot give you any logical reasons, there are possibly reasons
why building some things manually might help. Oh well, I think in that case
I just pass a make option CONFIG_NOCOMBINE, as you said.
Jan Engelhardt
--
next prev parent reply other threads:[~2006-08-25 9:51 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1156429585.3012.58.camel@pmac.infradead.org>
2006-08-24 15:24 ` [PATCH 0/4] Compile kernel with -fwhole-program --combine David Woodhouse
2006-08-24 16:48 ` Jan Engelhardt
2006-08-24 17:05 ` David Woodhouse
2006-08-25 6:01 ` Jan Engelhardt
2006-08-25 7:26 ` Sam Ravnborg
2006-08-25 10:14 ` David Woodhouse
2006-08-25 8:55 ` David Woodhouse
2006-08-25 9:11 ` Jan Engelhardt
2006-08-25 9:45 ` David Woodhouse
2006-08-25 9:51 ` Jan Engelhardt [this message]
2006-08-25 10:01 ` David Woodhouse
2006-08-24 17:15 ` [OLPC-devel] " Arnd Bergmann
2006-08-24 17:25 ` David Woodhouse
2006-08-24 21:49 ` Adrian Bunk
2006-08-24 21:54 ` David Woodhouse
2006-08-25 20:11 ` Rob Landley
2006-08-25 20:35 ` David Woodhouse
2006-08-26 1:59 ` Segher Boessenkool
2006-08-28 10:52 ` Helge Hafting
2006-08-28 11:03 ` Jan Engelhardt
2006-08-28 11:21 ` David Woodhouse
2006-09-01 19:35 ` Ian Stirling
2006-09-01 21:15 ` David Woodhouse
2006-08-24 15:25 ` [PATCH 1/4] Inconsistent extern declarations David Woodhouse
2006-08-24 16:13 ` Alexey Dobriyan
2006-08-24 17:50 ` David Woodhouse
2006-08-24 21:17 ` Adrian Bunk
2006-08-24 15:26 ` [PATCH 2/4] Core support for --combine -fwhole-program David Woodhouse
2006-08-24 17:27 ` Josh Triplett
2006-08-24 17:33 ` David Woodhouse
2006-08-24 21:33 ` Adrian Bunk
2006-08-25 9:37 ` David Woodhouse
2006-08-25 10:30 ` Adrian Bunk
2006-08-25 10:40 ` David Woodhouse
2006-08-24 15:26 ` [PATCH 3/4] Add __global tag where needed David Woodhouse
2006-08-24 21:30 ` Adrian Bunk
2006-08-25 9:52 ` David Woodhouse
2006-08-25 10:26 ` Adrian Bunk
2006-08-25 10:34 ` David Woodhouse
2006-08-25 10:50 ` Adrian Bunk
2006-08-24 15:28 ` [PATCH 4/4] Some extra --combine hacks David Woodhouse
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=Pine.LNX.4.61.0608251149560.5613@yvahk01.tjqt.qr \
--to=jengelh@linux01.gwdg.de \
--cc=dwmw2@infradead.org \
--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 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.