s
to help aclocal find the libtool macro definitions.
After installing Libtool to the same prefix as the prerelease Automake, the
problem disappeared.
Cheers,
Dave Hart
l 2.4.6
I saw no interesting differences between various Automake versions after
1.16.5, nor with Autoconf 2.71 vs. 2.72. Let me know if there's more I can
do to home in on the problem.
--
Cheers,
Dave Hart
It seems debbugs.gnu.org is down or running behind, so here's what I've
found. Further testing after I composed the report shows the Automake
1.16i prerelease also suffers the problem.
-- Forwarded message -----
From: Dave Hart
Date: Sat, 29 Jun 2024 at 17:18
Subject
gure.ac' and run 'aclocal' and 'autoconf' again.
Makefile.am:161: If 'LT_INIT' is in 'configure.ac', make sure
Makefile.am:161: its definition is in aclocal's search path.
Makefile.am: installing 'build-aux/depcomp'
parallel-tests: inst
be gremlins in our build
system that make it tricky, I haven't looked into it. I have my hands full
with more pressing issues than overhauling the build system.
--
Cheers,
Dave Hart
what's documented. I think I'll go with the documented approach as I
am not concerned about the corner case. I don't know what tool deficiency
might trigger it, but I'm going to assume for now that it's good enough to
optimize build time only when --disable-depedency-tracking is used.
Cheers,
Dave Hart
On Sat, 30 Sept 2023 at 05:07, Jan Engelhardt wrote:
> On Saturday 2023-09-30 05:27, Dave Hart wrote:
>
> >I've added code to the ntp.org Makefile.am files to ensure the static
> >utility library libntp.a is up-to-date for each program that uses it, to
> >ensur
behavior.
Thanks in advance.
Dave Hart
rammers think, and Autotools for
simpler cases hide that entirely behind a blissfully simplified facade
of m4 macros invocation that many can use without understanding, until
things get slightly less boilerplate. Then out come the
pitchfork-wielding masses blaming their unknowable black boxes rather
than take the time to hump the Autoconf and Automake learning curve.
Grinchfully,
Dave Hart
eneric
but involves a separate PCH invocation to "compile" the headers, while
VC++ requires precomp.h be the first item included in each
participating file but doesn't require a separate compiler invocation
-- the first one that can use the precomp.pch generates it.
The compile-time savings can be relatively huge. Support in Automake
would be lovely and I'd be happy to help test any patches.
Cheers,
Dave Hart
cd eq_ss
make install
Cheers,
Dave Hart
endif
>
> CLEANFILES = $(noinst_SCRIPTS) $(noinst_PLOTS)
>
> EXTRA_DIST = $(noinst_PLOTS) $(noinst_DATA) $(noinst_R)
Perhaps try adding $(noinst_SCRIPTS) to EXTRA_DIST? Just a stab in
the dark without looking at the manual...
Cheers,
Dave Hart
are using systems where GNU is not built-in, and
would be negatively impacted by the additional prerequisite required
to build NTP.
However, as long as this experimentation with requiring GNU make is
done in an Automire fork and not Automake, I have no qualms greater
than concern for maintainer attention to Automake fading over time in
favor of Automire.
Cheers,
Dave Hart
y ntpd and its prerequisite directories
components build, and I agree again. If anyone knows of examples of
non-recursive Makefile implementations that manage to preserve the
recursive make property of being able to make in a subdir to make a
subset, please share so we can learn from their pioneering.
Cheers,
Dave Hart
utomake is used in the
wild, not always in purely free software scenarios and not only by
developers. Automake-produced makefiles are used by end users
building from source with no interest in developing software.
Cheers,
Dave Hart
packages uses Automake. Doing it with an Automake fork called
Automire wouldn't be such a problem, but Stefano probably doesn't find
forking appealing for a number of sound reasons.
Thanks for the choice to support use of Automake by non-GPL packages,
and for hearing the concerns of a maintainer of such a package.
Cheers,
Dave Hart
o use Autoconf and
Automake, likely has a different perspective which might well matter
more than mine.
Cheers,
Dave Hart
orrection if my facts are confused. I'm
certainly unclear on the differences between sources.redhat.com and
sourceware.org.
Cheers,
Dave Hart
st be included in the
Makefile.am files using Automake's automatic dependency tracking.
Cheers,
Dave Hart
dir)/scripts/test/install/bin/something --or --other
That may be more straightforward than portably modifying the
environment for submakes.
Cheers,
Dave Hart
en the up-to-date generated sources can be transported (such as via
make dist, or committing to SCM) to the cross-build environment.
Cheers,
Dave Hart
he
depth restriction. Bonus points will be given for not requiring the
developer renaming/removing headers to manually trigger the mechanism.
;)
Below is our depsver.mf fragment [1], with comments that may well be
more accurate than my recollection above.
Cheers,
Dave Hart
[1] depsver.mf:
$(DEPD
e mechanism.
;)
Below is our depsver.mf fragment [1], with comments that may well be
more accurate than my recollection above.
Cheers,
Dave Hart
[1] depsver.mf:
$(DEPDIR)/deps-ver: $(top_srcdir)/deps-ver
@[ -f $@ ] || \
cp
Hi Ralf,
On Thu, Mar 31, 2011 at 05:28 UTC, Ralf Wildenhues wrote:
> Hello Dave,
>
> * Dave Hart wrote on Wed, Mar 30, 2011 at 11:06:02PM CEST:
>> Right, one approach would be to run a dist-hook which strips all
>> resource forks from distdir files.
>>
>> An
ke could round-trip to remove them on Darwin (tar, extract with
resource forks named ._filename, find | xargs to rm the ._* files, tar
again).
Cheers,
Dave Hart
hat have them (and not break on systems without) by
using m4_ifdef to conditionalize the use. For example, this is how
ntp-dev enables Automake's silent rules generation without requiring
automake 1.11, which was the first release to provide AM_SILENT_RULES:
m4_ifdef(
[AM_SILENT_RULES],
[AM_SILENT_RULES([yes])]
)
Cheers,
Dave Hart
reference once and get on with more important
things than remember which combination of overrides I need at
configure time.
Cheers,
Dave Hart
$(STATIC_RESOLV)
endif
^ one word
If you have more than the hypothetical mytestprog in EXTRA_PROGRAMS
which require the additional library, use simply LDADD instead of
mytestprog_LDADD.
Cheers,
Dave Hart
On Tue, Jan 18, 2011 at 19:30 UTC, Ralf Wildenhues wrote:
> * Dave Hart wrote on Tue, Jan 18, 2011 at 09:49:02AM CET:
>> While you're waiting for that,
>> perhaps you could pursue the problem I
>> did take the time to provide a reduced test case for in November:
>>
h doesn't support AM_COND_IF
conditionalization of AC_CONFIG_FILES.
I am annoyed no one has taken the time to follow up after I took the
time to produce a reduced test case illustrating the automake
misbehavior, and each time I see a request for a reduced repro, I
wonder what I might have done wrong in anticipating the request and
providing the reduced test case in the initial report.
Cheers,
Dave Hart
license.
Cheers,
Dave Hart
On Sun, Dec 19, 2010 at 14:13 UTC, Ralf Wildenhues
wrote:
> * Dave Hart wrote on Sun, Dec 19, 2010 at 02:47:58PM CET:
>> On Sun, Dec 19, 2010 at 10:48 UTC, Ralf Wildenhues wrote:
>> > * Dave Hart wrote on Sat, Dec 18, 2010 at 07:57:13PM CET:
>> >> m4_ifndef([AM_C
On Sun, Dec 19, 2010 at 10:48 UTC, Ralf Wildenhues
wrote:
> Hi Dave,
> * Dave Hart wrote on Sat, Dec 18, 2010 at 07:57:13PM CET:
>> m4_ifndef([AM_COND_IF], [AC_DEFUN([AM_COND_IF],
>> [m4_ifndef([$1_TRUE],
>> [m4_fatal([$0: no such condition "$1"])])
On Sat, Dec 18, 2010 at 18:28 UTC, Dave Hart wrote:
> How is this for a AM_COND_IF that works at the m4sh level on older Automake:
I did not properly integrate Ralf's latest AM_COND_IF changes
considering Stefano's feedback about _AM_COND_VALUE_foo on older
Automake. 3rd t
[else
$3
])dnl
fi[]dnl
])])
I do not know the difference between m4_default and m4_n usage here,
I'm just applying the latest AM_COND_IF changes. If this code is not
appropriate for Automake prior to 1.11, please let me know.
Cheers,
Dave Hart
On Sat, Dec 18, 2010 at 11:56 AM, Ralf Wildenhues
wrote:
> Hello Dave,
>
> * Stefano Lattarini wrote on Sat, Dec 18, 2010 at 11:18:04AM CET:
>> On Saturday 18 December 2010, Dave Hart wrote:
>> > I'd like a package I depend on to use AM_COND_IF, but it does not want
quot;])])dnl
if _AM_COND_VALUE_$1; then
m4_default([$2], [:])
m4_ifval([$3],
else
$3
])dnl
fi[]dnl
])])
Thanks,
Dave Hart
On Fri, Nov 26, 2010 at 2:23 AM, Dave Hart wrote:
> 1. Unpack tar
> 2. configure
> 3. make
>
> Assuming success so far, then proceed to:
>
> 4. patch
Sorry, since you are modifying a .m4:
5. autoreconf
6. configure
7. make
You may be able to skip autoreconf, I'
ld be able to see your steps lead to trouble, and be more
willing to listen when you are told exactly what your problem is and
how to get around it.
1. Unpack tar
2. configure
3. make
Assuming success so far, then proceed to:
4. patch
5. make
Enjoy the journey,
Dave Hart
unicode_files)
>
> does ? Note that having that rule is not sufficient on linux (that is, even
> if $(EXEEXT) 'should' (but not 'must', as .exe suffix is not necessary) be
> added on widnows, it does not work on linux)
In that case you may need to add cmap_tounicode.c to BUILT_SOURCES,
leaving cmapdump out of same.
Cheers,
Dave Hart
bopts required by the subpackage? How
might I convince in-the-field Autoconf and Automake to stop fighting
amongst the packages over which owns subproj/libopts/Makefile? Can
you help me in my quest to stop grepping Makefiles before kicking off
a "make distcheck"? :)
Thanks for your time,
Dave Hart
y are you reporting this to the Automake mailing list? Ralf kindly
pointed you in the right direction, and asked you to provide details
_if_ you still think Automake is in a position to help. I don't see
you suggesting what Automake should be doing differently, instead, I
see a pax bug report sent to the Automake list.
Grumpily,
Dave Hart
venting this scheme, and I may have missed
an important part.
Cheers,
Dave Hart
On Tue, Aug 31, 2010 at 09:57 UTC, someone
wrote:
> But my Makefile is also removed :-(
> So, I need to call the configure script to build it again.
./config.status will regenerate the Makefile without a full configure run.
Cheers,
Dave Hart
you have not explained to the list why you feel the wierd
structure is warranted. Why don't you get things going the way that's
recommended, first, get some experience, and then starting making
dictates that break POLA after you're less likely to be shooting
yourself in the foot?
Cheers,
Dave Hart
would be something
like:
CPPFLAGS=$SAVED_CPPFLAGS -I$loop_dir
AC_COMPILE_IFELSE(
AC_LANG_PROGRAM(
[[
#include "openssl/err.h"
#include "openssl/rand.h"
]],
[[
ERR_load_crypto_strings();
]]
),
[ break ],
[]
)
Cheers,
Dave Hart
ill probably find bliss down the road of AC_COMPILE_IFELSE in a
loop that tries first with no additional -I, then with each of a list
of possible include directories, and adds the resulting -I directive
to a *CPPFLAGS variable while still respecting any user CPPFLAGS.
Cheers,
Dave Hart
st of directories for the needed .h, rather than simply
/usr/local/include.
Instead of "my project needs -I/foo/include on system bar", I suggest
"my project needs to find the correct foo.h on all systems".
Cheers,
Dave Hart
put, because it invokes
the compiled binary from $PATH if it is not in the current directory,
and we invoke it in the source directory (so that we can distribute
the .texi and most users and even developers then don't need the
latest Autogen to build NTP).
Cheers,
Dave Hart
A.K.A. h...@ntp.org
[
On Thu, Dec 17, 2009 at 22:29 UTC, Joakim Tjernlund wrote:
> AM_CONDITIONAL seems to be an automake 1.11 feature
You're running up against something else. AM_CONDITIONAL goes back
some time, and has worked splendidly for the NTP reference
implementation built using Automake 1.10.
Chee
50 matches
Mail list logo
