On Wed, 24 Jan 2001, Maxim Sobolev wrote:
>
> It's not a very accurate estimate, as the magic can be in the distfile
> itself, i.e. properly written configure script or makefile may know
> that FreeBSD need a -pthread and -D_THREAD_SAFE.
>
For some unknown reason, math.h needs _REENTRANT in Fr
On Wed, 24 Jan 2001, Garrett Rooney wrote:
> On Wed, Jan 24, 2001 at 07:07:20PM -0400, Craig Hawco wrote:
> >
> >
> > On Wed, 24 Jan 2001, Daniel Eischen wrote:
> >
> > >
> > > Using -pthread will prevent linking to libc and only link to
> > > libc_r. After the change I just committed, you nee
On Wed, Jan 24, 2001 at 07:07:20PM -0400, Craig Hawco wrote:
>
>
> On Wed, 24 Jan 2001, Daniel Eischen wrote:
>
> >
> > Using -pthread will prevent linking to libc and only link to
> > libc_r. After the change I just committed, you need to link
> > to both libc_r and libc (in that order), just
On Wed, 24 Jan 2001, Daniel Eischen wrote:
>
> Using -pthread will prevent linking to libc and only link to
> libc_r. After the change I just committed, you need to link
> to both libc_r and libc (in that order), just like you would
> for a threaded application on just about any other OS (only
In message <[EMAIL PROTECTED]> Alfred Perlstein writes:
: -D_THREAD_SAFE used to (or still does) make various foo_r function
: prototypes available.
Currently it does not do this. The foo_r prototypes are always
available. Well, when we aren't compiling _ANSI_SOURCE or
_POSIX_SOURCE. Dan was r
Dan Nelson wrote:
> In the last episode (Jan 24), Maxim Sobolev said:
> > Dan Nelson wrote:
> > > I thought the old way was just -pthread, and it would handle
> > > everything. I did a quick scan of the devel/ and net/ branches of our
> > > ports tree, and of 43 thread-using ports, 36 of the por
In the last episode (Jan 24), Maxim Sobolev said:
> Dan Nelson wrote:
> > I thought the old way was just -pthread, and it would handle
> > everything. I did a quick scan of the devel/ and net/ branches of our
> > ports tree, and of 43 thread-using ports, 36 of the ports simply add
> > -pthread.
On Wed, 24 Jan 2001, Dan Nelson wrote:
> In the last episode (Jan 24), Daniel Eischen said:
> > On Wed, 24 Jan 2001, Alfred Perlstein wrote:
> > > * Daniel M. Eischen <[EMAIL PROTECTED]> [010124 05:26] wrote:
> > > > As discussed a few days ago, I've just committed the changes to libc
> > > > and
Dan Nelson wrote:
> In the last episode (Jan 24), Daniel Eischen said:
> > On Wed, 24 Jan 2001, Alfred Perlstein wrote:
> > > * Daniel M. Eischen <[EMAIL PROTECTED]> [010124 05:26] wrote:
> > > > As discussed a few days ago, I've just committed the changes to libc
> > > > and libc_r to allow them
* Dan Nelson <[EMAIL PROTECTED]> [010124 10:32] wrote:
> In the last episode (Jan 24), Daniel Eischen said:
> > On Wed, 24 Jan 2001, Alfred Perlstein wrote:
> > > * Daniel M. Eischen <[EMAIL PROTECTED]> [010124 05:26] wrote:
> > > > As discussed a few days ago, I've just committed the changes to l
In the last episode (Jan 24), Daniel Eischen said:
> On Wed, 24 Jan 2001, Alfred Perlstein wrote:
> > * Daniel M. Eischen <[EMAIL PROTECTED]> [010124 05:26] wrote:
> > > As discussed a few days ago, I've just committed the changes to libc
> > > and libc_r to allow them to be linked together via -l
On Wed, 24 Jan 2001, Jordan Hubbard wrote:
> > What's not clear ;-) Use -lc_r instead of -pthread.
> >
> > gcc -Wall -o foo foo.c -lc_r
> >
> > The old way was:
> >
> > gcc -Wall -D_THREAD_SAFE -o foo foo.c -pthread
>
> H. And does the -pthread argument do anything anymore? If n
> What's not clear ;-) Use -lc_r instead of -pthread.
>
> gcc -Wall -o foo foo.c -lc_r
>
> The old way was:
>
> gcc -Wall -D_THREAD_SAFE -o foo foo.c -pthread
H. And does the -pthread argument do anything anymore? If not,
why not have it default to simply linking in libc_r f
On Wed, 24 Jan 2001, Alfred Perlstein wrote:
> * Daniel M. Eischen <[EMAIL PROTECTED]> [010124 05:26] wrote:
> > As discussed a few days ago, I've just committed the changes to libc
> > and libc_r to allow them to be linked together via -lc_r. If you're
> > running -current and have any threaded
* Daniel M. Eischen <[EMAIL PROTECTED]> [010124 05:26] wrote:
> As discussed a few days ago, I've just committed the changes to libc
> and libc_r to allow them to be linked together via -lc_r. If you're
> running -current and have any threaded apps built using libc_r.so.5,
> you'll need to rebuil
Daniel Eischen wrote:
> On Wed, 24 Jan 2001, Maxim Sobolev wrote:
> > "Daniel M. Eischen" wrote:
> >
> > > As discussed a few days ago, I've just committed the changes to libc
> > > and libc_r to allow them to be linked together via -lc_r. If you're
> > > running -current and have any threaded a
On Wed, 24 Jan 2001, Maxim Sobolev wrote:
> "Daniel M. Eischen" wrote:
>
> > As discussed a few days ago, I've just committed the changes to libc
> > and libc_r to allow them to be linked together via -lc_r. If you're
> > running -current and have any threaded apps built using libc_r.so.5,
> > y
On Wed, Jan 24, 2001 at 03:37:24PM +0200, Maxim Sobolev wrote:
> "Daniel M. Eischen" wrote:
>
> > For porters, the __FreeBSD_version has been bumped to 500016 to
> > reflect the above change.
>
> Could you please bump version number of libc/libc_r shared libraries, so the
> programs linked with o
"Daniel M. Eischen" wrote:
> As discussed a few days ago, I've just committed the changes to libc
> and libc_r to allow them to be linked together via -lc_r. If you're
> running -current and have any threaded apps built using libc_r.so.5,
> you'll need to rebuild them without the -pthread option
19 matches
Mail list logo
