Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


At 5:23am -0400 Thu, 25 Aug 2011, Caolán McNamara wrote:
On Wed, 2011-08-24 at 18:06 +0100, Michael Meeks wrote:
        But then again, it links to libstdc++
...
        libstdc++.so.6 =>  /usr/lib/libstdc++.so.6 (0xb7658000)
...

There was a mention of a "/usr/local/bin/g++", which makes me wonder
about mismatching libstdc++.so.X. To humour me, what about...

rm -rf external/*/lib/*
rm -rf solver/*/*/lib/libstdc++*
rm -rf solver/*/*/lib/libgcc_s.so*

I went ahead and did that with no love.  For reference:

$ ldd sal/unxlngx6/lib/libuno_sal.so | grep stdc
        libstdc++.so.6 => /usr/local/lib64/libstdc++.so.6 (0x00007f122c7cb000)

At my novice gcc level, my research suggests it's to do with including libstdc++ in the build command. I still don't know exactly why the compilation fails with GCC v4.6 (compiled three weeks ago) yet doesn't with GCC v4.4, but I can fix it one of two ways:

-----
$ hash -r
$ which gcc g++; gcc --version | head -1; g++ --version | head -1
/usr/local/bin/gcc
/usr/local/bin/g++
gcc (GCC) 4.6.1
g++ (GCC) 4.6.1

# fails
$ gcc -o .../oosplash [...]

# works; rest of build can now finish successfully
$ gcc -o .../oosplash [...] -lstdc++
   or
$ g++ -o .../oosplash [...]
-----

Have others had any issues compiling LO with GCC 4.6? It's frustrating and telling that I'm the only one noticing it. What voodoo have I overlooked?

Thanks,

Kevin


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.