The autoconf wrapper has been re-released to recognize the new autoconf
version 2.72 (with some modifications for Cygwin).
Multiple versions of Autoconf can be installed at the same time --
the autoconf wrapper choses among them.
--
--
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO
Autoconf Archive has been updated to the latest upstream release
2023.02.20 on Cygwin.
The GNU Autoconf Archive is a collection of more than 450 macros for
GNU Autoconf that have been contributed as free software by friendly
supporters of the cause from all over the Internet
Autoconf Archive has been updated to the latest upstream release
2023.02.20 on Cygwin.
The GNU Autoconf Archive is a collection of more than 450 macros for
GNU Autoconf that have been contributed as free software by friendly
supporters of the cause from all over the Internet
Autoconf Archive has been updated to the latest upstream release
2022.09.03 on Cygwin.
The GNU Autoconf Archive is a collection of more than 450 macros for
GNU Autoconf that have been contributed as free software by friendly
supporters of the cause from all over the Internet
Autoconf Archive has been updated to the latest upstream release
2022.09.03 on Cygwin.
The GNU Autoconf Archive is a collection of more than 450 macros for
GNU Autoconf that have been contributed as free software by friendly
supporters of the cause from all over the Internet
On 14/03/2022 22:15, Adam Dinwoodie wrote:
The latest version of Autoconf is 2.71, but the version detection
incorrectly considers 2.70 and higher as being the same as 2.59 and
lower for the purposes of specifying documentation directories. Correct
that, and make the version detection a bit
The latest version of Autoconf is 2.71, but the version detection
incorrectly considers 2.70 and higher as being the same as 2.59 and
lower for the purposes of specifying documentation directories. Correct
that, and make the version detection a bit more future-proof by parsing
out the actual
On Mon, Mar 14, 2022 at 07:05:20PM +, Jon Turney wrote:
> On 13/03/2022 20:44, Adam Dinwoodie wrote:
> > configure="${confdir}/configure"
> > confver=$(grep -m 1 'GNU Autoconf' ${configure} | cut -d ' ' -f 6)
> > + confver_maj=${confver%%.*
On 13/03/2022 20:44, Adam Dinwoodie wrote:
configure="${confdir}/configure"
confver=$(grep -m 1 'GNU Autoconf' ${configure} | cut -d ' ' -f 6)
+ confver_maj=${confver%%.*}
+ confver_min=${confver##*.}
+ if [ $confver_maj -ne 2 ]
+ then
+
The latest version of Autoconf is 2.71, but the version detection
incorrectly considers 2.70 and higher as being the same as 2.59 and
lower for the purposes of specifying documentation directories. Correct
that, and make the version detection a bit more future-proof by parsing
out the actual
2 -a $confver_min -ge 60 ] || [ $confver_maj -ge
> > 3 ]
>
> Great. Thanks.
>
> I think it would be acceptable to error on autoconf >=3.0, rather than
> assuming it's going to be autoconf 2.6+ compatible.
No problem, I'll respin now. I'd thought about doing exactly that, but
the c
On 11/03/2022 22:40, Adam Dinwoodie wrote:
The latest version of Autoconf is 2.71, but the version detection
incorrectly considers 2.70 and higher as being the same as 2.59 and
lower for the purposes of specifying documentation directories. Correct
that, and make the version detection a bit
The latest version of Autoconf is 2.71, but the version detection
incorrectly considers 2.70 and higher as being the same as 2.59 and
lower for the purposes of specifying documentation directories. Correct
that, and make the version detection a bit more future-proof by parsing
out the actual
On Sat, 19 Feb 2022 16:53:46 -0700, Brian Inglis
> On 2022-02-19 16:37, Lemures Lemniscati wrote:
> > On Sat, 19 Feb 2022 10:11:06 -0700, Brian Inglis
> >> On 2022-02-18 22:26, Lemures Lemniscati wrote:
> >>> On Fri, 18 Feb 2022 12:33:30 -0700, Brian Inglis
>
On 2022-02-19 16:37, Lemures Lemniscati wrote:
On Sat, 19 Feb 2022 10:11:06 -0700, Brian Inglis
On 2022-02-18 22:26, Lemures Lemniscati wrote:
On Fri, 18 Feb 2022 12:33:30 -0700, Brian Inglis
Any idea why autoconf tests for iconv now fail with undefined refs to iconv{_open,,_close}!
>>
On Sat, 19 Feb 2022 10:11:06 -0700, Brian Inglis
> On 2022-02-18 22:26, Lemures Lemniscati wrote:
> > On Fri, 18 Feb 2022 12:33:30 -0700, Brian Inglis
> >> Any idea why autoconf tests for iconv now fail with undefined refs to
> >> iconv{_open,,_close}! STC attached,
On 2022-02-18 22:26, Lemures Lemniscati wrote:
On Fri, 18 Feb 2022 12:33:30 -0700, Brian Inglis
Any idea why autoconf tests for iconv now fail with undefined refs to
iconv{_open,,_close}! STC attached, log, -E output. Tried also with -l iconv.
https://cygwin.com/cgi-bin2/jobs.cgi?srcpkg
On 2022-02-19 00:51, Lemures Lemniscati wrote:
About libisocodes 1.2.4, these patches (attached) may help cygport-build.
Thanks Lem,
The first gets that build running, I already updated the second based on
the checked in version.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
On Fri, 18 Feb 2022 12:33:30 -0700, Brian Inglis
> Any idea why autoconf tests for iconv now fail with undefined refs to
> iconv{_open,,_close}! STC attached, log, -E output. Tried also with -l iconv.
About libisocodes 1.2.4, these patches (attached) may help cygport-build.
Lem
On Fri, 18 Feb 2022 12:33:30 -0700, Brian Inglis
> Any idea why autoconf tests for iconv now fail with undefined refs to
> iconv{_open,,_close}! STC attached, log, -E output. Tried also with -l iconv.
https://cygwin.com/cgi-bin2/jobs.cgi?srcpkg=playground=3861
Hi, Brian.
This will succes
Any idea why autoconf tests for iconv now fail with undefined refs to
iconv{_open,,_close}! STC attached, log, -E output. Tried also with -l
iconv.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical
Autoconf Archive has been updated to the latest upstream release
2022-02-12 on Cygwin.
The GNU Autoconf Archive is a collection of more than 450 macros for
GNU Autoconf that have been contributed as free software by friendly
supporters of the cause from all over the Internet
Autoconf Archive has been updated to the latest upstream release
2022-02-12 on Cygwin.
The GNU Autoconf Archive is a collection of more than 450 macros for
GNU Autoconf that have been contributed as free software by friendly
supporters of the cause from all over the Internet
On 1/2/2022 12:22 PM, Marco Atzeri wrote:
On 05.12.2021 10:34, Achim Gratz wrote:
In order for cygport to work correctly when autoconf 2.71 is requested,
please pull the first commit (b25cb3faa) on my to-upstream branch into
upstream and release a new version. I'd appreciate if the full
On 05.12.2021 10:34, Achim Gratz wrote:
In order for cygport to work correctly when autoconf 2.71 is requested,
please pull the first commit (b25cb3faa) on my to-upstream branch into
upstream and release a new version. I'd appreciate if the full branch
would be pulled, these are all used by me
> On 12/5/2021 3:50 AM, Achim Gratz wrote:
> >
> > Autoconf has been updated to the latest upstream release 2.71, see the
> > packaging notes below. Additionally the automake wrapper has been
> > updated to the latest upstream version 15 (with some modifications for
&
On 2021-12-07 13:16, Ken Brown wrote:
[Redirected from the cygwin list,
https://cygwin.com/pipermail/cygwin/2021-December/250149.html]
On 12/7/2021 3:08 PM, Ken Brown wrote:
On 12/5/2021 3:50 AM, Achim Gratz wrote:
Autoconf upstream has stated that the 2.7x releases are not fully
backwards
[Redirected from the cygwin list,
https://cygwin.com/pipermail/cygwin/2021-December/250149.html]
On 12/7/2021 3:08 PM, Ken Brown wrote:
On 12/5/2021 3:50 AM, Achim Gratz wrote:
Autoconf upstream has stated that the 2.7x releases are not fully
backwards compatible. Cygwin therefore chose
On 12/5/2021 3:50 AM, Achim Gratz wrote:
Autoconf upstream has stated that the 2.7x releases are not fully
backwards compatible. Cygwin therefore chose to provide a new
autoconf2.7 package (keeping autoconf2.5 available) and modifying the
wrapper script to allow packaging systems to set
On 12/5/2021 3:50 AM, Achim Gratz wrote:
Autoconf has been updated to the latest upstream release 2.71, see the
packaging notes below. Additionally the automake wrapper has been
updated to the latest upstream version 15 (with some modifications for
Cygwin).
Great work, thanks for doing
In order for cygport to work correctly when autoconf 2.71 is requested,
please pull the first commit (b25cb3faa) on my to-upstream branch into
upstream and release a new version. I'd appreciate if the full branch
would be pulled, these are all used by me for quite some time already.
e33b0b7f1
Autoconf has been updated to the latest upstream release 2.71, see the
packaging notes below. Additionally the automake wrapper has been
updated to the latest upstream version 15 (with some modifications for
Cygwin).
GNU Autoconf is an extensible package of m4 macros that produce shell
scripts
Autoconf has been updated to the latest upstream release 2.71, see the
packaging notes below. Additionally the automake wrapper has been
updated to the latest upstream version 15 (with some modifications for
Cygwin).
GNU Autoconf is an extensible package of m4 macros that produce shell
scripts
Autoconf Archive has been updated to the latest upstream release
2021-02-19 on Cygwin.
The GNU Autoconf Archive is a collection of more than 450 macros for
GNU Autoconf that have been contributed as free software by friendly
supporters of the cause from all over the Internet
Autoconf Archive has been updated to the latest upstream release
2021-02-19 on Cygwin.
The GNU Autoconf Archive is a collection of more than 450 macros for
GNU Autoconf that have been contributed as free software by friendly
supporters of the cause from all over the Internet
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
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
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
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
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 loc
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
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
ntial rolling release distros. As long as these guys don't use
> > > the newer version it seems unlikely that we would actually need it, plus
> > > I don't see us spending time and effort debugging things that aren't
> > > even Cygwin specific.
>
> My 2c : Cygwin sho
ally need it, plus
> > I don't see us spending time and effort debugging things that aren't
> > even Cygwin specific.
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.
If I install autoconf-
ing things that aren't
> even Cygwin specific.
>
> > After that version released in January, I've only had to patch one
> > package so far, which specified it in August, and they later reduced
> > it after discussion with distro package maintainers:
> >
> > $
ary, I've only had to patch one
> package so far, which specified it in August, and they later reduced
> it after discussion with distro package maintainers:
>
> $ grep 'AC_PREREQ(\[2\.[0-9]\+\])' */*.patch
> bison/bison-3.7.90-revert-autoconf-upgrade.patch:-AC_PREREQ([2.71])
>
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
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 v
Hi Guys,
anyone working or planning to take over the Autoconf ?
The 2.71 version seems becoming popular in some package source code.
Regards
Marco
On 2021-10-02 10:35, Brian Inglis wrote:
On 2021-10-02 08:13, Ken Brown via Cygwin-apps wrote:
On 10/2/2021 1:48 AM, Brian Inglis wrote:
On 2021-10-01 22:15, Achim Gratz wrote:
Brian Inglis writes:
As autoconf requires: autoconf2.1 autoconf2.5 bash sed, I believe that
would be the more
On 2021-10-02 08:13, Ken Brown via Cygwin-apps wrote:
On 10/2/2021 1:48 AM, Brian Inglis wrote:
On 2021-10-01 22:15, Achim Gratz wrote:
Brian Inglis writes:
As autoconf requires: autoconf2.1 autoconf2.5 bash sed, I believe that
would be the more appropriate place for an autoconf-archive
On 10/2/2021 1:48 AM, Brian Inglis wrote:
On 2021-10-01 22:15, Achim Gratz wrote:
Brian Inglis writes:
As autoconf requires: autoconf2.1 autoconf2.5 bash sed, I believe that
would be the more appropriate place for an autoconf-archive
requirement, otherwise cygport would have to require
On 2021-10-01 22:15, Achim Gratz wrote:
Brian Inglis writes:
As autoconf requires: autoconf2.1 autoconf2.5 bash sed, I believe that
would be the more appropriate place for an autoconf-archive
requirement, otherwise cygport would have to require it, which is not
so obvious.
No. If a build
Brian Inglis writes:
> As autoconf requires: autoconf2.1 autoconf2.5 bash sed, I believe that
> would be the more appropriate place for an autoconf-archive
> requirement, otherwise cygport would have to require it, which is not
> so obvious.
No. If a build needs autoconf-archive
macro: AX_CODE_COVERAGE
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation."
CI scallywag setup does not install nor does cygport nor autoconf
require autoconf-archive so packages have to include in BUILD_REQUIRES.
As autoconf requires: autoconf2.1 a
If this token and others are legitimate, please use m4_pattern_allow.
> See the Autoconf documentation."
>
> CI scallywag setup does not install nor does cygport nor autoconf
> require autoconf-archive so packages have to include in BUILD_REQUIRES.
>
> As autoconf requ
Hi folks,
Autotools needs m4 macros in autoreconf-archive to config for gcov and
other dependencies or build fails with e.g.
"configure.ac:33: error: possibly undefined macro: AX_CODE_COVERAGE
If this token and others are legitimate, please use m4_pattern_allow.
See the Aut
On 2020-11-18 11:19, Biswapriyo Nath via Cygwin wrote:
I am not familiar with newlib. Please feel free whatever you want to
do with my previously provided diff. Also my previous question is
unanswered.
Cygwin provides autoconf 2.69 but it's what builds the package that counts, also
perhaps
I am not familiar with newlib. Please feel free whatever you want to
do with my previously provided diff. Also my previous question is
unanswered.
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:
On Nov 18 15:06, Biswapriyo Nath via Cygwin wrote:
> Currently the autoconf files in newlib-cygwin repo are in 2.64 version
> but the latest autoconf package is version 2.69. So, autoreconf
> command shows errors. Possible diff attached.
We can update to 2.68, but not 2.69. Newlib still
Currently the autoconf files in newlib-cygwin repo are in 2.64 version
but the latest autoconf package is version 2.69. So, autoreconf
command shows errors. Possible diff attached.
diff --git a/config/override.m4 b/config/override.m4
index 52bd1c3..1c3c298 100644
--- a/config/override.m4
+++ b
=config.sub;hb=HEAD'
-/bin/chmod a+x config.sub
-fi
/usr/bin/aclocal --force
/usr/bin/autoconf -f
/bin/rm -rf autom4te.cache
diff --git a/winsup/config.guess b/winsup/config.guess
deleted file mode 100755
index 872b96a16..0
--- a/winsup/config.guess
+++ /dev/null
@@ -1,1537 +0,0 @@
-#! /bin
This now required as cygwin_build is defined in terms of
target_builddir.
(Note that in other subdirectories, the autoconf variable
target_builddir is AC_SUBST-ed as a side-effect of using a macro from
winsup/acinclude.m4, which is perhaps less than ideal)
---
winsup/testsuite/Makefile.in | 1
Remove autoconf variable DLL_NAME, which has a constant value which is
only used in one place.
---
winsup/cygwin/Makefile.in | 4 ++--
winsup/cygwin/configure.ac | 3 ---
2 files changed, 2 insertions(+), 5 deletions(-)
diff --git a/winsup/cygwin/Makefile.in b/winsup/cygwin/Makefile.in
index
The autoconf variable all_host is used to make building of the stub
library used by the testsuite conditional on not cross-compiling.
Make it unconditional, so we will notice if it's broken when
cross-compiling.
---
winsup/cygserver/configure.ac | 11 ---
winsup/cygwin/Makefile.in
Remove autoconf variable INSTALL_LICENSE, which has a constant value
which is only used once.
---
winsup/Makefile.in | 4 +---
winsup/configure.ac | 4
2 files changed, 1 insertion(+), 7 deletions(-)
diff --git a/winsup/Makefile.in b/winsup/Makefile.in
index 148d98531..dc1c0 100644
The following packages have been uploaded to the Cygwin distribution:
* autoconf-archive-2019.01.06-1
The GNU Autoconf Archive is a collection of more than 450 macros
for GNU Autoconf that have been contributed as free software by friendly
supporters of the cause from all over the Internet
The following packages have been uploaded to the Cygwin distribution:
* autoconf-archive-2019.01.06-1
The GNU Autoconf Archive is a collection of more than 450 macros
for GNU Autoconf that have been contributed as free software by friendly
supporters of the cause from all over the Internet
The following packages have been uploaded to the Cygwin distribution:
* autoconf-archive-2017.09.28-1
The GNU Autoconf Archive is a collection of more than 450 macros for GNU
Autoconf that have been contributed as free software by friendly supporters
of the cause from all over the Internet
and tried to configure enough to
build doc.
Seems to be problem with autoconf autopoint gettext package
version - something run by autoreconf seems to be detecting
gettext 0.19.8-1 as 0.19.8.1 instead of 0.19.8 which causes
autopoint to fail:
This is already fixed in cygport git master.
Thanks
nd tried to configure enough to build doc.
> > Seems to be problem with autoconf autopoint gettext package version
> > - something run by autoreconf seems to be detecting gettext 0.19.8-1 as
> > 0.19.8.1 instead of 0.19.8 which causes autopoint to fail:
>
> This is al
On 2016-11-09 18:02, Brian Inglis wrote:
Looked for gawk doc in /usr/share/doc/gawk*/ - no HTML, PDF etc.
Checked for gawk doc as a package - no gawk-doc or anything like it.
Downloaded gawk package source and tried to configure enough to build doc.
Seems to be problem with autoconf autopoint
Looked for gawk doc in /usr/share/doc/gawk*/ - no HTML, PDF etc.
Checked for gawk doc as a package - no gawk-doc or anything like it.
Downloaded gawk package source and tried to configure enough to build doc.
Seems to be problem with autoconf autopoint gettext package version
- something run
that. This is not mentioned in
the autoconf manual I'm looking at. I don't know if the source
code comment or the manual is correct (it's been 20 years since I
last used fortran...)
Hi Peter,
thanks for the hint, unfortunately it makes no difference.
Looking at the upstream code I notice
(unlimited)
before the usual
LT_PREREQ([2.4.2])
LT_INIT([win32-dll])
is causing the libtool to be incorrectly set, versus
the right case
It seems libtool is incorrectly set for MSVC platform
I tried to move the libtool inizialization before the
AC_FC_LINE_LENGTH but autoconf is objecting on wrong
$libname | sed -e s/^lib/cyg/``echo \$release |
> \$SED -e s/[.]/-/g`\$versuffix\$shared_ext"
> +soname_spec=""
> -
>
> It seems libtool is incorrectly set for MSVC platform
>
> I tried to move the libtool inizialization bef
y set for MSVC platform
I tried to move the libtool inizialization before the
AC_FC_LINE_LENGTH but autoconf is objecting on wrong preference.
It seems a bug impacting only cygwin.
Regards
Marco
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cyg
The following packages have been uploaded to the Cygwin distribution:
* autoconf-archive-2016.03.20-1
The GNU Autoconf Archive is a collection of more than 450 macros for GNU
Autoconf that have been contributed as free software by friendly supporters
of the cause from all over the Internet
The following packages have been uploaded to the Cygwin distribution:
* autoconf-archive-2016.03.20-1
The GNU Autoconf Archive is a collection of more than 450 macros for GNU
Autoconf that have been contributed as free software by friendly supporters
of the cause from all over the Internet
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=44b72b43d6e867408a1ce6bc7df6d60a5c968183
commit 44b72b43d6e867408a1ce6bc7df6d60a5c968183
Author: Peter Foley <pefol...@pefoley.com>
Date: Thu Mar 31 14:04:18 2016 -0400
Update autoconf for doc/lsaauth/utils
Don
o copy and/or distribute it,
-dnl with or without modifications, as long as this notice is preserved.
-
-dnl From Bruno Haible.
-
-dnl AC_LIB_ARG_WITH is synonymous to AC_ARG_WITH in autoconf-2.13, and
-dnl similar to AC_ARG_WITH in autoconf 2.52...2.57 except that is doesn't
-dnl require excessive brac
The following package has been added to the Cygwin distribution:
* autoconf-archive-2014.10.15-1
The GNU Autoconf Archive is a collection of more than 500 macros for GNU
Autoconf that have been contributed as free software by friendly
supporters of the cause from all over the Internet. Every
The following package has been added to the Cygwin distribution:
* autoconf-archive-2014.10.15-1
The GNU Autoconf Archive is a collection of more than 500 macros for GNU
Autoconf that have been contributed as free software by friendly
supporters of the cause from all over the Internet. Every
Gcc requires that an unpatched, pristine version of autoconf be
used when preparing patches for official submission. For various
reasons [1] these pristine versions cannot coexist with the
existing autoconf packages in /usr.
gcc-4.3.x and gcc-4.4.x development requires autoconf-2.59
gcc-4.5.x
Gcc requires that an unpatched, pristine version of autoconf be
used when preparing patches for official submission. For various
reasons [1] these pristine versions cannot coexist with the
existing autoconf packages in /usr.
gcc-4.3.x and gcc-4.4.x development requires autoconf-2.59
gcc-4.5.x
Gcc requires that an unpatched, pristine version of autoconf be
used when preparing patches for official submission. For various
reasons [1] these pristine versions cannot coexist with the
existing autoconf packages in /usr.
gcc-4.3.x and gcc-4.4.x development requires autoconf-2.59
gcc-4.5.x
Gcc requires that an unpatched, pristine version of autoconf be
used when preparing patches for official submission. For various
reasons [1] these pristine versions cannot coexist with the
existing autoconf packages in /usr.
gcc-4.3.x and gcc-4.4.x development requires autoconf-2.59
gcc-4.5.x
Hi All,
As latest gcc's are not ignoring anymore -no-undefined
and the configure halt with error if LDFLAGS=-no-undefined
is defined in advance
*** Startup tests
checking build system type... i686-pc-cygwin
checking host system type... i686-pc-cygwin
On 2013-07-21 03:43, marco atzeri wrote:
As latest gcc's are not ignoring anymore -no-undefined
and the configure halt with error if LDFLAGS=-no-undefined
is defined in advance
Right, as gcc no longer ignores arguments it doesn't accept.
I am currently building packages adding almost at the
On 7/8/2013 9:30 PM, Charles Wilson wrote:
I've updated the following 64bit packages:
autoconf-13-1 (wrapper)
autoconf2.1-2.13-12
autoconf2.5-2.69-2
See the 32bit announcement(s) for details.
Chuck,
I think you forgot to run the GEN-sware script after uploading the 64bit
packages
I've updated the following 64bit packages:
autoconf-13-1 (wrapper)
autoconf2.1-2.13-12
autoconf2.5-2.69-2
See the 32bit announcement(s) for details.
--
Chuck
The autoconf package has been updated to version 13. Recall that this
package is not the real autoconf, but is a wrapper system to delegate to
the appropriate version of real autoconf (either 2.13 or 2.69 at present).
This is a feature enhancement and compatibility update, which adds
support
The autoconf package has been updated to version 13. Recall that this
package is not the real autoconf, but is a wrapper system to delegate to
the appropriate version of real autoconf (either 2.13 or 2.69 at present).
This is a feature enhancement and compatibility update, which adds
support
On 2013-05-14 15:13, marco atzeri wrote:
Il 5/14/2013 9:05 PM, Corinna Vinschen ha scritto:
I fear you might not like my answer: The problem here is NOT that the
linking works, the problem is that, if the configure test is used to
find out if we're running on Windows or not, it's simply not
On May 14 20:19, Charles Wilson wrote:
On 5/14/2013 3:05 PM, Corinna Vinschen wrote:
I fear you might not like my answer: The problem here is NOT that the
linking works, the problem is that, if the configure test is used to
find out if we're running on Windows or not, it's simply not feasible
Il 5/14/2013 9:05 PM, Corinna Vinschen ha scritto:
On May 14 20:30, marco atzeri wrote:
I fear you might not like my answer: The problem here is NOT that the
linking works, the problem is that, if the configure test is used to
find out if we're running on Windows or not, it's simply not
On 5/14/2013 3:05 PM, Corinna Vinschen wrote:
I fear you might not like my answer: The problem here is NOT that the
linking works, the problem is that, if the configure test is used to
find out if we're running on Windows or not, it's simply not feasible
anymore when taking x86_64 Cygwin into
On 10/14/2012 7:07 PM, marco atzeri wrote:
Charles,
any chance of upgrading Autoconf to last version from current 2.68 ?
I start to see packages with
AC_PREREQ(2.69)
Regards
Marco
ping
GraphicsMagick-1.3.17 needs it.
Marco
--
Problem reports: http://cygwin.com/problems.html
Charles,
any chance of upgrading Autoconf to last version from current 2.68 ?
I start to see packages with
AC_PREREQ(2.69)
Regards
Marco
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Hi all,
There seems to be a packaging error in autoconf (autoconf2.5-2.68-1
according to cygcheck -f /usr/share/man/man1/autoconf-2.68.1.gz).
The shorter names for the man pages point to non-existent files:
~/workspace/TTCNv3 $ file /usr/share/man/man1/auto*
/usr/share/man/man1/autoconf-2.68.1
1 - 100 of 348 matches
Mail list logo
