Re: naming convention for object files.

2012-10-12 Thread Nicolas Bock
Hi Miles, thanks for the explanation. I had never hear of the SHORTNAME attribute before, this is good to know. nick On Thu, Oct 11, 2012 at 9:20 PM, Miles Bader wrote: > Nicolas Bock writes: >> libsomething_la_CPPFLAGS = -I../../ > ... >> the naming changed from a.F90

Re: naming convention for object files.

2012-10-11 Thread Nicolas Bock
trange. nick On Thu, Oct 11, 2012 at 11:51 AM, Nicolas Bock wrote: > Hello list, > > I am using libtool to compile a library of a bunch of F90 files. Those > files have various dependencies between them and since automake is not > capable of tracking those for Fortran I have to b

naming convention for object files.

2012-10-11 Thread Nicolas Bock
Hello list, I am using libtool to compile a library of a bunch of F90 files. Those files have various dependencies between them and since automake is not capable of tracking those for Fortran I have to by hand add lines like a.lo : b.lo c.lo to Makefile.am. Unfortunately automake's naming conven

exclude generated sources from dist

2011-04-20 Thread Nicolas Bock
Hello list, I can't figure out how to exclude some source files I generate with a script in the dist. The problem it seems is that I list the generated sources in the _SOURCES variable and the dist target automatically includes them. But I need to rebuild the sources at compile time of the packag

Re: build the same source twice with different macros

2010-11-15 Thread Nicolas Bock
Thanks all for the suggestions. I will give it a try... nick On Mon, Nov 15, 2010 at 14:08, Ralf Wildenhues wrote: > Hi Nicolas, > > * Nicolas Bock wrote on Mon, Nov 15, 2010 at 05:11:26PM CET: >> (1) I can use C++ and rewrite the function header as a template. >> (2) I c

build the same source twice with different macros

2010-11-15 Thread Nicolas Bock
Hello list, I have some functions written in C that take a floating point argument, e.g. void foos (float x); void food (double x); The function bodies are basically identical except of course for the different floating point types. In order to avoid having to write redundant code, I see 2 optio

Re: config.guess and config.sub don't work properly when specifying CC

2010-01-14 Thread Nicolas Bock
Thanks On Thu, Jan 14, 2010 at 16:24, Ralf Wildenhues wrote: > Hello Nicolas, > > * Nicolas Bock wrote on Thu, Jan 14, 2010 at 11:42:47PM CET: > > > * Nicolas Bock wrote on Wed, Jan 13, 2010 at 08:41:35PM CET: > > > > on Ubuntu 8.04 I find that if I specif

Re: config.guess and config.sub don't work properly when specifying CC

2010-01-14 Thread Nicolas Bock
las, > > * Nicolas Bock wrote on Wed, Jan 13, 2010 at 08:41:35PM CET: > > on Ubuntu 8.04 I find that if I specify CC when I run configure, the > > configure script dies when it runs config.sub. I get this output > > > > $ CC=/usr/local/gcc-4.3.0/bin/gcc ./config.guess > > x86_6

Re: config.guess and config.sub don't work properly when specifying CC

2010-01-13 Thread Nicolas Bock
Thanks, I forwarded my original question. nick On Wed, Jan 13, 2010 at 13:06, Ralf Wildenhues wrote: > Hello Nicolas, > > * Nicolas Bock wrote on Wed, Jan 13, 2010 at 08:41:35PM CET: > > on Ubuntu 8.04 I find that if I specify CC when I run configure, the > > configure scr

config.guess and config.sub don't work properly when specifying CC

2010-01-13 Thread Nicolas Bock
Hello list, on Ubuntu 8.04 I find that if I specify CC when I run configure, the configure script dies when it runs config.sub. I get this output $ CC=/usr/local/gcc-4.3.0/bin/gcc ./config.guess x86_64-unknown-linux- but when I run with the system compiler (gcc 4.2.4): $ ./config.guess x86_64-u

Re: subdirs that should not be configured

2009-07-09 Thread Nicolas Bock
Hi John, thanks for the advice. I thought there might be a mechanism built into automake and autoconf to express this paradigm, but the command line option solution is great! Thanks, nick On Thu, 2009-07-09 at 11:39 -0600, John Calcote wrote: > Hi Nicolas, > > On 7/9/2009 11:13 AM

subdirs that should not be configured

2009-07-09 Thread Nicolas Bock
Hello list, I have the following problem: I want to add an external package to our own package. The external package is already configured in the sense that its maintainer ran "make dist" and I simply untared the tar file into some directory underneath our source tree. I add that directory to AC_C

Re: source code type detection

2008-01-23 Thread Nicolas Bock
Thanks for the help On Wed, 2008-01-23 at 22:50 +, Harlan Stenn wrote: > Nick, > > > I wrote a Makefile.am which includes a source file called b.C, which is > > a C-source and not a C++-source. In configure.ac I have AC_PROG_CC. When > > I run automake I get the error message: > > > > Makef

source code type detection

2008-01-23 Thread Nicolas Bock
Hello list, I wrote a Makefile.am which includes a source file called b.C, which is a C-source and not a C++-source. In configure.ac I have AC_PROG_CC. When I run automake I get the error message: Makefile.am: C++ source seen but `CXX' is undefined Makefile.am: The usual way to define `CXX' is