Hi,
how can I find out when a certain autoconf macro was
introduced by autoconf ?
E.g. when I run autoconf with the --warnings=all option
I get good advices how to improve my macros.
However I guess when I upgrade the macros I'm indeed on top
with the current autoconf release but possibly break so
Wildenhues wrote:
> Hi Thomas,
>
> * Thomas Porschberg wrote on Fri, Feb 03, 2006 at 08:35:13AM CET:
> >
> > how can I find out when a certain autoconf macro was
> > introduced by autoconf ?
>
> Here's what I do to find out, in decreasing order of preference:
Am Tue, 14 Mar 2006 11:32:31 -0500
schrieb Chris Pickett <[EMAIL PROTECTED]>:
> [[ Sorry, I originally sent this from an unsubscribed account ]]
>
> Original Message
> Subject: Re: unit testing with autotools
> Date: Tue, 14 Mar 2006 11:25:06 -0500
> From: Chris Pickett <[EMAIL
Hi,
for my problem with the m4 macros for boost I think I can go the
following way:
I provide ac_boost_base.m4 which does the version check and defines
BOOST_CPPFLAGS, BOOST_LDFLAGS.
Boost users who only want use the template libs from boost have only to
include this macro.
Boost users who want u
Hi,
I wrote some m4 macros for the boost libraries(see
http://randspringer.de/boost/index.html).
ATM the default behavior is that the user has to give
--with-boost, --with-boost-files-date-time
to the configure script in order to set the boost compile/linker flags
(the last parameter of AC_ARG
Hi,
I have to establish a test system on Unix/Linux systems
which has to run/test Java, PLSQL, C/C++ and Shell programs.
Actually it should be able to run a complete test on a (sub)project.
My first idea was to provide several Makefiles and some shell scripts
for that task but maybe the purpose o
Hi,
we use autoconf, automake and libtool for our project.
I created a tarball with "make dist" and the latest set
of the GNU build utils (autoconf 2.61, automake 1.10, libtool 1.5.22)
and sent it to another programmer.
The other programmer run configure, compiled the program and got a
segmentat