From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: Sam Ravnborg <sam@ravnborg.org>,
gibbs@adaptec.com, Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [aic7xxx] Spurious recompile with defconfig
Date: Mon, 30 Dec 2002 18:12:49 -0700 [thread overview]
Message-ID: <145050000.1041297169@aslan.btc.adaptec.com> (raw)
In-Reply-To: <698528112.1041102051@aslan.scsiguy.com>
>> When compiling aic7xxx in 2.5.53 with defconfig the kernel always
>> recompiles because dependency for reg_print.c is not
>> per default in the aic7xxx Makefile.
>> Simple correction is to make PRETTY_PRINT dependend on BUILD_FIRMWARE.
>
> There must be some other problem in the Makefile. You can turn on
> reg pretty printing without having to build the firmware as there is
> a "shipped" version of that file. I'll see if I can figure out why the
> re-build is occurring.
The real problem here is that make choses the wrong path for getting
to reg_print.o and, since "intermediate files" were used, those files
are removed once the target is made (See "Chained Rules" in the gmake
info file). From the "make -d" output, for some reason make decides
that:
.o <- .s <- .c <- .c_shipped
is better than
.o <- .c <- .c_shipped
I can't see, from a cursory investigation of the 2.5.X Makefiles
why this happens, but it is certainly anoying. The info pages
indicate that the removal can be avoided by listing these files
as prerequisites to .SECONDARY, but I could only get that to work
by leaving the prerequisites empty (all files are marked secondary).
Of course this is just a workaround for incorrect behavior.
Perhaps someone with more knowledge of the 2.5.X build system could
look into this? That way we can restore the original (and correct)
behvior of the driver's Kconfig files.
--
Justin
next prev parent reply other threads:[~2002-12-31 1:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-28 8:56 Sam Ravnborg
2002-12-28 19:00 ` Justin T. Gibbs
2002-12-31 1:12 ` Justin T. Gibbs [this message]
2002-12-31 9:36 ` Sam Ravnborg
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=145050000.1041297169@aslan.btc.adaptec.com \
--to=gibbs@scsiguy.com \
--cc=gibbs@adaptec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=torvalds@transmeta.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
Powered by JetHome