From: Pierfrancesco Caci <ik5pvx@penny.ik5pvx.ampr.org>
To: linux-kernel@vger.kernel.org
Subject: unable to link 2.4.2
Date: 24 Feb 2001 09:45:52 +0100 [thread overview]
Message-ID: <87pug8eaf3.fsf@penny.ik5pvx.ampr.org> (raw)
Hi there, can someone please tell me what's going wrong with my
compilation of 2.4.2 ?
make[2]: Entering directory `/usr/src/linux/arch/i386/boot'
ld -m elf_i386 -Ttext 0x0 -s -oformat binary bbootsect.o -o bbootsect
ld: cannot open binary: No such file or directory
make[2]: *** [bbootsect] Error 1
make[2]: Leaving directory `/usr/src/linux/arch/i386/boot'
make[1]: *** [bzImage] Error 2
make[1]: Leaving directory `/usr/src/linux'
make: *** [stamp-build] Error 2
root@penny:/usr/src # . linux/scripts/ver_linux
-- Versions installed: (if some fields are empty or look
-- unusual then possibly you have very old versions)
Linux penny 2.4.1 #1 Sat Feb 3 20:43:54 CET 2001 i686 unknown
Kernel modules 2.4.2
Gnu C 2.95.3
Gnu Make 3.79.1
Binutils 2.10.91.0.2
Linux C Library 2.2.2
Dynamic linker ldd (GNU libc) 2.2.2
Procps 2.0.7
Mount 2.10s
Net-tools 2.05
Console-tools 0.2.3
Sh-utils 2.0.11
Modules Loaded isofs loop binfmt_misc mousedev hid input nfsd microcode sg ipt_limit iptable_mangle ipt_MASQUERADE iptable_nat ip_conntrack ipt_LOG iptable_filter ip_tables sb sb_lib uart401 nfs ipv6 lockd sunrpc af_packet eepro100 3c509 sound soundcore isa-pnp usbcore
Thanks in advance ....
Pf
--
-------------------------------------------------------------------------------
Pierfrancesco Caci | ik5pvx | mailto:p.caci@tin.it - http://gusp.dyndns.org
Firenze - Italia | Office for the Complication of Otherwise Simple Affairs
Linux penny 2.4.1 #1 Sat Feb 3 20:43:54 CET 2001 i686 unknown
next reply other threads:[~2001-02-24 8:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-24 8:45 Pierfrancesco Caci [this message]
2001-02-24 9:46 ` Peter Samuelson
2001-02-24 10:10 ` Pierfrancesco Caci
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=87pug8eaf3.fsf@penny.ik5pvx.ampr.org \
--to=ik5pvx@penny.ik5pvx.ampr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.caci@tin.it \
/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®