Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Brian Murphy <brm@murphy.dk>
To: linux-mips@linux-mips.org
Cc: ralf@linux-mips.org
Subject: [PATCH 2.5] kbuild error for mips (and possibly others)
Date: Tue, 15 Jul 2003 21:37:37 +0200	[thread overview]
Message-ID: <E19cVcH-0003Lr-00@brian.localnet> (raw)

Hi,
	there is a very annoying error in the 2.5 kbuild process
where the generation of the elfconfig.h file depends on the proper
configuration of the kernel being available (for mips at least) 
but configuring the kernel disallows the inclusion of the .config file
and thus the configuration and specifically CROSS_COMPILE is not set. 
This causes empty.o to fail to build because CC is now gcc and not 
mips(el)-linux-gcc and the -G option to gcc is invalid for my cross
compiler.

This patch fixes the problem. It also makes the *config targets 
not dependant on having the helper programs in scripts/ compiled
which they shouldn't be. They are not necessary.

/Brian

Index: scripts/Makefile
===================================================================
RCS file: /cvs/linux/scripts/Makefile,v
retrieving revision 1.20
diff -u -r1.20 Makefile
--- scripts/Makefile	5 Jun 2003 10:06:44 -0000	1.20
+++ scripts/Makefile	15 Jul 2003 19:28:29 -0000
@@ -7,6 +7,7 @@
 #                include/config/...
 # docproc: 	 Preprocess .tmpl file in order to generate .sgml docs
 # conmakehash:	 Create arrays for initializing the kernel console tables
+ifdef include_config
 
 host-progs	:= fixdep split-include conmakehash docproc kallsyms modpost \
 		   mk_elfconfig pnmtologo
@@ -33,3 +34,5 @@
 	$(call if_changed,elfconfig)
 
 targets += elfconfig.h
+
+endif

             reply	other threads:[~2003-07-15 19:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15 19:37 Brian Murphy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-15 19:42 [PATCH 2.5] kbuild error for mips (and possibly others) Brian Murphy

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=E19cVcH-0003Lr-00@brian.localnet \
    --to=brm@murphy.dk \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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