From: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
To: Blaisorblade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] Re: Problems in make
Date: Wed, 24 Nov 2004 13:06:54 +0100 [thread overview]
Message-ID: <41A4795E.5090004@fujitsu-siemens.com> (raw)
In-Reply-To: <200411231904.51431.blaisorblade_spam@yahoo.it>
Blaisorblade wrote:
> On Tuesday 23 November 2004 16:19, Bodo Stroesser wrote:
>
>>Blaisorblade wrote:
>>
>>>On Monday 22 November 2004 19:59, Bodo Stroesser wrote:
>>>
>>>>If arch/um/kernel/tt/include/mode-tt.h is changed, make doesn't compile
>>>>tracer.c, the resulting kernel is inconsistent and crashes!
>>>
>>>This is true for any dependency of files listed in USER_OBJS, which is
>>>broken. This problem is known and is pending fixing (and fixing requires
>>>designing a clean and Kbuild-supported replacement of USER_OBJS). I fixed
>>>it some time ago, around 2.6.1, but the fix was not integrated because it
>>>was too invasive.
>>>
>>>So: use always make clean ARCH=um before rebuilding (this even holds for
>>>dependencies on CONFIG_*).
>>>
>>>If that slows you down too much, then install ccache (I'm not explaining
>>>it here because there is nothing special on ccache with kernel
>>>compilation and because there is plenty of tutorials onto the net).
>
>
>>>Bye
>
>
>>As a quick solution to guarantee a correct result of the build, would it be
>>possible to remove all USER_OBJS, when starting to build?
>
> This is not a so bad idea, however if I interrupt a build with Ctrl-C and
> restart it without changes, it shouldn't clean all USER_OBJS.
Is this really necessary? What's the time for a complete build and what's the
time for building the USER_OBJS? Would not removing the USER_OBJS enable make
to build consistent kernels in all cases without being as inefficient as
make clean ARCH=um? Getting consistent kernels from make IMHO has the highest
priority.
Even when using ccache, after make clean the build takes some time.
>
> It is not also a one-liner (can be dumbly implemented easily, but some
> changes).
>
> What about adding a target like "rebuildclean" (a better name is welcome)?
>
> However, until I don't have the time to work on this, use the solution I
> suggested above.
>
>
>>Or, if this isn't
>>enough, even remove all objects in the arch/um subtree?
>
>
> We don't need to be this aggressive.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2004-11-24 12:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 18:59 [uml-devel] Problems in make Bodo Stroesser
2004-11-22 22:01 ` [uml-devel] " Blaisorblade
2004-11-23 15:19 ` Bodo Stroesser
2004-11-23 18:04 ` Blaisorblade
2004-11-24 12:06 ` Bodo Stroesser [this message]
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=41A4795E.5090004@fujitsu-siemens.com \
--to=bstroesser@fujitsu-siemens.com \
--cc=blaisorblade_spam@yahoo.it \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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