Re: Getting -m64 at the right time and place.

2008-11-16 Thread Charles Plessy
Le Sat, Nov 15, 2008 at 12:51:48PM -0800, Russ Allbery a écrit : > Charles Plessy <[EMAIL PROTECTED]> writes: > > > Would the following patch make sense? > > > > diff --git a/configure.ac b/configure.ac > > index ad2f1e6..4f2993a 100644 > > --- a/configure.ac > > +++ b/configure.ac > > @@ -23,10 +

Re: Getting -m64 at the right time and place.

2008-11-15 Thread Russ Allbery
Charles Plessy <[EMAIL PROTECTED]> writes: > Would the following patch make sense? > > diff --git a/configure.ac b/configure.ac > index ad2f1e6..4f2993a 100644 > --- a/configure.ac > +++ b/configure.ac > @@ -23,10 +23,7 @@ case "${host_cpu}-${host_os}" in > AC_COMPILE_IFELSE([AC_L

Re: Getting -m64 at the right time and place.

2008-11-15 Thread Aaron M. Ucko
Charles Plessy <[EMAIL PROTECTED]> writes: > Maq is likely to have to access files bigger than 2Gb sometimes, so > I probably should not remove -D_FILE_OFFSET_BITS=64. Indeed. > Would the following patch make sense? Yes, looks reasonable to me. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, u

Re: Getting -m64 at the right time and place.

2008-11-15 Thread Charles Plessy
Le Sat, Nov 15, 2008 at 08:37:49AM +0100, Mike Hommey a écrit : > On Sat, Nov 15, 2008 at 12:37:55PM +0900, Charles Plessy wrote: > > However, as I do not understand the purpose of -D_FILE_OFFSET_BITS=64, I am > > worried it would be breaking maq on 32-bit arches to remove it. > > It will only bre

Re: Getting -m64 at the right time and place.

2008-11-14 Thread Paul Wise
On Sat, Nov 15, 2008 at 12:37 PM, Charles Plessy <[EMAIL PROTECTED]> wrote: > I am working on a package that, when unmodified, fails on 32bits arches > because > -m64 is in the CFLAGS. We solved the problem by patching the configure file, > but of course this breaks when new upstream releases ref

Re: Getting -m64 at the right time and place.

2008-11-14 Thread Mike Hommey
On Sat, Nov 15, 2008 at 12:37:55PM +0900, Charles Plessy wrote: > However, as I do not understand the purpose of -D_FILE_OFFSET_BITS=64, I am > worried it would be breaking maq on 32-bit arches to remove it. It will only break its ability to read large files (> 2GB). That is what _FILE_OFFSET_BITS

Getting -m64 at the right time and place.

2008-11-14 Thread Charles Plessy
Dear mentors, I am working on a package that, when unmodified, fails on 32bits arches because -m64 is in the CFLAGS. We solved the problem by patching the configure file, but of course this breaks when new upstream releases refresh it with newer versions of autoconf. I am now exploring the possib