Re: 1.4.1@solaris8: __eprintf undefined

2001-09-10 Thread Gary V. Vaughan
On Tue, Sep 11, 2001 at 12:26:44AM +0200, Hubert Feyrer wrote: > On Mon, 10 Sep 2001, Gary V. Vaughan wrote: > > It is a long standing bug with gcc using native ld on solaris, > > revealed in this release because I have started using assert() in > > ltdl.c (which requires __eprintf from libgcc.a).

Re: 1.4.1@solaris8: __eprintf undefined

2001-09-10 Thread Hubert Feyrer
On Mon, 10 Sep 2001, Gary V. Vaughan wrote: > It is a long standing bug with gcc using native ld on solaris, > revealed in this release because I have started using assert() in > ltdl.c (which requires __eprintf from libgcc.a). > > Here are a couple of options: > > * upgrade to gcc 3.0.1 from

Re: 1.4.1@solaris8: __eprintf undefined

2001-09-10 Thread Gary V. Vaughan
On Mon, Sep 10, 2001 at 05:55:57PM +0200, Hubert Feyrer wrote: > On Mon, 10 Sep 2001, Andreas Wendt wrote: > > libtool seems not to link in libgcc.a when using gcc (where this symbol is > > defined). > > You may use Sun's native compiler cc to get it working. > > That's not an option, as the Sun

RE: 1.4.1@solaris8: __eprintf undefined

2001-09-10 Thread Hubert Feyrer
On Mon, 10 Sep 2001, Andreas Wendt wrote: > libtool seems not to link in libgcc.a when using gcc (where this symbol is > defined). > You may use Sun's native compiler cc to get it working. That's not an option, as the Sun 'cc' costs $. I'll play with -lgcc and see what happens, but it would b

RE: 1.4.1@solaris8: __eprintf undefined

2001-09-10 Thread Andreas Wendt
Hello Hubert, libtool seems not to link in libgcc.a when using gcc (where this symbol is defined). You may use Sun's native compiler cc to get it working. -- Andreas > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > Hubert Feyrer > Sent: Monday, Sep