Re: turning off dependency tracking when building fat binaries on Mac OSX

Hi Ralf, On 2/13/11 3:32 AM, Ralf Wildenhues wrote: Yep. I think that was one reason we explicitly documented the thing in INSTALL. With this configuration, your preprocessor will be wrong (because CFLAGS are not passed to it) which means macro values may be computed wrongly. I'm not sure I

$(srcdir)/foo is not generated because $(srcdir)/$(srcdir)/foo exists

Hello; I got bitten by how VPATH builds work and wondered if there is a good way to avoid getting bitten again. I have an Automake snippet (see below) that creates a file, `.revision', with current revision number and from this is a C header file `revision.h' created. Then to test that

bug#7988: the manual suggests installing macro files to hard-coded location

Hello, In the manual, http://sources.redhat.com/automake/automake.html#Invoking-aclocal, I read about the `--print-ac-dir' option: Prints the name of the directory that | |aclocal will search to find third-party .m4 files. When this option is given, normal processing is suppressed. This

Re: LDFLAGS for EXTRA_PROGRAMS

On 1/23/11 5:45 PM, Sergio Belkin wrote: Hi, How can I define an LDFLAGS once for all EXTRA_PROGRAMS, they are around 20 and I am a bit lazy :) ? Search for AM_LDFLAGS in the manual. Cheers, Peter

Re: Problem building 32-bit and 64-bit binaries on Mac OS X 10.6.4

[adding automake @; replies can drop libtool @] On 9/13/10 6:31 AM, Elvis Dowson wrote: Elvis Dowson wrote: I'm unable to build libtool as binary that includes both 32-bit and 64-bit intel architecture on Mac OS X 10.6.4 using gcc-4.0.1, and get the following error: gcc-4.0: -E, -S,

Re: Using bash scripts as tests for 'make check'

Hi Sam, On 7/3/10 6:52 PM, Sam Silla wrote: TEST: simple_test Looks like a typo; should it be TESTS = simple_test? cheers, Peter

Re: [Bug-gsl] autogen.sh overwrites file INSTALL

On 6/20/10 11:59 AM, Bob Friesenhahn wrote: My best guess is to add 'foreign' to AUTOMAKE_OPTIONS. Not an option for a GNU package, I suppose. Peter

Re: performing pre-build shell commands with automake

On 6/20/10 2:56 PM, Wesley Smith wrote: I've been looking through the automake docs trying to figure out how to execute shell commands as part of the build process but before anything actually gets compiled. Is this possible? I need this for things like Qt's 'moc' and some other script-based

Re: Header install path

Hi Patrick, On 5/22/10 3:09 PM, Patrick Rutkowski wrote: If I do include_HEADERS = foo.h, then foo.h goes into, let's say, /usr/local/include/foo.h But can I instead make it go into /usr/local/include/some/arbitrary/path/foo.h? I do: include_foodir = $(includedir)/foo

Re: Built-in target to delete all generated files

the target. Of note, GCS states that: More generally, ‘make maintainer-clean’ should not delete anything that needs to exist in order to run configure and then begin to build the program. Cheers, Peter -- Peter Johansson svndigest maintainer, http://dev.thep.lu.se/svndigest yat maintainer

Re: Include directive for all generated Makefile.in

-- Peter Johansson svndigest maintainer, http://dev.thep.lu.se/svndigest yat maintainer, http://dev.thep.lu.se/yat

Re: revision control info in generated files

Re: revision control info in generated files

the reason why it's distributed is because I have xxx_la_SOURCES += xxx.rc in my Makefile.am? exactly, so you could use 'nodist_xxx_la_SOURCES += xxx.rc' Cheers, Peter -- Peter Johansson svndigest maintainer, http://dev.thep.lu.se/svndigest yat maintainer, http://dev.thep.lu.se/yat

Re: revision control info in generated files

Jef Driesen wrote: mylib_la_SOURCES += version.c mylib_HEADERS += version.h BUILT_SOURCES = version.h EXTRA_DIST += $(srcdir)/version CLEANFILES += version-t Took me a while to figure out the escaping of the @ symbol. It seems to work fine, except that I would like to add

Re: revision control info in generated files

