Re: Want "make check" to test shared, static lib

Torbjörn, On 11/13/2013 06:45 PM, Torbjorn Granlund wrote: We in the GMP project would like to have "make check" run through our testsuite for both the static and shared libs (when both are built). We haven't been able to achive this. Please help. assuming that you are using libtool, just co

Re: how to change $(CC) for just some targets

Hi Brian, Am 6/3/2010 11:50 AM, schrieb Brian J. Murrell: > On Thu, 2010-06-03 at 11:42 -0700, Christian Rössel wrote: >> Hi Brian, > > Hey Christian, > > Thanx for taking the time. > >> I use a separate Makefile for MPI targets. > > This is what I did la

Re: how to change $(CC) for just some targets

Hi Brian, Am 6/3/2010 11:10 AM, schrieb Brian J. Murrell: > I have a Makefile.am with a number of targets in it. Some of those > targets need $(CC) and/or $(LD) to be reassigned to a particular value > while others are fine with the default (or could be explicitly assigned > gcc if need be). > >

Passing modified options to nested configure

Consider following cross-compile scenario where I want to build programs and libraries for the host (backend) as well as for the build (frontend). There are programs/libraries that should be build for the frontend only, for the backend only and for the frontend as well as for the backend. I issue f

Passing modified options to nested configure

Consider following cross-compile scenario where I want to build programs and libraries for the host (backend) as well as for the build (frontend). There are programs/libraries that should be build for the frontend only, for the backend only and for the frontend as well as for the backend. I issue f

What differs in cross-compiling mode?

configure switches to cross-compiling mode if I call it with build != host like in ./configure --build=powerpc64-unknown-linux-gnu --host=powerpc-bgp-linux-gnu CC=bgxlc Can someone explain to me what implications that has for configure checks and the build in general? I can see that configure say

Re: suggestions about AC_CONFIG_MACRO_DIR

Lorenzo Bettini wrote: > Braden McDaniel wrote: >> On 4/21/09 1:35 PM, Lorenzo Bettini wrote: >>> Hi >>> >>> I started adding some m4 macros to my program, that I put in the m4 >>> directory in my sources, and that will be installed during the make >>> install. >>> >>> I then added >>> >>> aclocald

make dist: sources missing

Hi, in the following project "make" succeeds but in the result of "make dist" the source test/src/bar.c is missing. "make distcheck" fails. Assume following directory layout: test/ test/cfg/ test/cfg/Makefile.am test/cfg/configure.ac test/cfg/src/ test/cfg/src/foo.c test/src/ test/src/bar.c I'm

Re: seperate CFLAGS/LFLAFS

Philip Herron wrote: > Hey > > I was just wondering say you have a Makefile.am like this: > > bin_PROGRAMS= myprog > AM_YFLAGS= -d > AM_LFLAGS= > > mprog_CFLAGS= -I$(top_srcdir)/include > myprog_SOURCES= foo1.c foo2.c bla.l bla_gram.y bla2.l bla bla bla > > Can you specify seperate FLAG lik

Re: cross compile: distinct object files, how?

Ralf Wildenhues wrote: > Hello Christian, > > * Christian Rössel wrote on Tue, Apr 14, 2009 at 03:20:35PM CEST: >> I have a cross-compile situation where I want to compile sources of a >> subdirectory for the host system as well as for the build system. I pass >> --hos

cross compile: distinct object files, how?

Hi, I have a cross-compile situation where I want to compile sources of a subdirectory for the host system as well as for the build system. I pass --host, --build and CC_FOR_BUILD to configure. Then I have two Makefile.am in distinct subdirectories, one has the statement CC=$(CC_FOR_BUILD), the ot