Jim Jagielski [EMAIL PROTECTED] writes:
If SysV is broken, we should prevent that from being used with
AcceptMutex as well (until we can figure out *why* it's broken)
FYI...
SysV isn't broken
daedalus was/is configured for only 10 semaphore sets; 2 are owned by
user id jim, 8 are owned by
Jeff Trawick [EMAIL PROTECTED] wrote:
Jim Jagielski [EMAIL PROTECTED] writes:
If SysV is broken, we should prevent that from being used with
AcceptMutex as well (until we can figure out *why* it's broken)
FYI...
SysV isn't broken
daedalus was/is configured for only 10 semaphore
Remy Maucherat [EMAIL PROTECTED] wrote:
Jeff Trawick [EMAIL PROTECTED] wrote:
Jim Jagielski [EMAIL PROTECTED] writes:
If SysV is broken, we should prevent that from being used with
AcceptMutex as well (until we can figure out *why* it's broken)
FYI...
SysV isn't broken
daedalus
If SysV is broken, we should prevent that from being used with
AcceptMutex as well (until we can figure out *why* it's broken)
[EMAIL PROTECTED] wrote:
gregames02/04/01 13:50:45
Modified:.STATUS
buildapr_hints.m4
Log:
FreeBSD: switch to FLOCK
Justin Erenkrantz [EMAIL PROTECTED] writes:
On Wed, Dec 12, 2001 at 06:36:58PM -0500, Jeff Trawick wrote:
I don't think so... what this does is add -liconv -lpthread (or
whatever) to the link of libapr.la
the other day we had something different which really was supposed to
get
On Wed, Dec 12, 2001 at 07:35:06PM -, [EMAIL PROTECTED] wrote:
trawick 01/12/12 11:35:06
Modified:.Makefile.in configure.in
buildapr_hints.m4
Log:
switch Apache/apr/apr-util to use run-time linking on AIX
Revision ChangesPath
1.67
Justin Erenkrantz [EMAIL PROTECTED] writes:
On Wed, Dec 12, 2001 at 07:35:06PM -, [EMAIL PROTECTED] wrote:
trawick 01/12/12 11:35:06
Log:
switch Apache/apr/apr-util to use run-time linking on AIX
@for i in $(SUBDIRS); do objects=$$objects $$i/[EMAIL PROTECTED]@;
On Wed, Dec 12, 2001 at 06:36:58PM -0500, Jeff Trawick wrote:
I don't think so... what this does is add -liconv -lpthread (or
whatever) to the link of libapr.la
the other day we had something different which really was supposed to
get libtool to do something
Nope. It just added EXTRA_LIBS
On Sat, Sep 22, 2001 at 08:23:21PM -, [EMAIL PROTECTED] wrote:
gstein 01/09/22 13:23:21
Modified:.configure.in
buildapr_hints.m4
Log:
AC_PROG_CC can only be used once within a configure script (at least with
autoconf 2.52). Shift the
Greg Stein [EMAIL PROTECTED] writes:
On Fri, Jun 01, 2001 at 07:55:52PM -0400, Jeff Trawick wrote:
Greg Stein [EMAIL PROTECTED] writes:
No. apr_hints is a last resort. Actual tests like the AC_TRY_COMPILE()
that
Justin did are the right way to do it. We should always try to avoid
No. apr_hints is a last resort. Actual tests like the AC_TRY_COMPILE() that
Justin did are the right way to do it. We should always try to avoid
hard-coding conditions to the host/library/whatever and *test* for them
instead.
Since the thread tests are the first real tests performed by APR's
Greg Stein [EMAIL PROTECTED] writes:
No. apr_hints is a last resort. Actual tests like the AC_TRY_COMPILE() that
Justin did are the right way to do it. We should always try to avoid
hard-coding conditions to the host/library/whatever and *test* for them
instead.
autoconf was written to use
Justin Erenkrantz [EMAIL PROTECTED] writes:
No. apr_hints is a last resort. Actual tests like the AC_TRY_COMPILE() that
Justin did are the right way to do it. We should always try to avoid
hard-coding conditions to the host/library/whatever and *test* for them
instead.
Since the thread
On Fri, Jun 01, 2001 at 08:01:06PM -0400, Jeff Trawick wrote:
Justin Erenkrantz [EMAIL PROTECTED] writes:
No. apr_hints is a last resort. Actual tests like the AC_TRY_COMPILE()
that
Justin did are the right way to do it. We should always try to avoid
hard-coding conditions to the
On Fri, Jun 01, 2001 at 07:55:52PM -0400, Jeff Trawick wrote:
Greg Stein [EMAIL PROTECTED] writes:
No. apr_hints is a last resort. Actual tests like the AC_TRY_COMPILE() that
Justin did are the right way to do it. We should always try to avoid
hard-coding conditions to the
On Fri, Jun 01, 2001 at 12:35:50AM -, [EMAIL PROTECTED] wrote:
orlikowski01/05/31 17:35:49
Modified:buildapr_hints.m4
Log:
Linux needs these options for the posix rwlocks to work.
Normally, _SVID_SOURCE and _BSD_SOURCE are defined by default.
However, we must
These have to do with glibc version, not kernel version... Maybe it
will work fine, but it doesn't help anybody to understand why it is
there.
Agreed. However, my logic was that these flags would only be useful in
kernel versions that supported threading, which implies 2.0 and later.
Of
On Fri, Jun 01, 2001 at 11:10:43AM -0400, Victor J. Orlikowski wrote:
These have to do with glibc version, not kernel version... Maybe it
will work fine, but it doesn't help anybody to understand why it is
there.
Agreed. However, my logic was that these flags would only be useful in
Justin Erenkrantz [EMAIL PROTECTED] writes:
On Fri, Jun 01, 2001 at 12:35:50AM -, [EMAIL PROTECTED] wrote:
orlikowski01/05/31 17:35:49
Modified:buildapr_hints.m4
Log:
Linux needs these options for the posix rwlocks to work.
Normally, _SVID_SOURCE and
19 matches
Mail list logo
