Re: i686-w64-mingw32-gcc: LC_MESSAGES

[JonY]

On 1/9/19 7:43 PM, Lee wrote:
>> MSVCR = MicroSoft Visual C Run-time (I think)
> 

Yes, as implemented by msvcrt.dll.

> Meaning i686-w64-mingw32-gcc uses the Microsoft libraries vs. cygwin
> gcc using posix compliant libraries?  Implying LC_MESSAGES not being
> defined is yet another instance of Microsoft not following accepted
> standards?
> 

Cygwin has its own runtime, Windows has its own. Microsoft does whatever
it well pleases, it never did claim POSIX or ISO C compliance.

See the printf/scanf hacks in mingw.

> The background for my question is 
> https://github.com/htacg/tidy-html5/issues/770
> Tidy removed the setlocale call from the library init function, so if
> users want a specific locale/language they're going to have to set it
> up themselves.
> I'd like to update the tidylib example code showing how to set the language, 
> but
>   setlocale(LC_ALL, "");
>   tidySetLanguage( setlocale(LC_MESSAGES, NULL) );
> probably isn't a good example if LC_MESSAGES is missing on some systems.
> 
> Thanks
> Lee
> 

Unfortunately, I don't know how that should be implemented on top of a
proprietary runtime layer, or any alternative function calls for that
matter.




signature.asc
Description: OpenPGP digital signature

[ANNOUNCEMENT] Updated: gcc-8.3.0-1 (x86/x86_64)

[JonY]

gcc-8.3.0-1 has been uploaded for Cygwin. This version is for testing.

Known issues:
* ADA support in i686 cygwin is broken, and is not available as of writing.
* i686 debuginfo file is currently broken.


  *** 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://sourceware.org/lists.html#unsubscribe-simple

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




signature.asc
Description: OpenPGP digital signature

Re: linker (binutils ld) is unable to resolve weak symbol, depends on object file order

[JonY]

On 6/7/19 10:04 AM, Michael Haubenwallner wrote:
> Hi,
> 
> so I'm encountering a strange problem related to object file order passed to
> the linker, with any binutils and gcc version available to setup-x86_64.exe:
> 
> $ cat weak-func.c
> extern void weakfunc() __attribute__((weak));
> void weakfunc() {}
> 
> $ cat weak-main.c
> extern void weakfunc() __attribute__((weak));
> int main() { weakfunc(); }
> 
> $ gcc -o weak.exe weak-func.c weak-main.c
> SUCCESS
> 
> But then, changing the order of input files on the command line does break
> (does work on Linux of course):
> 
> $ gcc -o weak.exe weak-main.c weak-func.c
> /usr/lib/gcc/x86_64-pc-cygwin/8.3.0/../../../../x86_64-pc-cygwin/bin/ld: 
> /tmp/ccIthYHe.o:weak-main.c:(.text+0xe): relocation truncated to fit: 
> R_X86_64_PC32 against undefined symbol `weakfunc'
> collect2: error: ld returned 1 exit status
> 
> So the difference is that the object providing weakfunc is passed to
> the linker after the object requiring weakfunc.
> 
> Attached is the weak-func.sh script that does perform these commands.
> 
> Thanks!
> /haubi/
> 

Unfortunately, PE doesn't really have a concept of weak symbols like
ELF, and is known to be broken in binutils.



signature.asc
Description: OpenPGP digital signature

[ANNOUNCEMENT] Updated: mingw64-{headers,runtime,winpthreads} 7.0.0-1

[JonY]

Now released for both 32bit and 64bit Cygwin:

Notable changes:
* _FORTIFY_SOURCE support thanks to Christian Franke.
* Lots of math fixes from Martin Storsjö.
* Many headers updated from Wine by Jacek Caban.
* UCRT support by Martin Storsjö.


  *** 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@cygwin.com

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

http://sourceware.org/lists.html#unsubscribe-simple

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

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

[ANNOUNCEMENT] Updated: w32api-{headers,runtime}-7.0.0-1 (x86/x86_64)

[JonY]

Now released for both 32bit and 64bit Cygwin:

w32api-headers-7.0.0-1
w32api-runtime-7.0.0-1

Based on mingw-w64-v7.0.0.

  *** 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@cygwin.com

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

http://sourceware.org/lists.html#unsubscribe-simple

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



signature.asc
Description: OpenPGP digital signature

Re: Updated: w32api-{headers,runtime}-7.0.0-1 (x86/x86_64)

[JonY]

On 11/13/19 3:36 PM, JonY wrote:
> Now released for both 32bit and 64bit Cygwin:
> 
> w32api-headers-7.0.0-1
> w32api-runtime-7.0.0-1
> 
> Based on mingw-w64-v7.0.0.
> 
>   *** 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@cygwin.com
> 
> If you need more information on unsubscribing, start reading here:
> 
> http://sourceware.org/lists.html#unsubscribe-simple
> 
> Please read *all* of the information on unsubscribing that
> is available starting at this URL.
> 

Looks like there may be issues with the 32bit version blocked by Cygwin
Calm, will investigate later today.



signature.asc
Description: OpenPGP digital signature

Re: [ANNOUNCEMENT] Updated: w32api-{headers,runtime}-7.0.0-1 (x86/x86_64)

[JonY]

On 11/14/19 3:14 PM, Brian Inglis wrote:
> On 2019-11-14 01:55, Biswapriyo Nath wrote:
>> Also, w32api-headers version 7 for x86_64 is missing.
>> Link: https://cygwin.com/cgi-bin2/package-grep.cgi?grep=w32api&arch=x86_64
> 
> Calm problems now resolved:
> Search Results
> Found 6 matches for w32api-headers
> cygwin32-w32api-headers-3.2.0-1 - Win32 API headers for Cygwin 32bit toolchain
> cygwin32-w32api-headers-4.0.4-1 - Win32 API headers for Cygwin 32bit toolchain
> w32api-headers-5.0.2-1 - MinGW-w64 Windows API headers for Cygwin
> w32api-headers-5.0.3-1 - MinGW-w64 Windows API headers for Cygwin
> w32api-headers-5.0.4-1 - MinGW-w64 Windows API headers for Cygwin
> w32api-headers-7.0.0-1 - MinGW-w64 Windows API headers for Cygwin
> 
> Shouldn't cygwin{32,64}-win32api-{headers,runtime}-7.0.0-1 (x86/x86_64) also 
> be
> available/updated at the same time?
> 

There was a problem with generating debuginfo for 32bit w32api-runtime,
llvm-objdump called by cygport isn't generating any. Making it use
binutils objdump fixed it.

I've uploaded the 32bit version as well.



signature.asc
Description: OpenPGP digital signature

[ANNOUNCEMENT] Updated: gcc-9.2.0-1 (x86/x86_64) (Testing)

[JonY]

gcc-9.2.0-1 has been uploaded for Cygwin. This version is for testing.

Known issues:
* ADA support is still broken, even for x86_64.


  *** 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://sourceware.org/lists.html#unsubscribe-simple

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



signature.asc
Description: OpenPGP digital signature

Re: [ANNOUNCEMENT] Updated: gcc-9.2.0-1 (x86/x86_64) (Testing)

[JonY]

On 2/1/20 6:34 PM, Steven Penny wrote:
> On Wed, 8 Jan 2020 13:38:17 +0000, JonY wrote:
>> gcc-9.2.0-1 has been uploaded for Cygwin. This version is for testing.
> 
> https://cygwin.com/ml/cygwin/2020-01/msg00077.html
> 
> Any chance of an update for these?
> 
> - mingw64-x86_64-gcc-core
> - mingw64-x86_64-gcc-g++
> 
> It appears they are both over a year old, which is quite some time for a
> compiler. I have some workarounds here in the meantime:
> 
> - http://repo.msys2.org/mingw/x86_64
> - https://github.com/mstorsjo/llvm-mingw
> - https://musl.cc
> 

I normally don't update mingw-w64 compilers unless the cygwin gcc has
stabilized.

Do you need it ASAP? I can work on it soon if required.



signature.asc
Description: OpenPGP digital signature

[ANNOUNCEMENT] Updated: gcc-9.2.0-2 (x86/x86_64)

[JonY]

gcc-9.2.0-2 has been uploaded for Cygwin. This version is the same as
-1, just repackaged and marked as stable.

Known issues:
* ADA support has been dropped, select version 7.4.0-1 if ADA support is
still needed.


  *** 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://sourceware.org/lists.html#unsubscribe-simple

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




signature.asc
Description: OpenPGP digital signature

Re: [ANNOUNCEMENT] Updated: gcc-9.2.0-2 (x86/x86_64)

[JonY]

On 2/24/20 8:21 PM, Achim Gratz wrote:
> JonY writes:
>> gcc-9.2.0-2 has been uploaded for Cygwin. This version is the same as
>> -1, just repackaged and marked as stable.
> 
> This version of gcc requires a newer binutils than defined as current in
> the Cygwin repo, so until this gets corrected one needs to manually
> switch to the test version binutils-2.31.1-1.
> 
> 
> Regards,
> Achim.
> 

Sorry, looks like I have the test version already installed locally.
I'll update binutils ASAP.



signature.asc
Description: OpenPGP digital signature

[ANNOUNCEMENT] Updated: binutils-2.34-1 (x86/x86_64)

[JonY]

The following packages have been uploaded to the Cygwin distribution:

* binutils-2.34

This version was tested by building gcc-9.2.0.


  *** 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://sourceware.org/lists.html#unsubscribe-simple

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




signature.asc
Description: OpenPGP digital signature

[ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64}-gcc-9.2.0-1

[JonY]

The mingw-w64 cross compilers have been updated:

* mingw64-i686-gcc-9.2.0-1
* mingw64-x86_64-gcc-9.2.0-1


  *** 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://sourceware.org/lists.html#unsubscribe-simple

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



signature.asc
Description: OpenPGP digital signature

[ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64}-binutils-2.34-1

[JonY]

The mingw-w64 cross compilers have been updated:

* mingw64-i686-binutils-2.34-1
* mingw64-x86_64-binutils-2.34-1

  *** 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://sourceware.org/lists.html#unsubscribe-simple

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




signature.asc
Description: OpenPGP digital signature

Re: [ANNOUNCEMENT] Updated: binutils-2.34-1 (x86/x86_64)

[JonY]

On 2/29/20 7:23 PM, Marco Atzeri wrote:
> Am 26.02.2020 um 11:35 schrieb JonY:
>> The following packages have been uploaded to the Cygwin distribution:
>>
>> * binutils-2.34
>>
>> This version was tested by building gcc-9.2.0.
>>
> 
> It seems there is a regression about -lpthread
> 
> *** Warning: linker path does not have real file for library -lpthread.
> *** I have the capability to make that library automatically link in when
> *** you link to this library.  But I can only do this if you have a
> *** shared version of the library, which you do not appear to have
> *** because I did check the linker path looking for a file starting
> *** with libpthread and none of the candidates passed a file format test
> *** using a file magic. Last file checked: /lib/libpthread.a
> 
> -- 
> Problem reports:   http://cygwin.com/problems.html
> FAQ:   http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
> 

Last file checked: /lib/libpthread.a

Is that correct? Do you have the complete command line? Is this
happening on both archs or just i686?



signature.asc
Description: OpenPGP digital signature

Cygwin libtool confused about link library

[JonY]

On 3/1/20 11:00 AM, Marco Atzeri wrote:
>>
>> Last file checked: /lib/libpthread.a
>>
>> Is that correct? Do you have the complete command line? Is this
>> happening on both archs or just i686?
>>
> 
> both archs.
> The error is likely coming from libtool and it is valid for all the 3
> libraries "-lpthread -lrt -ldl" , so I assume the current binutils is
> providing some feedback different than in the past to libtool
> 
> I tested again the build of gdal-3.0.2-2 that before the
> update of gcc and binutils was working fine.
> 
> I shorted the command line as the amount of object is very very large:
> 
> /bin/sh
> /cygdrive/d/cyg_pub/devel/gdal/prova302/gdal-3.0.2-2.x86_64/build/libtool 
> --mode=link
> --silent g++   -lcrypto -ljson-c -lqhull -L/usr/lib -lgeos_c -lwebp 
> -lsqlite3 -lodbc32 -lodbccp32 -lexpat -lopenjp2  -L/usr/lib -lnetcdf
> -lhdf5 -lgif -ljpeg -lgeotiff -ltiff -lpng -lcfitsio -lpq -lproj -lz
> -lpthread -lrt -ldl  -lws2_32 -lpsapi -lpcre -lcurl -liconv -L/usr/lib
> -lxml2 -lz -llzma -liconv -lm -o libgdal.la ./ogr/gml2ogrgeometry.lo
> ./ogr/ogr2gmlgeometr
> y.lo ./ogr/ogr_api.lo ..
> 
> /cygdrive/d/cyg_pub/devel/gdal/prova302/gdal-3.0.2-2.x86_64/build/third_party/o/RLE.lo
> \
>     -rpath /usr/lib \
>     -no-undefined \
>     -version-info 26:2:0
> 

I was a bit confused for a moment, but this looks like the cygwin
builds, not cross compiles.

My current (horrible hack)workaround is to edit the libtool script, change:
deplibs_check_method="pass_all"



Hello libtool folks,
Any ideas about this? Something confused the file magic command?
dlltool --identify does show libdl.a is associated with cygwin1.dll for
example.



signature.asc
Description: OpenPGP digital signature

Re: Failing build when using binutils 2.34-1 on Cygwin 32/64-bit

[JonY]

On 3/4/20 8:59 AM, Joachim Metz wrote:
> I maintain numerous projects, as part of that I've set up CI tests that use
> current Cygwin 32-bit and 64-bit. Recently I've noticed that builds were
> failing with errors like:
> 
> https://ci.appveyor.com/project/libyal/libfwsi/build/job/7b822r4j4ghfs2m5#L953
> 
> /usr/lib/gcc/i686-pc-cygwin/9.2.0/../../../../i686-pc-cygwin/bin/ld:
> fwsi_test_error.o: in function `fwsi_test_error_sprint':
> /home/appveyor/libfwsi/tests/fwsi_test_error.c:72: undefined reference to
> `_imp__libfwsi_error_sprint'
> 
> https://ci.appveyor.com/project/libyal/libfwsi/build/job/3qnu5pk3lm4u12pe#L960
> 
> /home/appveyor/libfwsi/tests/fwsi_test_error.c:72: undefined reference to
> `__imp_libfwsi_error_sprint'
> /home/appveyor/libfwsi/tests/fwsi_test_error.c:72:(.text.startup+0x24):
> relocation truncated to fit: R_X86_64_PC32 against undefined symbol
> `__imp_libfwsi_error_sprint'
> 
> Since I did not make significant changes to the project sources I started
> analyzing the build environment. I was able to reproduce the issues
> with binutils 2.34-1 on Cygwin 64-bit on a separate Windows 10
> installation.
> 
> When I reverted to binutils 2.31-1 the build issues do NOT surface. I
> suspect a change or issue with binutils 2.34-1 is causing the build issues.
> Happy to provide additional details / help troubleshooting where possible.
> 
> Kind regards,
> Joachim
> 

Can you compare the objects where that symbol is supposed to be defined
and the objects where it is supposed to be referenced between the 2
binutils versions?

Can you make a minimalist test case?

Might be a good idea to file a ticket with binutils too.




signature.asc
Description: OpenPGP digital signature

[ANNOUNCEMENT] Updated: gcc-9.2.0-3 (x86/x86_64)

[JonY]

gcc-9.2.0-3 has been uploaded for Cygwin. This version is the same as
-2, but rebuilt with ISL updated.

Known issues:
* ADA support has been dropped, select version 7.4.0-1 if ADA support is
still needed.


  *** 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://sourceware.org/lists.html#unsubscribe-simple

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



signature.asc
Description: OpenPGP digital signature

[ANNOUNCEMENT] Updated: mingw64-{i686,x86_64}-gcc-9.2.0-2

[JonY]

The mingw-w64 cross compilers have been updated:

* mingw64-i686-gcc-9.2.0-2
* mingw64-x86_64-gcc-9.2.0-2

These are the same as -1, but rebuilt with ISL updated.


  *** 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://sourceware.org/lists.html#unsubscribe-simple

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



signature.asc
Description: OpenPGP digital signature

Re: Cygwin libtool confused about link library

[JonY]

On 3/9/20 9:01 PM, Simon Marchi wrote:
>> Hello libtool folks,
>> Any ideas about this? Something confused the file magic command?
>> dlltool --identify does show libdl.a is associated with cygwin1.dll for
>> example.
> 
> Hi,
> 
> I stumbled on this and dug into libtool, here's what I found.
> 
> As part of the process of identifying the nature these libraries, libtool uses
> this nm + sed snippet [1]:
> 
>   win32_nmres=`eval $NM -f posix -A \"$func_to_tool_file_result\" |
> $SED -n -e '
>   1,100{
>   / I /{
>   s|.*|import|
>   p
>   q
>   }
>   }'`
>   ;;
> 
> The sed scripts looks for a line containing the " I " string.
> 
> With binutils < 2.34, the nm output looked like:
> 
>   /usr/lib/libdl.a[d00.o]: libdl_dll_iname I 
> 
> With binutils 2.34, the corresponding line is:
> 
>   /usr/lib/libdl.a[d00.o]: libdl_dll_iname D 0
> 
> And therefore the library is mis-identified.
> 
> The commit that introduced this regression is:
> 
>   commit a288c270991de1578ad28ac312120f4167347234
>   Author: Alan Modra 
>   Date:   Fri May 3 21:36:46 2019 +0930
> 
>   PR24511, nm should not mark symbols in .init_array as "t"
> 
> I tried building the latest commit on the binutils-2_34-branch, and the 
> behavior
> has been restored (the line shows " I " again).  The commit that restored the
> behavior is:
> 
>   commit 40bfb9762747f8336b17c70a0173d10200fa62eb
>   Author: Alan Modra 
>   Date:   Thu Feb 27 17:28:47 2020 +1030
> 
>   Re: PR24511, nm should not mark symbols in .init_array as "t"
> 
> So this should all go back to normal when there is a binutils 2.34.1 release 
> and it is
> packaged by Cygwin.  In the mean time, the commit that restored the behavior 
> could maybe
> be backported in the Cygwin package, but I don't know what the habits are in 
> Cygwin for
> this kind of thing.
> 
> Simon
> 
> [1] 
> https://github.com/autotools-mirror/libtool/blob/b9b44533fbf7c7752ffd255c3d09cc360e24183b/build-aux/ltmain.in#L3050-L3059
> 

