Achim Gratz writes:
> In light of the fact that 2.71 again is not backwards compatible, that
> patch needs to be somewhat more extensive and include different
> WANT_AUTOCONF settings.
Something like this, which keeps the default autoconf version at 2.69
for the moment (and is untested right now).
Ken Brown via Cygwin-apps writes:
> On 12/2/2021 5:15 AM, Jan Nijtmans via Cygwin-apps wrote:
>> Somewhere in cygport, a check is done for the autoconf version, please
>> change this check to allow autoconf 2.71 (as well as 2.59 and 2.69).
>> Then I can put back the "cygautoreconf" line in tcl.cygp
On 12/2/2021 8:32 AM, Corinna Vinschen via Cygwin-apps wrote:
On Dec 2 14:18, ASSI wrote:
As I said, I haven't looked at it in any detail, but it seems that
autoconf is already multi-version, so I guess it would be possible to
introduce an autoconf2.7 package in addition to the existing two.
Th
On Dec 2 14:18, ASSI wrote:
> Jan Nijtmans via Cygwin-apps writes:
> > My 2c : Cygwin should - at least - allow people to install autoconf-2.71
> > and - as long as the packages are prepared for it - things shouldn't break.
>
> As I said, I haven't looked at it in any detail, but it seems that
>
On 12/2/2021 5:15 AM, Jan Nijtmans via Cygwin-apps wrote:
Somewhere in cygport, a check is done for the autoconf version, please
change this check to allow autoconf 2.71 (as well as 2.59 and 2.69).
Then I can put back the "cygautoreconf" line in tcl.cygport.
You can do this locally until someon
Jan Nijtmans via Cygwin-apps writes:
> My 2c : Cygwin should - at least - allow people to install autoconf-2.71
> and - as long as the packages are prepared for it - things shouldn't break.
As I said, I haven't looked at it in any detail, but it seems that
autoconf is already multi-version, so I g
Op do 2 dec. 2021 om 11:41 schreef Corinna Vinschen via Cygwin-apps:
> Nope, I didn't. Make that:
>
> On Dec 2 08:23, ASSI wrote:
Indeed, sorry!. I stripped a little bit too much from the message ...
Regards,
Jan Nijtmans
On Dec 2 11:15, Jan Nijtmans via Cygwin-apps wrote:
> Op do 2 dec. 2021 om 10:22 schreef Corinna Vinschen via Cygwin-apps:
Nope, I didn't. Make that:
On Dec 2 08:23, ASSI wrote:
> > > Most distros still package 2.69 or even earlier and that includes some
> > > substantial rolling release dis
Op do 2 dec. 2021 om 10:22 schreef Corinna Vinschen via Cygwin-apps:
> > Most distros still package 2.69 or even earlier and that includes some
> > substantial rolling release distros. As long as these guys don't use
> > the newer version it seems unlikely that we would actually need it, plus
> >
On Dec 2 08:23, ASSI wrote:
> Brian Inglis writes:
> >> How likely is it that they actually rely on that version already?
> >
> > Somewhat likely for some GNU packages and gnulib macros that specify
> > version prereqs: AC_PREREQ is used in 80 packages I have sources for.
>
> Most distros still p
Brian Inglis writes:
>> How likely is it that they actually rely on that version already?
>
> Somewhat likely for some GNU packages and gnulib macros that specify
> version prereqs: AC_PREREQ is used in 80 packages I have sources for.
Most distros still package 2.69 or even earlier and that includ
On 2021-12-01 12:56, Achim Gratz wrote:
Marco Atzeri via Cygwin-apps writes:
anyone working or planning to take over the Autoconf ?
I haven't, but looking at the packages I picked up maybe I should.
The 2.71 version seems becoming popular in some package source code.
How likely is it th
Marco Atzeri via Cygwin-apps writes:
> anyone working or planning to take over the Autoconf ?
I haven't, but looking at the packages I picked up maybe I should.
> The 2.71 version seems becoming popular in some package source code.
How likely is it that they actually rely on that version already
I am sorry for the raw email address.
>-Original Message-
>From: cygwin-apps
>Sent: Wednesday, June 28, 2006 11:37 PM
>To: Cygwin-Apps Mailing List; Cygwin Mailing List
>Subject: FW: Autoconf 2.60 released
>
>
>-Original Message-
>From: Paul Eggert
>Paul Eggert
>Sent: Monday, June
On Fri, 4 Jul 2003, Jari Aalto+list.cygwin-apps wrote:
>
> I'm tyring to port some webdav stuff, but it needs new autoconf. The
> newest seems to be 2.57. Could we get an update or is there problems
> with new autoconf versions?
Install the 'autoconf-devel' package and put `/usr/autotool/devel/bi
"Charles Wilson" <[EMAIL PROTECTED]> wrote:
> Yeah, I've noticed that too. Perhaps I outsmarted myself:
> the wrapper script never actually "exits"
> -- it *execs* the real autoconf/make/whatever.
>
> So perhaps the trap doesn't get triggered when you exec.
Yep: that's what it is. I constructed
Conrad Scott wrote:
> The wrapper scripts for autoconf and autoheader use temporary files
> that they (are supposed to) remove on exit (using trap 0). But I tend
> to find *lots* of these directories in /tmp (e.g. /tmp/acX and
> /tmp/ahX). Just running autoconf or autoheader with no arg
Oops. Sorry for the crosspost. This actually belongs on the autoconf
mailing list. (Darned auto-complete put the wrong address in for Corinna).
But, since we're here:
It looks like my recent reports about problems with autoconf were
incorrect. Akim has nicely pointed out that PIBKAC.
--Ch
Akim Demaille wrote:
> |1) text from inside an AC_HELP_STRING() macro was NOT placed in the
> |help section. Instead, it was just willy-nilly put into the script
> |itself. Since help text is not, in general, valid shell script,
> |this caused errors. Other AC_HELP_STRING()'s b
19 matches
Mail list logo
