Re: Consequence of using ld to link libraries on Solaris

2004-04-14 Thread Gary V . Vaughan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15 Apr 2004, at 00:19, Albert Chin wrote: On Tue, Apr 13, 2004 at 10:42:05PM +0100, Gary V.Vaughan wrote: On 14 Apr 2004, at 18:55, Albert Chin wrote: I already have it done for Solaris, HP-UX, Tru64 UNIX, and IRIX. My patch is for the 1.5 branch. I

Re: Consequence of using ld to link libraries on Solaris

2004-04-13 Thread Albert Chin
On Tue, Apr 13, 2004 at 10:42:05PM +0100, Gary V.Vaughan wrote: > On 14 Apr 2004, at 18:55, Albert Chin wrote: > > >I already have it done for Solaris, HP-UX, Tru64 UNIX, and IRIX. My > >patch is for the 1.5 branch. I'll forward-port to the 1.6 branch and > >post the patch in a few days when I have

Re: Consequence of using ld to link libraries on Solaris

2004-04-13 Thread Gary V . Vaughan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 14 Apr 2004, at 18:55, Albert Chin wrote: On Tue, Apr 13, 2004 at 04:51:22PM +0100, Gary V.Vaughan wrote: On 13 Apr 2004, at 15:46, Bob Friesenhahn wrote: On Tue, 13 Apr 2004, Gary V.Vaughan wrote: So, to accommodate this, how about we use cc to crea

Re: Consequence of using ld to link libraries on Solaris

2004-04-13 Thread Albert Chin
On Tue, Apr 13, 2004 at 04:51:22PM +0100, Gary V.Vaughan wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 13 Apr 2004, at 15:46, Bob Friesenhahn wrote: > >On Tue, 13 Apr 2004, Gary V.Vaughan wrote: > > So, to accommodate this, how about we use cc to create shared > libr

Re: Consequence of using ld to link libraries on Solaris

2004-04-13 Thread Gary V . Vaughan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 13 Apr 2004, at 15:46, Bob Friesenhahn wrote: On Tue, 13 Apr 2004, Gary V.Vaughan wrote: So, to accommodate this, how about we use cc to create shared libraries on Solaris? This problem is not specific to Solaris. The same problem occurs on Digital

Re: Consequence of using ld to link libraries on Solaris

2004-04-13 Thread Bob Friesenhahn
On Tue, 13 Apr 2004, Gary V.Vaughan wrote: > >> > >> So, to accommodate this, how about we use cc to create shared > >> libraries on Solaris? > > > > This problem is not specific to Solaris. The same problem occurs on > > Digital Unix, or any other OS where libtool doesn't currently use the > > C

Re: Consequence of using ld to link libraries on Solaris

2004-04-13 Thread Gary V . Vaughan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12 Apr 2004, at 23:16, Bob Friesenhahn wrote: On Tue, 13 Apr 2004, Albert Chin wrote: When linking a C program and using the Sun C compiler, we use the Sun linker to create a shared libraries. The problem with this is if -mt is passed to the Sun C co

Re: Consequence of using ld to link libraries on Solaris

2004-04-12 Thread Bob Friesenhahn
On Tue, 13 Apr 2004, Albert Chin wrote: > When linking a C program and using the Sun C compiler, we use the Sun > linker to create a shared libraries. The problem with this is if -mt > is passed to the Sun C compiler _without_ -lpthread/-lthread. From > cc(1): > -mt Passes D_REENTRANT to pre

Consequence of using ld to link libraries on Solaris

2004-04-12 Thread Albert Chin
When linking a C program and using the Sun C compiler, we use the Sun linker to create a shared libraries. The problem with this is if -mt is passed to the Sun C compiler _without_ -lpthread/-lthread. From cc(1): -mt Passes D_REENTRANT to preprocessor. Appends -lthread after all oth