RESOLVED INVALID33401
Building Qt Webkit for embedded powerpc segfaults 
https://bugs.webkit.org/show_bug.cgi?id=33401
Summary Building Qt Webkit for embedded powerpc segfaults
Gabe Johnson
Reported 2010-01-08 14:11:53 PST
I am using ELDK 4.2 and Freescale mpc5121ads ltib compilers. ELDK is using gcc version 4.2.2 and binutils version 2.17.50.0.12. Freescale ltib is using gcc version 4.1.2 and binutils 2.17. When Qt Webkit is linking it crashes with "collect2: ld terminated with signal 11 [Segmentation fault]". The segfault occurs when building WebCore. If I enable verbose mode on the linker it appears to just crash while trying to attempt to open libgcc_s, here is a portion of the output: attempt to open /opt/trolltech/qte-4.6.0-powerpc/lib/libc.so failed attempt to open /opt/trolltech/qte-4.6.0-powerpc/lib/libc.a failed attempt to open /opt/trolltech/qte-4.6.0-powerpc/lib/libc.so failed attempt to open /opt/trolltech/qte-4.6.0-powerpc/lib/libc.a failed attempt to open /opt/freescale/usr/local/gcc-4.1.78-eglibc-2.5.78-1/powerpc-e300c3-linux-gnu/lib/gcc/powerpc-e300c3-linux-gnu/4.1.2/libc.so failed attempt to open /opt/freescale/usr/local/gcc-4.1.78-eglibc-2.5.78-1/powerpc-e300c3-linux-gnu/lib/gcc/powerpc-e300c3-linux-gnu/4.1.2/libc.a failed attempt to open /opt/freescale/usr/local/gcc-4.1.78-eglibc-2.5.78-1/powerpc-e300c3-linux-gnu/lib/gcc/powerpc-e300c3-linux-gnu/4.1.2/../../../../powerpc-e300c3-linux-gnu/lib/libc.so failed attempt to open /opt/freescale/usr/local/gcc-4.1.78-eglibc-2.5.78-1/powerpc-e300c3-linux-gnu/lib/gcc/powerpc-e300c3-linux-gnu/4.1.2/../../../../powerpc-e300c3-linux-gnu/lib/libc.a failed attempt to open /opt/freescale/usr/local/gcc-4.1.78-eglibc-2.5.78-1/powerpc-e300c3-linux-gnu/powerpc-e300c3-linux-gnu/libc/lib/libc.so failed attempt to open /opt/freescale/usr/local/gcc-4.1.78-eglibc-2.5.78-1/powerpc-e300c3-linux-gnu/powerpc-e300c3-linux-gnu/libc/lib/libc.a failed attempt to open /opt/freescale/usr/local/gcc-4.1.78-eglibc-2.5.78-1/powerpc-e300c3-linux-gnu/powerpc-e300c3-linux-gnu/libc/usr/lib/libc.so succeeded opened script file /opt/freescale/usr/local/gcc-4.1.78-eglibc-2.5.78-1/powerpc-e300c3-linux-gnu/powerpc-e300c3-linux-gnu/libc/usr/lib/libc.so opened script file /opt/freescale/usr/local/gcc-4.1.78-eglibc-2.5.78-1/powerpc-e300c3-linux-gnu/powerpc-e300c3-linux-gnu/libc/usr/lib/libc.so attempt to open /opt/freescale/usr/local/gcc-4.1.78-eglibc-2.5.78-1/powerpc-e300c3-linux-gnu/powerpc-e300c3-linux-gnu/libc/lib/libc.so.6 succeeded /lib/libc.so.6 (/opt/freescale/usr/local/gcc-4.1.78-eglibc-2.5.78-1/powerpc-e300c3-linux-gnu/powerpc-e300c3-linux-gnu/libc/lib/libc.so.6) attempt to open /opt/freescale/usr/local/gcc-4.1.78-eglibc-2.5.78-1/powerpc-e300c3-linux-gnu/powerpc-e300c3-linux-gnu/libc/usr/lib/libc_nonshared.a succeeded attempt to open /opt/freescale/usr/local/gcc-4.1.78-eglibc-2.5.78-1/powerpc-e300c3-linux-gnu/powerpc-e300c3-linux-gnu/libc/lib/ld.so.1 succeeded /lib/ld.so.1 (/opt/freescale/usr/local/gcc-4.1.78-eglibc-2.5.78-1/powerpc-e300c3-linux-gnu/powerpc-e300c3-linux-gnu/libc/lib/ld.so.1) attempt to open /opt/trolltech/qte-4.6.0-powerpc/lib/libgcc_s.so failed attempt to open /opt/trolltech/qte-4.6.0-powerpc/lib/libgcc_s.a failed attempt to open /opt/trolltech/qte-4.6.0-powerpc/lib/libgcc_s.so failed attempt to open /opt/trolltech/qte-4.6.0-powerpc/lib/libgcc_s.a failed attempt to open /opt/freescale/usr/local/gcc-4.1.78-eglibc-2.5.78-1/powerpc-e300c3-linux-gnu/lib/gcc/powerpc-e300c3-linux-gnu/4.1.2/libgcc_s.so failed attempt to open /opt/freescale/usr/local/gcc-4.1.78-eglibc-2.5.78-1/powerpc-e300c3-linux-gnu/lib/gcc/powerpc-e300c3-linux-gnu/4.1.2/libgcc_s.a failed attempt to open /opt/freescale/usr/local/gcc-4.1.78-eglibc-2.make: *** [../../../../lib/libQtWebKit.so.4.6.0] Error 1
Attachments
Add attachment proposed patch, testcase, etc.
Gabe Johnson
Comment 1 2010-01-12 13:50:31 PST
I downloaded the latest webkit source and tried to compile the qt port against a 4.6.0 build and it still segfaults.
Benjamin Poulain
Comment 2 2010-03-06 09:02:24 PST
Not much we can do in WebKit if you linker is buggy. You should report the problem to the developers of the linker.
Note You need to log in before you can comment on or make changes to this bug.