Re: [sigc] Build fails with g++ 3.3.2

[Martin Schulze <martin-ml hippogriff de>]

Am 11.12.2004 00:51:55 schrieb(en) Nomak:
> First, GCC is a compiler AND a linker, trying to seperate them and
> say
> "you can use any compiler but not any linker of GCC" is not really
> clever.
>
> Second, the STL is shipped with GCC, and AFAIK you can't use a STL
> from another version of GCC. So once again, it's not clever to
> separate them.
>
> Anayway, should upgrade the requirements, or make a note about this
> on
> the web site or in some BUILD file...

I only tried to isolate the problem and explain my suspicion that the  
fault lies in the packages that ship with to your distro. At least  
libsigc++-2.0.6 builds without any problems with a standard debian  
sarge configuration which currently has gcc 3.3.4.

Do you know any bugs that have been fixed between gcc 3.3.2 and gcc  
3.3.4 that can be the source of the errors? Does anybody else with  
access to a box with gcc <= 3.3.2 experience the problems?

Regards,

 Martin


> Nomak
>
> Martin Schulze wrote:
> > Am 09.12.2004 14:14:49 schrieb(en) Nomak:
> >> Hello,
> >>
> >> i can't build libsigc++ with g++ 3.3.2:
> >>
> >>
> >> libsigc++-2.0.6-build $ make
> >> make  all-recursive
> >> make[1]: Entering directory `/tmp/gtk/libsigc++-2.0.6-build'
> >> Making all in sigc++
> >> make[2]: Entering directory `/tmp/gtk/libsigc++-2.0.6-build/sigc+ 
> +'
> >> make  all-am
> >> make[3]: Entering directory `/tmp/gtk/libsigc++-2.0.6-build/sigc+ 
> +'
> >> make[3]: Nothing to be done for `all-am'.
> >> make[3]: Leaving directory `/tmp/gtk/libsigc++-2.0.6-build/sigc++'
> >> make[2]: Leaving directory `/tmp/gtk/libsigc++-2.0.6-build/sigc++'
> >> Making all in tests
> >> make[2]: Entering directory `/tmp/gtk/libsigc++-2.0.6-build/tests'
> >> /bin/sh ../libtool --mode=link g++ -g -O2
> -L/home/david/install/lib
> >> -o
> >> test_trackable test_trackable.o ../sigc++/libsigc-2.0.la
> >> g++ -g -O2 -o .libs/test_trackable test_trackable.o
> >> -L/home/david/install/lib ../sigc++/.libs/libsigc-2.0.so
> >> /home/david/install/lib/libstdc++.so
> >> -L/var/samba_public/gcc/gcc-3.4.2-build/i686-pc-linux-gnu/libstdc+ 
> +
> -
> >> v3
> >> /src
> >> -L/var/samba_public/gcc/gcc-3.4.2-build/i686-pc-linux-gnu/libstdc+ 
> +
> -
> >> v3
> >> /src/.libs
> >> -L/var/samba_public/gcc/gcc-3.4.2-build/gcc
> >> -L/home/david/install/lib/gcc/i686-pc-linux-gnu/3.4.2
> >> -L/home/david/install/lib/gcc/i686-pc-linux-gnu/3.4.2/../../..
> >> -Wl,--r
> >> path
> >> -Wl,/home/david/install/lib
> >> ../sigc++/.libs/libsigc-2.0.so: undefined reference to
> >> `std::__default_alloc_template<(bool)1,
> (int)0>::allocate(unsigned)'
> >> ../sigc++/.libs/libsigc-2.0.so: undefined reference to
> >> `std::__default_alloc_template<(bool)1, (int)0>::_S_free_list'
> >> ../sigc++/.libs/libsigc-2.0.so: undefined reference to
> >> `std::__default_alloc_template<(bool)1, (int)0>::_Lock::~_Lock
> >> [in-charge]()'
> >> ../sigc++/.libs/libsigc-2.0.so: undefined reference to
> >> `std::__default_alloc_template<(bool)1, (int)0>::_S_force_new'
> >> ../sigc++/.libs/libsigc-2.0.so: undefined reference to
> >> `std::__default_alloc_template<(bool)1,
> >> (int)0>::_Lock::_Lock[in-charge]()'
> >> ../sigc++/.libs/libsigc-2.0.so: undefined reference to
> >> `std::__default_alloc_template<(bool)1,
> >> (int)0>::_S_freelist_index(unsigned)'
> >> ../sigc++/.libs/libsigc-2.0.so: undefined reference to
> >> `std::__default_alloc_template<(bool)1,
> >> (int)0>::_S_node_allocator_lock'
> >> collect2: ld returned 1 exit status
> >> make[2]: *** [test_trackable] Error 1
> >> make[2]: Leaving directory `/tmp/gtk/libsigc++-2.0.6-build/tests'
> >> make[1]: *** [all-recursive] Error 1
> >> make[1]: Leaving directory `/tmp/gtk/libsigc++-2.0.6-build'
> >> make: *** [all] Error 2
> >>
> >> libsigc++-2.0.6-build $ g++ --version
> >> g++ (GCC) 3.3.2 (Mandrake Linux 10.0 3.3.2-6mdk)
> >>
> >>
> >> Could you update the compiler requirement on the web page to >
> 3.3.2
> >> or patch the code?
> >
> > No! The error above occurs during linking and doesn't have anything
> to
> > do with the compiler version. I see some undefined references to
> stl
> > functions. This could mean that libstdc++ is not included in the
> list
> > of libraries or that there is a general problem with the stl
> package
> > in your distribution.
> >
> > Regards,
> >
> >   Martin