On Monday 25 of June 2007, Ralf S. Engelschall wrote:
> RPM Package Manager, CVS Repository
> http://rpm5.org/cvs/
>
> ___
>_
>
> Server: rpm5.org Name: Ralf S. Engelschall
> Root: /v/rpm/c
On Monday 25 of June 2007, Andy Green wrote:
> Arkadiusz Miskiewicz wrote:
> >> Log:
> >> allow one to control/override the /usr/lib64 use via Autoconf option
> >> --enable-build-lib64
> >
> > Usually this is done by ./configure --libdir=/usr/lib64.
>
> Possibly I misunderstand, but is th
Arkadiusz Miskiewicz wrote:
>> Log:
>> allow one to control/override the /usr/lib64 use via Autoconf option
>> --enable-build-lib64
>
> Usually this is done by ./configure --libdir=/usr/lib64.
Possibly I misunderstand, but is that true? I believe --libdir just
sets where make install
On Mon, Jun 25, 2007, Arkadiusz Miskiewicz wrote:
> On Monday 25 of June 2007, Andy Green wrote:
> > Arkadiusz Miskiewicz wrote:
> > >> Log:
> > >> allow one to control/override the /usr/lib64 use via Autoconf option
> > >> --enable-build-lib64
> > >
> > > Usually this is done by ./confi
In my environments, I setup the compiler and CFLAGS before calling
configure w/ the right information to build 32, or 64 bit binaries.
Having configure try to guess and pass in additional values is a royal
pain. Passing in --libdir=/usr/lib64 (or equiv) is really the right
answer. There shouldn't
On Mon, Jun 25, 2007, Mark Hatle wrote:
> In my environments, I setup the compiler and CFLAGS before calling
> configure w/ the right information to build 32, or 64 bit binaries.
> Having configure try to guess and pass in additional values is a royal
> pain. Passing in --libdir=/usr/lib64 (or eq