Thanks for investigating, I'll see about doing a new binutils release.



signature.asc
Description: OpenPGP digital signature
"--Problem reports:   http://cygwin.com/problems.htmlFAQ:   
http://cygwin.com/faq/Documentation: 
http://cygwin.com/docs.htmlUnsubscribe info:  
http://cygwin.com/ml/#unsubscribe-simple";

[ANNOUNCEMENT] New package: lzip-1.8-1

[JonY]

Version 1.8-1 of "lzip" has been uploaded.

lzip is a lossless data compressor based on the LZMA algorithm with a 
user interface similar to gzip or bzip2. It supports recovery from 
damaged archives.


Homepage: 

Changes from upstream:

- version 1.8-1 -
   * configure: Set EXEEXT for Cygwin.
   * Makefile.in: Make sure installed programs have .exe extension

  *** 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@cygwin.com

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

http://sourceware.org/lists.html#unsubscribe-simple

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


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

Re: New package: lzip-1.8-1

[JonY]

On 11/17/2009 23:18, Buchbinder, Barry (NIH/NIAID) [E] wrote:

JonY sent the following at Wednesday, November 11, 2009 6:36 AM


Version 1.8-1 of "lzip" has been uploaded.

lzip is a lossless data compressor based on the LZMA algorithm with
a user interface similar to gzip or bzip2. It supports recovery from
damaged archives.

Homepage:<http://www.nongnu.org/lzip/lzip.html>


Apparently this was up-loaded only to /release-2/ (1.7).  The
announcement says nothing about this being a 1.7-only package.  If it
was meant to also be a 1.5 package, please upload it to /release/.

Thanks to all.

- Barry


Sorry, I have failed to mention it as being a 1.7 only package for now. 
I do not currently have Cygwin 1.5 installed.


I will try to get a Cygwin 1.5 build in a few days.

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

Re: New package: lzip-1.8-1

[JonY]

On 11/19/2009 21:26, Buchbinder, Barry (NIH/NIAID) [E] wrote:

JonY sent the following at Thursday, November 19, 2009 1:18 AM



JonY sent the following at Wednesday, November 11, 2009 6:36 AM


Version 1.8-1 of "lzip" has been uploaded.

lzip is a lossless data compressor based on the LZMA algorithm with a
user interface similar to gzip or bzip2. It supports recovery from
damaged archives.

Homepage:<http://www.nongnu.org/lzip/lzip.html>



On 11/17/2009 23:18, Buchbinder, Barry (NIH/NIAID) [E] wrote:


Apparently this was up-loaded only to /release-2/ (1.7).  The
announcement says nothing about this being a 1.7-only package.  If it
was meant to also be a 1.5 package, please upload it to /release/.


Sorry, I have failed to mention it as being a 1.7 only package for now.
I do not currently have Cygwin 1.5 installed.
I will try to get a Cygwin 1.5 build in a few days.


Jon,

Please don't feel that you have to prepare a 1.5 package for me.  I just
wanted to be sure that a mistake hadn't been made.

I've never used lzip and just wanted to try it.  I'm switching to 1.7
when it will be officially released and can try lzip then.

- Barry
   Disclaimer: Statements made herein are not made on behalf of NIAID.



Hi,
IMO, Cygwin 1.5 is nearly deprecated. For completeness, lzip for Cygwin 
1.5 should be up on the mirrors by now.


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

[1.7] .exe append weirdness

[JonY]

Hi,

I'm using a win64 target cross compiler under Cygwin. I noticed all the 
stripped dlls will eventually end with ".exe".


