From: John Bradford <john@grabjohn.com>
To: rmk@arm.linux.org.uk (Russell King)
Cc: linux-kernel@vger.kernel.org, kai@tp1.ruhr-uni-bochum.de
Subject: Re: 2.5.62: Cross-building broken
Date: Tue, 18 Feb 2003 13:49:33 +0000 (GMT) [thread overview]
Message-ID: <200302181349.h1IDnX6w001233@darkstar.example.net> (raw)
In-Reply-To: <20030218003410.A27937@flint.arm.linux.org.uk> from "Russell King" at Feb 18, 2003 12:34:10 AM
> Cross-building ARM from HPPA:
>
> $ make config CROSS_COMPILE=/home/rmk/bin/arm-linux- ARCH=arm
> make: Entering directory `/home/rmk/v2.5/linux-rpc'
> make -f scripts/Makefile.build obj=scripts
> gcc -Wp,-MD,scripts/.empty.o.d -D__KERNEL__ -Iinclude -Wall
> -Wstrict-prototypes -Wno-trigraphs -Os -fno-strict-aliasing -fno-common
> -mshort-load-bytes -msoft-float -Wa,-mno-fpu -Uarm -nostdinc -iwithprefix
> include -DKBUILD_BASENAME=empty -DKBUILD_MODNAME=empty -c -o
> scripts/empty.o scripts/empty.c
> make: Leaving directory `/home/rmk/v2.5/linux-rpc'
> cc1: Invalid option `short-load-bytes'
> make[1]: *** [scripts/empty.o] Error 1
> make: *** [scripts] Error 2
>
> We seem to be using the wrong compiler here, or the wrong CFLAGS.
Hmmm, cross compiling for Sparc works:
make config CROSS_COMPILE=/usr/local/bin/sparc-linux- ARCH=sparc
make -f scripts/Makefile.build obj=scripts
make -f scripts/Makefile.build obj=scripts/kconfig scripts/kconfig/conf
make[1]: `scripts/kconfig/conf' is up to date.
./scripts/kconfig/conf arch/sparc/Kconfig
#
# using defaults found in arch/sparc/defconfig
#
*
* Linux Kernel Configuration
*
*
* Code maturity level options
*
Prompt for development and/or incomplete code/drivers (EXPERIMENTAL) [Y/n/?]
John.
next prev parent reply other threads:[~2003-02-18 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 0:34 Russell King
2003-02-18 0:58 ` Kai Germaschewski
2003-02-18 13:49 ` John Bradford [this message]
2003-02-18 16:40 ` Geert Uytterhoeven
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=200302181349.h1IDnX6w001233@darkstar.example.net \
--to=john@grabjohn.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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®