From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: cleaning up "make headers_install" for various architectures
Date: Wed, 10 Oct 2007 12:44:58 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0710101234340.32502@localhost.localdomain> (raw)
there are a number of architectures that generate warnings (and, in
one case, an error) if you try to do:
$ make ARCH=whatever headers_install
when you don't have an appropriate cross-compiler installed. this
doesn't seem to make sense as you shouldn't have to do any actual
cross-compiling if you're just trying to install headers, should you?
the examples (i already mentioned the ia64 example on that list):
$ make ARCH=m68k headers_install
make: m68k-linux-gnu-gcc: Command not found
CHK include/linux/version.h
HOSTCC scripts/unifdef
MKDIR include
... etc etc ...
$ make ARCH=h8300 headers_install
make: h8300-elf-gcc: Command not found
make: h8300-elf-gcc: Command not found
CHK include/linux/version.h
make[1]: `scripts/unifdef' is up to date.
UNIFDEF include/asm/page.h
... etc etc ...
$ make ARCH=sparc64 headers_install
/bin/sh: sparc64-linux-gcc: command not found
make: sparc64-linux-gcc: Command not found
CHK include/linux/version.h
make[1]: `scripts/unifdef' is up to date.
MKDIR include/asm-sparc64
... etc etc ...
$ make ARCH=ia64 headers_install
/home/rpjday/k/git/arch/ia64/scripts/check-segrel.S: Assembler messages:
/home/rpjday/k/git/arch/ia64/scripts/check-segrel.S:1: Error: unknown pseudo-op: `.rodata'
/home/rpjday/k/git/arch/ia64/scripts/check-segrel.S:2: Error: no such instruction: `data4 @segrel(start)'
objdump: '/tmp/out3703': No such file/home/rpjday/k/git/arch/ia64/scripts/toolchain-flags: line 19: [: !=:
unary operator expected
the final example, parisc, just plain fails:
$ make ARCH=parisc headers_install
/home/rpjday/k/git/scripts/gcc-version.sh: line 16: hppa-linux-gcc: command not found
/home/rpjday/k/git/scripts/gcc-version.sh: line 17: hppa-linux-gcc: command not found
/home/rpjday/k/git/arch/parisc/Makefile:39: *** Sorry, GCC v3.3 or above is required.. Stop.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
next reply other threads:[~2007-10-10 16:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 16:44 Robert P. J. Day [this message]
2007-10-10 16:59 ` Randy Dunlap
2007-10-10 17:26 ` Robert P. J. Day
2007-10-10 18:38 ` parisc arch makefile clean-up needed [Was: cleaning up "make headers_install" for various architectures] Sam Ravnborg
2007-10-10 19:38 ` Kyle McMartin
2007-10-10 19:58 ` Sam Ravnborg
2007-10-10 20:21 ` Matthew Wilcox
2007-10-10 20:41 ` Sam Ravnborg
2007-10-10 21:33 ` Robert P. J. Day
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.64.0710101234340.32502@localhost.localdomain \
--to=rpjday@mindspring.com \
--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 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®