Jef Driesen wrote: On 12/04/10 14:59, Peter Johansson wrote: Also, I would try avoid distributing `version.h', but not sure how to do that from top of my head. Why would you not distribute it? Well, it's a matter of taste, but I see no real reason to include it in the tarball. I think

Re: revision control info in generated files

On 4/2/10 7:04 AM, Jef Driesen wrote: The problem I'm trying to solve is that I already have a version.h that is generated from a version.h.in template that contains: #define MYLIB_VERSION_MAJOR @MYLIB_VERSION_MAJOR@ #define MYLIB_VERSION_MINOR @MYLIB_VERSION_MINOR@ #define

Re: Keeping source directory structure

into: build-dir/common/map.o build-dir/linux/map.o It is not clear what the conflict is here. Are you creating several map.o files from the same map.cc? why? Cheers, Peter -- Peter Johansson svndigest maintainer, http://dev.thep.lu.se/svndigest yat maintainer, http://dev.thep.lu.se

Re: Public header files

Hi Jef, On 3/17/10 8:23 AM, Jef Driesen wrote: I only need it compiled into my library. The goal is that an application using my library can report the exact revision of the library (for diagnostic purpose). With the solution I outlined in my previous posts, I can already get the normal

Re: Public header files

On 3/16/10 8:29 AM, Jef Driesen wrote: On 15/03/2010 22:18, Ralf Wildenhues wrote: * Jef Driesen wrote on Sat, Mar 13, 2010 at 11:21:45PM CET: I suppose you are referring to solutions like this: m4_define([mylib_version_revision],m4_esyscmd([my_revision_script])) where the revision script

detect old Automake

and convenience it would be nice if Automake also returned 63 when an too old version was used. Is there any reason against that or would a patch be welcome? Thanks, Peter -- Peter Johansson svndigest maintainer, http://dev.thep.lu.se/svndigest yat maintainer, http://dev.thep.lu.se/yat

Re: detect old Automake

Hi Ralf, On 2/25/10 3:14 PM, Ralf Wildenhues wrote: Changing that to 63 is probably a good idea (but we'd need to check whether throughout autotools there is no expectance of the other value), Is anyone more than autoreconf and the missing script calling automake and thereby possibly

Re: create libraries with libtool, but don't install *.la files?

Hi, Andreas Jellinghaus wrote: Hi, the combination autoconf/automake/libtool makes it quite easy to create shared libraries. but how can I install the file created as a single *.so file, but without any *.la file etc. the shared libraries we create implement a fixed plugin interface thus they

Re: advice for pre-generating documentation

Hi Andreas, On 2/11/10 12:06 PM, Andreas Jellinghaus wrote: also I wonder: what about builddir vs. sourcedir? how do you handle that? if people have a tar.gz with pre-build documentation, it is in sourcedir. if people checkout svn and build in a seperate build root, the documentation is

Re: How to handle data/script files in a VPATH build ?

in the build tree? Cheers, Peter -- Peter Johansson svndigest maintainer, http://dev.thep.lu.se/svndigest yat maintainer, http://dev.thep.lu.se/yat

Re: silent installs

that shell code. When a developer asks for a silent build in order to catch problems all one should see is real warnings and problems. Have you tried Automake's silent-rules option? Peter -- Peter Johansson svndigest maintainer, http://dev.thep.lu.se/svndigest yat maintainer, http

Re: Shared Libraries

problem but i cant seem to find this in the manual. please see here: http://www.gnu.org/software/automake/manual/automake.html#Linking http://www.network-theory.co.uk/docs/gccintro/gccintro_17.html Cheers, Peter -- Peter Johansson svndigest maintainer, http://dev.thep.lu.se/svndigest

Re: libtool issue in a Makefile.am reference

On 1/25/10 2:25 AM, Murray S. Kucherawy wrote: I've got a package that first builds a library and then a binary that links to the library. The binary build references it via: progname_LIBADD = ../libdirectory/libraryname.la LIBADD is for libraries. For programs use progname_LDADD =

Re: making config files

On 1/14/10 7:28 AM, Daniel Pocock wrote: This is how I've been going about it: create $(top_srcdir)/ganglia.inc like so: FIXCONFIG = $(top)/scripts/fixconfig You probably mean $(top_builddir) %: %.tmpl $(FIXCONFIG) $(FIXCONFIG) $ AFAIU, %: %.tmpl is GNU Make specific and won't work

Re: making config files

Daniel Pocock wrote: Therefore, I felt that I should be aiming to have the config files generated at the last moment - probably during `make install', just before they are installed. Can anyone suggest best practice for doing this? please refer to

