Am 03.03.2010 13:40, schrieb Martin Jansa:
On Wed, Mar 03, 2010 at 01:36:29PM +0100, Stefan Buschmann wrote:
Hi,
for appr. 2 weeks or so now, my build of shr-unstable fails again.
This time it is the package 'mesa-dri' which fails with a compile
error:
From 'log.do_compile':
/workspace/projekte/oe/om/build/cross/armv4t/lib/gcc/arm-oe-linux-gnueabi/4.4.3/../../../../arm-oe-linux-gnueabi/bin/ld:
warning: libstdc++.so.6, needed by ../../lib/libGLU.so, not found
(try using -rpath or -rpath-link)
../../lib/libGLU.so: undefined reference to `operator new[](unsigned
int)@GLIBCXX_3.4'
../../lib/libGLU.so: undefined reference to `operator
delete(void*)@GLIBCXX_3.4'
../../lib/libGLU.so: undefined reference to `vtable for
__cxxabiv1::__class_type_i...@cxxabi_1.3'
../../lib/libGLU.so: undefined reference to
`__gxx_personality...@cxxabi_1.3'
../../lib/libGLU.so: undefined reference to `__cxa_end_clea...@cxxabi_1.3'
../../lib/libGLU.so: undefined reference to `operator
delete[](void*)@GLIBCXX_3.4'
../../lib/libGLU.so: undefined reference to `vtable for
__cxxabiv1::__si_class_type_i...@cxxabi_1.3'
../../lib/libGLU.so: undefined reference to `vtable for
__cxxabiv1::__vmi_class_type_i...@cxxabi_1.3'
../../lib/libGLU.so: undefined reference to `__cxa_pure_virt...@cxxabi_1.3'
../../lib/libGLU.so: undefined reference to `operator new(unsigned
int)@GLIBCXX_3.4'
But when I look into
'workspace/projekte/oe/om/build/cross/armv4t/arm-oe-linux-gnueabi/lib',
the mentioned files are there:
lrwxrwxrwx 1 sbusch sbusch 19 2010-03-02 17:44 libstdc++.so ->
libstdc++.so.6.0.13
lrwxrwxrwx 1 sbusch sbusch 19 2010-03-02 17:44 libstdc++.so.6
-> libstdc++.so.6.0.13
-rwxr-xr-x 1 sbusch sbusch 3968476 2010-03-02 17:44 libstdc++.so.6.0.13
The build system is ubuntu 9.10 Server.
Any ideas?
Yes
http://trac.shr-project.org/trac/ticket/971
correct fix is to make mesa-dri looking for libstdc++.so.6 in right
place, but I didn't have enought time to fix it properly yet :/.
Regards,
Strange, because I searched the bug tracker for that error and didn't
find this. Well, my fault ;-)
Now with that workaround the package was built successfully.
Thanks for the hint!
Stefan
_______________________________________________
Shr-devel mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-devel
