Re: missing help2man

Karl Berry wrote: > Sorry, I still do. I don't see that texinfo is doing anything different > than (say) coreutils, wrt help2man. Coreutils includes a copy of help2man with the distribution image so that it will always be available. Whether perl is available to run it is another story. Bob

Re: generated Makefile wants to run missing after configure (broken --disable-dependency-tracking?)

Vincent Lefevre wrote: > Bob Proulx wrote: > > But if you can't set the time on files then that won't work. > > That's precisely the problem: "touch" does not work, except for setting > mtime to the *current* time. That was why I posted the workaround

Re: generated Makefile wants to run missing after configure (broken --disable-dependency-tracking?)

Vincent Lefevre wrote: > The file system is a vfat, so that after de-archiving the tarball, the > timestamps are incorrect (the mtime can't be set back in the past). I think the best and easiest workaround is to set all of the file times to the same time. Then make will consider them up to date.

Re: My code got autolicensed...

Polarina wrote: > The automake and friends automatically licensed my code with GPLv2 (They > added the COPYING file with that license) when I wanted GPLv3. What > gives? I'm using version 1.10. > $ automake --add-missing --copy At the time that automake-1.10 was released GPLv2 was the appropri

Re: failure in "colorful tests"

Ralf Wildenhues wrote: > Agreed. Thanks. I've applied the patch below. Thanks! > HP-UX 10.20 - - + > HP-UX 11.23 - - + This really confused me because I was getting color. So I went back and looked at things closely and I realized why. Quite some years ago I "

Re: failure in "colorful tests"

Ralf Wildenhues wrote: > +case $TERM in > +dumb) exit 77;; > +esac > ... > Thanks! Do we need to guard against other TERM settings, too? Hmm... I was thinking more along the lines of this patch instead. I don't think the test should be skipped. I think it should be made independent of the invo

Re: ylwrap proposition

Ralf Wildenhues wrote: > It seems there are people stumbling over the "simple" renaming, see > bug 503 in Automake's GNATS: > I am not sure it is possible to predictably produce one solution that will work for everyone. I think tha

Re: ylwrap proposition

Sergey Poznyakoff wrote: > Bob Proulx ha escrit: > > I believe that it is very well known and well propagated knowledge > > that the strings yy and YY are often used to mutate the result into a > > unique identifier. Almost all practical documentation uses sed > > s

Re: ylwrap proposition

Sergey Poznyakoff wrote: > Ralf Wildenhues ha escrit: > > Can s/yy/.../ change anything unintended? E.g., do we need to ensure it > > only changes words beginning with yy? > > In theory it could, for example if the programmer used identifiers > beginning with, or containing `yy'. However, I can h

Re: automatic update Makefile.am -> Makefile.in -> Makefile no longer working

Hi Bruno, Bruno Haible wrote: > Or is there an "obvious" workaround that I'm not seeing? I don't know how obvious this is because I am in many ways not very knowledgeable about the internal workings of the autotools but in the output was a clue. > aclocal.m4:14: error: this file was generated fo

Re: automake 1.9.6 build failure

Mike Owens wrote: > Ralf Wildenhues wrote: > > Mike Owens wrote: > > > I am maintaining my copy of automake in a subversion vendor branch. I > > > have encountered a problem that is very difficult for me to diagnose. > > > The copy in subversion will not build on Solaris. The tarball will. > > > >

Re: A problem (bug) in automake (1.10 and earlier version) + patch

Peter Breitenlohner wrote: > The original message below was held for moderator approval because I had not > (yet) subscribed to this list. There was no need to send your message a second time. Your first message was delivered. Looking at the logs I see that your original message was received at

Re: automake-1.9.6 make check failures on HP-UX 11.11

Bob Proulx wrote: > I am using autoconf-2.59 right now but do have 2.59d available. But I > will pull the CVS autoconf and automake and if the patch is not > present will apply it and repeat the test. Having upgraded to m4-1.4.4, make-3.81, to CVS autconf, and to CVS automake, here is t

Re: automake-1.9.6 make check failures on HP-UX 11.11

Hi Ralf, Ralf Wildenhues wrote: > Do > cd tests > env VERBOSE=x TESTS="acloca17.test java.test missing.test \ > missing2.test obsolete.test" make -e check Here is the output from the current automake-1.9.6. One issue might be my version of GNU m4-1.4. I need to update it too. Actuall

automake-1.9.6 make check failures on HP-UX 11.11

On HP-UX 11.11 with perl 5.6.1 building and testing automake-1.9.6 produced the following failures: make check 2>&1 | tee log ...lots and lots of output...and 59 minutes later... = 5 of 514 tests failed (53 tests were not run) Please report to bug-au