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 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-
>
> b
Hello Martin,
* Martin Kalbfuß wrote on Mon, Jan 11, 2010 at 03:13:22AM CET:
> I have a libname with version number.
>
> liballegro-4.9.14
>
> I added this name to AC_CHECK_LIB. And it is found.
>
> # Checks for libraries.
>
> AC_CHECK_LIB([allegro-4.9.14], [al_create_display], [],
> [AC_MSG_E
Hello Martin,
* Martin Kalbfuß wrote on Sun, Jan 10, 2010 at 10:59:52PM CET:
> I like to know if
>
> make & make install & program_name
>
> is the typically development work flow.
For many developers, I guess so. (If you meant the above literally,
then you need to use && instead of &.)
Howeve
Hello Bernd,
* Bernd Jendrissek wrote on Mon, Jan 11, 2010 at 03:59:43PM CET:
> I have been trying to update to more recent autotools, and being a
> traceability nazi, I want to rebuild from as far upstream as possible.
> That means ignoring the distributed ./configure and Makefile.in and
> rebui
Hello Tomas,
* Tomas Oberhuber wrote on Sat, Jan 02, 2010 at 11:33:46AM CET:
> Now I try to compile whole project with nvcc. It seems to work but I get this
>
> ibtool: link:
> nvcc -shared -nostdlib
> .libs/libtnl-0.1.lax/libtnldebug-0.1.a/libtnldebug_0_1_la-tnlDebugStructure.o
> .libs/li
* Adam Mercer wrote on Thu, Dec 31, 2009 at 12:24:45AM CET:
> On Wed, Dec 30, 2009 at 22:17, Adam Mercer wrote:
>
> > Just made this change and autoreconf no longer complains if compile
> > isn't available. Thanks!
>
> And it's started complaining again :-(
>
> I've tried running automake manua
Hello Baurzhan,
* Baurzhan Ismagulov wrote on Wed, Dec 23, 2009 at 09:50:25AM CET:
> On Tue, Dec 22, 2009 at 10:48:22PM +0100, Ralf Wildenhues wrote:
> > nodist_ is to avoid distribution, that is, `make dist' putting the file
> > into the tarball. To avoid installation (whic
Hello Tomas,
* Tomas Oberhuber wrote on Tue, Dec 29, 2009 at 07:25:36PM CET:
> I am experiencing some troubles with cuda. I studied mailing lists about
> autoconf, automake and libtool and from what I have read
> I have understood that from the linking point of view nvcc and gcc are
> compatibl
Hi Adam,
* Adam Mercer wrote on Wed, Dec 30, 2009 at 11:57:27AM CET:
> On one of my projects I'm running into an issue, only on certain
> platforms, where the compile script isn't available. e.g. on CentOS 5
>
> $ autoreconf
> test/Makefile.am: required file `gnuscripts/compile' not found
> autor
Hello Jan,
* Jan Paral wrote on Mon, Dec 28, 2009 at 09:24:32PM CET:
> my library is split into several directories ... so I define _SOURCES
> variable
> as:
> libsatbase_a_SOURCES = cfgfile/grammar.c common/hash.cxx
>
> and I have several libraries in the project. The problem is when I co
Hello Martin,
* Martin Kalbfuß wrote on Wed, Dec 23, 2009 at 04:42:18AM CET:
> sklib_LIBRARIES = libsk.a
>
> libsk_a_SOURCES = \
> SKGeneral.mod \
> SKVideo.mod \
> SKVersion.mod \
> SKTime.mod
>
> sklib_HEADERS = \
> GeneralBase.def \
> SKGeneral.
Hi Baurzhan,
* Baurzhan Ismagulov wrote on Tue, Dec 22, 2009 at 08:00:13AM CET:
>
> Now, how can I exclude the source .py files from the installation? I've
> tried nodist_nobase_python_PYTHON, but that doesn't seem to do what I
> want.
nodist_ is to avoid distribution, that is, `make dist' putti
Hi Baurzhan,
* Baurzhan Ismagulov wrote on Tue, Dec 22, 2009 at 12:51:33AM CET:
> I've created a Makefile.am to compile and install Python files.
>
> Now, the files are copied into a single destination directory. I'd like
> to distribute the files preserving their paths, i.e., the structure
>
>
* Joakim Tjernlund wrote on Sun, Dec 20, 2009 at 03:58:47PM CET:
> Yes, thanks for the script layout. What would be even
> cooler is if one could add a custom macro in acinclude.m4
> that would override the libtool.m4 macro creating the -fPIC option
> and replace it with -fpic instead.
No, it woul
Hi Russell,
beside the typo you already found,
* Russell Shaw wrote on Thu, Dec 17, 2009 at 02:07:40PM CET:
> bin_PROGRAMS = appmain
>
> appmain_SOURCES = appmain.c
> nodist_appmain_SOURCES = gran.proc.tab.c
BUILT_SOURCES = gran.proc.tab.c
> gran.proc.tab.c: gran.spec
> eerat $< -o gra
* Joakim Tjernlund wrote on Thu, Dec 17, 2009 at 11:29:19PM CET:
> if @TEST@ then
> SUBDIRS+= dir1/dir2/@TEST@
> SUBDIRS+= dir3/dir2/@TEST@
> SUBDIRS+= dir4/@TEST@
>
> endif
The syntax is
if TEST
SUBDIRS += ...
endif
and there should not be any indentation of `if' and `endif', and
* Monty Taylor wrote on Wed, Dec 16, 2009 at 05:01:15AM CET:
> I have several document source files, each ending in pod, which will
> each produce one more more man pages when run through pod2man. Simply,
> something like this:
>
> function1.3: source.pod
> function2.3: source.pod
>
> %.3: %.pod
* Russ Allbery wrote on Wed, Dec 16, 2009 at 05:08:14AM CET:
> Do you really want to generate separate copies of the man page for each
> function documented by the same source POD file? It's more normal to
> generate one copy of the man page and then, during make install, symlink
> the other ones
Hi Jim,
* Jim Meyering wrote on Tue, Dec 15, 2009 at 07:48:21AM CET:
> Ralf Wildenhues wrote:
> > Adding LIBTOOL here is wrong; you meant LIBTOOLIZE.
>
> I've removed it.
> I don't see anything except bootstrap that runs $(LIBTOOLIZE). Do you?
No, adding LIBTOOLIZ
* Bob Friesenhahn wrote on Tue, Dec 15, 2009 at 03:24:29AM CET:
> On Mon, 14 Dec 2009, Martin Kalbfuß wrote:
> >
> >When I have a look at the config.h I see only empty defines like
> >
> >#define SKMajor
> >
> >What's wrong here?
>
> Shell lines prior to AC_INIT are ignored. This is definitely an
Hi Joost,
* Joost Kraaijeveld wrote on Mon, Dec 14, 2009 at 09:21:01AM CET:
> When compiling a (large) project with multiple Makefiles (with make -k
> -j6 all ) , I get errors from libtool:
>
> ../../../../../libtool: line 747: echo: write error: Broken pipe
> ../../../../../../library/DagdaORB/
Hello,
* Jim Meyering wrote on Sun, Dec 13, 2009 at 11:44:15AM CET:
> Paolo Bonzini wrote:
> > This rule could actually be moved to Automake's distcheck target.
>
> Good idea.
> FYI, here's the definition I have now:
> (added GPERF and LIBTOOL, and made it overridable)
Adding LIBTOOL here is wro
* Ralf Wildenhues wrote on Tue, Dec 08, 2009 at 11:13:45PM CET:
> For release branches older than branch-1-10, the respective fix has been
> applied to the git tree, but there are currently no plans to produce new
> official releases for them; contact us if you absolutely need to have
GNU Automake 1.11.1 as well as 1.10.3 fix a security-related race
condition that affects `make dist' and `make distcheck' for all packages
that use Automake. Before the fix, the `distdir' target (which is used
by both `dist' and `distcheck') would first populate a directory below
the build tree wi
We're pleased to announce the release of Automake 1.10.3.
Automake is a tool for automatically generating `Makefile.in's
suitable for use with Autoconf, compliant with the GNU Makefile
standards, and portable to various make implementations.
This is a bugfix release over 1.10.2. All of these bug
We're pleased to announce the release of Automake 1.11.1.
Automake is a tool for automatically generating `Makefile.in's
suitable for use with Autoconf, compliant with the GNU Makefile
standards, and portable to various make implementations.
This is a pure bugfix release. It contains fixes for t
Hello Andreas,
besides answers already given:
* Andreas Otto wrote on Fri, Dec 04, 2009 at 09:41:16AM CET:
> as you see both *lo and *.o are created. the *.o are useless and just
> extend the compiling time
> Q: what can I do to avoid build static libraries ...
foo_LIBTOOLFLAGS = -tag=disable-s
Hello Joakim,
* Joakim Tjernlund wrote on Wed, Dec 02, 2009 at 11:59:11PM CET:
> I basicall want to do in a Makefile.am
> ifdef automake version > 1.4
> AM_LDFLAGS=...
> else
> LDFLAGS=...
> endif
> Because am version == 1.4 does not like
> some newer automake macros and I am moving a big proj
Hello Robert, and sorry for not replying on this earlier:
* Robert Collins wrote on Wed, Sep 23, 2009 at 10:03:42AM CEST:
> There was discussion about getting version numbers from VCS recently;
> I've done a slightly different thing for a while now:
> AC_DEFUN([SUBUNIT_MAJOR_VERSION], [0])
> AC_DE
Hi Ken,
* Ken Perl wrote on Sun, Nov 29, 2009 at 07:11:11AM CET:
> I may configure; make successfully on Linux, but when I tried to build
> it for win32 crossly on Linux, I have trouble, see below steps,
>
> ./configure --build i686-pc-linux-gnu --host i586-mingw32msvc
> make
> i586-mingw32msvc-g
Hi Ed,
* Ed Hartnett wrote on Fri, Nov 27, 2009 at 12:32:20PM CET:
> We have a documentation directory, and it's the only one for which "make
> -j check" does not work. (Without the -j, it works.)
> Here's how it fails:
> TEXINPUTS=".:$TEXINPUTS" \
> MAKEINFO='/bin/sh /machine/netcdf/n4
Hello Andreas,
* Andreas Otto wrote on Wed, Nov 25, 2009 at 10:39:54AM CET:
> I have integrated an subpackage into an already existing package
> everything works well but one problem still exists
>
> the debugging feature is turned on in the toplevel package with
> --enable-symbols and in t
Hi Jim,
* Jim Meyering wrote on Wed, Nov 25, 2009 at 09:15:45PM CET:
> Considering that that text is at least 10 years old, I think
> we can say with confidence that the reason for it (that then-old
> version of tar) is no longer relevant. I would like to update
> that part of the GNU Coding Stan
Hi Harlan,
* Harlan Stenn wrote on Thu, Nov 26, 2009 at 12:10:26PM CET:
> I wrote:
> > In what version of automake did abs_builddir first appear?
> >
> > I know it was post-1.9.6...
>
> Looks like it first appeared in 1.10.
autoconf/NEWS documents it as new in 2.53, and broken in 2.58 (it was
r
Hello Thomas, Bob,
* Bob Friesenhahn wrote on Wed, Nov 25, 2009 at 12:23:39AM CET:
> On Tue, 24 Nov 2009, Thomas Dickey wrote:
> >>
> >>Make sure that the directory into which the distribution unpacks (as
> >> well as any subdirectories) are all world-writable (octal mode 777).
> >> This is so
Hi Kent,
* Kent Boortz wrote on Mon, Nov 09, 2009 at 04:30:29PM CET:
> My real question is, how can I specify what TAR to use in "make dist",
> and avoid GNU TAR for my packaging, when 'tar-ustar' is specified to
> automake?
If you have a configure test which will find a good tar program for you,
Hello Alan, Jim,
* Jim Meyering wrote on Sun, Nov 22, 2009 at 04:32:57PM CET:
> Alan Curry wrote:
> > So was the drwxrwxrwx in the tarball put there to teach a lesson to those
> > who trust a tarball to have sane permissions? Or is it a bug?
>
> On one hand, you can also think of it as a LART for
Hello Martin,
* Martin Kalbfuß wrote on Mon, Nov 23, 2009 at 09:13:05PM CET:
> I replaced the default linker by setting object_LINK to "gm2 -o $@" ,But
> this doesn't work, because gm2 needs the source file names instead of
> the object file names. Can I tell automake or make to pass .mod instead
Hi Alfred,
* Alfred M. Szmidt wrote on Mon, Nov 16, 2009 at 08:33:10PM CET:
> You didn't answer why you need this switch, only that you want it.
Various threads on this list during the last months document this,
I would say. It otherwise isn't even hard to guess. ;-)
Cheers,
Ralf
Hi Jan,
* Jan Engelhardt wrote on Mon, Nov 09, 2009 at 02:09:14AM CET:
> in the automake tarballs, the 'bootstrap' script is missing, but it
> would be needed when modifying any of the automake files in a tarball.
Sounds reasonable to me, esp. since it doesn't even use git in any way
(yet).
>
* Daniel Leidert wrote on Sat, Nov 14, 2009 at 01:44:52PM CET:
> I will check my local copies as soon as I'm back. All I can say is,
> that the above works well (also if builddir != srcdir).
I'm not sure it will work with non-GNU makes, though.
Cheers,
Ralf
* Daniel Leidert wrote on Fri, Nov 13, 2009 at 10:19:43PM CET:
> Clifford Yapp wrote:
> > I have a situation where I need to copy png images from a source
> > directory to the build directory prior to running other build rules,
> > and I am having some trouble formulating a rule to do the job.
> >
* Ed Hartnett wrote on Fri, Nov 13, 2009 at 08:47:47PM CET:
> Ralf Wildenhues writes:
> > * Ed Hartnett wrote on Fri, Nov 13, 2009 at 05:14:24PM CET:
> >> The netCDF C library uses other libraries, for example the hdf5,
> >> hdf5_hl, and zlib libraries. I was b
Hi Ed,
* Ed Hartnett wrote on Fri, Nov 13, 2009 at 05:14:24PM CET:
> The netCDF C library uses other libraries, for example the hdf5,
> hdf5_hl, and zlib libraries. I was building the library without
> explicitly linking to these other libraries, assuming that libtool would
> magically handle this
* Vincent Torri wrote on Fri, Nov 06, 2009 at 12:57:43AM CET:
> On Thu, 5 Nov 2009, Ralf Wildenhues wrote:
> >* Vincent Torri wrote on Thu, Nov 05, 2009 at 11:38:52PM CET:
> >>base_sources = \
> >[...]
> >>if EET_AMALGAMATION
> >>libeet_la_SOURCES = eet_
* Vincent Torri wrote on Thu, Nov 05, 2009 at 11:38:52PM CET:
> still no luck :) I paste the code below. I did a make
> maintainer-clean, then ./autogen.sh, then make distcheck, to be sure
> that i restart from something clean.
> base_sources = \
[...]
> if EET_AMALGAMATION
> libeet_la_SOURCES = e
* Vincent Torri wrote on Thu, Nov 05, 2009 at 10:23:38AM CET:
> On Thu, 5 Nov 2009, Ralf Wildenhues wrote:
> >* Vincent Torri wrote on Thu, Nov 05, 2009 at 08:06:51AM CET:
> >>>>using just nodist_ is not sufficient : make distcheck fails:
> >>>>
&g
* Vincent Torri wrote on Wed, Nov 04, 2009 at 10:30:08PM CET:
> >On Wed, 4 Nov 2009, Ralf Wildenhues wrote:
> >
> >>You can simply add the generated file to nodist_libeet_la_SOURCES
> >>instead of to libeet_la_SOURCES.
> >
> >indeed. Actually, i used nod
* Vincent Torri wrote on Wed, Nov 04, 2009 at 08:05:34PM CET:
> On Wed, 4 Nov 2009, Ralf Wildenhues wrote:
> >* Vincent Torri wrote on Wed, Nov 04, 2009 at 07:52:17PM CET:
> >>we have added an option to our configuration stuff that concatenates
> >>all the source file
Hello Vincent,
* Vincent Torri wrote on Wed, Nov 04, 2009 at 07:52:17PM CET:
> we have added an option to our configuration stuff that concatenates
> all the source files, creates another from one from them, and
> compiles it. The problem is that this new source file is
> automatically added to th
* Peter Johansson wrote on Wed, Nov 04, 2009 at 01:55:21PM CET:
> Ralf Wildenhues wrote:
> >* Peter Johansson wrote on Tue, Nov 03, 2009 at 07:31:56PM CET:
> >>http://www.nongnu.org/autoconf-archive/ax_add_am_macro_static.html
> >Hmm, the idea of having such a is not b
* Peter Johansson wrote on Tue, Nov 03, 2009 at 07:31:56PM CET:
> Joseph Garvin wrote:
> >I have a number of autotooled libraries. Currently their Makefile.am's
> >are largely redundant, so I thought I would use the 'include' keyword
> >and have them pull their common parts from some file. But as f
Hi Jason,
* Jason Sewall wrote on Sun, Nov 01, 2009 at 06:28:31PM CET:
> On Sun, Nov 1, 2009 at 6:45 AM, Ralf Wildenhues wrote:
> >
> > Is anyone using it? Has anyone seen issues with it?
>
> I didn't even know it existed, but I just tried it out and it seems to
>
Since the 1.11 release I have not seen one bug report about
$AUTOMAKE_JOBS aka. automake running several Perl threads to
update several Makefile.in files concurrently, for speed.
If you have more than a couple of Makefile.am files and a SMP
system, then it should help.
Is anyone using it? Has any
* Andreas Otto wrote on Sun, Nov 01, 2009 at 12:17:05PM CET:
> this add a new target ".vpath_hook" to the build environment and this target
> copy the files/directories listed in "VPATH_FILES" from the src into the
> build environment. the "copy" is necessary because tools like "JAR"
> expe
Hello Andre,
Your example is pretty complex, and doesn't make the problem obvious.
Merely adding libCustomPlugin.la to BUILT_SOURCES doesn't seem to
introduce a cycle in the build dependencies, at least from a 'make -n'
in an example package that has this Makefile.am but no other files.
It may he
Hello Andreas,
* Andreas Otto wrote on Sun, Oct 25, 2009 at 07:20:16PM CET:
> currently I try to improve my build environment. I want to add "OS"
> independent build results like
>
> java "class" files or mono "clr" libraries/excutable
>
> into the distribution
>
> 1) the
Hi Bob,
* Bob Friesenhahn wrote on Wed, Oct 21, 2009 at 10:03:41PM CEST:
> clean-codersLTLIBRARIES:
> -test -z "$(coders_LTLIBRARIES)" || rm -f $(coders_LTLIBRARIES)
> @list='$(coders_LTLIBRARIES)'; for p in $$list; do \
> dir="`echo $$p | sed -e 's|/[^/]*$$||'`"; \
>
* Andreas Otto wrote on Wed, Oct 21, 2009 at 08:04:15AM CEST:
> Am Dienstag 20 Oktober 2009 21:07:35 schrieb Ralf Wildenhues:
> > * Andreas Otto wrote on Tue, Oct 20, 2009 at 08:53:14AM CEST:
> > > I use the flag file "Net-Msgque/.distclean" to distinguish the VPATH
&g
* Andreas Otto wrote on Tue, Oct 20, 2009 at 08:53:14AM CEST:
> Am Dienstag 20 Oktober 2009 08:27:01 schrieb Ralf Wildenhues:
> > >
> > > distclean-local:
> > > test -f Net-Msgque/.distclean && rm -fr Net-Msgque
> >
> > Won't that a
Hello Andreas,
thanks for sharing your solution. A couple of comments:
* Andreas Otto wrote on Mon, Oct 19, 2009 at 12:20:26PM CEST:
> if USE_PERL
>
> PERLMAKEFILE = Net-Msgque/Makefile
> PERLDEPEND= Net-Msgque/Makefile.PL Net-Msgque/typemap Net-
> Msgque/lib/Net/Msgque.pm
> PERLCONFIG
* Stefan Bienert wrote on Mon, Oct 19, 2009 at 02:06:40PM CEST:
> cd ../.. && /bin/sh
> /home/user/projects/documentation.git/share/misc/config/missing --run
> automake-1.10 --gnu share/doc/Makefile
> share/doc/Makefile.am:76: user target `dvi' defined here...
> automake-1.10: ... overrides Automa
* Stefan Bienert wrote on Mon, Oct 19, 2009 at 12:45:19AM CEST:
> Is there a way to stop automake producing a rule for dvi docs?
> It just makes my 'distcheck' fail.
dvi:
Cheers,
Ralf
I recently discovered Devel::Cover (Debian package libdevel-cover-perl).
This rocks. Kudos to Paul Johnson for writing this module.
To use Devel::Cover, I have started a branch perl-coverage (off of
maint) which introduces a few helper targets, e.g.,
make check-coverage
which is veeery slow, b
Hello,
* Jan Engelhardt wrote on Sat, Oct 17, 2009 at 07:04:39PM CEST:
> when one decides to drive make in a non-recursive fashion, one has to
> write an Automake file like this:
>
> lib_LTLIBRARIES = foo/bar.la
> foo_bar_la_SOURCES = foo/one.c foo/two.c
>
> Usually I stuff that into a file cal
Hello Petter,
thanks for the report.
Please note that the current version of Automake is 1.11, so you are
encouraged to upgrade.
For verbose output of the failed tests, you can run
cd tests
env TESTS="exdir2.test libtool3.test libtool7.test \
ltcond.test ltcond2.test ltconv.test ltlibsrc
Hello Andreas,
beside the advice already give to you:
* Andreas Otto wrote on Thu, Oct 15, 2009 at 12:59:39PM CEST:
> to build a perl extension it's best to use the perl build-system based on
>
> perl Makefile.PL
>
>the command create a Makefile in the same directory of Makefile.PL
* Ralf Corsepius wrote on Wed, Oct 14, 2009 at 09:23:10AM CEST:
> On 10/14/2009 07:05 AM, Ralf Wildenhues wrote:
> >
> >I still fail to understand. What problem do you have with either
> > echo export V=1>> ~/.bashrc
> >
> >or
> > echo enable_sile
* Vincent Torri wrote on Wed, Oct 14, 2009 at 07:48:35AM CEST:
> $(builddir)/eina_amalgamation.c: $(sources_used) Makefile
> -rm -f $(builddir)/eina_amalgamation.c
$(builddir) is always equal to '.'; also, non-GNU makes don't identify
FILE and ./FILE; so you are better off omitting '$(buildd
[ dropping autoconf@ ]
* Ralf Corsepius wrote on Tue, Oct 13, 2009 at 05:20:30PM CEST:
> On 10/13/2009 04:49 PM, Bob Friesenhahn wrote:
> >On Tue, 13 Oct 2009, Ralf Corsepius wrote:
> >>
> >>The problem is verifying "correctness of building" packages in batches.
> >>
> >>i.e. to monitor/inspect CF
Hello Martin,
* Martin Kalbfuß wrote on Tue, Oct 13, 2009 at 11:21:13PM CEST:
> I want to create a library for the GNU-Modula compiler. But the
> libraries are pure object files in a separate directory. Some kind of
> package.
>
> Is there a target for this?
No. But if you write the compile rul
Hello,
forgive my ignorance on the subject: what are the (desired) semantics of
elisp files?
Currently, you trip over Automake bugs when you use lisp files in
subdirs (with or without subdir-objects):
lisp_LISP = sub/am.el
or use nobase_:
nobase_lisp_LISP = sub/am.el
Elias reported part of
* Bruno Haible wrote on Tue, Oct 06, 2009 at 10:47:45PM CEST:
> How about prefixing every diagnostic with "warning:" or "error:", like gcc
> does it?
>
> foo.c:1:9: warning: integer constant is too large for its type
> foo.c:2:7: error: too many decimal points in number
Good idea, noted. We
Hello,
please don't top-post, thanks.
* vicious3030 wrote on Fri, Oct 02, 2009 at 11:29:34PM CEST:
> Ralf Wildenhues wrote:
> > You can either
> > AC_SUBST([thirdPartyPath], [/home/blah/third])
> >
> > in configure.ac, or have a common fragment that you
>
[ adding automake@ ]
Hello Ralf,
* Ralf Corsepius wrote on Tue, Oct 06, 2009 at 05:49:52PM CEST:
> a) AM_SILENT_RULES are harmful (I know, you know that I think about
> this (mal-) "feature" this way - Working around the issues they are
> causing in Fedora packaging is a major nuissance.)
Could
Hello Bruno, Ian,
thanks for the report.
* Bruno Haible wrote on Sat, Oct 03, 2009 at 02:42:08PM CEST:
> Here is a situation where automake 1.9.6 errs out because of a missing
> invocation of AM_PROG_CC_C_O in a configure.ac, but automake >= 1.10 don't
> err out any more and instead produces a Ma
Hello Gaetan,
* Gaetan Nadon wrote on Fri, Oct 02, 2009 at 08:30:51PM CEST:
>
> Our components use "foreign" and "dist-bzip2" options. We distribute the
> tarballs. When running distclean, the tarballs are not removed from the
> build tree. This is not a problem for us. I was wondering if this is
* vicious3030 wrote on Tue, Sep 29, 2009 at 12:01:28AM CEST:
>
> I'm working on putting together my first automake project, 3 executables,
> multiple convenience libraries, among a few folders.
> It includes some third party libraries and header files that are stored
> elsewhere.
> I'd like to hav
* David Bruce wrote on Mon, Sep 28, 2009 at 01:08:58AM CEST:
> On 9/27/09, Ralf Wildenhues wrote:
> > * David Bruce wrote on Sat, Sep 26, 2009 at 04:51:01AM CEST:
> >> My project is not creating valid tarballs with "make dist", and "make
> >>
* Robert Collins wrote on Sun, Sep 27, 2009 at 11:40:31PM CEST:
> The landscape has changed though, and I suspect that if we gather stats
> about this we'll see that install-sh is dead weight for most packages
> nearly all of the time.
The statistics are that <15K of code text is nearly negligible
* Ralf Wildenhues wrote on Sun, Sep 27, 2009 at 11:01:07AM CEST:
> It is possible to use different names than Makefile.am for the automake
> input files, with a caveat: in recursion rules, automake outputs plain
> `$(MAKE)' only, without -f. That still allows the following: for th
* Robert Collins wrote on Sun, Sep 27, 2009 at 01:13:48PM CEST:
> Ralf Wildenhues wrote:
> What would be the best way? Do you think this might cause other
> >>> problems?
> >> I suggest dropping install-sh completely except for the coreutils
> >> package.
&g
Hello Andy,
* Andy Tai wrote on Sat, Sep 26, 2009 at 08:13:06PM CEST:
> Hi, I wonder if there is a way to place the GNU autotools files in a source
> tree in a subdirectory from the source files, such as
>
> if I have sources files
>
> source1.c source2.c
>
> and there may be a Makefile in this
* Robert Collins wrote on Sun, Sep 27, 2009 at 10:37:01AM CEST:
> Brian Gough wrote:
> > - AC_PROG_INSTALL could confirm that the install program it finds
> > works in the way it will be used in "make install" and give an
> > error otherwise.
>
> Perhaps it already does for the system in
Hi Brian, Russ,
* Russ Allbery wrote on Sun, Sep 27, 2009 at 09:10:52AM CEST:
> Brian Gough writes:
>
> > Maybe it would be good to have a check for problems with install-sh.
> > I can see a couple of ways this could be done:
>
> > - make distcheck could (i) use install-sh and (ii) independent
Hi David,
* David Bruce wrote on Sat, Sep 26, 2009 at 04:51:01AM CEST:
> My project is not creating valid tarballs with "make dist", and "make
> distcheck" fails at the VPATH build stage.
Please post your Makefile.am files in toplevel and src. We might also
need to see your configure.ac file.
T
* Martin Kalbfuß wrote on Mon, Sep 21, 2009 at 08:02:54PM CEST:
> Now I try to distribute GNU Modula-2 Modules with Autotools. Modula-2
> doesn't use archived static libraries like C does. Instead the object
> files are distributed and installed with the definition modules in a
> subdirectory of th
* Robert Collins wrote on Sat, Sep 19, 2009 at 08:30:03AM CEST:
> On Sat, 2009-09-19 at 08:24 +0200, Ralf Wildenhues wrote:
> > * Robert Collins wrote on Sat, Sep 19, 2009 at 06:16:25AM CEST:
> > > It would be nice if there was an option to tell automake not to (do
> >
Hello Robert,
* Robert Collins wrote on Sat, Sep 19, 2009 at 06:16:25AM CEST:
> It would be nice if there was an option to tell automake not to (do
> 'uninstall' as part of distcheck | require that uninstall leaves no
> files behind)
You can do the latter by overriding either distuninstallcheck r
Hello Martin,
* Martin Kalbfuß wrote on Thu, Sep 17, 2009 at 01:12:44AM CEST:
> I try to build up a test suit for my library. I have a description for
> using autotest for a program. But haven't found anything about testing
> libraries. Are there any good descriptions or examples?
Examples for te
* Xochitl Lunde wrote on Mon, Sep 14, 2009 at 05:12:11PM CEST:
> > Do you require GNU make or do you target portable make?
> > If the former, then you should be able to use pattern rules.
>
> Xochitl: Our current build structure has now 4 separate directory trees
> with makefiles. A Linux set, a
* Dave Steenburgh wrote on Mon, Sep 14, 2009 at 04:40:50PM CEST:
> My apologies for not replying sooner; I certainly appreciate everyone's
> input. This weekend just got crazy.
No problem at all, I sometimes take months to reply.
> On Fri, Sep 11, 2009 at 1:59 PM, Ralf Wi
Hello Lorenzo,
* Lorenzo Bettini wrote on Mon, Sep 14, 2009 at 09:19:16AM CEST:
> In a Makefile.am I'd like to use $(notdir $<) but that's a GNU make
> extension... is there a way of achieving the same result in a
> portable way? Does automake provide a special variable/function for
> that?
As l
Hello Martin,
* Martin Kalbfuß wrote on Tue, Sep 15, 2009 at 03:45:26AM CEST:
> I try to build a simple hello world program written in pascal(gpc).
> There's no AC_PROG_GPC or something. So I have to do it on my own. gpc
> supports all gcc options + some pascal specific options. hat I have so
> fa
Hello Xochitl,
* Xochitl Lunde wrote on Thu, Sep 10, 2009 at 09:27:31PM CEST:
> I have an embedded platform for which I override all the make rules by
> writing the make rules by hand in Makefile.am. I have tested this out,
> and it works great, but because we have many unit tests, I have to co
Hello Kenneth,
* Kenneth Porter wrote on Thu, Sep 10, 2009 at 09:40:22PM CEST:
> I'm porting a proprietary Windows DLL and demo app to Linux and I'm
> trying to figure out the best way to structure the build system. I'm
> trying to figure out how to use autoconf, automake, and libtool and
> whethe
Hello Dave,
* Dave Steenburgh wrote on Fri, Sep 11, 2009 at 05:24:58PM CEST:
> I have this problem with several of my programs, but it's most frustrating
> with my current program, which at the moment has a flat directory structure.
> The program in question is developed little by little, so from
* NightStrike wrote on Thu, Sep 10, 2009 at 01:18:38AM CEST:
> When I put fortran sources in a binary that also contains C sources,
> the compiler optimization flags get messed up.
Not really. It's the AC_PROG_{CC,CXX,...} macros that select
appropriate default {C,CXX,...}FLAGS if the user hasn'
Hello Dan,
* Dan Smithers wrote on Wed, Sep 09, 2009 at 05:12:46PM CEST:
> Should the C++ compiler use the CFLAGS passed into automake? or do I
> need to manually include them in CXXFLAGS?
Neither. At least if you are a package author, then you shouldn't pass
CFLAGS to the C++ compiler nor CXXFL
Hello Sam,
* Sam Steingold wrote on Thu, Sep 03, 2009 at 06:26:53AM CEST:
> Some packages install "build-aux" files (config.guess, config.sub,
> install-sh et al) so that their add-ons can rely on them.
> It would seem to be a relatively easy:
>
> = configure.ac
> AC_PATH_PROG(foo_path, foo)
401 - 500 of 1852 matches
Mail list logo
