[ANNOUNCEMENT] Updated: nasm-2.00-1

[ANNOUNCEMENT] Updated: nasm-2.00-1

[Dean Scarff]

Version 2.00-1 of nasm has been uploaded, and should be available on  
the cygwin mirrors in the near future.  Please find it under the  
"Devel" category in cygwin's setup utility.

This release constitutes a major revision of the upstream stable  
sources.  From http://nasm.sf.net/ :

> After 7 months of intense development, the NASM team brings you  
> NASM 2.0!!! This version of NASM supercedes version 0.98.39 (and  
> Apple's 0.98.40) and introduces full 64-bit (x86-64/x64/AMD64/Intel  
> 64) architecture and object file support. We have also addressed  
> quite a few bugs and feature requests along the way.

Special note:

I have removed support for the GNUWin32 COFF format ("-f gnuwin32"  
option).  This format was introduced to work around historical  
disagreements between MinGW interpretation, Microsoft implementation,  
and the COFF/PE specifications of the VirtualSize field for .bss  
section headers.  These have been (reportedly) resolved in binutils  
since 2003.  Please use "-f win32" now in contexts where "-f  
gnuwin32" was used.

If you get link errors, such as "ld: PE operations on non PE file",  
when linking nasm objects produced with "nasm -f win32", and you are  
using the latest version of Cygwin's binutils, please send a report  
to the cygwin mailing list.

In general, questions, comments, and reports should go to the cygwin  
mailing list: cygwin@cygwin.com

               *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from 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

If you need more information on unsubscribing, start reading here:

http://sources.redhat.com/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is  
available starting at this URL.

--
Dean


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

[Packaging BUG] Re: [ANNOUNCEMENT] Updated: nasm-2.00-1

[Dr. Volker Zell]

>>>>> Dean Scarff writes:

    > Version 2.00-1 of nasm has been uploaded, and should be available on
    > the cygwin mirrors in the near future.  Please find it under the
    > "Devel" category in cygwin's setup utility.

There is a /usr/share/doc/html directory which should be under
/usr/share/doc/nasm-2.00

Ciao
  Volker
  

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: [Packaging BUG] Re: [ANNOUNCEMENT] Updated: nasm-2.00-1

[Dean Scarff]

Ack.  Updating RSN.

> There is a /usr/share/doc/html directory which should be under
> /usr/share/doc/nasm-2.00

-- 
Dean


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Cygport bug: autoconf 2.6x check fails 2.61.

[Dean Scarff]

[-- Attachment #1: Type: text/plain, Size: 594 bytes --]

Volker wrote:
> There is a /usr/share/doc/html directory which should be under
> /usr/share/doc/nasm-2.00

This appears to be a cygport bug (although I should have seen it
before uploading the package).

Cygport claims in the README that cygconf should call configure with
--docdir=/usr/share/doc/${P} for autoconf 2.60 configure scripts. I
assume the intention is there to support 2.6x too; but it doesn't
work.

I've attached a patch that fixes it with the magic of wildcards;
although relying on side-effect undocumented insertions into configure
scripts isn't robust at all IMO.

-- 
Dean


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: cygport-patch --]
[-- Type: text/x-diff, Size: 324 bytes --]

--- cygport-0.2.10	2007-12-08 01:05:11.892666000 +0900
+++ cygport	2007-12-08 01:05:53.720791000 +0900
@@ -802,7 +802,7 @@
 	fi
 
 	case "x$(grep -m 1 'GNU Autoconf' ${confdir}/configure | cut -d ' ' -f 6)" in
-		x2.6[0-9])
+		x2.6[0-9]*)
 			confargs+=" --datarootdir=/usr/share --docdir=/usr/share/doc/${P}"
 			;;
 		*)


[-- Attachment #3: Type: text/plain, Size: 218 bytes --]

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: Cygport bug: autoconf 2.6x check fails 2.61.

[Dave Korn]

On 07 December 2007 17:09, Dean Scarff wrote:

-		x2.6[0-9])
+		x2.6[0-9]*)


  I don't see why both of those regexes wouldn't successfully match '2.61'
