[ANNOUNCEMENT] Updated: autoconf-devel-2.53a-1

[ANNOUNCEMENT] Updated: autoconf-devel-2.53a-1

[Charles Wilson]

Version 2.53-1 of the autoconf-devel package is now available.
It contains GNU autoconf-2.53, installed into /usr/autotool/devel.

GNU Autoconf-2.53a contains some bugfixes that cropped up in the
2.53 release.

Changes since 2.53-1
o update to the GNU 2.53a release
o all 163 self tests successful (3 skipped)
o There DOES seem to a problem in BOTH 2.53 and 2.53a, where
   seemingly valid configure.in/acinclude.m4 files lead to buggy
   configure scripts.  This bug ALSO exists in 2.52.  So, in that
   respect, 2.53a-1 is no worse than any other cygwin release
   of autoconf-devel.
o See NOTES below.

--
Chuck Wilson

To update your installation, click on the "Install Cygwin now" link
on the http://cygwin.com/ web page.  This downloads setup.exe to
your system.  Save it and run setup, answer the questions and pick
up 'autoconf-devel' from the 'Devel' category.

Note that downloads from sources.redhat.com (aka cygwin.com) aren't
allowed due to bandwidth limitations.  This means that you will need
to find a mirror which has this update.

In the US, ftp://mirrors.rcn.net/mirrors/sources.redhat.com/cygwin/
is a reliable high bandwidth connection.

In Japan, ftp://ftp.u-aizu.ac.jp/pub/gnu/gnu-win32/ is already
updated.

In DK, http://mirrors.sunsite.dk/cygwin/ is usually up-to-date.

If one of the above doesn't have the latest version of this package
you can either wait for the site to be updated or find another
mirror.

Please  send questions or comments to the Cygwin mailing list at:
cygwin@sources.redhat.com .  If you want to subscribe go to:
http://cygwin.com/lists.html I would appreciate if you would use
this mailing list rather than emailing me directly.  This includes
ideas and comments about the setup utility or Cygwin in general.

If you want to make a point or ask a question the Cygwin mailing
list is the appropriate place.

                *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

To unsubscribe to the cygwin-announce mailing list, look at the
"List-Unsubscribe: " tag in the email header of this message. Send
email to the address specified there.  It will be in the format:

cygwin-announce-unsubscribe-YOU=YOURDOMAIN.COM@cygwin.com

NOTES:

Although autoconf-2.53a passes all of its own self tests on cygwin,
it still misbehaves in some cases.  In general, if autoconf
completes without error, it should NEVER create a configure script
with syntax errors.  autoconf-2.53a, autoconf-2.53, and autoconf-2.52
ALL do so in a specific case.

I've been working with cvs-1.11.2, and when re-autoconf'ing, autoconf
gets really confused. I mean, it totally loses track of what it's doing,
and puts in comments without '#' marks, drops 'help' text in the
middle of the running script, etc.  To give you a clue, here are the
fixes I had to apply by hand to configure:
   1) the --enable-client help text was not put into the help section,
      but rather just dropped willy-nilly into the script itself.
   2) case statements were completely hosed (no closing ')', a random
      'fi' just dropped in there...
   3) if statements not closed: 'fi' or 'else' ommitted...

However, I must reiterate: I get similar errors with 2.52 and
2.53(no a). This is not a bug specific to this latest release.
Second, it is not a bug in my configure.in/acinclude.m4 code --
autoconf should either generate a syntactically correct configure
script, or generate an error message itself.  It should never
generate buggy script and not report an error.

--- cvs-1.11.2-orig/configure	2002-05-19 06:46:53.000000000 -0400
+++ cvs-1.11.2/configure	2002-05-19 06:16:46.000000000 -0400
@@ -848,6 +848,8 @@
    --disable-dependency-tracking Speeds up one-time builds
    --enable-dependency-tracking  Do not reject slow dependency extractors
    --enable-encryption     enable encryption support
+  --enable-client         include code for running as a remote client
+                          (default)
    --enable-server         include code for running as a server (default)

  Optional Packages:
@@ -6037,6 +6039,7 @@
  #define HAVE_GETSPNAM 1
  _ACEOF

+fi

  echo "$as_me:$LINENO: checking whether utime accepts a null argument" >&5
  echo $ECHO_N "checking whether utime accepts a null argument... 
$ECHO_C" >&6
@@ -6307,9 +6310,7 @@

  # So?  What about this header?
  case $ac_header_compiler:$ac_header_preproc in
