Re: lib vs. lib64 on bi-arch systems

Ralf Wildenhues wrote: > For that, you can > ./configure --libdir='${exec_prefix}/lib64' Sam and I are arguing that this should be the default. Let's move the discussion to the autoconf list: Bruno

Re: lib vs. lib64 on bi-arch systems

Hello, * Sam Steingold wrote on Tue, Sep 09, 2008 at 11:20:25PM CEST: > > so this boils down to a bug in libsigsegv (coming from autconf): > make install should install it in lib64, not lib, right? For that, you can ./configure --libdir='${exec_prefix}/lib64' (but I may just be misunderstandin

Re: lib vs. lib64 on bi-arch systems

Hi, Bruno Haible wrote: Sam Steingold wrote: I get the following output from ./configure --with-libsigsegv-prefix=/home/sds/src/top CC='gcc -m64' build-O --with-module=rawsock on Linux ada 2.6.24-1-sparc64-smp: INCSIGSEGV= gl_save_CPPFLAGS= CPPFLAGS= checking for libsigsegv... (cached) no

Re: lib vs. lib64 on bi-arch systems (was: libsigsegv.m4: --with-libsigsegv-prefix is ignored)

Hi, Sam Steingold wrote: > I get the following output from > > ./configure --with-libsigsegv-prefix=/home/sds/src/top CC='gcc -m64' build-O > --with-module=rawsock > > on Linux ada 2.6.24-1-sparc64-smp: > > > INCSIGSEGV= > gl_save_CPPFLAGS= > CPPFLAGS= > checking for libsigsegv... (cached) n