From: Catalin BOIE <util@deuroconsult.ro>
To: linux-kernel@vger.kernel.org
Subject: 2.6.0test3mm1 + gcc 3.2.3 | gcc3.3 compile error (Input/output error)
Date: Tue, 12 Aug 2003 16:03:28 +0300 (EEST) [thread overview]
Message-ID: <Pine.LNX.4.56.0308121603010.8716@hosting.rdsbv.ro> (raw)
Hello!
I have some problems to compile 2.6.0test3mm1.
I had no problem compiling 2.6.0test1 and test2 and all mm patches.
My config:
Linux Dino 2.6.0-test2-mm4 #1 Mon Aug 4 12:48:32 EEST 2003 i686 unknown
unknown GNU/Linux
Gnu C 3.3
Gnu make 3.80
util-linux 2.11z
mount 2.11z
e2fsprogs 1.33
jfsutils 1.1.2
reiserfsprogs 3.6.8
xfsprogs 2.3.9
quota-tools 3.08.
PPP 2.4.1
nfs-utils 1.0.5
Linux C Library 2.3.1
Dynamic linker (ldd) 2.3.1
Linux C++ Library 5.0.4
Procps 2.0.13
Net-tools 1.60
Kbd 1.08
Sh-utils 5.0
The error is:
ld -m elf_i386 -r -o init/built-in.o init/main.o init/version.o
init/mounts.o init/initramfs.o
ld -m elf_i386 -T arch/i386/kernel/vmlinux.lds.s
arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/built-in.o
--start-group usr/built-in.o arch/i386/kernel/built-in.o
arch/i386/mm/built-in.o arch/i386/mach-default/built-in.o
kernel/built-in.o mm/built-in.o fs/built-in.o ipc/built-in.o
security/built-in.o crypto/built-in.o lib/lib.a arch/i386/lib/lib.a
lib/built-in.o arch/i386/lib/built-in.o drivers/built-in.o
sound/built-in.o arch/i386/pci/built-in.o net/built-in.o --end-group -o
.tmp_vmlinux1
arch/i386/kernel/built-in.o: could not read symbols: Input/output error
make: *** [.tmp_vmlinux1] Error 1
Any hints?
It may be that I upgrade binutils?
Thank you very much!
---
Catalin(ux) BOIE
catab@deuroconsult.ro
next reply other threads:[~2003-08-12 13:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-12 13:03 Catalin BOIE [this message]
2003-08-12 13:15 ` Lars Duesing
2003-08-12 13:22 ` Catalin BOIE
2003-08-13 20:08 ` insecure
2003-08-14 5:45 ` Catalin BOIE
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.56.0308121603010.8716@hosting.rdsbv.ro \
--to=util@deuroconsult.ro \
--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®