-  yes:no
-fi
-
+  yes:no )
      { echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the 
compiler, rejected by the preprocessor!" >&5
  echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected 
by the preprocessor!" >&2;}
      { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the 
preprocessor's result" >&5
@@ -9124,18 +9125,14 @@
    :
  else
    LIBOBJS="$LIBOBJS hostname.$ac_objext"
+fi


-
-    --enable-client         include code for running as a remote client
-                          (default)
  # Check whether --enable-client or --disable-client was given.
  if test "${enable_client+set}" = set; then
    enableval="$enable_client"
    case "${enableval}" in
-      yes
-fi
- client=yes;;
+      yes) client=yes;;
        no) client=no;;
        *) { { echo "$as_me:$LINENO: error: bad value ${enableval} for 
client option" >&5
  echo "$as_me: error: bad value ${enableval} for client option" >&2;}
@@ -9529,9 +9526,7 @@

  # So?  What about this header?
  case $ac_header_compiler:$ac_header_preproc in
-  yes:no
-fi
-
+  yes:no )
      { echo "$as_me:$LINENO: WARNING: gdbm.h: accepted by the compiler, 
rejected by the preprocessor!" >&5
  echo "$as_me: WARNING: gdbm.h: accepted by the compiler, rejected by 
the preprocessor!" >&2;}
      { echo "$as_me:$LINENO: WARNING: gdbm.h: proceeding with the 
preprocessor's result" >&5
@@ -9566,13 +9561,12 @@
  echo "$as_me: error: cannot find gdbm.h" >&2;}
     { (exit 1); exit 1; }; }
  fi
-
-,
+  else
        { { echo "$as_me:$LINENO: error: cannot find libgdbm" >&5
  echo "$as_me: error: cannot find libgdbm" >&2;}
-   { (exit 1); exit 1; }; })
+   { (exit 1); exit 1; }; }
    fi
