Re: glib2: libgthread-2.0 linked without pthread support

2011-11-24 Thread Stuart Henderson
On 2011-11-22, Justin Lindberg wrote: > However, somehow the binaries distributed with the 5.0 release and > recent snapshots still aren't getting linked with the right library. Sure, but this is a problem with the R port, not anything else. Fixing it anywhere else is wrong (in particular what y

Re: glib2: libgthread-2.0 linked without pthread support

2011-11-22 Thread Kenneth R Westerback
On Tue, Nov 22, 2011 at 08:12:16AM -0800, Justin Lindberg wrote: > On 11/21/11 23:04, Antoine Jacoutot wrote: > >On Mon, Nov 21, 2011 at 06:11:48PM -0800, Justin Lindberg wrote: > >>The problem is that the shared object library > >> > >>/usr/local/lib/libgthread-2.0.so.2800.0 > >>or > >>/usr/local/

Re: glib2: libgthread-2.0 linked without pthread support

2011-11-22 Thread Antoine Jacoutot
On Tue, Nov 22, 2011 at 08:12:16AM -0800, Justin Lindberg wrote: > On 11/21/11 23:04, Antoine Jacoutot wrote: > >On Mon, Nov 21, 2011 at 06:11:48PM -0800, Justin Lindberg wrote: > >>The problem is that the shared object library > >> > >>/usr/local/lib/libgthread-2.0.so.2800.0 > >>or > >>/usr/local/

Re: glib2: libgthread-2.0 linked without pthread support

2011-11-22 Thread Justin Lindberg
On 11/21/11 23:04, Antoine Jacoutot wrote: On Mon, Nov 21, 2011 at 06:11:48PM -0800, Justin Lindberg wrote: The problem is that the shared object library /usr/local/lib/libgthread-2.0.so.2800.0 or /usr/local/lib/libgthread-2.0.so.2992.0 as it is by now in -CURRENT tries to execute function cal

Re: glib2: libgthread-2.0 linked without pthread support

2011-11-22 Thread Pascal Stumpf
On Mon, 21 Nov 2011 17:37:42 -0800, Justin Lindberg wrote: > ld: unrecognized option '-pthread' > ld: use the --help option for usage information Use gcc(1) instead of calling ld directly.

Re: glib2: libgthread-2.0 linked without pthread support

2011-11-21 Thread Antoine Jacoutot
On Mon, Nov 21, 2011 at 06:11:48PM -0800, Justin Lindberg wrote: > The problem is that the shared object library > > /usr/local/lib/libgthread-2.0.so.2800.0 > or > /usr/local/lib/libgthread-2.0.so.2992.0 > as it is by now in -CURRENT > > tries to execute function calls that are implemented in >

Re: glib2: libgthread-2.0 linked without pthread support

2011-11-21 Thread Justin Lindberg
On 11/21/11 18:11, Justin Lindberg wrote: On 11/21/11 17:37, Justin Lindberg wrote: On 11/21/11 04:46, Antoine Jacoutot wrote: On Mon, Nov 21, 2011 at 12:51:22PM +0100, Antoine Jacoutot wrote: On Mon, Nov 21, 2011 at 03:31:12AM -0800, Justin Lindberg wrote: OpenBSD 5.0 amd64 -- probably all a

Re: glib2: libgthread-2.0 linked without pthread support

2011-11-21 Thread Justin Lindberg
On 11/21/11 17:37, Justin Lindberg wrote: On 11/21/11 04:46, Antoine Jacoutot wrote: On Mon, Nov 21, 2011 at 12:51:22PM +0100, Antoine Jacoutot wrote: On Mon, Nov 21, 2011 at 03:31:12AM -0800, Justin Lindberg wrote: OpenBSD 5.0 amd64 -- probably all arches Still not fixed in current. I tried

Re: glib2: libgthread-2.0 linked without pthread support

2011-11-21 Thread Justin Lindberg
On 11/21/11 04:46, Antoine Jacoutot wrote: On Mon, Nov 21, 2011 at 12:51:22PM +0100, Antoine Jacoutot wrote: On Mon, Nov 21, 2011 at 03:31:12AM -0800, Justin Lindberg wrote: OpenBSD 5.0 amd64 -- probably all arches Still not fixed in current. I tried to run R, and libgthread-2.0 segfaulted bec

Re: glib2: libgthread-2.0 linked without pthread support

2011-11-21 Thread Antoine Jacoutot
On Mon, Nov 21, 2011 at 12:51:22PM +0100, Antoine Jacoutot wrote: > On Mon, Nov 21, 2011 at 03:31:12AM -0800, Justin Lindberg wrote: > > OpenBSD 5.0 amd64 -- probably all arches > > Still not fixed in current. > > > > I tried to run R, and libgthread-2.0 segfaulted > > because apparently it was no

Re: glib2: libgthread-2.0 linked without pthread support

2011-11-21 Thread Antoine Jacoutot
On Mon, Nov 21, 2011 at 03:31:12AM -0800, Justin Lindberg wrote: > OpenBSD 5.0 amd64 -- probably all arches > Still not fixed in current. > > I tried to run R, and libgthread-2.0 segfaulted > because apparently it was not linked with pthread. > > I confirmed this, because relinking the shared > l