Is libtool portable across platforms?

2001-10-18 Thread Pier Fumagalli
I was wondering, if I generate libtool via buildconf on a named machine (let's say, Solaris), is that libtool portable to another platform (let's say Linux) Pier

Re: Is libtool portable across platforms?

2001-10-18 Thread Sascha Schumann
On Thu, 18 Oct 2001, Pier Fumagalli wrote: I was wondering, if I generate libtool via buildconf on a named machine (let's say, Solaris), is that libtool portable to another platform (let's say Linux) Of course it is. :-) - Sascha Experience

Re: Is libtool portable across platforms?

2001-10-18 Thread Pier Fumagalli
Sascha Schumann at [EMAIL PROTECTED] wrote: On Thu, 18 Oct 2001, Pier Fumagalli wrote: I was wondering, if I generate libtool via buildconf on a named machine (let's say, Solaris), is that libtool portable to another platform (let's say Linux) Of course it is. :-) That's what I

[STATUS] (apr) Wed Oct 17 23:45:11 EDT 2001

2001-10-18 Thread Rodent of Unusual Size
APACHE PORTABLE RUNTIME (APR) LIBRARY STATUS: -*-text-*- Last modified at [$Date: 2001/10/12 21:44:21 $] Release: 2.0a9 : released December 12, 2000 2.0a8 : released November 20, 2000 2.0a7 : released October 8, 2000 2.0a6 : released August 18, 2000

Re: Is libtool portable across platforms?

2001-10-18 Thread Jim Jagielski
It's as portable as libtool itself is... Building on Solaris, for example, doesn't create a Solaris-specific version. Pier Fumagalli wrote: I was wondering, if I generate libtool via buildconf on a named machine (let's say, Solaris), is that libtool portable to another platform (let's say

Re: [PATCH] Re: cvs commit: apr/threadproc/unix proc.c

2001-10-18 Thread Jeff Trawick
Here is yet another patch. When compared with the previous patch, this one adds the native status to the parameter lists of apr_proc_wait() and apr_proc_wait_all_procs(). Fewer MPM changes are necessary. missing: fix the doc in apr_thread_proc.h roll the changes into

Re: [PATCH] Re: cvs commit: apr/threadproc/unix proc.c

2001-10-18 Thread Greg Ames
Jeff Trawick wrote: I'm happy with the APR-ized notion of how-did-the-process-exit and what-is-the-signal-or-exit-code but throwing away the native status is a real problem. [...] missing from patch: doc in header files, other mpms, apr/threadproc/foo, where foo != unix, testing

Re: [PATCH] Re: cvs commit: apr/threadproc/unix proc.c

2001-10-18 Thread Justin Erenkrantz
On Thu, Oct 18, 2001 at 01:44:08PM -0400, Jeff Trawick wrote: Here is yet another patch. When compared with the previous patch, this one adds the native status to the parameter lists of apr_proc_wait() and apr_proc_wait_all_procs(). Fewer MPM changes are necessary. missing: fix the doc in

Re: [PATCH] Re: cvs commit: apr/threadproc/unix proc.c

2001-10-18 Thread Ryan Bloom
On Thursday 18 October 2001 10:44 am, Jeff Trawick wrote: Here is yet another patch. When compared with the previous patch, this one adds the native status to the parameter lists of apr_proc_wait() and apr_proc_wait_all_procs(). Fewer MPM changes are necessary. missing: fix the doc in

Re: [PATCH] Re: cvs commit: apr/threadproc/unix proc.c

2001-10-18 Thread Jeff Trawick
Justin Erenkrantz [EMAIL PROTECTED] writes: I think WIFSTOPPED needs to be checked (do all platforms have this? Linux does). But, I'm not sure that should return APR_CHILD_DONE or NOTDONE - since the process may resume later on. This gets hairy. Also, is returning APR_EGENERAL the right

Re: [PATCH] Re: cvs commit: apr/threadproc/unix proc.c

2001-10-18 Thread Jeff Trawick
Ryan Bloom [EMAIL PROTECTED] writes: I am missing something here. This patch requires us to use the non-portable W* macros in Apache. That is wrong. This patch does not force an APR app to use any W* macros other than WCOREDUMP(), and most apps don't care about that.

Re: [PATCH] Re: cvs commit: apr/threadproc/unix proc.c

2001-10-18 Thread Ryan Bloom
On Thursday 18 October 2001 12:15 pm, Jeff Trawick wrote: Ryan Bloom [EMAIL PROTECTED] writes: I am missing something here. This patch requires us to use the non-portable W* macros in Apache. That is wrong. This patch does not force an APR app to use any W* macros other than WCOREDUMP(),