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
> Any idea why autoconf tests for
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}!
STC
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, log, -E output. Tried also
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.
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 successfully
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
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
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 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
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
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
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
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
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
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
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 requires
On 30/07/2016 06:23, Marco Atzeri wrote:
On 29/07/2016 21:32, Peter Rosin wrote:
On 2016-07-29 14:23, Marco Atzeri wrote:
Reading the source comment for AC_FC_LINE_LENGTH indicates that
you should call AC_FC_FREEFORM or AC_FC_FIXEDFORM before you call
AC_FC_LINE_LENGTH. You do not do that.
On 29/07/2016 21:32, Peter Rosin wrote:
On 2016-07-29 14:23, Marco Atzeri wrote:
Hi Eric,
building latest Arpack
https://github.com/opencollab/arpack-ng/releases
https://github.com/opencollab/arpack-ng/issues/41
I hit a strange case where the presence of a single line
On 2016-07-29 14:23, Marco Atzeri wrote:
> Hi Eric,
>
> building latest Arpack
> https://github.com/opencollab/arpack-ng/releases
> https://github.com/opencollab/arpack-ng/issues/41
>
> I hit a strange case where the presence of a single line
>
> AC_FC_LINE_LENGTH(unlimited)
>
> before the
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
On 11/15/2011 5:06 AM, Csaba Raduly wrote:
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:
The symlinks don't appear in the output of
On 2010-03-29 23:28, NightStrike wrote:
Autoconf is listed twice in the list of installable packages from
cygwin, and described thusly:
autoconf2.1 - Stable version, latest = 2.13-10
autoconf2.5 - Development version, latest =2.65-1
Think it's about time that these are labeled differently?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Matthew on 11/22/2009 9:06 AM:
Cygwin 1.5.25-15, autoconf 2.64, HandBrake svn 2953, lame 3.98, and gcc 4.3.2
It appears it is still happening.
It appears WHAT is still happening? You left out some important context.
C:\cygwin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Matthew on 11/22/2009 9:06 AM:
cd HandBrake
./configure --launch-jobs=1 --launch --gcc=/usr/bin/gcc-4.exe
Where does --launch come from? That's not a typical argument in configure
scripts generated by Autoconf, nor is it one supported
lemkemch wrote on 10 August 2008 18:46:
I am not familar enough with autoconf to be able to tell how that line
gets into configure. I can't find it in configure.in. All I can see is
stuff like AH_VERBATIM([HAVE_UINT64_T] and AC_CHECK_TYPES([uint8_t,
int8_t, uint16_t, int16_t, uint32_t,
lemkemch wrote on 10 August 2008 18:46:
I am not familar enough with autoconf to be able to tell how that line
gets into configure. I can't find it in configure.in. All I can see is
stuff like AH_VERBATIM([HAVE_UINT64_T] and AC_CHECK_TYPES([uint8_t,
int8_t, uint16_t, int16_t, uint32_t,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Dave Korn on 8/10/2008 12:40 PM:
|
|This is an autoconf bug upstream really. They'd know best what how to
| patch it long term.
Not only that, I already have patched it long-term, as of autoconf 2.62:
Eric Blake wrote:
According to Dave Korn on 8/10/2008 12:40 PM:
|
|This is an autoconf bug upstream really. They'd know best what how to
| patch it long term.
Not only that, I already have patched it long-term, as of autoconf 2.62:
Hi All...
Does
set -o igncr
export SHELLOPTS
before building it help? Can you ignore the CR by bash later?
...Karl
From: René Berber Subject: Re: autoconf
Date: Thu, 30 Nov 2006 22:32:16 -0600
René Berber wrote:
Bob Rossi wrote:
[snip]
Here's the full story. I'm trying to build apr
Bob Rossi wrote:
Hi,
I'm using autoconf. I notice when I use things like
AC_CHECK_SIZEOF (int)
that the ac_cv_sizeof_int has the value of 4\r.
There is an extra carriage return in there. I start my configure
script with
./configure --build=mingw32
could that be the problem?
Is there any
On Thu, Nov 30, 2006 at 05:04:08PM -0500, Bob Rossi wrote:
Hi,
I'm using autoconf. I notice when I use things like
AC_CHECK_SIZEOF (int)
that the ac_cv_sizeof_int has the value of 4\r.
I narrowed it down further. It's AC_CHECKS_SIZEOF that does
acgeneral.m4: fprintf(f, %d\n, sizeof($1));
On Thu, Nov 30, 2006 at 06:45:10PM -0500, Larry Hall (Cygwin) wrote:
Bob Rossi wrote:
Hi,
I'm using autoconf. I notice when I use things like
AC_CHECK_SIZEOF (int)
that the ac_cv_sizeof_int has the value of 4\r.
There is an extra carriage return in there. I start my configure
script
Bob Rossi wrote:
On Thu, Nov 30, 2006 at 06:45:10PM -0500, Larry Hall (Cygwin) wrote:
Bob Rossi wrote:
Hi,
I'm using autoconf. I notice when I use things like
AC_CHECK_SIZEOF (int)
that the ac_cv_sizeof_int has the value of 4\r.
There is an extra carriage return in there. I start my
On Thu, Nov 30, 2006 at 09:45:21PM -0500, Larry Hall (Cygwin) wrote:
Bob Rossi wrote:
On Thu, Nov 30, 2006 at 06:45:10PM -0500, Larry Hall (Cygwin) wrote:
Bob Rossi wrote:
Hi,
I'm using autoconf. I notice when I use things like
AC_CHECK_SIZEOF (int)
that the ac_cv_sizeof_int has the value
Bob Rossi wrote:
On Thu, Nov 30, 2006 at 09:45:21PM -0500, Larry Hall (Cygwin) wrote:
Bob Rossi wrote:
On Thu, Nov 30, 2006 at 06:45:10PM -0500, Larry Hall (Cygwin) wrote:
Bob Rossi wrote:
Hi,
I'm using autoconf. I notice when I use things like
AC_CHECK_SIZEOF (int)
that the
On Thu, Nov 30, 2006 at 10:11:01PM -0500, Larry Hall (Cygwin) wrote:
Bob Rossi wrote:
On Thu, Nov 30, 2006 at 09:45:21PM -0500, Larry Hall (Cygwin) wrote:
Bob Rossi wrote:
On Thu, Nov 30, 2006 at 06:45:10PM -0500, Larry Hall (Cygwin) wrote:
Bob Rossi wrote:
Hi,
I'm using autoconf. I
Bob Rossi wrote:
[snip]
Here's the full story. I'm trying to build apr. It needs to be built
with mingw in order to have thread support. It specifically disables
thread support with cygwin.
So, instead of getting the mingw
environment, I'd like to use the cygwin environment cause I my build
René Berber wrote:
Bob Rossi wrote:
[snip]
Here's the full story. I'm trying to build apr. It needs to be built
with mingw in order to have thread support. It specifically disables
thread support with cygwin.
So, instead of getting the mingw
environment, I'd like to use the cygwin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Charli Li on 6/28/2006 9:39 PM:
I am sorry for the raw email address.
What about the top-posting, the cross-posting, and the replying to
yourself without trimming the message? Besides, the maintainer of the
autoconf package probably
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 26, 2006
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 26, 2006
Gary R. Van Sickle wrote:
From: Dave Korn
[snip]
I don't get that. I've got the default alternatives set,
so IIUIC it should have selected the most recent autoconf, shouldn't it?
I imagine this is intended to work with everything in the
default installation state, but as you see it
Thanks for helping David, Brian. Your answers are almost entirely
correct. David, here's the current status:
(1) autoconf now uses the same wrapper that is shipped by Mandr* Red
Hat (and others, I think) instead of my crappy home grown one. So
you've got a wrapper package ('autoconf'),
From: Dave Korn
[snip]
I don't get that. I've got the default alternatives set,
so IIUIC it should have selected the most recent autoconf,
shouldn't it?
I imagine this is intended to work with everything in the
default installation state, but as you see it certainly doesn't WFM!
Dave Korn wrote:
I'm having trouble with the cygwin auto*tool package and the wrappers it
puts around the different tool versions. I've looked in the following places
I think that they key point is that for automake, the automatic version
guessing is no longer done, there are no wrapper
Dave Korn wrote:
Umm, it definitely *does* have an effect; see the differences it made to the
examples I posted in the previous case. Is it possible I have some remnants
of the old autoconf stuff lying around? I updated this morning and didn't see
any problems, and nor does cygcheck
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Keith Moore on 12/16/2005 4:12 PM:
That said, another possible solution would be to
rip out the lines mentioned above, and replace all
occurances of exeext with EXEEXT (the variable
set by the autoconf-generated magic).
That sounds
Larry Adams (The Cacti Group) wrote:
I have an issue with both the autoconf AC_CONFIG_FILES and AC_CONFIG_COMMANDS
MACROS in the current 2.59 version of autoconf. When compiling
the ./configure shell script, the use of these macros prepents each command
with several white spaces causing the
* In message [EMAIL PROTECTED]
* On the subject of Re: autoconf 2.54-1 writes dos files
* Sent on Tue, 2 Sep 2003 21:46:50 +0200
* Honorable Gerrit P. Haase [EMAIL PROTECTED] writes:
I don't need to set PERLIO and get no CR/LF line endings.
Me neither. :-)
Apparently, I needed to reboot
Hello Sam,
the real information about your perl version is displayed via
`perl -V` (capital V):
Built under cygwin
Compiled at Sep 1 2003 15:23:12
Gerrit
--
=^..^=
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Hello Gerrit,
* In message [EMAIL PROTECTED]
* On the subject of Re: autoconf 2.54-1 writes dos files
* Sent on Tue, 2 Sep 2003 14:41:12 +0200
* Honorable Gerrit P. Haase [EMAIL PROTECTED] writes:
the real information about your perl version is displayed via
`perl -V` (capital V):
Summary
Hallo Sam,
the real information about your perl version is displayed via
`perl -V` (capital V):
Characteristics of this binary (from libperl):
Compile-time options: MULTIPLICITY USE_64_BIT_INT USE_LARGE_FILES
PERL_IMPLICIT_CONTEXT
Built under cygwin
Compiled at Aug 29 2003
me being a perl-hater :-), you can hardly expect me to harbor some
non-standard perl.
IT IS NOT POSSIBLE TO *BE* A PERL HATER! You see, in this world there's two
kinds of people, my friend: Those who love Perl, and those who learn to love
Perl. You learn to love Perl.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf
Of Gary R. Van Sickle
IT IS NOT POSSIBLE TO *BE* A PERL HATER! You see, in this world
there's two
kinds of people, my friend: Those who love Perl, and those who
learn to love
Perl. You learn to love Perl.
Hi Sam,
you wrote this:
I just noticed that autoconf 2.54-1 writes configure files with DOS
CR/LF line ends!
what's up?!
and that:
$ cygcheck.exe -c -h perl
Cygwin Package Information
Package Version
perl 5.8.0-5
Hmmm, this is strange. Are you sure you
* In message [EMAIL PROTECTED]
* On the subject of RE: autoconf 2.54-1 writes dos files
* Sent on Mon, 1 Sep 2003 00:57:25 -0500
* Honorable Gary R. Van Sickle [EMAIL PROTECTED] writes:
me being a perl-hater :-), you can hardly expect me to harbor some
non-standard perl
Sam Steingold wrote:
* In message [EMAIL PROTECTED]
* On the subject of Re: autoconf 2.54-1 writes dos files
* Sent on Sat, 30 Aug 2003 22:17:07 +0100
* Honorable Elfyn McBratney ... writes:
Sam Steingold wrote:
* Honorable Elfyn McBratney [EMAIL PROTECTED] writes:
Thanks
* In message [EMAIL PROTECTED]
* On the subject of Re: autoconf 2.54-1 writes dos files
* Sent on Sun, 31 Aug 2003 00:47:09 +0100
* Honorable Elfyn McBratney ... writes:
Sam Steingold wrote:
your e-mail address is in the header!
No, I think not. You replied to my message; with my e
Hallo Sam,
you wrote this:
I just noticed that autoconf 2.54-1 writes configure files with DOS
CR/LF line ends!
what's up?!
and that:
$ cygcheck.exe -c -h perl
Cygwin Package Information
Package Version
perl 5.8.0-5
Elfyn wrote:
What's the output of `mount'
Hi Gerrit,
* In message [EMAIL PROTECTED]
* On the subject of Re: autoconf 2.54-1 writes dos files
* Sent on Sun, 31 Aug 2003 20:39:03 +0200
* Honorable Gerrit P. Haase [EMAIL PROTECTED] writes:
you wrote this:
I just noticed that autoconf 2.54-1 writes configure files with DOS
CR/LF
Sam Steingold wrote:
I just noticed that autoconf 2.54-1 writes configure files with DOS
CR/LF line ends!
what's up?!
I check unix in default text file type setup option and I do not
have any CRs in the configure.in files!
autoconf is a perl program. There were some releases of perl that had a
* In message [EMAIL PROTECTED]
* On the subject of Re: autoconf 2.54-1 writes dos files
* Sent on Sat, 30 Aug 2003 15:14:16 -0400
* Honorable Charles Wilson [EMAIL PROTECTED] writes:
Sam Steingold wrote:
I just noticed that autoconf 2.54-1 writes configure files with DOS
CR/LF line
Sam Steingold wrote:
* In message [EMAIL PROTECTED]
* On the subject of Re: autoconf 2.54-1 writes dos files
* Sent on Sat, 30 Aug 2003 15:14:16 -0400
* Honorable Charles Wilson [EMAIL PROTECTED] writes:
Sam Steingold wrote:
I just noticed that autoconf 2.54-1 writes configure
* In message [EMAIL PROTECTED]
* On the subject of Re: autoconf 2.54-1 writes dos files
* Sent on Sat, 30 Aug 2003 21:36:48 +0100
* Honorable Elfyn McBratney [EMAIL PROTECTED] writes:
Sam Steingold wrote:
* In message [EMAIL PROTECTED]
* On the subject of Re: autoconf 2.54-1 writes dos
Sam Steingold wrote:
* In message [EMAIL PROTECTED]
* On the subject of Re: autoconf 2.54-1 writes dos files
* Sent on Sat, 30 Aug 2003 21:36:48 +0100
* Honorable Elfyn McBratney [EMAIL PROTECTED] writes:
Thanks for addressing me as honorable, but please don't quote my e-mail address
* In message [EMAIL PROTECTED]
* On the subject of Re: autoconf 2.54-1 writes dos files
* Sent on Sat, 30 Aug 2003 22:17:07 +0100
* Honorable Elfyn McBratney ... writes:
Sam Steingold wrote:
* Honorable Elfyn McBratney [EMAIL PROTECTED] writes:
Thanks for addressing me as honorable
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/bin'
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?
There is no new version. See
ftp://ftp.gnu.org/pub/gnu/autoconf/
Cygwin's autoconf-devel
Hallo,
checking whether make sets $(MAKE)... ac_maketemp=make: not found
no
I never saw this before...MAKE was set by make as long as I can think
of. What may cause such a behaviour?
I found the culprit, I played around with SAPDB which messed up my
environment, actually there were some
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 various
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
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.
On Fri, Apr 05, 2002 at 05:40:36PM +0100, (1pH3r_IVI4IV14( wrote:
When configuring a package using autoconf-2.53, the built-in check for
mmap (AC_FUNC_MMAP I believe) fails:
[...]
checking for working mmap... no
[...]
That's expected unfortunately. The mmap test in autoconf (I know
this
James Harvey wrote:
OK, thanks. A colleague of mine noticed a bug, in that:
export M4PATH=${AUTO_STABLE}/share/autoconf:${M4PATH}
will set M4PATH to '/foo/share.autoconf:' if it was not previously set, and
an empty path equates to the current directory, which is probably not what
was
Chuck wrote:
James Harvey wrote:
I've been converting some of our build system to use the cygwin
autotools
recently, and I think I've come across a bug in the autoconf/autoheader
wrapper scripts (I assume these may occur in the other auto* scripts,
but
these are the specific ones I
Thanks for the report I'll try to get around to this soon, and will
release new versions of the wrappers
--Chuck
James Harvey wrote:
I've been converting some of our build system to use the cygwin autotools
recently, and I think I've come across a bug in the autoconf/autoheader
wrapper
83 matches
Mail list logo
