From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: <linux-parisc@vger.kernel.org>
Subject: Re: Error compiling 3.9.0
Date: Thu, 02 May 2013 14:41:40 +0200 [thread overview]
Message-ID: <2d7b2933c7dcaa9e8d7650da13a68795@sf-mail.de> (raw)
In-Reply-To: <BLU0-SMTP551CEF6DC18E943F6141C397BD0@phx.gbl>
Am 02.05.2013 03:34, schrieb John David Anglin:
> On 30-Apr-13, at 12:40 PM, Rolf Eike Beer wrote:
>
>>>> Nope, but probably this:
>>>>
>>>> *hppa64-unknown-linux-gnu-ld: scripts/link-vmlinux.sh: line 52:
>>>> 5398
>>>> Segmentation fault ${LD} ${LDFLAGS} ${LDFLAGS_vmlinux} -o
>>>> ${2} -T
>>>> ${lds} ${KBUILD_VMLINUX_INIT} --start-group ${KBUILD_VMLINUX_MAIN}
>>>> --end-group ${1}
>>>
>>> No, it's probably a kernel bug. Is the crash consistent? If it
>>> isn't,
>>> then it's an OS or kernel bug.
>>
>> I have got the same crash again. This are the first 2 tries I ever
>> made with
>> binutils 2.23.1 for 64 bit binaries, so I have nothing to compare to.
>
> I have successfully built 3.9.0 with debian binutils 2.23.2-2, so I
> think the above
> issue is specific to your kernel, config, etc. So, full details are
> needed. Particularly,
> details on how to reproduce the fault are needed.
It's a plain 3.9.0, the .config was attached to the first mail. I
always get the same problem at the same place:
KSYM .tmp_kallsyms1.o
hppa64-unknown-linux-gnu-ld: scripts/link-vmlinux.sh: line 52: 11674
Segmentation fault ${LD} ${LDFLAGS} ${LDFLAGS_vmlinux} -o ${2} -T
${lds} ${KBUILD_VMLINUX_INIT} --start-group ${KBUILD_VMLINUX_MAIN}
--end-group ${1}
make: *** [vmlinux] Error 139
Greetings,
Eike
next prev parent reply other threads:[~2013-05-02 12:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 9:37 Error compiling 3.9.0 Rolf Eike Beer
[not found] ` <BLU0-SMTP783053E3D7F49E33ED18CB97B30@phx.gbl>
[not found] ` <e5606dd2f0529641a897f078e3814e82@sf-mail.de>
2013-04-30 14:45 ` John David Anglin
2013-04-30 16:40 ` Rolf Eike Beer
2013-05-02 1:34 ` John David Anglin
2013-05-02 12:41 ` Rolf Eike Beer [this message]
2013-05-03 19:06 ` John David Anglin
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=2d7b2933c7dcaa9e8d7650da13a68795@sf-mail.de \
--to=eike-kernel@sf-tec.de \
--cc=linux-parisc@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