spec file is (intended to be) hand-written, or at
least hand-tuned; so decisions about which directories to
list in it are made by a human, not by code.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
It must be said that they would have sounded bette
ion *not* as a criticism, but merely as a data point relevent
to the version-check question. It's perfectly ok to add new
features that require the new program version to process them;
it's a disregard for *backward* compatibility that's antisocial
behaviour, and again, I'm not acc
because I chose to CVSify the package.
Maybe this isn't Karl's responsibility; and I'm not sure what, if
anything, can be done about it in any case; but it seemed worth
bringing up while we're on the subject.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROT
target for making the texinfo-based subset of the
HTML might indeed be "texinfohtml", and correspondingly for
install and uninstall. But that should be purely a detail of
automake's implementation:
html: texinfohtml whatever_other_html_targets_make_sense
It need not, a
be that the
right aclocal program is still finding the old 1.4 macros. I
don't know how to check for that, but take a look at aclocal.m4,
to see if you can find anything that indicates which version of
the Automake-related macros aclocal picked up.
--
| | /\
|-_|/ > Eric Siegerman, To
0: using the `aclocal' command, and then run `automake' again.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
It must be said that they would have sounded better if the singer
wouldn't throw his fellow band members to the ground and toss the
drum kit around during songs.
- Patrick Lenneau
it :-)
[Usually I avoid me-too posts, but in this case it seems
warranted.]
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
It must be said that they would have sounded better if the singer
wouldn't throw his fellow band members to the ground a
On Thu, Feb 05, 2004 at 10:49:07AM +1100, Robert Collins wrote:
> On Thu, 2004-02-05 at 10:36, Eric Siegerman wrote:
>
> > I believe this fails on the following corner case. Suppose the
> > date ordering is like this (with data.h being the oldest):
> > da
d "foo" is suppressed.
This scales to multiple outputs too, but it gets a bit ugly, since
one has to impose a serial ordering on all of them:
data.c data.h data.x data.y: data.foo
foo data.foo
data.h: data.c
data.x: data.h
data.y: data.x
I h
of the subpackage to be buildable,
you have to defeat this behaviour (or rather, you had to do so
the last time I tried it), by:
AC_CONFIG_AUX_DIR([.])
See http://www.mail-archive.com/[EMAIL PROTECTED]/msg08005.html
for the gory details.
--
| | /\
|-_|/ > Eric Siegerman, Tor
hardwired,
it'll frustrate some users who want it the other way; and unless
all levels are hardwired the same way, it'll confuse and
frustrate *most* users.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
It must be said that they would have so
ence to undefined
function bazzle(), but nothing *following* foo.o on the command
line can satisfy that reference. You get an "undefined" error.
But with:
ld foo.o -lbar
the linker knows, while searching -lbar, that it needs bazzle().
The situation with two libraries is s
help
avoid them.
The situation seems very similar to that of Autoconf's
config.cache. Those files used to be kept between runs by
default, but it was decided that doing so causes too many
problems, so now the default is to throw them away; the user must
ask for the less-safe behaviour.
--
| |
ly runs if the first one succeeded, runs the tests
while ignoring errors.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
When I came back around from the dark side, there in front of me would
be the landing area where the crew was, and the Earth, all in the vi
the values into
it. Then call the script from the Makefiles, either explicitly
or via an implicit rule.
> -- and sometimes I need to do it to a file where there isn't a
> Makefile in that directory.
So add one...
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL P
DIRS = ... ...
SUBDIRS = $(UNCONDITIONAL_SUBDIRS) @MAKE_SNTP@
DIST_SUBDIRS = $(UNCONDITIONAL_SUBDIRS) sntp
That won't solve your other problems of course.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
When I came back around from the dark side, the
l supported, but more or
less deprecated.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
A distributed system is one on which I cannot get any work done,
because a machine I have never heard of has crashed.
- Leslie Lamport
On
some systems it's called "md5sum"; other systems might not have
it at all. But "cmp" is as sure to be there as are "cat" and
"ls".
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
A distributed system is one on which I cannot get any work done,
because a machine I have never heard of has crashed.
- Leslie Lamport
On Fri, Feb 14, 2003 at 06:41:04PM +, Dr. David Kirkby wrote:
> Eric Siegerman wrote:
> AC_HAVE_HEADERS(gsl/gsl_sf_ellint.h,[gsl_inc_count=$(($gsl_inc_count +
> 1))])
Right; "$((expr))" -- "arithmetic expansion" it's called in
ksh(1) -- is another nonstandar
der* -- but it understands Java better than I believe make
(and thus automake) ever will. So one possibility might be to
pull the code for the task out of ant, and turn it into a
standalone Java-compiler driver; then call it from a Makefile, as
the gods and Stuart Feldman intended :-) A few other
rojects where you need a different version, name it
explicitly:
/usr/local/stow/automake-1.4/bin/automake [options]
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
Just Say No to the "faceless cannonfodder" stereotype.
- http://www.ainurin.net/ (an Orc site)
intermediate is foo.c (leaving aside the even-more-transient
y.tab. silliness); foo.o and foo.h are both legitimate final
products of the rule.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
Just Say No to the "faceless cannonfodder" stereotype.
- http://www.ainurin.net/ (an Orc site)
quickly become
a habit ... well, fairly quickly; the first couple of wasted
builds are a great inducement to learning :-)
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
Just Say No to the "faceless cannonfodder" stereotype.
- http://www.ainurin.net/ (an Orc site)
* * * * * *
> _EOF_
G!
A simple warning message, please:
${filename}: WARNING: ${variable} appears in conditional text
The rest belongs in the manual, *not* on stderr.
>
> sleep 30
>
*Shudder*
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTEC
sn't exist
> yet at that point]
As a longer-term solution, perhaps some of those checks should be
done, not by Automake itself, but by the generated distcheck
target; specifically, checks for files like README that aren't
needed by the build.
--
| | /\
|-_|/ > Eric Siegerman, To
On Tue, Sep 03, 2002 at 11:31:49PM +0200, Alexandre Duret-Lutz wrote:
> >>> "Eric" == Eric Siegerman <[EMAIL PROTECTED]> writes:
> Eric> *please* consider making it an extra subdirectory
> Eric> level instead of a filename component, as in Josef's
&g
f necessary)
- It makes the directory listings a lot easier to read; one
doesn't have to filter out all of (what is to them) the noise
Disadvantage:
- It breaks makewhatis
But using filename components -- "foo.xx.1" -- breaks the main
"man" functionality, or e
E again, you maintain end users' isolation from
the autotools.
Your core developers will still be working from your CVS repo ...
but then, by the above argument, they'll have installed the
correct autotools versions.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL
le. That's spread widely enough by now that
it shouldn't confuse anyone.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
Anyone who swims with the current will reach the big music steamship;
whoever swims against the current will perhaps reach the source.
- Paul Schneider-Esleben
ent. If you
"simplify" it, someone who wants to add a packager with a funny
interface will have to write a glue script, and many (most? all?)
packages will have to distribute same. Not exactly a
simplification...
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PRO
ase
builder's system of course).
N.B.: I called the new variables foo_COMPRESSOR, to leave room
for a foo_DECOMPRESSOR. "make dist" doesn't need the latter, but
the autoconf foo-figure-outer macros should be (able to be) fully
generalized.
--
| | /\
|-_|/ > Eric S
ith which
> automake was built.
Why is that onerous?
It is *extremely* onerous to have two packages, A and B, which
are intended to interoperate, each of which requires a different
version of program X to be first in the path.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.
the recurring "How to make Make make all my
source files" question
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
Anyone who swims with the current will reach the big music steamship;
whoever swims against the current will perhaps reach the
On Sun, Jul 07, 2002 at 03:46:14PM -0600, Tom Tromey wrote:
> If this is a popular thing to do, perhaps someone could implement
> direct pod support [...]
Is there any documentation of Automake internals, and/or the
funny metalanguage used for writing such support?
--
| | /\
|-_|/ &g
directory.
Try one of these (but do NOT do both; that wouldn't work either):
1. Say
templatedir = ${pkgdatadir}
template_DATA = templates/test.share
2. Create templates/Makefile.am, containing:
templatedir = ${pkgdatadir}/templates
template_DATA = tes
messages
in the queue when he took it over, dating back as far as 2000.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
Anyone who swims with the current will reach the big music steamship;
whoever swims against the current will perhaps reach the source.
- Paul Schneider-Esleben
might do the trick:
DISTCLEANFILES = ${AUTOGEN}
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
"Outlook not so good." That magic 8-ball knows everything!
I'll ask about Exchange Server next.
- Anonymous
et's see what happens when AM_MAINTAINER_MODE is used:
>
4. The package just builds.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
"Outlook not so good." That magic 8-ball knows everything!
I'll ask about Exchange Server next.
- Anonymous
e to remove the Makefile last. This avoids the problem
> since "configure" is not removed. But once we have "./configure
> --clean", I don't see the point of having "./config.status --clean".
> As far as I can see, anybody who wants to invok
interrupted the "make distclean";
> Paul> if there was more work to do, another "make distclean" would
> Paul> still do it.
>
> IIUC, you're saying config.status --clean should end with the top
> level. I agree.
And, if asked to clean a subdirectory, should c
n the build procedure does not ultimately involve
compiling to $(OBJEXT) files, and then linking?
Thanks in advance.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
"Outlook not so good." That magic 8-ball knows everything!
I'll ask about Exchange Server next.
- Anonymous
akefile is missing.
Yes, please!
> If "rm Makefile" is the the last thing that "make distclean" does,
i.e. autoconf guarantees that Makefile be the last file listed
in @configure_targets@, and Automake put that macro at the end
of distclean-local or whatever it's called,
> then this alternate proposal is more robust than the method you
> proposed.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
"Outlook not so good." That magic 8-ball knows everything!
I'll ask about Exchange Server next.
- Anonymous
d
compatibility is less of an absolute requirement.
- On the other hand, it probably DOES make sense to use
autoconf with cons, and you can probably start doing so in
small ways without a lot of effort. Simply identify a few
system-dependent facts that autoconf can figure out mo
On Thu, May 31, 2001 at 08:37:07PM +0100, Richard Boulton wrote:
> On Thu, May 31, 2001 at 02:29:37PM -0400, Eric Siegerman wrote:
> > So what *is* harmful about recursive makes (besides the admitted
> > performance penalty)?
>
> Read "Recursive make considered harmful
remake just a single module, as
opposed to the entire project?
So what *is* harmful about recursive makes (besides the admitted
performance penalty)?
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
With sufficient thrust, pigs fly just fine. However, this i
On Wed, May 23, 2001 at 06:49:46PM +0100, Gary V . Vaughan wrote:
> On Tuesday 22 May 2001 6:43 pm, Eric Siegerman wrote:
> > The bootstrap could be a simple shell script that makes no
> > attempt to optimize out unnecessary actions -- after all, you
> > would rarely be runn
a simple shell script that makes no
attempt to optimize out unnecessary actions -- after all, you
would rarely be running it unless all the actions *were*
necessary.
> REALLYREALLYCLEAN?
> CLEANOFTHECLEAN?
> :-)
PRISTINE
(No smiley; I mean it.)
--
| | /\
|-_|/ > Eric
t;.
Of course, to abide by the broken gnits rule you refer to, it'll
have to the be the major release number whose evenness matters:
1.x is development; 2.x stable.
(That the gnits two-number rule is "broken" is only my opinion,
of course, but that opinion was formed directly
t was
capable of removing a /usr/local!
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
to me, Charlie Brown represented the courage to be sincere in the face of
ridicule. he was NOT a loser.
thank you, Mr. Schulz.
- Robert C. Mayo
try to do the Right
Thing (which, as others have pointed out, is impossible in
theory), but to make Automake work better with stow, which makes
the Right Thing trivial.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
to me, Charlie Brown represented the co
50 matches
Mail list logo