I am on 32bit Windows XP sp3, Cygwin 1.7.0-64. (Upgrading to -65 causes 
"system shared memory version mismatch detected" for all Cygwin apps, 
its another issue altogether.


This does not happen to native win32 dlls produced with -m32 or with 
Cygwin dlls.


Here's an example session:


u...@user ~
$ echo "int f(void){return 5;}"|x86_64-w64-mingw32-gcc -xc - -shared -o 1.dll

u...@user ~
$ ls
1.dll*

u...@user ~
$ x86_64-w64-mingw32-strip -vs 1.dll
copy from `1.dll' [pei-x86-64] to `stEvbXqW' [pei-x86-64]

u...@user ~
$ ls
1.dll.exe*



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

Re: Mismatch [1.5] [1.7]: lzip-1.8-1

[JonY]

On 11/22/2009 11:17, Christopher Faylor wrote:

On Sat, Nov 21, 2009 at 10:09:38PM +, Dave Korn wrote:

Fergus Daly wrote:


In setup.ini timestamp 1258779760
install: release/lzip/lzip-1.8-1.tar.bz2 101110 bca3c8d04c4fc90d576b264aaa0a08b7
source: release/lzip/lzip-1.8-1-src.tar.bz2 68215 
305bd012b1137907eb41972111d36def
In setup-2.ini timestamp 1258809078
install: release/lzip/lzip-1.8-1.tar.bz2 66427 a9edda6f8c04cc644897f8adc5323ce3
source: release/lzip/lzip-1.8-1-src.tar.bz2 68198 
12dbe475f1b28bede603bdfac091331b
Same version number, different versions?


  Well, yes; one's for 1.5 and the other is for 1.7.


But one really should be -1 and the other -2 for just this reason.



Ok, should I release a -2 at the same time for both 1.5 and 1.7, or a -2 
just for 1.5 should do?


I didn't have Cygwin 1.5 installed when I packaged for 1.7. lzip for 1.5 
was released after OP asked about it, some time later after lzip for 1.7 
was uploaded.


Sorry about the mess.

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

Re: Mismatch [1.5] [1.7]: lzip-1.8-1

[JonY]

On 11/22/2009 12:17, Eric Blake wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to JonY on 11/21/2009 9:12 PM:


But one really should be -1 and the other -2 for just this reason.



Ok, should I release a -2 at the same time for both 1.5 and 1.7, or a -2
just for 1.5 should do?


Release a single -2 for just one of the two versions (your choice of
whether it is for 1.5 or for 1.7); but do NOT do a -2 for both 1.5 and
1.7, or we are right back to the complaint.  In future builds, if you want
to continue supporting both 1.5 and 1.7, be sure that the numbering for
1.5 is different than the numbering for 1.7.  That way, when someone asks
about -1, you can unambiguously determine for which version of cygwin they
are asking about.



Hi,

Good point, I haven't thought of that. I've sent -2 for 1.7 to cygwin-apps.

Perhaps somebody should add a hint to packaging guide at 
<http://cygwin.com/setup.html> about maintaining packages for 2 or more 
versions of Cygwin.


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

[ANNOUNCEMENT] [1.7] Updated: lzip 1.8-2

[JonY]

Version 1.8-2 of "lzip" has been uploaded for Cygwin 1.7.

lzip is a lossless data compressor based on the LZMA algorithm with a
user interface similar to gzip or bzip2. It supports recovery from
damaged archives.

Homepage: 

This update fixes a packaging conflict with lzip-1.8-1 on Cygwin 1.5.
There are no actual changes, just a release version bump. Sorry for the
mess.

Changes:

- version 1.8-2 -
* Fix up packaging so Cygwin 1.5 and 1.7 builds do not conflict.

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@cygwin.com

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

http://sourceware.org/lists.html#unsubscribe-simple

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

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

Re: [ANNOUNCEMENT] [1.7] Updated: lzip 1.8-2

[JonY]

On 11/23/2009 17:25, Corinna Vinschen wrote:

On Nov 23 07:28, Fergus wrote:

Sorry, still something not quite right.
setup-2.ini timestamp 1258914641
shows

@ lzip
sdesc: "Lossless data compressor based on the LZMA algorithm."
ldesc: "lossless data compressor based on the LZMA algorithm, with very
  safe integrity checking and a user interface similar to the one of
  gzip or bzip2."
category: Archive
requires: cygwin libgcc1 libstdc++6

but no mention of

version:
install:
source:


Which makes sort of sense, given that no lzip tar archive was in the
release-2/lzip subdirectory.  I fixed that on cygwin.com, so it should
be propagated to the mirrors soon.



Hi,

I thought that setup.ini generation was smart enough to figure it out, 
I'll be sure to have those in the .hint file next time.


btw, lzip-1.8-2.tar.bz2 was missing?

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

Re: [ANNOUNCEMENT] [1.7] Updated: lzip 1.8-2

[JonY]

On 11/23/2009 19:05, Corinna Vinschen wrote:

On Nov 23 18:28, JonY wrote:

On 11/23/2009 17:25, Corinna Vinschen wrote:

On Nov 23 07:28, Fergus wrote:

but no mention of

version:
install:
source:


Which makes sort of sense, given that no lzip tar archive was in the
release-2/lzip subdirectory.  I fixed that on cygwin.com, so it should
be propagated to the mirrors soon.


I thought that setup.ini generation was smart enough to figure it
out, I'll be sure to have those in the .hint file next time.


No!  Don't do that, these are autogenerated values which are NOT
supposed to be in the setup.hint file.


btw, lzip-1.8-2.tar.bz2 was missing?


Yes, as well as the -src.tar.bz2 file.  That was the sole reason for
the missing setup-2.ini entries.



I thought cgf uploaded the packages. Upload went missing?

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

Re: [1.5] question about python/ctypes/dlopen

[JonY]

On 12/4/2009 22:53, kiorky wrote:

Hello, i'm trying to use python ctypes which use under the hood dlopen.
I have a strange permission denied running this following code, if someone have
clues ...

Base code

$ cat test_ctypes.py
from ctypes import  CDLL
CDLL('libgeos_c.dll.a')



Hi,

have you tried loading "cyggeos_c-1.dll" instead of the import library?

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

Re: [1.5] question about python/ctypes/dlopen

[JonY]

On 12/4/2009 23:33, kiorky wrote:



JonY a écrit :

On 12/4/2009 22:53, kiorky wrote:
Hi,

have you tried loading "cyggeos_c-1.dll" instead of the import library?


Yep, just look at the second part of the first mail
It results in "bad address" instead of "permission denied"



Hi,

Sorry, I was jumping to conclusions, I'm not a python guru either. I 
tried with:


>>> import ctypes
>>> ctypes.CDLL("/bin/cygwin1.dll");


It seems to work. I suggest loading other dlls for testing.

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

Re: Appropriate expectation on the degree of cygwin and MS interoperability

[JonY]

On 1/1/2010 20:06, neil.mowb...@calgacus.com wrote:

Folks,

A bit of a vague question but any greater clarity concerning the appropriate
level of interoperability between Cygwin and MS would be appreciated.

I have my Windows 6 and 7 platforms configured to build software using
different toolchains, the most common being (1) Visual Studio 10 and (2)
Cygwin with gcc-4.

When using the Visual Studio toolchain I will prefer a cygwin tool over a
MS tool, so for example, I always use bash and gnu make and never use the
cmd shell/power shell or nmake.  Taking this further, I will try to use
nm over dumpbin and ar over lib.

For the most part the cygwin tools interoperate with MS artifacts but
it does break down, especially, with 64bit artifacts.  For example, nm
can work with 32bit object files created by MS cl.exe but it cannot
work with 64bit MS object files (unrecognised file format).

The question is: how far should I expect the interoperability to go?
For example, is the fact that nm cannot handle 64bit MS object files
a (1) defeat in cygwin/nm or (2) I should be grateful that it works
with 32bit files and otherwise lower my expectation?

I suppose at its core the question is about the intent of cygwin.  Is
it (1) to provide unix like capabilities to a MS platform (in which case
one would expect/demand a high degree of interoperability), or
(2) to provide a unix like island inside a MS platform?

The problem with (2) is one cannot really stay isolated from the
host MS environment.

My previous question of how/if one can use cyginw *.h *.dll *.a
artifacts in a MS compiled program is essentaily the same theme
although I have lower expectations that it is possible.

Any pointers?


Hi,

for nm to recognize 64bit objects, you need to rebuild binutils to 
recognize 64bit objects. Use 
--enable-target=i686-pc-cygwin,x86_64-w64-mingw32 with binutils 
configure. Beware that MSVC now uses the "short" library format instead 
of the older "long" library format used by the GNU toolchain.


See  for toolchains targeting win64.

IMHO Cygwin is more of an island, you're supposed to use Cygwin tools 
only under Cygwin. Others might have different opinions.


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

Re: Appropriate expectation on the degree of cygwin and MS interoperability

[JonY]

On 1/1/2010 20:37, JonY wrote:

On 1/1/2010 20:06, neil.mowb...@calgacus.com wrote:

Folks,

A bit of a vague question but any greater clarity concerning the
appropriate
level of interoperability between Cygwin and MS would be appreciated.

I have my Windows 6 and 7 platforms configured to build software using
different toolchains, the most common being (1) Visual Studio 10 and (2)
Cygwin with gcc-4.

When using the Visual Studio toolchain I will prefer a cygwin tool over a
MS tool, so for example, I always use bash and gnu make and never use the
cmd shell/power shell or nmake. Taking this further, I will try to use
nm over dumpbin and ar over lib.

For the most part the cygwin tools interoperate with MS artifacts but
it does break down, especially, with 64bit artifacts. For example, nm
can work with 32bit object files created by MS cl.exe but it cannot
work with 64bit MS object files (unrecognised file format).

The question is: how far should I expect the interoperability to go?
For example, is the fact that nm cannot handle 64bit MS object files
a (1) defeat in cygwin/nm or (2) I should be grateful that it works
with 32bit files and otherwise lower my expectation?

I suppose at its core the question is about the intent of cygwin. Is
it (1) to provide unix like capabilities to a MS platform (in which case
one would expect/demand a high degree of interoperability), or
(2) to provide a unix like island inside a MS platform?

The problem with (2) is one cannot really stay isolated from the
host MS environment.

My previous question of how/if one can use cyginw *.h *.dll *.a
artifacts in a MS compiled program is essentaily the same theme
although I have lower expectations that it is possible.

Any pointers?


Hi,

for nm to recognize 64bit objects, you need to rebuild binutils to
recognize 64bit objects. Use
--enable-target=i686-pc-cygwin,x86_64-w64-mingw32 with binutils
configure. Beware that MSVC now uses the "short" library format instead
of the older "long" library format used by the GNU toolchain.



Correction:
I mean ".obj" object file format, not the ".lib" library format. The
latter stays mostly the same.

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

Re: old install instructions? -mnomingw being removed?

[JonY]

On 1/2/2010 07:52, Ken Tilton wrote:

Sorry, I am a complete noob to all this make/install/gcc stuff, I am just trying
to make a fresh build of a DLL I have used for years to see if it resolves a
problem.

I installed cygwin 1.7.1 today on a windows 7 laptop.

The directions for my library are great:

"VER=8.4.12
SRCDIR=`pwd`

cd $SRCDIR/tcl$VER/win
env 'CC=gcc -mno-cygwin' ./configure --enable-threads
make libtclstub84.a

cd $SRCDIR/tk$VER/win
env 'CC=gcc -mno-cygwin' ./configure --enable-threads
make libtkstub84.a

cd $SRCDIR/Togl
env 'CC=gcc -mno-cygwin' ./configure --with-tcl=../tcl$VER/win --with-
tk=../tk$VER/win

make"

That's from doc for the lib which is Togl, an OpenGL add-on widget to Tcl/Tk.
Unfortunately the mailing list does not seem active, because:

The first env command responds "C compiler cannot create executables" and refers
me to the config.log. That has a few lines showing the -mno-cygwin flag has been
removed and telling me to use a mingw-targeted cross-compiler.

Not sure if those are warnings or that is why later what looks to be a hello-
world-like little C compile reports failure leading next to the "cannot create
exes" message.

Googling did turn up a long-ago discussion mentioning deprecating no-mingw (and
to my relief that this is not something poor know-nothings like me should
encounter) but the obvious solution ("a mingw-targeted cross-compiler") did not
work out two ways:

1. Just googling that did not cause anything to jump out at me.
2. I am wondering if this is a cross-compiler situaton, since I am on Windows
trying to build a windows DLL.

Any clues greatly appreciated!

kt



Hi,

The -mno-cygwin option has been removed from gcc4.

If you need it, install the gcc-mingw package via the Cygwin setup, and
use CC="gcc-3 -mno-cygwin" instead. It is an older version of GCC, but
it will get you somewhere.

Yes, it is a cross-compile situation. MinGW and Cygwin are considered
different hosts even if both are running on Windows. Cygwin programs
use cygwin1.dll while MinGW programs use msvcrt.dll.

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

Re: [ANNOUNCEMENT] [1.7] Updated: cygport-0.9.80-1

[JonY]

On 1/7/2010 16:42, Yaakov (Cygwin/X) wrote:

The following package has been updated for Cygwin 1.7:

*** cygport: 0.9.80-1



Hi,

The Cygwin setup lists 0.9.9-1 as latest, 0.9.80-1 as another available 
version, so any idea whats wrong?


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

Re: [ANNOUNCEMENT] [1.7] Updated: cygport-0.9.80-1

[JonY]

On 1/8/2010 03:05, Yaakov (Cygwin/X) wrote:

On 07/01/2010 10:05, JonY wrote:

The Cygwin setup lists 0.9.9-1 as latest, 0.9.80-1 as another available
version, so any idea whats wrong?


I checked setup.ini, and it shows 0.9.80-1 as latest and 0.9.9-1 as
previous.


Yaakov



Hi,

Strangely, I had to manually select 0.9.80-1 over the default 0.9.9-1. 
Anyway, 0.9.80-1 installed without issues once I selected it.


Thanks for updating it.

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

[ANNOUNCEMENT] Updated: lzip-1.9-1

[JonY]

Version 1.9-1 of "lzip" has been uploaded.

lzip is a lossless data compressor based on the LZMA algorithm with a
user interface similar to gzip or bzip2. It supports recovery from
damaged archives.

Homepage: 

This is a new upstream release. Changes include:

2010-01-17  Antonio Diaz Diaz  

* Version 1.9 released.
* main.cc (main): return at least 1 if closing stdout fails.
* Makefile.in: Added "--name" option to help2man invocation.
* testsuite/check.sh: Use "test1" instead of "COPYING" for testing.

  *** 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@cygwin.com

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

http://sourceware.org/lists.html#unsubscribe-simple

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


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

Re: ./configure on cygwin in window platform

[JonY]

On 2/1/2010 21:49, J J wrote:

Please help me out. I spent for three days but I still could install gcc in 
window on cygwin.

Problem is I could not install gcc file, 
(mingw-w64-trunk-snapshot-20091222.tar.bz2), on cygwin in window platform.

I would like to unpack and intall gcc (mingw-w64-trunk-snapshot-20091222.tar.bz2) on 
cygwin on window platform. I follow instruction posted on 
http://cygwin.wikia.com/wiki/How_to_install_GCC_4.3.0. The problem I have found out is I 
could not process the configure step as below. The result shows "No such file or 
directory"

Steps:
$ mkdir build
$ cd build
$ ../gcc-*/configure --enable-languages=c,c++
$ make
$ make install

May it be because of (1) setting srcdir or objdir non-correctly or (2) else ?

What I have done are:
1. Download gcc file and load it into /usr/build. Build subfolder is created by 
me. -->  ( equal to $ mkdir build  and  $ cd build)
2. Unpack gcc tar.bz2 file (mingw-w64-trunk-snapshot-20091222.tar.bz2) on that 
location. -->  It generates trunk subfolder that contains some subfolder too.
3. $mkdir build  and $cd build -->  current location is urs/build
4. $ ../trunk/configure --enable-languages=c,c++  -->  It does not work. Error = "No 
such file or directory"

Comparing to what you recommend on http://gcc.gnu.org/install/configure.html ,

To configure GCC:
% mkdir objdir
% cd objdir
% srcdir/configure [options] [target]

You mentions that  objdir can not be a subdirectory of srcdir.  This is why I 
tried one more time with the different folder and the same level under usr 
folder. What I did are:

1. Download gcc (mingw-w64-trunk-snapshot-20091222.tar.bz2) for window platform 
again into usr/tmp
2. Unpack it in the usr/tmp/. The path result are approximately
 usr/tmp/trunk/mingw..1*
 usr/tmp/trunk/mingw..2*
 usr/tmp/trunk/mingw..3*
 usr/tmp/trunk/mingw..4*

3. $cd build -->  under usr folder -->  current location is usr/build -->  
build is already created by me on the previous work.
4  command to configure ->  $../mingw-w64-trunk-snapshot-20091222.tar.bz2/configure 
--enable-language=c,c++  -->  Show error msg = "No such file or directory"
5. Try $ ../trunk/mingw-w64-trunk-snapshot-20091222.tar.bz2/configure 
--enable-language=c,c++  -->  Show error msg = "No such file or directory".


Please help me out. I don't why I could not and thank you very much,
Jasmine
Ps. I am pretty much new with cygwin and this is my first time.


Hi,

you've unpacked it to usr/tmp/trunk..., in usr/build, use ../trunk
/.../mingw... instead.

You have also forgot to set --target, please read the mingw-w64 build
instructions more carefully.

I suggest you read .
It would help a new user like you to make sense of the CLI environment.


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

[ANNOUNCEMENT] Updated: lzip-1.10-1

[JonY]

Version 1.10-1 of "lzip" has been uploaded.

lzip is a lossless data compressor based on the LZMA algorithm with a
user interface similar to gzip or bzip2. It supports recovery from
damaged archives.

Homepage: 

This is a new upstream release. Changes include:

2010-04-05  Antonio Diaz Diaz  

* Version 1.10 released.
* decoder.h: Input_buffer integrated in Range_decoder.
* main.cc: File specified with option "-o" is now created with
  mode 0666 if umask allows it, deleted if interrupted by user.
* main.cc: New constant "o_binary".
* main.cc: Dictionary size for options -2, -3, -4 and -8 has
  been changed to improve linearity of compressed sizes.
* lzip.h: Fixed warnings produced by over-optimization (-O3).
* Makefile.in: Added quotes to directory names.


  *** 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@cygwin.com

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

http://sourceware.org/lists.html#unsubscribe-simple

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


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

Re: GIT (was: Coverity Scan)

[JonY]

On 4/26/2014 07:27, Andrey Repin wrote:
> This is exactly what makes me dislike it strongly. This, and idiotic model of
> copying whole repository to my machine, when I only want to glance at the
> source code, and find the culprit of my current issues.
> I've spent 3 hours downloading a 200Mb repo of a project, where the Subversion
> client pulled 4 or 5Mb HEAD of it in like 10 minutes, once I realized what an
> idiotic weight I pulled and went to google to see if it can be done better.
> And "fine control" doesn't mix with "project consistency" at all.
> Subversion is aimed at versioning of a whole project, in a supposedly
> consistent state at each version. What can be more "fine" than this, is beyond
> my understanding.

git clone --depth 1 if you don't care about history.

> You can still commit separate files from working copy, though, but this
> practice is discouraged for the greater good of the project you develop.
> 

Don't you need to git add individual files to mark for commit? Won't you
get into the same problems if you forgot to commit files in SVN?





signature.asc
Description: OpenPGP digital signature

ioctl crash in mpg123

[JonY]

Hi,

I am debugging a crash in Cygwin 1.7.29-2 ioctl but I am not familiar
with the OSS sounds API. I traced the ioctl calls and made this example,
is it supposed to work?

#include 
#include 
#include 
#include 
#include 
#include 
#include 

int main(){
  int fmt = AFMT_MU_LAW;
  int chan = 0;
  int fd = open("/dev/dsp", O_WRONLY);
  ioctl(fd, SNDCTL_DSP_RESET, NULL);
  ioctl(fd, SNDCTL_DSP_RESET, NULL);
  ioctl(fd, SNDCTL_DSP_RESET, NULL);
  ioctl(fd, SNDCTL_DSP_SETFMT, &fmt);
  ioctl(fd, SNDCTL_DSP_STEREO, &chan); /* crashes here */
  close(fd);
  exit(0);
}



signature.asc
Description: OpenPGP digital signature

Re: ioctl crash in mpg123

[JonY]

On 5/2/2014 23:15, Christopher Faylor wrote:
> On Fri, May 02, 2014 at 07:16:25PM +0800, JonY wrote:
>> Hi,
>>
>> I am debugging a crash in Cygwin 1.7.29-2 ioctl but I am not familiar
>> with the OSS sounds API. I traced the ioctl calls and made this example,
>> is it supposed to work?
> 
> If you're asking if Cygwin is supposed to SEGV in certain situations the
> answer is "no".
> 
> This should be fixed in the next snapshot.
> 
> Thanks for the test case.
> 
> cgf
> 

Thanks for fixing this quickly!




signature.asc
Description: OpenPGP digital signature

Re: gcc-4.9.0 patch status

[JonY]

On 5/8/2014 17:20, Rainer Emrich wrote:
> I try to bootstrap gcc-4.9.0 for cygwin 64-bit, but this fails in adalib.
> AFAIS upstream are still some patches missing which are in the gcc-4.8.2-3 
> source.
> 
> Does anybody knows the status for these patches?
> 

I am working on them, albeit slowly, you can look at the current 4.8.x
patches, some need rebasing.




signature.asc
Description: OpenPGP digital signature

Re: gcc-4.9.0 patch status

[JonY]

On 5/8/2014 17:43, JonY wrote:
> On 5/8/2014 17:20, Rainer Emrich wrote:
>> I try to bootstrap gcc-4.9.0 for cygwin 64-bit, but this fails in adalib.
>> AFAIS upstream are still some patches missing which are in the gcc-4.8.2-3 
>> source.
>>
>> Does anybody knows the status for these patches?
>>
> 
> I am working on them, albeit slowly, you can look at the current 4.8.x
> patches, some need rebasing.
> 
> 

CC'ed. I only plan to put 4.9.0 into experimental if I do actually fix
the patches. The actual release will probably come from 4.9.1 or later.




signature.asc
Description: OpenPGP digital signature

[ANNOUNCEMENT] Updated: w32api-headers-3.1.0-2

[JonY]

New release for both 32bit and 64bit Cygwin:

w32api-headers-3.1.0-2

This update contains some correction and updates for the GL headers.

  *** 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@cygwin.com

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

http://sourceware.org/lists.html#unsubscribe-simple

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





signature.asc
Description: OpenPGP digital signature

[ANNOUNCEMENT] Updated: gcc-4.9.0-1 experimental (x86_64)

[JonY]

gcc-4.9.0-1 for 64-bit Cygwin is now uploaded as experimental, no
serious testing has been done yet, you may use it for not-so-important work.

  *** 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://sourceware.org/lists.html#unsubscribe-simple

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




signature.asc
Description: OpenPGP digital signature

Re: Default manifest

[JonY]

On 5/21/2014 21:19, Ken Brown wrote:
>>
>> For the default manifest to get going we also need the patcha new GCC
>> with Nick's patch from
>>
>>https://gcc.gnu.org/ml/gcc-patches/2014-04/msg01378.html
>>
>> Is that easily backportable to GCC 4.8, or does 4.8 not support the
>> %if-exists functionality?
> 
> JonY, any chance we could get a release of GCC that includes this patch?
> 
> Ken
> 

Sure, I'll take a jab at it this weekend.




signature.asc
Description: OpenPGP digital signature

[ANNOUNCEMENT] Updated: gcc-4.8.3-1 (x86/x86_64)

[JonY]

gcc-4.8.3-1 is now uploaded for both 32-bit and 64-bit Cygwin. This
includes a patch to automatically link in the default manifest for
executable files.

Known issues:
Cygwin 64-bit gcc-4.8.3-1 debuginfo package is missing and was not
generated by cygport, I am still investigating this.

  *** 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://sourceware.org/lists.html#unsubscribe-simple

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




signature.asc
Description: OpenPGP digital signature

Re: [ANNOUNCEMENT] Updated: gcc-4.8.3-1 (x86/x86_64)

[JonY]

On 5/29/2014 03:47, Chris J. Breisch wrote:
> Ken Brown wrote:
>> On 5/28/2014 1:13 PM, Chris J. Breisch wrote:
> 
> Yes, the behavior looks exactly like what you described there.
> 
> $ objdump -j .rsrc -s /usr/bin/g++.exe
> 
> /usr/bin/g++.exe: file format pei-x86-64
> 
> Contents of section .rsrc:
> objdump: Reading section failed
> 
> 

gcc.exe seems to work fine though, this could explain the broken debuginfo.

cgf: Should I remove 4.8.3-1 from x86_64 for now until it is fixed?




signature.asc
Description: OpenPGP digital signature

Re: [ANNOUNCEMENT] Updated: gcc-4.8.3-1 (x86/x86_64)

[JonY]

On 5/29/2014 06:20, JonY wrote:
> On 5/29/2014 03:47, Chris J. Breisch wrote:
>> Ken Brown wrote:
>>> On 5/28/2014 1:13 PM, Chris J. Breisch wrote:
>>
>> Yes, the behavior looks exactly like what you described there.
>>
>> $ objdump -j .rsrc -s /usr/bin/g++.exe
>>
>> /usr/bin/g++.exe: file format pei-x86-64
>>
>> Contents of section .rsrc:
>> objdump: Reading section failed
>>
>>
> 
> gcc.exe seems to work fine though, this could explain the broken debuginfo.
> 

64bit 4.8.3-1 has been removed. Please use 4.8.2-3 for now.





signature.asc
Description: OpenPGP digital signature

Re: [ANNOUNCEMENT] Updated: gcc-4.8.3-1 (x86/x86_64)

[JonY]

On 5/29/2014 07:00, JonY wrote:
> 64bit 4.8.3-1 has been removed. Please use 4.8.2-3 for now.
> 

I just realized I just uploaded a fixed 4.8.3-1 with the same 4.8.3-1
version string. I will upload again as 4.8.3-2 soon.




signature.asc
Description: OpenPGP digital signature

Re: [ANNOUNCEMENT] Updated: gcc-4.8.3-1 (x86/x86_64)

[JonY]

On 6/3/2014 03:35, Angelo Graziosi wrote:
> JonY  wrote:
>> I will upload again as 4.8.3-2 soon.
> 
> This evening setup.ini has
> 
> 4.8.2-3 in current
> 
> ==> 4.8.3-2 in prev <==
> 
> 
> Sure this is what you want?
> 

Oh,

Looks like I messed up, I was wondering where it went. I am having
problems connecting to sourceware to check.




signature.asc
Description: OpenPGP digital signature

[ANNOUNCEMENT] Updated: gcc-4.8.3-2 (x86_64)

[JonY]

gcc-4.8.3-2 is now uploaded for 64-bit Cygwin. It is a rebuild of -1,
now with the other frontend drivers working. Debug info is also included.

  *** 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://sourceware.org/lists.html#unsubscribe-simple

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





signature.asc
Description: OpenPGP digital signature

Re: Question on gcc install

[JonY]

On 6/18/2014 05:33, Arthur Schwarz wrote:
> Hi Larry;
> 
> I think I mislead you. Netbeans is quite comfortable with cygwin, and I
> believe demands it in a Windows environment. What Netbeans requires is the
> exact oath to use for gcc, g++, gfortran, the assembler, make file, gdb, and
> qmake (optional). The make file path and gdb are invariant. The other
> executables must be provided (except for the unadornded gcc, g++, gfortran,
> and as). 
> 

http://wiki.osdev.org/Target_Triplet

No, gdb happens to be invariant because you don't have cross gdb
installed. You cannot debug 32bit code with 64bit gdb on Windows.

> The issue of "what's going on" first came up because gcc -m32 did not work
> for any compiler. In talking with  Marc Glisse @ gcc.gnu.org, he had some
> questions on c++config.h. In finding the path to and looking at this file I
> became confused as to the directories available, their use and their
> association with the executables and gcc versions. Given the latest (16 Jun)
> release I am further confused.
> 

Cygwin gcc has never supported -m32.

> At the present time /bin/gcc.exe, etc., works. /bin/*mingw*.exe either
> compiles but does not link, or does not compile - which seems to be a header
> issue. gcc -m32 does not work which may be a gcc.gnu issue.
> 

Can you at least be specific about the errors? It is rather frustrating
reading your emails, being so vague about and all. Are you mixing Cygwin
and mingw code?

> If there is a resource document that I can look at to find the meaning of
> life, could you tell me where to find it? I have downloaded the gcc.gnu.org
> document set for vrs. 4.8.3, Is this sufficient?

My advice is, stop jumping to conclusions, and stop assuming facts about
how things are related, and fix your email client to reply to threads
properly instead of starting a new thread for every reply.




signature.asc
Description: OpenPGP digital signature

Re: Question on gcc install

[JonY]

On 6/18/2014 23:11, Arthur Schwarz wrote:
> I am including cygcheck.out as an attachment. 
> 
> Andrey Repin pointed out to me that my various e-mail responses are
> scattered all over the mailing list. I am very sorry for this and hope that
> at least this e-mail is put in the appropriate place so that proper tracking
> can be done. If you have not seen my prior posts then some of the history
> and flavor of comments in this post may be lost.
> 

Please don't add "--" to separate your text from others too, it is
treated as a signature in some clients.

> I don't think that there is an error in cygwin. I think that the number of
> executables, directories, etc. is by intent. What I am trying to do is to
> discover the intent and then, if necessary, report errors.
> 
> Here are a list of guesses:
>/bin
>   i686-pc-cygwin.*  Related toolchain for a compiler
>   i686-pc-mingw32.* i686/x86 indicates the compiler instruction set
>   i686-w64-mingw32.*pc/w64 = 32/64-bits the input architecture (?)
>   x86_64-pc-cygwin.*cygwin/mingw32 the compiler producer
>   x86_64-w64-mingw32.*
> 
> It is also possible (again I'm guessing) the prefix represents the output
> architecture rather than the compiler architecture. This would (perhaps)
> explain why the gcc -m32 option has been disabled. If the -m32 option is not
> disabled by intent then there is a compiler bug, and if it is disabled by
> intent then this indicates a departure from behavior for a direct port.
> 

None of the toolchains are multilib capable, so -m32/-m64 is not going
to work. See also http://wiki.osdev.org/Target_Triplet

> Each prefix has two related directories:
>/usr   used by the compiler
>   i686-pc-cygwin/
>   i686-pc-mingw32/
>   i686-w64-mingw32
>   x86_64-pc-cygwin
>   x86_64-w64-mingw32
> 
>/usr/lib/gcc  contains version specific data for user (& compiler?)
>   i686-pc-cygwin/vrs/
>   i686-pc-mingw32/vrs/
>   i686-w64-mingw32/vrs/
>   x86_64-pc-cygwin/vrs/
>   x86_64-w64-mingw32/vrs/
> 
> Prefixes with an appended version number in /bin are given as a visual
> indication of the version of the software associated with the prefix. For
> example, i686-pc-cygwin-gcc-4.8.2.exe indicates that the toolchain for
> i686-pc-cygwin is specific to gcc 4.8.2. I think that
> i686-pc-cygwin-gcc-4.8.2.exe is the same file as i686-pc-cygwin-gcc.exe.
> 

Yes.

> Supposing the following seems to have occurred with this release.
> 1: The use of appended version numbers in /bin has been abandoned.
> 2: The latest distribution (16 Jun) has an error in that x86_64-w64-mingw32
> does not have an associated file in /usr/. There is an associated file in
> /usr/lib/gcc however.
> 

What?

> What I would (ultimately) like to discover is resource material containing
> the exact expected configurations and the meanings for all the prefixes.

http://wiki.osdev.org/Target_Triplet

> What is what and what goes where. And I would like to have a resource rather
> than wasting bandwidth on the mailing list. To this I would add that the
> information in /usr/share/doc/gcc is not specific to the installation on
> cygwin, and also that /usr/share/gcc-vrs/ has a nested python script. What
> on Earth is the python script for?
> 

It is for gdb pretty-printing. Your questions are more appropriate on
gcc-help.




signature.asc
Description: OpenPGP digital signature

Re: Question on gcc install

[JonY]

On 6/20/2014 07:58, Arthur Schwarz wrote:
> Hi JonY;
> 
> I hope that this clarifies some of the thing yous mentioned (as well as
> others unmentioned).
> 
> None of the toolchains are multilib capable, so -m32/-m64 is not going
> to work. See also http://wiki.osdev.org/Target_Triplet
>"> info gcc -> Option Index" shows -m32 and -m64 as valid 
>Options Are there plans to change the info files so that 
>they better represent the distributed versions of the 
>compiler?
> 

Yes, they are valid options to gcc, but that does not mean gcc is able
to honor them. None of the builds are specifically set up for multilib.

> No, gdb happens to be invariant because you don't have cross gdb
> installed. You cannot debug 32bit code with 64bit gdb on Windows.
>Would it be possible to clarify that 64-bit compiler target
>Will only work on a compatible 64-bit gdb (same for 32-bit)
>and that in order to get gcc to generate code for 32-bit
>targets the setup-x86.exe must be used ant that in order to
>get 64-bit target code setup-x86_64.exe must be used?
> 
> 

No, use the cross compilers, host and target triplets are not tied to
each other. You can easily run a 32bit compiler that targets 64bt etc,
eg x86_64-w64-mingw32-gcc on 32bit Cygwin.

>> If there is a resource document that I can look at to find the meaning of
>> life, could you tell me where to find it? I have downloaded the 
>> gcc.gnu.org document set for vrs. 4.8.3, Is this sufficient?
> 
> My advice is, stop jumping to conclusions, 
>Could you please clarify what in the above sentence draws a 
>conclusion? Are you saying that if I have concluded that
>documentation exists that it does not?
> 

You jump to conclusion about "version" strings and "triplets", assume
differences where there are none.

> and stop assuming facts about how things are related, 
>Could you please clarify what in the above sentence supports your 
>statement? Are you saying that the gcc documentation for vrs. 4.8.3
>Is not related to the gcc port?
> 

Just start using ${prefix}-gcc for cross compiles, and "gcc" for native
compiles, likewise for other frontend drivers.

> 
>What on Earth is the python script for?
>   It is for gdb pretty-printing. Your questions are more 
>   appropriate on gcc-help.
>  Is there some reason a gdb script is located under
>  A gcc directory and not a gdb directory?
> 

Because libstdc++ internal structures are tied to gcc, not gdb.

> 
>Supposing the following seems to have occurred with this release.
>   1: The use of appended version numbers in /bin has been 
>  abandoned.

That is up to upstream gcc to decide, I don't control how the executable
end up as.

>   2: The latest distribution (16 Jun) has an error in that 
>  x86_64-w64-mingw32 does not have an associated file 
>  in /usr/. There is an associated file in /usr/lib/gcc 
>  however.
> 

It doesn't really matter where it goes, there is no meaning in it.

>   What?
>  In trying to understand your comment I assume that you
>  Are questioning items 1: and 2: above. 
>  1: the latest download, unlike previous downloads, is
>  Missing compiler files such as 
>  i686-pc-cygwin-gcc-4.8.2.exe.

Use "i686-pc-cygwin-gcc", so you don't have to mess around each and
every update.

>  2: In all cases except x86_64-w64-mingw32, there is
> a directory in /usr and /usr/lib/gcc with the
> same toolchain prefix as in /bin. Without being
> tendentious I assume that you understand the
> toolchain prefix as defined in 
> http://wiki.osdev.org/Target_Triplet. You have 
> requested that I make no assumptions, so I now
> assume that the omission is deliberate and 
> need no further investigation or action.
> 

That is right, because there is no hidden conspiracy theory behind it.

>From http://wiki.osdev.org/Target_Triplet the compiler names
>are:
>   machine-vendor-operatingsystem
> 
>For the cygwin distribution this translates to:
> i686-pc-cygwin
> ||  o- operating system
> |o- vendor
> o- target platform
> 
> x86_64-pc-cygwin
> |  |  o- operating system
> |  o- vendor
> o- target platform
> 
> i686-pc-mingw32/
> ||  o- operating system
> |o- vendor
> o- target platform
> 
> i686-w64-mingw32
> ||   o- operating system
> |o-

Re: Question on gcc install

[JonY]

On 6/20/2014 22:37, Arthur Schwarz wrote:
> 
>> At the present time /bin/gcc.exe, etc., works. /bin/*mingw*.exe either
>> compiles but does not link, or does not compile - which seems to be a
> header
>> issue. gcc -m32 does not work which may be a gcc.gnu issue.
>>
> 
> Can you at least be specific about the errors? It is rather frustrating
> reading your emails, being so vague about and all. Are you mixing Cygwin
> and mingw code?
> 
>Sorry. I was remiss.
> 
>Execution fails on all of the mingw compilers with the same error
>message. All compilations use the same command line options.
> 
>> i686-pc-mingw32-g++ -Wall -Wno-reorder -Wno-unused-value -DYYDEBUG=1 
>  -DDEBUG_IO   -c -g -MMD -MP -MF
> 
>> slip.exe
> 
> /E/home/skidmarks/Projects/SLIP/slip/dist/Debug/mingw-Windows/slip.exe:
> error while loading shared libraries: libstdc++-6.dll: cannot open shared
> object file: No such file or directory
> 
> RUN FAILED (exit value 127, total time: 15ms)
> 

You are not supposed to run cross compiled executable files. This is not
even a linker error.

> After execution I ran the following find on /usr.
> 
>> find /usr/i686-pc-cygwin 
>/usr/i686-pc-mingw32 
>/usr/i686-w64-mingw32 
>/usr/x86_64-w64-mingw32 -iname 'libstdc++-6.dll'
> 
> i686-pc-mingw32/sys-root/mingw/bin/libstdc++-6.dll
> i686-w64-mingw32/sys-root/mingw/bin/libstdc++-6.dll
> x86_64-w64-mingw32/sys-root/mingw/bin/libstdc++-6.dll
> 
> /usr/i686-pc-cygwin apparently does not use this dll and the generated mingw
> executables can not find it. Can anything be done about this - I refrain
> from 'guessing', 'inferring', or 'assuming (causality)'.
> 
> 

Do not guess, there is nothing to infer from it, it is done on purpose.
You will need to copy these to where your executable programs are
running. Additionally, you mustn't mix DLLs from different toolchains,
so in this case, take the dll from i686-pc-mingw32.






signature.asc
Description: OpenPGP digital signature

Re: Question on gcc install

[JonY]

On 6/22/2014 00:43, Arthur Schwarz wrote:
>> /E/home/skidmarks/Projects/SLIP/slip/dist/Debug/mingw-Windows/slip.exe:
>> error while loading shared libraries: libstdc++-6.dll: cannot open 
>> shared object file: No such file or directory
>>
>> RUN FAILED (exit value 127, total time: 15ms)
>>
> 
> You are not supposed to run cross compiled executable files. This is not
> even a linker error.
> 
> I compiled my program with each of the mingw32 compilers.
> After each compilation I copied the libstdc++-6.dll into
> the directory containing the compiled executable and then
> ran the compiled code. After each execution I received the
> same error. Are you saying that the mingw32 compiled code
> is cross-compiled to a non-intel, non-windows and/or
> non-cygwin architecture and that is why the code doesn't
> execute? What are you supposed to do with mingw32 compiled
> code instead of executing it?
> 
> 

There you go again with all the implications, mingw32 code is cross
compiled from Cygwin's point of view, so don't run it under Cygwin. Run
it under cmd or something.

Was that too hard to understand?




signature.asc
Description: OpenPGP digital signature

Re: Question on gcc install

[JonY]

On 6/22/2014 12:24, René Berber wrote:
> On 6/21/2014 9:13 PM, JonY wrote:
> 
>> There you go again with all the implications, mingw32 code is cross
>> compiled from Cygwin's point of view, so don't run it under Cygwin. Run
>> it under cmd or something.
>>
>> Was that too hard to understand?
> 
> Yes, because its not true, the code runs fine under Cygwin (as long as
> the executable and its dependencies are in the PATH, or on the current
> working directory, and all of them have the executable attribute set,
> i.e. it follows Windows' rules) the same as any other Windows program
> runs under Cygwin.

Sure you can make it work by messing with PATH, but you'd run into other
issues like PATH translation from the command line etc. Do to simplify
it for the user, just don't do it if you don't know what you're doing.




signature.asc
Description: OpenPGP digital signature

[ANNOUNCEMENT] Updated: mingw64-*-gcc-4.8.3-1

[JonY]

This update includes:

Update:
mingw64-*-gcc-4.8.3-1

*** NOTES ***
gcc-4.8.x is built as is from FSF sources.

C++11 std::to_string is now supported. Caveat: C++11 mode implies C99
mode vsnprintf and vsnwprintf, any calls to these will be redirected to
__mingw_* variants, not to msvcrt. That means no more using "%I64d" in
C++11 mode, use "%lld" or inttypes.h macros instead.

Default manifest support is still not included yet and will be added in
the next release.

**

The cross compiler can produce Win32 and Win64 native binaries. As a
cross compiler, you may use --host=i686-w64-mingw32 or
--host=x86_64-w64-mingw32 for autotools based source packages to build
for Windows.

  *** 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@cygwin.com

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

http://sourceware.org/lists.html#unsubscribe-simple

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






signature.asc
Description: OpenPGP digital signature

Re: cygwin64 problems after update: gcc 4.8.3-2, cygcheck -p

[JonY]

On 7/6/2014 04:15, Lakhsa wrote:
> G'Day,
> 
> after having updated my cygwin64 installation (Win7-64) for OpenSSL
> development I have encountered 2 problems:
> 
>   * compiling for 32-bit with '-m32 -i686' now fails with internal
> compiler error: in extract_insn, at recog.c:2154
>   * cygcheck -p [any_binary] produces a seg fault
> 
> Both used to work until last update of the cygwin64-only setup end of
> June 2014 from FTP server at Uni Erlangen.

Really? cygwin gcc has never been built with multilib support, I don't
know how it is possible that "it used to work".





signature.asc
Description: OpenPGP digital signature

Re: cygwin64 problems after update: gcc 4.8.3-2, cygcheck -p

[JonY]

On 7/6/2014 19:04, Lakhsa wrote:
> After some extended research and trials with a fresh OpenSSL master
> clone openssl32_trial this seems to be a problem of the cygwin ports of GCC.
> I've added some information about this - maybe one of the developers
> listening in on the OpenSSL project could have a closer look.
> 

cygwin gcc has never been built with multilib support, I don't
know how it is possible that "it used to work".




signature.asc
Description: OpenPGP digital signature

Re: Core dump on 32-bit Cygwin if program calls dlopen

[JonY]

On 7/15/2014 21:08, Corinna Vinschen wrote:
>>
>> FWIW, the problem disappears if I revert gcc-core and libgcc1 to 4.8.2-2.
> 
> JonY, do you have a chance to have a look into this issue?
> 

Sorry, I have been busy these few weeks, but I am well aware that there
is a problem with one of the libgcc changes, but has yet to investigate it.

I believe Jon Turney has looked into it somewhat.




signature.asc
Description: OpenPGP digital signature

Re: Core dump on 32-bit Cygwin if program calls dlopen

[JonY]

On 7/16/2014 15:02, Corinna Vinschen wrote:
> Hi JonY,
> 
> On Jul 15 16:39, Corinna Vinschen wrote:
>> On Jul 15 21:55, JonY wrote:
>>> On 7/15/2014 21:08, Corinna Vinschen wrote:
>>>>>
>>>>> FWIW, the problem disappears if I revert gcc-core and libgcc1 to 4.8.2-2.
>>>>
>>>> JonY, do you have a chance to have a look into this issue?
>>>>
>>>
>>> Sorry, I have been busy these few weeks, but I am well aware that there
>>> is a problem with one of the libgcc changes, but has yet to investigate it.
>>>
>>> I believe Jon Turney has looked into it somewhat.
>>
>> Sounds good.  Thanks in advance.
> 
> Yesterday I asked my collegues to take a stab at the issue and one of
> them, DJ Delorie, came up with a libgcc patch already.  It hasn't been
> sent upstream yet.  Can we give it a try, perhaps by creating a new
> libgcc DLL, please?
> 

Thanks, I'll get to it this weekend, should I make the new gcc an
experimental version? Or is just the libgcc binary required?





signature.asc
Description: OpenPGP digital signature

Re: Core dump on 32-bit Cygwin if program calls dlopen

[JonY]

On 7/18/2014 02:24, Corinna Vinschen wrote:
>>> Is this essentially the same problem as described here?
>>>
>>>  
>>
>> No, I think it is an unforeseen consequence of the patch [3] to fix that bug
>> [4], which I believe is present in 4.8.3-1, introducing a new problem when
>> an executable which doesn't depend on libgcc dlopen()s a dll which does.
>>
>> [1] https://cygwin.com/ml/cygwin/2014-07/msg00083.html
>> [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61752
>> [3] https://sourceware.org/ml/cygwin/2013-07/msg00528.html
>> [4] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57982
> 
> I asked DJ to take another look, but I guess ultimately we need the
> attention of one of the GCC Windows maintainers.  Kai Tietz seems to be
> unavailable right now, unfortunately.
> 

Looks like I haven't had much luck at poking the code to work over the
weekends.





signature.asc
Description: OpenPGP digital signature

Re: Core dump on 32-bit Cygwin if program calls dlopen

[JonY]

On 7/24/2014 21:45, Corinna Vinschen wrote:
> 
> JonY, any chance we could get a gcc package with the new crtbegin.o
> soon?

Yes, I just uploaded gcc-4.8.3-2, I'll announce once it hits the mirrors.





signature.asc
Description: OpenPGP digital signature

[ANNOUNCEMENT] Updated: gcc-4.8.3-2 (x86)

[JonY]

gcc-4.8.3-2 is now uploaded for 32-bit Cygwin. This release hopefully
fixes the dw2 unwind problem, thanks to DJ for the crtbegin patch.

  *** 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://sourceware.org/lists.html#unsubscribe-simple

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





signature.asc
Description: OpenPGP digital signature

Re: New Git v2.0.4 build to test

[JonY]

On 8/6/2014 22:18, Corinna Vinschen wrote:
>> `git fetch` occasionally hangs in the test suites in 64-bit)
>> and there are probably some problems I haven't identified yet.
>>
>> I'm currently in the process of working through the Git test suite
>> output to identify missing features, since it's the best way I've found
>> to identify features the Git compile process has quietly skipped since a
>> required library wasn't installed.
> 
> If the git build system uses autotools, you might have an easier time by
> scanning the config.log file created during the configure call.
> 

It does, I have been using git 2.x since the last 2 months. And yes,
PCRE is an optional requirement.





signature.asc
Description: OpenPGP digital signature

[ANNOUNCEMENT] Updated: binutils-2.24.51-5 (x86/x86_64)

[JonY]

binutils-2.24.51-5 is now uploaded for both 32-bit and 64-bit Cygwin.
This includes a patch to exclude __dso_handle from being externally
visible in DLLs for the upcoming Cygwin __cxa_atexit support.

  *** 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://sourceware.org/lists.html#unsubscribe-simple

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




signature.asc
Description: OpenPGP digital signature

[ANNOUNCEMENT] Updated: gcc-4.8.3-3 (x86/x86_64)

[JonY]

gcc-4.8.3-3 has been uploaded for 32bit and 64bit Cygwin. This rebuild
now uses __cxa_atexit for better C++ standards compliance.

Note that any C++ code built with this version WILL NOT RUN on earlier
versions of Cygwin (1.7.32-1).

  *** 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://sourceware.org/lists.html#unsubscribe-simple

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






signature.asc
Description: OpenPGP digital signature

Re: ld segfaults with -flto after upgrading to gcc 4.8.3-3 (64-bit)

[JonY]

On 8/22/2014 08:20, Christoph H. Hochstaetter wrote:
> Hi,
> 
> I just upgraded gcc from 4.8.3-2 to 4.8.3-3. ld segfaults if gcc (and thus
> ld) is used with link time optimization (-flto).

Looks like it is crashing at exit(), not sure how that happens, Corinna,
help? :)





signature.asc
Description: OpenPGP digital signature

[ANNOUNCEMENT] Updated: mingw64-{headers,runtime,winpthreads} w32api-* 3.2.0-1

[JonY]

Now released for both 32bit and 64bit Cygwin:

mingw64-*-headers-3.2.0-1
mingw64-*-runtime-3.2.0-1
mingw64-*-winpthreads-3.2.0-1
w32api-headers-3.2.0-1
w32api-runtime-3.2.0-1

Notable changes:
* Add aliases for non-dllimport _get_invalid_parameter_handler and
_set_invalid_parameter_handler

* Fix D2DERR_INSUFFICIENT_BUFFER definition

* Fix off by one ipsectypes.h: Begin IPSEC_CIPHER_TYPE enumeration at 1

* Add missing @4 decoration for TryAcquireSRWLockExclusive, and
TryAcquireSRWLockExclusive

And many more fixes.

  *** 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@cygwin.com

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

http://sourceware.org/lists.html#unsubscribe-simple

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




signature.asc
Description: OpenPGP digital signature

Re: [ANNOUNCEMENT] Updated: mingw64-{headers,runtime,winpthreads} w32api-* 3.2.0-1

[JonY]

binsjTA3y_sIu.bin
Description: PGP/MIME version identification


encrypted.asc
Description: OpenPGP encrypted message

Re: [ANNOUNCEMENT] Updated: mingw64-{headers,runtime,winpthreads} w32api-* 3.2.0-1

[JonY]

On 9/17/2014 17:02, Dominik Straßer wrote:
> Hi,
> these files did not yet appear on any mirrors.
> Did anything go wrong here ?
> 
> Best regards
> 
> Dominik

Sorry about the earlier mail, I meant to say kernel.org looks alright.





signature.asc
Description: OpenPGP digital signature

Re: [ANNOUNCEMENT] Updated: mingw64-{headers,runtime,winpthreads} w32api-* 3.2.0-1

[JonY]

On 9/17/2014 17:55, Dominik Straßer wrote:
> Really ?
> I just checked mirrors.kernel.org in the cygwin installer and it gives
> me only 3.1.0-1 for e.g. mingw64-x86_64-runtime.
> 

Yes, looks like the x86_64 headers and runtime are missing, I will
upload them shortly.




signature.asc
Description: OpenPGP digital signature

Re: ld crashes with segmentation fault when linking with libmpir.a

[JonY]

On 9/18/2014 03:20, Daniel R. Grayson wrote:
> ld crashes with segmentation fault when linking with libmpir.a
> 
> To reproduce:
> 
> wget http://mpir.org/mpir-2.6.0.tar.bz2
> tar xjf mpir-2.6.0.tar.bz2
> cd mpir-2.6.0
> ./configure --build=x86_64-pc-cygwin
> make
> ld -u __gmpn_gcdext .libs/libmpir.a
> 

What are you trying to accomplish? I suspect this will not work on Windows.





signature.asc
Description: OpenPGP digital signature

Re: ld crashes with segmentation fault when linking with libmpir.a

[JonY]

binxs4f60pc5A.bin
Description: PGP/MIME version identification


encrypted.asc
Description: OpenPGP encrypted message

Re: ld crashes with segmentation fault when linking with libmpir.a

[JonY]

On 9/18/2014 17:37, Marco Atzeri wrote:
> On 18/09/2014 11:23, JonY wrote:
> 
> any specific reason to encrypt mails on a public mailing list ?
> 


Sorry about that, for some reason it is trying to encrypt all mails to
cygwin.com automatically for the last few days, I don't know which
pubkey it uses either.

I have now add an exclude filter for Cygwin.






signature.asc
Description: OpenPGP digital signature

Re: AW: ld crashes with segmentation fault when linking with libmpir.a

[JonY]

On 9/24/2014 05:27, Christoph H. Hochstaetter wrote:
> I am experiencing 100% reproducible SIGSEGVs in ld if I use link time
> optimization (-flto). See https://cygwin.com/ml/cygwin/2014-08/msg00439.html
> 
> What actually helped is to go back to gcc 4.8.3-2 or use experimental 4.9.0.
> Maybe this works for you too although the problem is actually not ld itself
> but the gcc linker plugin cyglto_plugin.dll.
> 
> Corinna suspects that not all of DJ's and Yaakov's changes were actually
> merged into 4.8.3-3
> 

No, its the opposite, 4.8.3-2 and 4.9.0 does not contain DJ's changes.




signature.asc
Description: OpenPGP digital signature

[ANNOUNCEMENT] Updated: binutils-2.24.51-6 (x86/x86_64)

[JonY]

binutils-2.24.51-6 is now uploaded for both 32-bit and 64-bit Cygwin.
This version fixes a security issue with libbfd.

  *** 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://sourceware.org/lists.html#unsubscribe-simple

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





signature.asc
Description: OpenPGP digital signature

Re: gcc packaging bug?

[JonY]

On 11/4/2014 05:46, Ken Brown wrote:
> The setup.hint files for gcc and its subpackages now say
> 
> curr: 4.8.3-2
> prev: 4.8.3-3
> test: 4.9.2-1
> 
> I assume this is a typo; it causes everyone who is not installing the
> test release to get downgraded from 4.8.3-3 to 4.8.3-2.

No, this is deliberate, 4.8.3-3 is bugged, it could not build later
versions of gcc.





signature.asc
Description: OpenPGP digital signature

Re: gcc packaging bug?

[JonY]

On 11/4/2014 06:04, JonY wrote:
> On 11/4/2014 05:46, Ken Brown wrote:
>> The setup.hint files for gcc and its subpackages now say
>>
>> curr: 4.8.3-2
>> prev: 4.8.3-3
>> test: 4.9.2-1
>>
>> I assume this is a typo; it causes everyone who is not installing the
>> test release to get downgraded from 4.8.3-3 to 4.8.3-2.
> 
> No, this is deliberate, 4.8.3-3 is bugged, it could not build later
> versions of gcc.
> 

I forgot to mention 4.8.3-4 will be uploaded soon to fix the problem
atexit use in libgcc. It was causing configure failures in stage1 libgcc
by causing link test to return $? 0 even if it failed.





signature.asc
Description: OpenPGP digital signature

[ANNOUNCEMENT] Updated: gcc-4.9.2-1 (x86/x86_64) (Test)

[JonY]

gcc-4.9.2-1 has been uploaded for 32bit and 64bit Cygwin. This version
is set to test.

Note that any C++ code built with this version WILL NOT RUN on earlier
versions of Cygwin (1.7.32-1).

  *** 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://sourceware.org/lists.html#unsubscribe-simple

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







signature.asc
Description: OpenPGP digital signature

Re: gcc packaging bug?

[JonY]

On 11/4/2014 06:11, Yaakov Selkowitz wrote:
> On 2014-11-03 16:04, JonY wrote:
>> On 11/4/2014 05:46, Ken Brown wrote:
>>> The setup.hint files for gcc and its subpackages now say
>>>
>>> curr: 4.8.3-2
>>> prev: 4.8.3-3
>>> test: 4.9.2-1
>>>
>>> I assume this is a typo; it causes everyone who is not installing the
>>> test release to get downgraded from 4.8.3-3 to 4.8.3-2.
>>
>> No, this is deliberate, 4.8.3-3 is bugged, it could not build later
>> versions of gcc.
> 
> How so?

As explained in the other email, it made failed link test return $? 0
anyway. This broke the stage 1 libgcc configure tests.

Reverting to an older version of gcc and then using it to build 4.9.2-1
succeeded. I also used 4.9.2-1 to build a copy of itself as test, seems
like it works. The only real change was changing atexit use to
__cxa_atexit in libgcc.

Corinna mentioned some problems with gcc misoptimizing atexit over IRC.




signature.asc
Description: OpenPGP digital signature

Re: gcc packaging bug?

[JonY]

On 11/4/2014 08:48, Doug Henderson wrote:
> On 3 November 2014 14:46, Ken Brown wrote:
>> The setup.hint files for gcc and its subpackages now say
>>
>> curr: 4.8.3-2
>> prev: 4.8.3-3
>> test: 4.9.2-1
> 
> Setup-x86_64.exe is reporting that cygwin-devel is a dependency of
> gcc-core now. Is this an intentional change?
> 
> Doug
> 

Yes, cygwin may split into a devel package in the future. It is a dummy
package for now.




signature.asc
Description: OpenPGP digital signature

Re: gcc packaging bug?

[JonY]

On 11/4/2014 17:54, Marco Atzeri wrote:
> 
> 
> please also check why gcc-g++ requires Python3 (at least on 64 bit)
> 

Done, the mirrors should be refresh shortly (for x86 32bit as well).





signature.asc
Description: OpenPGP digital signature

Re: [ANNOUNCEMENT] Updated: gcc-4.9.2-1 (x86/x86_64) (Test)

[JonY]

On 11/6/2014 07:21, David Stacey wrote:
> On 03/11/2014 22:08, JonY wrote:
>> gcc-4.9.2-1 has been uploaded for 32bit and 64bit Cygwin. This version
>> is set to test.
> 
> I've just noticed that gcc-java requires libgcj15. Given that libgcj15
> is part of the test release, should the dependency be libgcj14?
> 
> Dave.

Right, I should just make it depend on both, they shouldn't clash.





signature.asc
Description: OpenPGP digital signature

Re: [ANNOUNCEMENT] Updated: gcc-4.9.2-1 (x86/x86_64) (Test)

[JonY]

On 11/6/2014 07:21, David Stacey wrote:
> On 03/11/2014 22:08, JonY wrote:
>> gcc-4.9.2-1 has been uploaded for 32bit and 64bit Cygwin. This version
>> is set to test.
> 
> I've just noticed that gcc-java requires libgcj15. Given that libgcj15
> is part of the test release, should the dependency be libgcj14?
> 
> Dave.

Right, I should just make it depend on both, they shouldn't clash.





signature.asc
Description: OpenPGP digital signature

Re: [ANNOUNCEMENT] Updated: gcc-4.9.2-1 (x86/x86_64) (Test)

[JonY]

On 11/6/2014 20:11, Marco Atzeri wrote:
> 
> 
> On 11/6/2014 10:12 AM, JonY wrote:
>> On 11/6/2014 07:21, David Stacey wrote:
>>> On 03/11/2014 22:08, JonY wrote:
>>>> gcc-4.9.2-1 has been uploaded for 32bit and 64bit Cygwin. This version
>>>> is set to test.
>>>
>>> I've just noticed that gcc-java requires libgcj15. Given that libgcj15
>>> is part of the test release, should the dependency be libgcj14?
>>>
>>> Dave.
>>
>> Right, I should just make it depend on both, they shouldn't clash.
>>
>>
> 
> check again spurious Python3 dependency, I saw one from gcc-java
> 

Done, removed.





signature.asc
Description: OpenPGP digital signature

Re: Fwd: gcc-4.9.2-1 (x86_64) generates segfault during linking

[JonY]

On 11/7/2014 05:06, Falk Tannhäuser wrote:
> Since I updated gcc from version 4.9.0-1 to 4.9.2-1, I obtain the error
>   collect2: Fehler: ld mit Signal 11 [Segmentation fault] beendet
> when compiling and linking a C or C++ program. However, an executable is
> generated and appears to work as expected.
> I installed the latest test release of cygwin so far (1.7.33-0.7).
> 
> Falk

Does it somehow work if you link with gcc -fno-lto?






signature.asc
Description: OpenPGP digital signature

Re: Fwd: gcc-4.9.2-1 (x86_64) generates segfault during linking

[JonY]

On 11/7/2014 06:59, Falk Tannhäuser wrote:
> Am 06.11.2014 um 23:37 schrieb JonY:
>> On 11/7/2014 05:06, Falk Tannhäuser wrote:
>>> Since I updated gcc from version 4.9.0-1 to 4.9.2-1, I obtain the error
>>>collect2: Fehler: ld mit Signal 11 [Segmentation fault] beendet
>>> when compiling and linking a C or C++ program. However, an executable is
>>> generated and appears to work as expected.
>>> I installed the latest test release of cygwin so far (1.7.33-0.7).
>>
>> Does it somehow work if you link with gcc -fno-lto?
> 
> Yes, this fixes the problem.
> 

There seems to be some confusion in the __cxa_atexit in Cygwin 1.7.32,
basically 4.9.1 will only work with .32.

1.7.33 fixed the incorrect behavior that unfortunately broke gcc
__cxa_atexit usage. The next 1.7.33-0.8 should be more tolerant of the
old .32 behavior.

After 1.7.33 is officially released, gcc-4.8.3-4 and 4.9 will switch to
the standard conformant behavior.





signature.asc
Description: OpenPGP digital signature

[ANNOUNCEMENT] Updated: gcc-4.8.3-4 (x86)

[JonY]

gcc-4.8.3-4 has been uploaded for 32bit Cygwin. It contains some fixes
for the libgcc unload handler.

  *** 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://sourceware.org/lists.html#unsubscribe-simple

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




signature.asc
Description: OpenPGP digital signature

[ANNOUNCEMENT] Updated: gcc-4.8.3-5 (x86_64)

[JonY]

gcc-4.8.3-5 has been uploaded for 64bit Cygwin. It contains some fixes
for the libgcc unload handler. The -4 release was an accident that did
not contain the fix.

  *** 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://sourceware.org/lists.html#unsubscribe-simple

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





signature.asc
Description: OpenPGP digital signature

[ANNOUNCEMENT] mingw64-*-windows-default-manifest (x86/x86_64)

[JonY]

The default manifest file is used to workaround a bug in the Windows
version reporting API. The manifest file needs to be updated for every
Windows release, and all programs relinked to take effect.

  *** 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://sourceware.org/lists.html#unsubscribe-simple

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





signature.asc
Description: OpenPGP digital signature

Re: [ANNOUNCEMENT] Updated: gcc-4.8.3-4 (x86)

[JonY]

On 11/15/2014 23:53, Marco Atzeri wrote:
> On 11/15/2014 5:35 AM, JonY wrote:
>> gcc-4.8.3-4 has been uploaded for 32bit Cygwin. It contains some fixes
>> for the libgcc unload handler.
> 
>  gcc-java requires (again) python3.
> 
> Please amend
> Marco

Done.

Yaakov, do you mind implementing an exclude feature in cygport to filter
out known optional dependencies?




signature.asc
Description: OpenPGP digital signature

Re: [ANNOUNCEMENT] Updated: gcc-4.8.3-5 (x86_64)

[JonY]

On 11/18/2014 15:44, Yaakov Selkowitz wrote:
> On 2014-11-18 01:36, Achim Gratz wrote:
>> JonY <10walls  gmail.com> writes:
>>> gcc-4.8.3-5 has been uploaded for 64bit Cygwin. It contains some fixes
>>> for the libgcc unload handler. The -4 release was an accident that did
>>> not contain the fix.
>>
>> Can you please check the setup.hint files?  I think that gcc-core should
>> require windows-default-manifest, both on x86 and x86_64.
> 
> Fixed on sourceware.  Jon, please add this to
> gcc.cygport:gcc_core_REQUIRES.

Done, added.





signature.asc
Description: OpenPGP digital signature

[ANNOUNCEMENT] Updated: mingw64-{headers,runtime,winpthreads} w32api-* 3.3.0-1

[JonY]

Now released for both 32bit and 64bit Cygwin:

mingw64-*-headers-3.3.0-1
mingw64-*-runtime-3.3.0-1
mingw64-*-winpthreads-3.3.0-1
w32api-headers-3.3.0-1
w32api-runtime-3.3.0-1

Notable changes:
* _USE_MATH_DEFINES now exposes constants like M_PI from math.h.
* Fix squareroot(-0.0) in accordance to C99 rules.
* Fix several syntax errors in autogenerated comments.
* Fix dwmapi.h struct padding errors.
* Fix MsgWaitForMultipleObjects hidden in winuser.h due to incorrect
endif placement.
* Remove broken strtok_r macro from winpthreads headers and use a real
definition from BSD.
* netioapi.h now includes ws2ipdef.h.
* Fix incorrect long long suffix in winbase.h and winnt.h macros.


  *** 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@cygwin.com

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

http://sourceware.org/lists.html#unsubscribe-simple

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




signature.asc
Description: OpenPGP digital signature

[ANNOUNCEMENT] Updated: w32api-headers 3.3.0-2

[JonY]

Now released for both 32bit and 64bit Cygwin:

w32api-headers-3.3.0-2

Notable changes:
* userenv.h (CreateProfile): backport prototype from master.
* lmaccess.h (USER_INFO_24): backport struct declaration from master.

  *** 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@cygwin.com

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

http://sourceware.org/lists.html#unsubscribe-simple

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




signature.asc
Description: OpenPGP digital signature

Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.34-002

[JonY]

On 12/10/2014 07:28, Angelo Graziosi wrote:
> Corinna Vinschen wrote:
>> How nice.  We have all the work and they simple grab it and don't give
>> anything back to their upstream project.
> 
> ...the *Dark* side of free (GPL?) software... I guess..
> 

No, this is exactly how GPL is supposed to work, now that it has been
corrected, anyone can grab the MSYS2 sources.




signature.asc
Description: OpenPGP digital signature

[ANNOUNCEMENT] Updated: binutils-2.25-1 (x86/x86_64)

[JonY]

Binutils updated to 2.25 following upstream release.

  *** 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://sourceware.org/lists.html#unsubscribe-simple

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





signature.asc
Description: OpenPGP digital signature