linux-kernel - Re: ld: <...> internal error, aborting at arange-set.c line 202 in arange_set

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 28 Apr 2008 00:56:50 +0200
From:	"Jesper Juhl" <jesper.juhl@...il.com>
To:	"Patrick J. Volkerding" <volkerdi@...ckware.com>
Cc:	"Nick Clifton" <nickc@...cifixinc.com>,
	"Richard Henderson" <rth@...hat.com>, "Ian Taylor" <ian@...s.com>,
	"Jeff Law" <law@...hat.com>, "Jim Wilson" <wilson@...hat.com>,
	"DJ Delorie" <dj@...orie.com>,
	"Alan Modra" <amodra@...pond.net.au>,
	"Michael Meissner" <meissner@...hat.com>,
	"Daniel Jacobowitz" <dan@...ian.org>, linux-kernel@...r.kernel.org
Subject: Re: ld: <...> internal error, aborting at arange-set.c line 202 in arange_set_new

2008/4/28 Patrick J. Volkerding <volkerdi@...ckware.com>:
> Jesper Juhl wrote:
>
> > Hi,
> >
> > For your information;
> > I just test build Linus' tip of the kernel tree (HEAD at
> 064922a805ec7aadfafdd27aa6b4908d737c3c1d) on a up-to-date Slackware-current
> distro and hit this problem:
> >
> > ...
> >  GEN     .version
> >  CHK     include/linux/compile.h
> >  UPD     include/linux/compile.h
> >  CC      init/version.o
> >  LD      init/built-in.o
> >  LD      .tmp_vmlinux1
> > ld: size of bfd_vma > size of splay_tree types
> > ld: BFD (Linux/GNU Binutils) 2.18.50.0.4.20080208 internal error, aborting
> at arange-set.c line 202 in arange_set_new
> >
> > ld: Please report this bug.
> >
>
>  Hello all,
>
>  Slackware-current does not use binutils 2.18.50.0.4.20080208, but rather
> binutils-2.17.50.0.17.  We've run into a few unusual issues with newer
> binutils versions, so we tend to be rather cautious about having that
> package on the bleeding edge.
>
>  I'd be curious if using the binutils-2.17.50.0.17 package from
> slackware-current would avoid this problem, but also wanted to let people
> know that the system in question had a critical part of the toolchain
> replaced with something that didn't come from our set of packages.
>

Fron the slackware-current changelog :
Sat Feb 23 01:30:50 CST 2008
...
d/binutils-2.18.50.0.4-i486-1.tgz: Upgraded to binutils-2.18.50.0.4.

$ which ld
/usr/bin/ld
juhl@...gon:~/kernel/linux-2.6$ grep usr/bin/ld /var/log/packages/*
...
/var/log/packages/binutils-2.18.50.0.4-i486-1:usr/bin/ld
...

That's the package I have and it was indeed part of Slackware current
when I fetched it.

I see now, on closer inspection that the changelog also says ;

Fri Feb 29 14:00:57 CST 2008
...
d/binutils-2.17.50.0.17-i486-1.tgz: Reverted to binutils-2.17.50.0.17 due to
       many reports of ld bugs...
...

My scripts missed that, but I'll grab that package now and downgrade
and try to reproduce the problem.


-- 
Jesper Juhl <jesper.juhl@...il.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/