On 5/2/2013 8:41 AM, Rolf Eike Beer wrote:
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
Although I can confirm the branch distance issue with your .config, I
don't see the above. Thus, some
debugging on your part would be needed to find out what's going on.
There should be info about the segmentation fault in your system log.
Gdb can tell you which application
faulted but without a debug version, it will be hard to tell what's
happening. Failing command would need
debugging.
Dave
--
John David Anglin dave.anglin@xxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