-
+fi
  fi # cygwin

  test -f src/options.h && (



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

inn port

[Mario Schmidt]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Charles Wilson,

i just noticed, that you are doing some good work on your cygwin
ports. I want to ask you, if you can review and help with my newest
port of "INN" ?!

i finally good it compiled, installed and are now working on some
details. Can you help me in a specific problem i got during compile?
If ya would, i give you the latest .diff and instructions for my inn
port.

TAI
Mario

____________________________________________
ms.software
Winkelstr. 2
D-42853 Remscheid
Germany

Tel.: +49-(0)-2191-949774
Fax : +49-(0)-2191-949774
Web : http://pcfon.de/ms.software/
Mail: mailto:info@pcfon.de
ICQ : #106641465

- -----BEGIN PGP PUBLIC KEY BLOCK-----
Version: PGPfreeware 6.5.8 for non-commercial use
<http://www.pgp.com>

mQGiBDuqdI4RBAD2UO6KYB9oGzKpxiknIeHUAke4bBwddrtmGu0t4/u8/mNWvWak
bSE9/MRjEun5YRBPnXUg7VNyuVvDV0BN8BPttG8YLJEffDXD6JErQ1F7HAkVijvc
b6npCb8a2Qwr4Ual4AWk9OOnhTdvwc17hCkgShTut8wnHWks7hypMcS1fQCg/1Kd
r+IcLq+iX/UQyrRjzSx2HxEEALBZnhwN563Yci2cR+t9HPx2i3VMWFk8cQMS7vWL
pkWUbl8sutQQC926P8BPSWy+/0xGAkmP9hHIBoyXDQzJUnb8lzTQISAVdu61lw+H
2RfrvRRx1k/DXikVLCyu6AvVGibrn24afVZ/qArituIEZoKes9oQkV2icieB701Z
PFFdA/oDjzINrOXWlibrywLRSD88KE8mitlmU6erZYd1MEGiWiwfOgMKLwRlVHmG
WVZb5N14CnAMWAeQwVPtegddYiFv9DrcdktlETjZguZuEgWMkGePtL190d/3Zaj9
QVyFXTSSaf+oBgDNaD2Y26N3NSvMpErUFz9EtTn4Vbhf9fnfDrQdTWFyaW8gU2No
bWlkdCA8aW5mb0BwY2Zvbi5kZT6JAE4EEBECAA4FAjuqdI4ECwMCAQIZAQAKCRAU
RnxU2QwBD/55AKDbJwsYS/Lq8MzLKR7Q7L3hbgYrnQCg76up30inkc67fBJ4XiiF
HgRAmL25Ag0EO6p0jhAIAPZCV7cIfwgXcqK61qlC8wXo+VMROU+28W65Szgg2gGn
VqMU6Y9AVfPQB8bLQ6mUrfdMZIZJ+AyDvWXpF9Sh01D49Vlf3HZSTz09jdvOmeFX
klnN/biudE/F/Ha8g8VHMGHOfMlm/xX5u/2RXscBqtNbno2gpXI61Brwv0YAWCvl
9Ij9WE5J280gtJ3kkQc2azNsOA1FHQ98iLMcfFstjvbzySPAQ/ClWxiNjrtVjLhd
ONM0/XwXV0OjHRhs3jMhLLUq/zzhsSlAGBGNfISnCnLWhsQDGcgHKXrKlQzZlp+r
0ApQmwJG0wg9ZqRdQZ+cfL2JSyIZJrqrol7DVekyCzsAAgIH/jPInX3WVpuIHC0Y
Uax/YxXmeXarOLmDezGJI0PB7Mlp5jg5S8oF9/2C0tRjq8yB4RjJZhK8AifFxvSz
Ivl8+yEg+4wvZi3yJzAwXy/LnM8veK+Yc9yzFZv+jUzPnSc1KRXBqZCQONOxQveJ
DPZrfhy75DE+ZAN7kKW6qMm237oPC4BkPiCAXKSIoOuGg6YnNzPnPJiLNpSLDuV5
cZRxKdhwuRvOS7Jowd/UfvoTQYfJdY41xaKzYr9z4SRBAaRoY5g0mkHFMOx8rmhA
+P0T4OpslgjUL9UTBEpCTJs6wPec0uDQ3bFKW7ZmCfaLDoCj1oyL/A9r+2VJefSA
zjl6hwaJAEYEGBECAAYFAjuqdI4ACgkQFEZ8VNkMAQ8kTACgln4N+fyMWDw1OsSH
v76sx8LaobUAnA2AK50QE9U+wkEEE409K47jl5z7uQDNBDuqWNEQAwDzPtRahitB
8eSmLuXY1ayKEaH6ua5K5odGfICI9fTn6dViSAQyYJuRyql3Ra5qSFjD2yplBM/5
THTJRGatQiS/fUh+c9kngoUQyy+3DfoZK+aQMh7FoxGTuHqPwf1v0cMAAgIC+wYr
ANn4TUnTWRAROE2XTUaS1jsINK3FSOxgPfQDbIh7X42uZ13j6XVoFlKcq60PorOf
eV4jOmeudsM7IS4FFMFNsWtG12hKVCPW61tlV715cIwlorBymGDyLr44ebNNwokA
RgQYEQIABgUCO6p1fwAKCRAURnxU2QwBD2dVAJ94qVZMU7SsL+/bV1yqFglb6jtW
jgCfYzCEiswC4QKp4L1dF9ywn4f8BmQ=
=xmmz
- -----END PGP PUBLIC KEY BLOCK-----

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com>

iQA/AwUBPOhMChRGfFTZDAEPEQKpFACfd1/fHmAfvwoGDseHTkGzGG0fJK8AoL1u
6qBaE6t4HH8Y7ZIsKymHKPVT
=AllX
-----END PGP SIGNATURE-----


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: inn port

[Charles Wilson]

Mario Schmidt wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi Charles Wilson,


Please don't address help requests to specific people.  This is a 
general mailing list; help is provided thru the cooperative efforts of 
everyone.  (But don't send cygwin mail to private email addrs, either -- 
most people dislike that).

 
> i just noticed, that you are doing some good work on your cygwin
> ports. I want to ask you, if you can review and help with my newest
> port of "INN" ?!


I personally have no more time for any additional responsibilities. 
Which is why you have a much better chance getting help by asking the 
list in general; of the thousands of people subscribed, the chances are 
than one or more of them have an interest in getting INN working on 
cygwin. No offence intended, but I don't -- netnews doesn't float my 
boat.  Sorry.

> 
> i finally good it compiled, installed and are now working on some
> details. Can you help me in a specific problem i got during compile?
> If ya would, i give you the latest .diff and instructions for my inn
> port.

Not me, but perhaps someone else on this list will be able to provide 
more assistance.  Why don't you outline your problem on the list itself, 
rather than trying to keep the details offline?

--Chuck


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: [ANNOUNCEMENT] Updated: autoconf-devel-2.53a-1

[Charles Wilson]

Charles Wilson wrote:


> o There DOES seem to a problem in BOTH 2.53 and 2.53a, where
>    seemingly valid configure.in/acinclude.m4 files lead to buggy
>    configure scripts.  This bug ALSO exists in 2.52.  So, in that
>    respect, 2.53a-1 is no worse than any other cygwin release
>    of autoconf-devel.

According to Akim (chief autoconf guru on the autoconf mailing list), 
the problem IS in my configure.in/acinclude.m4 files.  We haven't yet 
nailed down exactly WHERE the problem is -- but he says it's NOT in 
autoconf itself.

So, sorry for the false alarm...

--Chuck


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: inn port

[Gerrit P. Haase]

Mario,

>> i just noticed, that you are doing some good work on your cygwin
>> ports. I want to ask you, if you can review and help with my newest
>> port of "INN" ?!

>> i finally good it compiled, installed and are now working on some
>> details. Can you help me in a specific problem i got during compile?
>> If ya would, i give you the latest .diff and instructions for my inn
>> port.

I'm interested.

Could you post a patch to the list so we all can try to compile Inn
and see whats up?

BTW, My mail to your address is bouncing so lets keep it on the list.


Gerrit
-- 
=^..^=


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/