From: "Houten K.H.C. van (Karel)" <K.H.C.vanHouten@research.kpn.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Karel van Houten <K.H.C.vanHouten@research.kpn.com>,
Simon Gee <simong@oz.agile.tv>,
linux-mips@oss.sgi.com, K.H.C.vanHouten@research.kpn.com
Subject: Re: Recommended toolchain
Date: Thu, 29 Mar 2001 19:28:37 +0200 [thread overview]
Message-ID: <200103291728.TAA01350@sparta.research.kpn.com> (raw)
In-Reply-To: "Your message of Tue, 27 Mar 2001 21:02:33 +0200." <Pine.GSO.3.96.1010327205904.17103B-100000@delta.ds2.pg.gda.pl>
Hi all,
"Maciej W. Rozycki" writes:
> What's wrong with the toolchain wrt the kernel now? I've been compiling
>2.4 kernels successfully till the end of January -- it's just a lack of
>time and a nasty bug I want to track down that stop me from trying to
>compile a new kernel these days.
This happens when I compile kernel 2.4.0-test9 with
binutils 2.10.1, gcc 2.95.3, glibc 2.2.2 on my 5000/260 (R4k)
(the same source/config compiles fine with 2.8.1/egcs-2.90.27/glibc-2.0.6):
# make boot
....
ld -static -G 0 -T arch/mips/ld.script.little -Ttext 0x80040000 arch/mips/kernel
/head.o arch/mips/kernel/init_task.o init/main.o init/version.o \
--start-group \
arch/mips/kernel/kernel.o arch/mips/mm/mm.o kernel/kernel.o mm/mm.o fs/f
s.o ipc/ipc.o arch/mips/dec/dec.o \
drivers/block/block.o drivers/char/char.o drivers/misc/misc.o drivers/ne
t/net.o drivers/media/media.o drivers/parport/parport.a drivers/scsi/scsidrv.o
drivers/cdrom/cdrom.a drivers/tc/tc.a \
net/network.o \
arch/mips/lib/lib.a /usr/src/linux/lib/lib.a arch/mips/dec/prom/rexlib.a
\
--end-group \
-o vmlinux
nm vmlinux | grep -v '\(compiled\)\|\(\.o$\)\|\( [aU] \)\|\(\.\.ng$\)\|\(LASH[RL
]DI\)' | sort > System.map
make[1]: Entering directory `/usr/src/linux-2.4.0t9-R4k/arch/mips/boot'
./elf2ecoff /usr/src/linux/vmlinux vmlinux.ecoff -a
wrote 20 byte file header.
wrote 56 byte a.out header.
wrote 240 bytes of section headers.
wrote 4 byte pad.
writing 30560 bytes...
Intersegment gap (-2147256160 bytes) too large.
make[1]: *** [vmlinux.ecoff] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4.0t9-R4k/arch/mips/boot'
make: *** [boot] Error 2
WARNING: multiple messages have this Message-ID (diff)
From: "Houten K.H.C. van (Karel)" <K.H.C.vanHouten@research.kpn.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Karel van Houten <K.H.C.vanHouten@research.kpn.com>,
Simon Gee <simong@oz.agile.tv>,
linux-mips@oss.sgi.comK.H.C.vanHouten@research.kpn.com
Subject: Re: Recommended toolchain
Date: Thu, 29 Mar 2001 19:28:37 +0200 [thread overview]
Message-ID: <200103291728.TAA01350@sparta.research.kpn.com> (raw)
Message-ID: <20010329172837.bAOcArEs9HgbFhU69hF8CbhU5acju6ZA9inmm2FZUmA@z> (raw)
In-Reply-To: "Your message of Tue, 27 Mar 2001 21:02:33 +0200." <Pine.GSO.3.96.1010327205904.17103B-100000@delta.ds2.pg.gda.pl>
Hi all,
"Maciej W. Rozycki" writes:
> What's wrong with the toolchain wrt the kernel now? I've been compiling
>2.4 kernels successfully till the end of January -- it's just a lack of
>time and a nasty bug I want to track down that stop me from trying to
>compile a new kernel these days.
This happens when I compile kernel 2.4.0-test9 with
binutils 2.10.1, gcc 2.95.3, glibc 2.2.2 on my 5000/260 (R4k)
(the same source/config compiles fine with 2.8.1/egcs-2.90.27/glibc-2.0.6):
# make boot
....
ld -static -G 0 -T arch/mips/ld.script.little -Ttext 0x80040000 arch/mips/kernel
/head.o arch/mips/kernel/init_task.o init/main.o init/version.o \
--start-group \
arch/mips/kernel/kernel.o arch/mips/mm/mm.o kernel/kernel.o mm/mm.o fs/f
s.o ipc/ipc.o arch/mips/dec/dec.o \
drivers/block/block.o drivers/char/char.o drivers/misc/misc.o drivers/ne
t/net.o drivers/media/media.o drivers/parport/parport.a drivers/scsi/scsidrv.o
drivers/cdrom/cdrom.a drivers/tc/tc.a \
net/network.o \
arch/mips/lib/lib.a /usr/src/linux/lib/lib.a arch/mips/dec/prom/rexlib.a
\
--end-group \
-o vmlinux
nm vmlinux | grep -v '\(compiled\)\|\(\.o$\)\|\( [aU] \)\|\(\.\.ng$\)\|\(LASH[RL
]DI\)' | sort > System.map
make[1]: Entering directory `/usr/src/linux-2.4.0t9-R4k/arch/mips/boot'
./elf2ecoff /usr/src/linux/vmlinux vmlinux.ecoff -a
wrote 20 byte file header.
wrote 56 byte a.out header.
wrote 240 bytes of section headers.
wrote 4 byte pad.
writing 30560 bytes...
Intersegment gap (-2147256160 bytes) too large.
make[1]: *** [vmlinux.ecoff] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4.0t9-R4k/arch/mips/boot'
make: *** [boot] Error 2
next prev parent reply other threads:[~2001-03-29 17:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-20 3:06 Recommended toolchain Simon Gee
2001-03-20 20:12 ` Karel van Houten
2001-03-20 20:12 ` Karel van Houten
2001-03-20 20:37 ` Ralf Baechle
2001-03-20 20:37 ` Ralf Baechle
2001-03-27 19:02 ` Maciej W. Rozycki
2001-03-29 17:28 ` Houten K.H.C. van (Karel) [this message]
2001-03-29 17:28 ` Houten K.H.C. van (Karel)
2001-03-29 17:39 ` Karel van Houten
2001-03-29 17:39 ` Karel van Houten
2001-03-29 18:10 ` Maciej W. Rozycki
2001-04-01 14:39 ` Houten K.H.C. van (Karel)
2001-04-01 18:54 ` Florian Lohoff
2001-03-29 17:51 ` Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2001-03-21 14:00 Phil Thompson
2001-03-21 12:11 ` Erik Mullinix
2001-03-21 16:06 ` Keith M Wesolowski
2001-03-21 18:46 Phil Thompson
2001-03-21 22:06 ` Keith M Wesolowski
2001-03-22 7:49 ` Geert Uytterhoeven
2001-03-22 9:39 Phil Thompson
2001-03-22 9:43 ` Geert Uytterhoeven
2003-04-10 19:23 recommended toolchain carbonated beverage
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=200103291728.TAA01350@sparta.research.kpn.com \
--to=k.h.c.vanhouten@research.kpn.com \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
--cc=simong@oz.agile.tv \
--cc=vhouten@kpn.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