already.  Your patch looks like it's trying to make the regex accept "2.6"
with no second digit after the decimal place as well.  Can you perhaps
clarify?


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Cygport bug: autoconf 2.6x check fails 2.61.

[Dean Scarff]

>   I don't see why both of those regexes wouldn't successfully match
> '2.61' already.  Your patch looks like it's trying to make the regex
> accept "2.6" with no second digit after the decimal place as well.
> Can you perhaps clarify?

Oh dear.  Apparently MIME inline attachments + gmane + ezmlm isn't a
good combination.  There was an explanation ;)

In short, the grep + cut doesn't quite work like it used to because
there is a trailing period.  The case glob (which is not a POSIX regex
under the Bourne shell, right?) matches "x2.61." as well as "x2.60",
which is what we want.

Either way the whole thing isn't a robust check, autoconf's manual
doesn't make any claims to insert that particular string.

-- 
Dean


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Cygport bug: autoconf 2.6x check fails 2.61.

[Yaakov (Cygwin Ports)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Dean Scarff wrote:
> In short, the grep + cut doesn't quite work like it used to because
> there is a trailing period.  The case glob (which is not a POSIX regex
> under the Bourne shell, right?) matches "x2.61." as well as "x2.60",
> which is what we want.

AFAIK that trailing period wasn't there with 2.60.  I have already fixed
this locally, but I see it hasn't got into CVS yet; it will soon.

> Either way the whole thing isn't a robust check, autoconf's manual
> doesn't make any claims to insert that particular string.

Can you find a better solution?  PTC.


Yaakov

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHWZMHpiWmPGlmQSMRCCJYAJ9j6Gd+h2BNAaA0OYlWBswvSIczNwCfSF7x
7GDvvQPlxhdGJqvK8fpez3I=
=wX/Y
-----END PGP SIGNATURE-----

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Cygport bug: autoconf 2.6x check fails 2.61.

[Christopher Faylor]

On Fri, Dec 07, 2007 at 05:19:26PM -0000, Dave Korn wrote:
>On 07 December 2007 17:09, Dean Scarff wrote:
>
>-		x2.6[0-9])
>+		x2.6[0-9]*)
>
>
>  I don't see why both of those regexes wouldn't successfully match '2.61'
>already.  Your patch looks like it's trying to make the regex accept "2.6"
>with no second digit after the decimal place as well.  Can you perhaps
>clarify?

Minor point of order: that's not a regex.  It's a shell glob.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Cygport bug: autoconf 2.6x check fails 2.61.

[Dean Scarff]

Yaakov wrote:
> Dean Scarff wrote:
>> In short, the grep + cut doesn't quite work like it used to because
>> there is a trailing period.  The case glob (which is not a POSIX
>> regex under the Bourne shell, right?) matches "x2.61." as well as
>> "x2.60", which is what we want.

> AFAIK that trailing period wasn't there with 2.60.  I have already

That's what I assumed (and indicated with my examples too).

> fixed this locally, but I see it hasn't got into CVS yet; it will
> soon.

>> Either way the whole thing isn't a robust check, autoconf's manual
>> doesn't make any claims to insert that particular string.

> Can you find a better solution?  PTC.

% wtf PTC
Gee...  I don't know what PTC means...

Test by feature rather than by version: I guess I'm getting a little
inspiration from the subject material here (autoconf).  Also there's
no need to be so sensitive to context and formatting changes (which a
grep | cut certainly is).  I've got two mutually exclusive patches,
you can choose one or none as you see fit; I haven't tested them
against all the obvious Autoconf versions either (2.59, 2.60 and 2.61
would seem prudent).  It's all a bit of an overkill though: I'm sure
my last patch will be fine for the forseeable future (and I feel bad
for dropping noisy patches on the cygwin list).

