On Thu, Sep 18, 2014 at 12:24:12PM +0200, Gustaf Neumann wrote:
> Am 17.09.14 23:19, schrieb Andrew Piskorski:
> > The Naviserver makefiles often definite a LIB variable, e.g.:
> >
> >LIB = nsthread
> What is the exact problem you see: is it the case, when LIB is set
> in a Makefile (as cited),
Am 18.09.14 18:33, schrieb Maurizio Martignano:
> I still do not quite understand/explain why the nsthread module is so
> different between Aolserver and Naviserver. And again as the two pieces of
> software are implemented at the moment, the Aolserver version seems to be
> more portable.
not sure,
Dear Gustav,
This is ok.
I still do not quite understand/explain why the nsthread module is so
different between Aolserver and Naviserver. And again as the two pieces of
software are implemented at the moment, the Aolserver version seems to be
more portable.
Thank you,
Maurizio
-Orig
Am 18.09.14 00:50, schrieb Andrew Piskorski:
> AFAICT from reading that code, when using Microsoft's compiler
> NSTHREAD_EXPORTS is never set, and thus NS_STORAGE_CLASS is never set
> to NS_EXPORT, it is always set to NS_IMPORT and thus is wrong when
> building nsthread.
i think the intention was t
historically, unix used "int" for pids. the open group / ieee
standard defines pid_t [1], which is used e.g. for fork(), getpid(),
kill() etc.
on linux, mac os x etc. Therefore, the use of pid_t instead of "int"
is a good thing, especially, since pids are passed around as
arguments and returned
Am 17.09.14 23:19, schrieb Andrew Piskorski:
> The Naviserver makefiles often definite a LIB variable, e.g.:
>
>LIB = nsthread
What is the exact problem you see: is it the case, when LIB is set
in a Makefile (as cited), or is the problem, when it is *not* set.
In the latter case, "make" picks
