From: Cliff Albert <cliff@oisec.net>
To: Bill Huey <billh@gnuppy.monkey.org>,
linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: Kernel Link Problems
Date: Thu, 18 Oct 2001 15:37:38 +0200 [thread overview]
Message-ID: <20011018153738.A9582@oisec.net> (raw)
In-Reply-To: <20011017162941.A32145@gnuppy> <20011018152516.A9089@oisec.net>
In-Reply-To: <20011018152516.A9089@oisec.net>
On Thu, Oct 18, 2001 at 03:25:16PM +0200, Cliff Albert wrote:
> > I'm running the 2.4.12-ac3 and I get this while linking vmlinuz:
> >
> > ld -m elf_i386 -Ttext 0x100000 -e startup_32 -o bvmlinux head.o misc.o piggy.o
> > ld: bvmlinux: Not enough room for program headers (allocated 2, need 3)
> > ld: final link failed: Bad value
> >
>
> Same thing happening here on 2.4.12-ac{2,3}, 2.4.12-ac1 will link correctly
>
> ld -m elf_i386 -Ttext 0x100000 -e startup_32 -o bvmlinux head.o misc.o piggy.o
> ld: bvmlinux: Not enough room for program headers (allocated 2, need 3)
> ld: final link failed: Bad value
>
> Distribution is Debian/unstable (apt-get dist-upgraded just before compile)
>
> Linux neve 2.4.12-ac1 #7 Fri Oct 12 21:27:50 CEST 2001 i686 unknown
>
> Gnu C 2.95.4
> Gnu make 3.79.1
> util-linux 2.11l
> mount 2.11l
> modutils 2.4.10
> e2fsprogs 1.25
> reiserfsprogs 3.x.0j
> Linux C Library 2.2.4
> Dynamic linker (ldd) 2.2.4
> Procps 2.0.7
> Net-tools 1.60
> Kbd 1.06
> Sh-utils 2.0.11
Some more investigation pointed me that this maybe a flaw in some package in debian-unstable. As 2.4.12-ac2 compiled on my laptop (which was not uptodate) and i've had reports that ac3 compiled just fine on machines running debian-stable.
--
Cliff Albert | RIPE: CA3348-RIPE | www.oisec.net
cliff@oisec.net | 6BONE: CA2-6BONE | icq 18461740
prev parent reply other threads:[~2001-10-18 13:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-17 23:29 Bill Huey
2001-10-18 13:25 ` Cliff Albert
2001-10-18 13:36 ` Bill Huey
2001-10-18 13:37 ` Cliff Albert [this message]
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=20011018153738.A9582@oisec.net \
--to=cliff@oisec.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=billh@gnuppy.monkey.org \
--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®