Re: FreeBSD Problems

[Ari Johnson]

I'd say that the native thread library is the way to go.  FreeBSD
implements pthreads quite nicely, and I've had excellent luck using them
with CommonC++.  The problems come in with things like friends.cpp failing
to compile because nanosleep() isn't declared (putting an extern "C"
declaration for it right where it's used in a macro in cc++/config.h works
for me), and the fact that I absolutely cannot compile the library with
GCC 3.x, due to some kind of screwy include file monkey business; although
I can compile anything else with GCC 3.x just fine.
 -- Ari Johnson

On Fri, 1 Nov 2002, David Sugar wrote:

>
> I would like to see us have a clean and consistent build under FreeBSD.
> Currently, there are two choices possible with it; one to build against
> LinuxThreads, and one to do so with the native runtime thread library.
> Which do you think would be better for FreeBSD?
>
> David
>
> On Fri, 1 Nov 2002, Ari Johnson wrote:
>
> >
> > I think I'm going to just sit down and try to figure out what's wrong with
> > CommonC++ (from cvs) on FreeBSD.  I keep figuring out a quick hack around
> > things, but they are things that should be fixed.  So here's #1:
> >
> > friends.cpp: In function `static void ost::Thread::sleep(long unsigned 
> > int)':
> > friends.cpp:134: implicit declaration of function `int ost::nanosleep(...)'
> >
> > Anyone with insight as to why this is occurring?
> >  -- Ari Johnson
> >
> >
> >
> > _______________________________________________
> > Bug-commoncpp mailing list
> > address@hidden
> > http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> >
>