Re: amhello with generated version

On 1/7/10 6:14 AM, Baurzhan Ismagulov wrote: All this without having to modify, check in or tag anything after checking out. Are these use cases supported in the your development version? I'm not sure I fully understand the details of your use cases. Are these project maintained by you or

amhello with generated version

Hi, It has been discussed recently that the way the VERSION is set with automake is suboptimal when the VERSION is changing frequently [1]. The problem is basically that autoconf has to be re-run every time the VERSION is updated, which is not convenient if the VERSION is updated, e.g., at

Re: ifdef expessions in Makefile.am

Joakim Tjernlund wrote: I want to do something that is similar to: SUBDIRS+= dir1/dir2/@TEST@ but only if @TEST@ is defined. Any suggestions? http://www.gnu.org/software/automake/manual/automake.html#Conditional-Subdirectories -- Peter Johansson svndigest maintainer, http

Re: ifdef expessions in Makefile.am

? Thanks, Peter -- Peter Johansson svndigest maintainer, http://dev.thep.lu.se/svndigest yat maintainer, http://dev.thep.lu.se/yat

Re: Add missing bootstrap file

Gaetan Nadon wrote: If you want to modify files in automake, then you are doing development, rather than just installing the software. Given that automake requires itself, there may be special things to do. In any case, nothing should be added to the tarball that isn't required for

Re: Include files outside srcdir?

Hi Ralf, Ralf Wildenhues wrote: * Peter Johansson wrote on Tue, Nov 03, 2009 at 07:31:56PM CET: I'm not sure exactly what you wanna achieve here. But there is an autoconf macro http://www.nongnu.org/autoconf-archive/ax_add_am_macro_static.html which allows you to have autoconf to generate

Re: Include files outside srcdir?

projects. Peter -- Peter Johansson svndigest maintainer, http://dev.thep.lu.se/svndigest yat maintainer, http://dev.thep.lu.se/yat

Re: builddir question

Andreas Otto wrote: is a builddir other than . possible ? No http://www.gnu.org/software/autoconf/manual/autoconf.html#Preset-Output-Variables -- Peter Johansson svndigest maintainer, http://dev.thep.lu.se/svndigest yat maintainer, http://dev.thep.lu.se/yat

instspc.test fails on Mac OS X 10.4

Hi, I experience a failure of instspc.test in automake 1.11 test suite. Please find the test-suite.log (gzipped) attached. I use: autoconf (GNU Autoconf) 2.64 GNU Make 3.80 GNU bash, version 2.05b.0(1)-release (powerpc-apple-darwin8.0) Thanks, Peter test-suite.log.gz Description: GNU Zip

Broken link to Recursive Make Considered Harmful

://aegis.sourceforge.net/auug97.pdf Cheers, Peter -- Peter Johansson svndigest maintainer, http://dev.thep.lu.se/svndigest yat maintainer, http://dev.thep.lu.se/yat

Re: setting src_foo_CPPFLAGS in non-recursive build

