Hello,
The problem when building webkitgtk with new glibc has been mention in this
page: https://bugs.webkit.org/show_bug.cgi?id=103194, and there is a patch
for it. Only applying the patch if you have that glibc version >= 2.17.

Regards


On Tue, Apr 2, 2013 at 6:20 PM, James Richard Tyrer <[email protected]> wrote:

> On 04/01/2013 11:59 AM, Niels Terp wrote:
> > Hi,
> >
> > I have compiled all the required and the recommended dependencies, and
> all
> > the optional but MathML.
> >
> > I then compile WebKitGTK+ straight from the book. After compiling for
> > several hours, it stops with this error:
> >
> >    CXXLD  Programs/WebKitPluginProcess
> > /usr/bin/ld:
> >
> Source/WebKit2/Platform/unix/Programs_WebKitPluginProcess-SharedMemoryUnix.o
> > : undefined reference to symbol 'shm_open@@GLIBC_2.2'
> > /usr/bin/ld: note: 'shm_open@@GLIBC_2.2' is defined in DSO
> /lib/librt.so.1
> > so try adding it to the linker command line
> > /lib/librt.so.1: could not read symbols: Invalid operation
> > collect2: error: ld returned 1 exit status
> > make[1]: *** [Programs/WebKitPluginProcess] Fejl 1
> > make[1]: Forlader katalog '/home/niels/xc/webkitgtk-1.10.2'
> >
> > Can anybody help with this ?
>
> I pursued it to compile.
>
> Sorry that I can't remember if it was C or C++ code that it failed on so
> you will have to check.  Assuming that it was C++, you need to do this:
>
>         export CXX_FLAGS="-L/lib -lrt"
>
> and start over from 'configure'.  If it was C rather than C++, then it
> would be C_FLAGS.  This trick can often be used to "nudge" something
> into compiling.
>
> --
> James Tyrer
>
> Linux (mostly) From Scratch
> --
> http://linuxfromscratch.org/mailman/listinfo/blfs-support
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
>

Attachment: webkitgtk-1.10.2-Explicitly-link-against-librt.patch
Description: Binary data

-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to