Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 Feb 2006 16:34:54 -0800
From:      Steve Kargl <sgk@troutmask.apl.washington.edu>
To:        Alexander Kabaev <kabaev@gmail.com>
Cc:        freebsd-current@freebsd.org, Dan Nelson <dnelson@allantgroup.com>
Subject:   Re: [jakub@redhat.com:Linking against libpthread via -pthread?
Message-ID:  <20060211003454.GA96721@troutmask.apl.washington.edu>
In-Reply-To: <20060210191637.374daa37@kan.dnsalias.net>
References:  <20060210181715.GA21782@troutmask.apl.washington.edu> <20060210193907.GE2090@dan.emsphone.com> <20060210194503.GA10370@troutmask.apl.washington.edu> <20060210195204.GF2090@dan.emsphone.com> <20060210191637.374daa37@kan.dnsalias.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Feb 10, 2006 at 07:16:37PM -0500, Alexander Kabaev wrote:
> > > > In the last episode (Feb 10), Steve Kargl said:
> > > > > Some background information:  I routinely build GCC mainline on
> > > > > i386-*-freebsd and amd64-*-freebsd.  GCC mainline is introducing
> > > > > OpenMP support.  When libgomp.so.1 is built, the compiler is
> > > > > given the -pthread option throughout the construction of
> > > > > libgomp.so.1. However, a "ldd libgomp.so.1" shows no dependence
> > > > > on libpthread.so.2

(context snipped)

> No. The change to link in libc by default and libpthread with -pthread
> are inthe works and will be committed shortly. There is not way around
> this if we want working versioned libc and libpthread in our system.

Thanks for the info.  I'll relay this to the GCC developers
working on libgomp.

-- 
Steve



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060211003454.GA96721>