, and was supposed to be src_foo2_CPPFLAGS = -I`pwd`/include and with that modification everything works fine. Going back to my original project, I found a similar typo :( So now everything works perfectly fine. Sorry about the noise. Thanks, Peter -- Peter Johansson svndigest maintainer, http

Re: Integration of git-based release workflow into make dist

Hi Bob and Roger, Bob Friesenhahn wrote: I have not verified if referencing a file outside of the source tree really works properly. My experience is that inclusion of an external file will be ignored by Automake, in other words, the include statement ends up in the Makefile. It might still

distcheck warning: libtool --finish...

or why do I get that warning? It seems I get th e same warning when I issue: make install DESTDIR=`pwd`/tmp stdout Thanks, Peter -- Peter Johansson svndigest maintainer, [1]http://dev.thep.lu.se/svndigest yat maintainer, [2]http://dev.thep.lu.se/yat References 1. http

Re: library dependencies SUBDIR problem automake

there any other way to modify the makefile.am of an application so that it will execute the makefile's of it's dependend library (components)? Please see this thread: http://lists.gnu.org/archive/html/automake/2009-03/msg00010.html Cheers, Peter -- Peter Johansson svndigest maintainer, http

Re: running tests under in a tests/ directory

aaragon wrote: Got it, but I tried LIBADD = $(top_srcdir)/yafeq/libyafeq.la and it doesn't work. However, LDADD = $(top_srcdir)/yafeq/libyafeq.la does work. So I hope this is finally the way to do it. Typically .la files are built and not shipped as source, and thus appearing in

Re: running tests under in a tests/ directory

Bob Friesenhahn wrote: It is not necessary to specify top_builddir because that is where the Makefile is written and the directory where the build is performed. As you say, specifying $(top_srcdir) may cause harm since it is likely to break VPATH builds. Sorry, I thought we were dealing with

Re: running tests under in a tests/ directory

aaragon wrote: I'm actually building the tests inside a test directory: $(top_srcdir)/tests, and the library I'm trying to link to is under $(top_srcdir)/yafeq. So if I remove the $(top_srcdir) then it doesn't work anymore. So the only way I made it work so far is using LDADD =

Re: vpath builds and nobase_include_HEADERS

in comp2/Makefile.am Cheers, Peter -- Peter Johansson svndigest maintainer, http://dev.thep.lu.se/svndigest yat maintainer, http://dev.thep.lu.se/yat

Re: RFE: allow for computed version number

Hi Bob, Bob Friesenhahn wrote: Doesn't any approach which depends on an automatically generated file assure that the version control system is one step out of date? Every time you do a 'commit' the version file is one step newer and therefore needs to be committed. Your analysis seems to

Re: vpath builds and nobase_include_HEADERS

is in CC or what do you mean post on-list? Please explain! Thanks, Peter -- Peter Johansson svndigest maintainer, http://dev.thep.lu.se/svndigest yat maintainer, http://dev.thep.lu.se/yat

Re: RFE: allow for computed version number

think of this approach? I think that is an excellent direction and it is fairly easy to propagate that information into a `version.c' or similar file. However, I wonder if it's possible, using this approach, to also override $(VERSION) (or dirstdir) in the Makefile? Thanks, Peter -- Peter

Re: create symlinks during install

tried the following: install-exec-hook: $(LN_S) -f foo $(bindir)/bar $(LN_S) -f foo $(bindir)/baz Please see the Automake manual for a good example http://www.gnu.org/software/automake/manual/automake.html#Extending Cheers, -- Peter Johansson svndigest maintainer, http

Re: subdirs for multiple binaries

a seperate program but i want to link in some of the code to the main program. If you don't mind using libtool, please have a look here http://www.gnu.org/software/automake/manual/automake.html#Libtool-Convenience-Libraries Cheers, Peter -- Peter Johansson svndigest maintainer, http

Re: Finding library procedures in /usr/local/lib/

John Calcote wrote: I sure don't know what's happening to my email messages lately. This is the third time this month that some response of mine has apparently been completely lost by Google mail. I sent this response to this thread last night (via Mozilla Thunderbird client), which goes

Re: library dependency

Hello John, John Wohlbier wrote: mv -f .deps/lib1src.Tpo .deps/lib1src.Plo make: *** No rule to make target `../lib2/liblib2.la', needed by `liblib1.la'. Stop. Does automake allow for automatically building lib2 when make is typed within lib1? If so, how is it done? If not, is this an

Re: incremental make install

not change. http://git.savannah.gnu.org/gitweb/?p=automake.git;a=blob;f=NEWS;h=6fcc1a535b0bbab7333230d780fde8f194836131;hb=HEAD Cheers, -- Peter Johansson svndigest maintainer, http://dev.thep.lu.se/svndigest yat maintainer, http://dev.thep.lu.se/yat

Re: incremental make install

/archive/html/automake-patches/2006-10/msg00070.html so it might be useful. Cheers, -- Peter Johansson svndigest maintainer, http://dev.thep.lu.se/svndigest yat maintainer, http://dev.thep.lu.se/yat

Re: auto-inserting COPYING

Hi Karl, Karl Berry wrote: I just learned that in some circumstances automake will insert a COPYING file if it's missing (albeit with a warning), e.g., at make dist? (I didn't look into the precise details.) This is a very old feature and according to NEWS it was actually deprecated in

build broken after adding ACLOCAL_AMFLAGS = -I m4

it is always a bit annoying to be forced to email co-developers saying: you need to run autoreconf. I use Automake 1.10 and Autoconf 2.61. Thanks, Peter -- Peter Johansson svndigest maintainer, http://dev.thep.lu.se/svndigest yat maintainer, http://dev.thep.lu.se/yat

