Re: [sigc] Re: [gtkmm] Re: Problems compiling libsigc++-2.0.3 on Slackware

[Martin Schulze <martin-ml hippogriff de>]

Am 13.08.2004 10:34:21 schrieb(en) martin-ml hippogriff de:
> Hi Juergen,
>
> if I remember correctly, Yaakov (whom you refer to below) had a
> different
> problem. I think he ran 'autoconf' but that resulted in a wrong
> sigc++config.h being created during configure.
>
> As regards to your problem I'm afraid that I don't have any idea what
> is
> causing it. Have you tried the simple std::list compile test that I
> posted
> earlier on the mailing list? I can repost it tonight if you missed
> that
> mail.

Here comes the test I mean:

#include <list>

struct foo {
int m;
};


struct bar {
typedef std::list<foo> foo_list_type;
foo_list_type foo_list;
};


int main() {
bar my_bar;
return 0;
}

(see  
http://lists.gnome.org/archives/libsigc-list/2004-August/msg00001.html)


Regards,

 Martin

> > Hallo Martin,
> >
> > On Sat, 2004-08-07 at 14:57 +0200, Martin Schulze wrote:
> >> BTW, this should be discussed on libsigc-list gnome org 
> >>
> >> Am 07.08.2004 14:54:29 schrieb(en) Martin Schulze:
> >> > Am 06.08.2004 22:58:30 schrieb(en) Yaakov Selkowitz:
> > ...
> >> >> | I cannot build libsigc++-2.0.3 on Slackware-9.1 updated to
> gcc-
> >> >> 3.3.2
> > ...
> >> > Could you post your generated file sigc++config.h, please?
> >> >
> >> > Please also try to compile the following tarball and post
> configure
> >> > output, compiler errors and sigc++config.h (if the problem
> persists):
> >> >
> >> >  http://www.hippogriff.de/libsigc++-2.0.4-test3.tar.gz
> > ...
> > I just test it (to be precise, I used
> http://www.hippogriff.de/libsigc+
> > +-2.0.4-test4.tar.gz) , but I still have the same error.
> >
> > make[3]: Entering directory
> > `/usr/src_mousehomenet/Desktops/Gnome/libsigc++-2.0.4/sigc++'
> > if /bin/sh ../libtool --mode=compile g++ -DHAVE_CONFIG_H   -I.. - 
> I..
>   -
> > g -O2 -MT signal_base.lo -MD -MP -MF ".deps/signal_base.Tpo" -c -o
> > signal_base.lo signal_base.cc; \
> > then mv -f ".deps/signal_base.Tpo" ".deps/signal_base.Plo"; else rm
> -f
> > ".deps/signal_base.Tpo"; exit 1; fi
> >  g++ -DHAVE_CONFIG_H -I.. -I.. -g -O2 -MT signal_base.lo -MD -MP -
> > MF .deps/signal_base.Tpo -c signal_base.cc  -fPIC -DPIC -
> > o .libs/signal_base.o
> > In file included from signal.h:10,
> >                  from /usr/include/pthread.h:24,
> >                  from /usr/include/c++/3.3.4/i686-pc-linux-
> > gnu/bits/gthr-default.h:37,
> >                  from /usr/include/c++/3.3.4/i686-pc-linux-
> > gnu/bits/gthr.h:98,
> >                  from /usr/include/c++/3.3.4/i686-pc-linux-gnu/ 
> bits/c+
> > +io.h:37,
> >                  from /usr/include/c++/3.3.4/bits/fpos.h:44,
> >                  from /usr/include/c++/3.3.4/iosfwd:49,
> >                  from /usr/include/c++/3.3.4/bits/stl_algobase. 
> h:70,
> >                  from /usr/include/c++/3.3.4/list:67,
> >                  from ../sigc++/signal_base.h:24,
> >                  from signal_base.cc:20:
> > ../sigc++/trackable.h:76: error: template-id `
> >    list<sigc::internal::trackable_callback>' used as a declarator
> > ../sigc++/trackable.h:76: error: parse error before `;' token
> > ../sigc++/trackable.h:77: error: 'callback_list' is used as a type,
> but
> > is not
> >    defined as a type.
> >
> > I find the same behaviour on three systems, all slackware and
> gcc-3.3.2
> > or gcc-3.3.4. Everywhere I have the following gcc specs (gcc -v)
> > Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.[24]/ 
> specs
> > Configured with: ../gcc-3.3.[24]/configure --prefix=/usr --enable-
> > threads
> > Thread model: posix
> > gcc version 3.3.[24]
> >
> > Is there something wrong with these specs?
> >
> > 	Regards Juergen
> >
> >
> >
> > --
> > Juergen Rose <rose rz uni-potsdam de>
> > University of Potsdam
> >
> >
>
> _______________________________________________
> libsigc-list mailing list
> libsigc-list gnome org
> http://mail.gnome.org/mailman/listinfo/libsigc-list