From: "Patrick J. Volkerding" <volkerdi@slackware.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Nick Clifton <nickc@specifixinc.com>,
Richard Henderson <rth@redhat.com>, Ian Taylor <ian@airs.com>,
Jeff Law <law@redhat.com>, Jim Wilson <wilson@redhat.com>,
DJ Delorie <dj@delorie.com>, Alan Modra <amodra@bigpond.net.au>,
Michael Meissner <meissner@redhat.com>,
Daniel Jacobowitz <dan@debian.org>,
linux-kernel@vger.kernel.org
Subject: Re: ld: <...> internal error, aborting at arange-set.c line 202 in arange_set_new
Date: Sun, 27 Apr 2008 17:43:04 -0500 [thread overview]
Message-ID: <48150178.4050900@slackware.com> (raw)
In-Reply-To: <alpine.LNX.1.00.0804272326320.14738@dragon.funnycrock.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.
Best regards,
Pat
next prev parent reply other threads:[~2008-04-27 23:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 21:35 ld: <...> internal error, aborting at arange-set.c line 202 in arange_set_new Jesper Juhl
2008-04-27 22:43 ` Patrick J. Volkerding [this message]
2008-04-27 22:56 ` Jesper Juhl
2008-04-27 23:10 ` Jesper Juhl
2008-04-27 22:55 ` Alan Modra
2008-04-28 0:12 ` Daniel Jacobowitz
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=48150178.4050900@slackware.com \
--to=volkerdi@slackware.com \
--cc=amodra@bigpond.net.au \
--cc=dan@debian.org \
--cc=dj@delorie.com \
--cc=ian@airs.com \
--cc=jesper.juhl@gmail.com \
--cc=law@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=meissner@redhat.com \
--cc=nickc@specifixinc.com \
--cc=rth@redhat.com \
--cc=wilson@redhat.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