build broken after adding ACLOCAL_AMFLAGS = -I m4

it is always a bit annoying to be forced to email co-developers saying: you need to run autoreconf. I use Automake 1.10 and Autoconf 2.61. Thanks, Peter -- Peter Johansson svndigest maintainer, http://dev.thep.lu.se/svndigest yat maintainer, http://dev.thep.lu.se/yat

Re: Treat pdf, html like info

Hi Stefan, Stefan Bienert wrote: Hi there, is there an easy way to traet pdf, html in the same way info targets are treated? I would like to have `make all` producing info, pdf and html docs from texinfo sources. If you wanna extend 'all', use 'all-local' such as all-local: pdf html

Re: [automake] Dependency question with _LDADD

Hi Michel, Michel Briand wrote: Peter Johansson [EMAIL PROTECTED] - Tue, 07 Oct 2008 11:21:26 -0400 Hello Michel, Michel Briand wrote: Hi all, I implemented a new idea for program's version. In src/bin/Makefile.am: internal_version.c: ${top_srcdir}/PROGRAM_VERSION

Re: [automake] Dependency question with _LDADD

Michel Briand wrote: Sorry for the confusion ! Its my fault I would not have chosen VERSION for my variable in Makefile.am since it duplicates one predefined variable (configure). I should have named it MY_VERSION, or better TRAINING_PROGRAM_VERSION The variable is dynamic. Make will

Re: [automake] Dependency question with _LDADD

Hello Michel, Michel Briand wrote: Hi all, I implemented a new idea for program's version. In src/bin/Makefile.am: internal_version.c: ${top_srcdir}/PROGRAM_VERSION ${top_srcdir}/vtempl.pl $(component) $(VERSION) $(templ) $@ training_SOURCES = training.c internal_version.c The

Re: Doxygen + Autotools integration

Hi Stefano, Stefano D'Angelo wrote: Hi all, My name is Stefano and I'm the author of NASPRO (http://naspro.atheme.org). I've been playing a bit lately trying to write support for Doxygen on Autoconf/Automake and here I am to give you the results of my work. Have you checked the macro

Re: Doxygen + Autotools integration

Hi Stefano, Stefano D'Angelo wrote: 2008/10/2 Peter Johansson [EMAIL PROTECTED]: Hi Stefano, Hi Peter, Have you checked the macro written by Oren Ben-Kiki that is available from the Autoconf Macro Archive: Yes (I also named that in my prevoius e-mail - http://www.ben

Re: [automake] Dependency question with _LDADD

Hello Michael, Michel Briand wrote: Peter Johansson [EMAIL PROTECTED] - Wed, 27 Aug 2008 10:50:48 -0400 Michel Briand wrote: :: src/lib/Makefile.am :: # Library: libtraining # Generates its own pkg-config definition file AM_CPPFLAGS = -DLIBRARY_VERSION

Re: multiple targets, different build options

John Richetta wrote: (I'm an autotools newbie.) What is the automake sanctioned way of providing different top-level make targets, that build my application with different options? For example, say I want to build foo_nondebug, and foo_debug, and (luckily) all of my application code resides

Re: [automake] Dependency question with _LDADD

Michel Briand wrote: :: src/lib/Makefile.am :: # Library: libtraining # Generates its own pkg-config definition file AM_CPPFLAGS = -DLIBRARY_VERSION=\$(LIBRARY_VERSION)\ Why not put AC_DEFINE([LIBRARY_VERSION], ...) in configure.ac, so you don't need the

Re: Warn: non-POSIX variable name

Steven Woody wrote: On Tue, Aug 19, 2008 at 3:43 PM, Brian Dessent [EMAIL PROTECTED] wrote: Steven Woody wrote: Thank you. Adding -Wno-portablility to AM_INIT_AUTOMAKE works. But I don't understand your other words: For the former, run the script at configure-time rather than at

Re: Warn: non-POSIX variable name

Steven Woody wrote: Thank you Peter. I have two more questions: 1, Where and how you set the HAVE_SVN_WC? I have the following in my configure.ac: # Check if svnversion is installed AC_PATH_PROG([SVNVERSION], [svnversion], [no]) # checking if we build in a subversion WC wc_found=no; if

<    1   2