Joe Orton wrote:
On Tue, Mar 30, 2004 at 03:51:34PM +0100, Joe Orton wrote:
On Tue, Mar 30, 2004 at 09:25:30AM -0500, Jeff Trawick wrote:
here's a more concrete example
apr HEAD
RHEL 3.0 for PPC
libtool 1.4.3 from system install
CFLAGS="-Xcompiler -m64" LDFLAGS="-Xcompiler -m64 -Xlinker -melf64ppc"
Joe Orton wrote:
On Tue, Mar 30, 2004 at 09:25:30AM -0500, Jeff Trawick wrote:
here's a more concrete example
apr HEAD
RHEL 3.0 for PPC
libtool 1.4.3 from system install
CFLAGS="-Xcompiler -m64" LDFLAGS="-Xcompiler -m64 -Xlinker -melf64ppc" \
./configure
Isn't that equivalent to the simpler CC="g
On Tue, Mar 30, 2004 at 03:51:34PM +0100, Joe Orton wrote:
> On Tue, Mar 30, 2004 at 09:25:30AM -0500, Jeff Trawick wrote:
> > here's a more concrete example
> >
> > apr HEAD
> > RHEL 3.0 for PPC
> > libtool 1.4.3 from system install
> >
> > CFLAGS="-Xcompiler -m64" LDFLAGS="-Xcompiler -m64 -Xlin
On Tue, Mar 30, 2004 at 09:25:30AM -0500, Jeff Trawick wrote:
> here's a more concrete example
>
> apr HEAD
> RHEL 3.0 for PPC
> libtool 1.4.3 from system install
>
> CFLAGS="-Xcompiler -m64" LDFLAGS="-Xcompiler -m64 -Xlinker -melf64ppc" \
> ./configure
Isn't that equivalent to the simpler CC="
here's a more concrete example
apr HEAD
RHEL 3.0 for PPC
libtool 1.4.3 from system install
CFLAGS="-Xcompiler -m64" LDFLAGS="-Xcompiler -m64 -Xlinker -melf64ppc" \
./configure
it builds, test programs work, but apr-config just has -pthread for CFLAGS and
nothing for LDFLAGS
but in build/apr_rul
Joe Orton wrote:
On Tue, Mar 30, 2004 at 07:05:22AM -0500, Jeff Trawick wrote:
[EMAIL PROTECTED] wrote:
jorton 2004/03/30 01:58:22
Modified:xlatexlate.c
Log:
* xlate/xlate.c (check_sbcs): Remove function which made unsafe
assumptions (a theoretical issue), and was buggy in not resettin
On Tue, Mar 30, 2004 at 07:05:22AM -0500, Jeff Trawick wrote:
> [EMAIL PROTECTED] wrote:
> >jorton 2004/03/30 01:58:22
> >
> > Modified:xlatexlate.c
> > Log:
> > * xlate/xlate.c (check_sbcs): Remove function which made unsafe
> > assumptions (a theoretical issue), and was buggy in
[EMAIL PROTECTED] wrote:
jorton 2004/03/30 01:58:22
Modified:xlatexlate.c
Log:
* xlate/xlate.c (check_sbcs): Remove function which made unsafe
assumptions (a theoretical issue), and was buggy in not resetting the
iconv handle on failure (the cause of at least one real issue).
(has anybody else seen this?)
On Mon, Mar 29, 2004 at 05:22:20PM -0500, Marc M. Adkins wrote:
> On Monday 29 March 2004 01:16 am, Joe Orton wrote:
> > On Sun, Mar 28, 2004 at 04:57:53PM -0500, Marc M. Adkins wrote:
> > > Is it possible that apr_thread_rwlock_wrlock will allow recursive
> > > behavior on Windows but not on Linux
If the platform resolves to win32 (building subset/win32/*.c) then we
just need to trick it - win 32 has its own hardcode cases.
Bill
At 09:16 PM 3/29/2004, Greg Matheson wrote:
>Has anyone built on MinGW? I want to use Subversion with
>perl so I need the SWIG bindings and this requires building
On Monday 29 March 2004 01:16 am, Joe Orton wrote:
> On Sun, Mar 28, 2004 at 04:57:53PM -0500, Marc M. Adkins wrote:
> > Is it possible that apr_thread_rwlock_wrlock will allow recursive
> > behavior on Windows but not on Linux? By this I mean that a specific
> > thread will request a write lock a
Has anyone built on MinGW? I want to use Subversion with
perl so I need the SWIG bindings and this requires building
Subversion's redistribution of the APR.
This fails for me on Win98 in configure, unable to
to make a decision on shared memory.
checking for mmap... no
checking for munmap... n
13 matches
Mail list logo