The first figures the help output is relatively stable, and
essentially all you want to know is whether configure supports a
docdir switch, so test for that.  Of course, this will have problems
if someone clever decides to include "--docdir=" in their help output,
and somehow doesn't support it as an option (although all the autoconf
options are currently hardcoded in autoconf's general.m4).
Furthermore if the list of installation directory variables supported
by Autoconf keeps growing, they might just drop support for listing them
in the help in the one-line-per-option format.
===================================================================
RCS file: /cvsroot/cygwin-ports/cygport/bin/cygport.in,v
retrieving revision 1.89
diff -u -3 -r1.89 cygport.in
--- bin/cygport.in      3 Dec 2007 23:00:54 -0000       1.89
+++ bin/cygport.in      7 Dec 2007 19:08:39 -0000
@@ -1007,15 +1007,12 @@
                          --sbindir=/usr/sbin --libexecdir=/usr/sbin \
                          --localstatedir=/var --sysconfdir=/etc"
 
-       case "x$(grep -m 1 'GNU Autoconf' ${configure} | cut -d ' ' -f 6)" in
-               x2.6[0-9])
-                       confargs+=" --datarootdir=/usr/share --docdir=/usr/share/doc/${P}"
-                       ;;
-               *)
-                       confargs+=" --datadir=/usr/share --infodir=/usr/share/info \
-                               --mandir=/usr/share/man"
-                       ;;
-       esac
+       if ${configure} --help | grep -e --docdir= >/dev/null ; then
+               confargs+=" --datarootdir=/usr/share --docdir=/usr/share/doc/${P}"
+       else
+               confargs+=" --datadir=/usr/share --infodir=/usr/share/info \
+                          --mandir=/usr/share/man"
+       fi
 
        # AC_HAVE_MMAP fails despite a working mmap, so we force this to yes
        # (see http://www.cygwin.com/ml/cygwin/2004-09/msg00741.html

The second approach is to actually *try* to use docdir.  If configure
doesn't support it then it will fail quickly.  If configure does
support it but fails for other reasons, it will write to config.log.
This relies on the config.log file and behaviour.  It's also not very
extensible when there's more future-autoconf-features you want to take
advantage of.  You can deal with that in the future, no?  It's not the
most elegant piece of code either.
===================================================================
RCS file: /cvsroot/cygwin-ports/cygport/bin/cygport.in,v
retrieving revision 1.89
diff -u -3 -r1.89 cygport.in
--- bin/cygport.in      3 Dec 2007 23:00:54 -0000       1.89
+++ bin/cygport.in      7 Dec 2007 19:48:57 -0000
@@ -1006,25 +1006,26 @@
        confargs="--prefix=/usr --exec-prefix=/usr --bindir=/usr/bin \
                          --sbindir=/usr/sbin --libexecdir=/usr/sbin \
                          --localstatedir=/var --sysconfdir=/etc"
-
-       case "x$(grep -m 1 'GNU Autoconf' ${configure} | cut -d ' ' -f 6)" in
-               x2.6[0-9])
-                       confargs+=" --datarootdir=/usr/share --docdir=/usr/share/doc/${P}"
-                       ;;
-               *)
-                       confargs+=" --datadir=/usr/share --infodir=/usr/share/info \
-                               --mandir=/usr/share/man"
-                       ;;
-       esac
+       docdir=" --datarootdir=/usr/share --docdir=/usr/share/doc/${P}"
+       nodocdir=" --datadir=/usr/share --infodir=/usr/share/info \
+                          --mandir=/usr/share/man"
 
        # AC_HAVE_MMAP fails despite a working mmap, so we force this to yes
        # (see http://www.cygwin.com/ml/cygwin/2004-09/msg00741.html
        # and following thread for details)
        export ac_cv_func_mmap_fixed_mapped=yes;
 
+       # if Autoconf-generated configure scripts fail with an
+       # unrecognised option, they do not write a log.
+       configured=no
        verbose ${configure} \
-               --srcdir="${confdir}" ${confargs} "${@}" ${CYGCONF_ARGS} \
-               || error "configure failed"
+               --srcdir="${confdir}" ${confargs} ${docdir} "${@}" ${CYGCONF_ARGS} && \
+               configured=yes
+       [ "${configured}" = no -a ! -s config.log ] && \
+               verbose ${configure} \
+               --srcdir="${confdir}" ${confargs} ${nodocdir} "${@}" ${CYGCONF_ARGS} && \
+               configured=yes
+       [ "${configured}" = yes ] || error "configure failed"
 }
 
 # cmake configuration


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/