mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Cc: Sam Ravnborg <sam@ravnborg.org>
Subject: No forces rebuild while changing GCC?
Date: Thu, 20 May 2004 20:16:17 +0200	[thread overview]
Message-ID: <20040520181617.GE1912@lug-owl.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]

Hi!

I'm currently playing with patches for gcc HEAD to build a vax-linux
cross-compiler. For testing it, I first want to build parts of the
kernel with my HEAD toolchain, Ctrl-C, and continue/finish building with
my old compiler (2.95.2).

I do changing gcc by putting one or the other gcc into $PATH. However,
whenever I change GCC, kbuild decides to rebuild everything.

I tried to not overwrite compile.h (my commenting out the mv command in
scripts/mkcompile_h), but that didn't help either. I even tried
recompiling my HEAD gcc with exactly the same version string that my old
gcc had, but that didn't work either:(

How can I force to keep my old .o files?

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
   ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2004-05-20 18:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-20 18:16 Jan-Benedict Glaw [this message]
2004-05-20 18:56 ` Sam Ravnborg
2004-05-20 20:15   ` Jan-Benedict Glaw
2004-05-21 12:18     ` 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=20040520181617.GE1912@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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®