cygwin announce mail went missing?

Hi, I sent an announcement about mingw64-*-headers and runtime update a few days ago, but I don't see it. Did it go missing? signature.asc Description: OpenPGP digital signature

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

I have just updated the CRT and runtime libraries for the mingw-w64 cross compilers, along with the w32api for Cygwin 32bit and 64bit. mingw64-*-headers-3.0.0-1 mingw64-*-runtime-3.0.0-1 w32api-{headers,runtime}-3.0.0-1 The cross compiler can produce Win32 and Win64 native binaries. As a cross c

Re: cygwin announce mail went missing?

On 9/26/2013 01:20, Andrey Repin wrote: > Greetings, JonY! > >> I sent an announcement about mingw64-*-headers and runtime update a few >> days ago, but I don't see it. Did it go missing? > > Pathed on this side all fine. > Odd, I specifically disabled the gm

Re: i686-w64-mingw32-gcc of cygwin64 is broken

On 9/26/2013 19:03, Frédéric Bron wrote: >> Compiled binary seems to crash here. >> I updated mingw64 runtime/headers yesterday. >> >> $ echo "main(){}" >t.c && i686-w64-mingw32-gcc t.c -o t >> $ ./t >> Segmentation fault > > These have been updated: > mingw64-*-headers-3.0.0-1 > mingw64-*-runtime

Re: winbase.h issue

On 9/26/2013 18:47, Noboru Uchida wrote: > When I try the following: > > $ echo "#include " >foo.cc && c++ -c foo.cc > > I get tons of redefinition errors on Interlocked functions in winbase.h. > Looks like it happens only in C++ mode. signature.asc Description: OpenPGP digital signature

Re: winbase.h issue

On 9/26/2013 21:07, JonY wrote: > On 9/26/2013 18:47, Noboru Uchida wrote: >> When I try the following: >> >> $ echo "#include " >foo.cc && c++ -c foo.cc >> >> I get tons of redefinition errors on Interlocked functions in winbase.h. >> &

Re: winbase.h issue

On 9/26/2013 21:16, JonY wrote: > On 9/26/2013 21:07, JonY wrote: >> On 9/26/2013 18:47, Noboru Uchida wrote: >>> When I try the following: >>> >>> $ echo "#include " >foo.cc && c++ -c foo.cc >>> >>> I get tons of redefin

[ANNOUNCEMENT] Updated: w32api-headers-3.0.0-2 and mingw64-i686-runtime-3.0.0-2 (x86_64)

I have just updated the w32api-headers and mingw64-i686-runtime package for 64bit Cygwin. The new w32api-headers should fix the winbase.h conflicts, while the new runtime is a rebuild of -1 to fix the segfault issues due to a mistake in the first release. *** CYGWIN-ANNOUNCE UNSUBSC

Re: w32api-headers-3.0.0.-1 in question

On 10/4/2013 18:02, Denis Excoffier wrote: > Hello, > > I use cygwin 32 bits, last snapshot. > > Since the last update of > - mingw64-i686-headers-3.0.0-1 > - mingw64-i686-runtime-3.0.0-1 > - w32api-headers-3.0.0-1 > - w32api-runtime-3.0.0-1 > (see http://cygwin.com/ml/cygwin-announce/2013-09/msg

Re: Hooks do not work?

On 10/26/2013 14:32, niXman wrote: > compiled as: > gcc hook.c -shared -oopenhook.dll > gcc main.c -omain > > run as: > LD_PRELOAD=/home/niXman/openhook.dll ./main > > But a can't see the output. > What I am doing wrongly? > LD_PRELOAD is an ELF interpreter feature and bares no effect on Window

[ANNOUNCEMENT] Updated: gcc-4.8.2-1 (x86_64)

I have updated gcc for 64bit Cygwin to the latest released version. There aren't any Cygwin specific changes introduced since 4.8.1, so it should work similarly. The last 32bit 4.8.x build didn't go so well, will try again this weekend. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If

Re: ATTENTION GCC PACKAGE MAINTAINER - Re: GCC: core, g++ version mismatch

cc-core and gcc-g++. >>> >>> gcc-core is listed as having 4.8.2-1 available, gcc-g++ is still at >>> 4.8.1-3. >>> >>> Updating gcc-core (and libgcc1 with it) breaks all build attempts for >>> me. >>> >>> Cygwin64: 2.830, Win64 &

Re: ATTENTION GCC PACKAGE MAINTAINER - Re: GCC: core, g++ version mismatch

On 10/31/2013 00:09, Christopher Faylor wrote:. > > I restrict the filenames that can be uploaded and neglected to add '+'. > I just added it now so you will have to upload those files again. Sorry > for the inconvenience. > Done, reuploaded. >> Strange that I did not get any errors on my end,

Re: upset messages

On 11/9/2013 18:45, Corinna Vinschen wrote: > On Nov 9 10:36, wrote: >> upset: *** /var/ftp/pub/cygwin/x86/setup.ini: error - package gcc-java >> requires nonexistent package java-ecj >> upset: *** /var/ftp/pub/cygwin/x86/setup.ini: error - package gcc-java >> requires package java-ecj which ha

Re: upset messages

On 11/10/2013 00:51, Corinna Vinschen wrote: > On Nov 9 21:20, JonY wrote: >> On 11/9/2013 18:45, Corinna Vinschen wrote: >>> On Nov 9 10:36, wrote: >>>> upset: *** /var/ftp/pub/cygwin/x86/setup.ini: error - package gcc-java >>>> requires nonexistent

[ANNOUNCEMENT] Updated: gcc-4.8.2-1 (x86)

gcc-4.8.x is finally out for 32bit Cygwin. This should fix the python crash issue. *** 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

Re: [ANNOUNCEMENT] Updated: gcc-4.8.2-1 (x86)

On 11/10/2013 12:34, marco atzeri wrote: > Il 11/10/2013 4:31 AM, JonY ha scritto: >> >> gcc-4.8.x is finally out for 32bit Cygwin. This should fix the python >> crash issue. >> > > ok, > but why is pulling python3 as dependency ? > > python3

Re: [ANNOUNCEMENT] Updated: gcc-4.8.2-1 (x86)

On 11/10/2013 12:34, marco atzeri wrote: > Il 11/10/2013 4:31 AM, JonY ha scritto: >> >> gcc-4.8.x is finally out for 32bit Cygwin. This should fix the python >> crash issue. >> > > ok, > but why is pulling python3 as dependency ? > > python3

Re: [ANNOUNCEMENT] Updated: gcc-4.8.2-1 (x86_64)

On 11/8/2013 02:21, Eric Lilja wrote: > On 2013-10-29 23:40, JonY wrote: >> >> The last 32bit 4.8.x build didn't go so well, will try again this >> weekend. >> > > Any news regarding 32-bit 4.8.x? Thanks for working on this! 32bit version is now out.

Re: python aborts

On 11/11/2013 20:59, Corinna Vinschen wrote: >> I pinged the upstream maintainer who probably wasn't aware of this yet. > > The patche is checked in upstream. JonY, any chance for an updated > gcc toolchain soon? > The 4.8.2-1 release should already contain this pa

Re: C++11 program link failure under GCC 4.8.2-1

On 11/12/2013 06:17, JonY wrote: > On 11/12/2013 05:17, Yucong Sun wrote: >> Hi, >> >> I'm trying to compile a program under cygwin with latest gcc 4.8.2, >> the program compiles fine, but link failed. I'm suspecting this has >> something todo with libstd

Re: C++11 program link failure under GCC 4.8.2-1

On 11/12/2013 07:37, Yucong Sun wrote: > Yes, the sha1 matches. > > sunyc@sunyc-wks /lib/gcc/i686-pc-cygwin/4.8.2 > $ sha1sum.exe libstdc++.* > f4dfadfddade3aceaf4852cd5db31372ab7ef0d1 *libstdc++.a > 963e2a697c3a1a7d036d975b07f4c408bbd1cb2d *libstdc++.dll.a > > Also I couldn't find GLIB_xxx versi

Re: C++11 program link failure under GCC 4.8.2-1

On 11/12/2013 10:33, Yucong Sun wrote: > I've tried on both 32bit and 64bit clean cygwin install, the result is > same. Something is wrong with cygwin's gcc. > > my configure script by default uses g++ --std=c++11, this still have > problem of " no snprintf " , after I replace all snprintf() with

Re: C++11 program link failure under GCC 4.8.2-1

On 11/13/2013 02:35, Yucong Sun wrote: > Good new! I've found the link failure issue, it is caused by "-rdynamic" > > sunyc@sunyc-wks ~ > $ cat 2.cc > #include > > struct tick_event { > int i; > }; > > int main() { > std::deque list; > > tick_event *a = new tick_event; > list.

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

This update includes: Update: mingw64-*-gcc-4.8.2-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

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

4.8.2-2 is a rebuilt of -1 with an additional --libexecdir=/usr/lib, this should fix reports of spawn failures when called with /bon/gcc. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag

Re: [ANNOUNCEMENT] Updated: gcc-4.8.2-2 (x86)

On 12/10/2013 18:52, Achim Gratz wrote: > JonY <10walls gmail.com> writes: >> 4.8.2-2 is a rebuilt of -1 with an additional --libexecdir=/usr/lib, >> this should fix reports of spawn failures when called with /bon/gcc. > > This update breaks libquadmath0 because the l

Re: [ANNOUNCEMENT] Updated: gcc-4.8.2-2 (x86)

On 12/11/2013 02:07, Corinna Vinschen wrote: > On Dec 10 18:32, Achim Gratz wrote: >> Corinna Vinschen writes: >>> Does it make sense to remove the libquadmath0gcc-ada package entirely >>> for now? >> >> Yes, the whole libquadmath0gcc-ada directory including the files in it. >> Then setup.ini shoul

Re: /bin before /usr/bin makes i686-w64-mingw-gcc fail

On 1/11/2014 04:43, Thomas Nilsson wrote: > During some unfortunate events I happened to get /bin as the first > directory in my PATH. This caused the gcc cross compilers to fail with: > > i686-w64-mingw32-gcc: error: spawn: No such file or directory This is a known problem, don't do that. Wi

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

New release for both 32bit and 64bit Cygwin: mingw64-*-headers-3.1.0-1 mingw64-*-runtime-3.1.0-1 mingw64-*-winpthreads-3.1.0-1 mingw64-*-gcc-4.8.2-2 w32api-{headers,runtime}-3.1.0-1 This release includes some deadlock fix for winpthreads and workarounds for intrin.h C++ linkages. The cross compi

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

I have rebuilt gcc for 64bit Cygwin, this release includes ADA support. KNOWN REGRESSIONS: The compiler internals are in /usr/libexec rather than in /usr/lib. This is a mistake on my part. Expect a fixed rebuild in 2-4 weeks time. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you w

Re: Re> [ANNOUNCEMENT] Updated: gcc-4.8.2-2 (x86_64)

On 2/15/2014 01:40, Angelo Graziosi wrote: > JonY wrote: >> KNOWN REGRESSIONS: >> The compiler internals are in /usr/libexec rather than in /usr/lib. This >> is a mistake on my part. Expect a fixed rebuild in 2-4 weeks time. > > On the mirrors I find tar-balls (still

[ANNOUNCEMENT] Updated: gcc-4.8.2-3 (x86_64)

I have rebuilt gcc for 64bit Cygwin, this time, internals are in /usr/lib to get around failures when gcc is called from /bin. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the emai

Re: Compiled executables requiring admin rights - different results between MinGW host type

On 3/13/2014 02:41, Corinna Vinschen wrote: > So, if you have a bit of time, it would be nice to get new > mingw64-i686-binutils and mingw64-x86_64-binutils packages (as well > as a new Cygwin binutils, but cgf already knows about this). > Sure, I'll get to it this weekend. signature.asc Des

[ANNOUNCEMENT] Updated: mingw64-*-binutils-2.24.0.0.5a026fc-1 (x86/x86_64)

Version 2.24.0.0.5a026fc-1 of mingw64-*-binutils have been uploaded. This version includes automatic manifest generation to prevent UAC from automatically called based on executable file name. For the 64bit target, the assembler includes a new -Wa,-mbig-obj option to allow objects with up to 2**3

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

On 3/27/2014 16:55, Angelo Graziosi wrote: > CGF wrote >> I don't support those packages so there >> is no need to pollute the thread with pointless observations > > It was just to remember thet Cygwin distro needs alsot those upgrades... > > I suppose that JonY r

Re: does using mingw-gcc require to compile all libraries with it?

On 3/28/2014 17:00, ton...@free.fr wrote: > Hello, > I just installed mingw-gcc-4.7.3 on top of my cygwin installation. > > Trying to build a library that needs openssl lib, I get undefined references > to __errno and __getreent from this library. > - I understood those variables are from cygw

[ANNOUNCEMENT] Updated: mingw64-*-binutils-2.24.0.1.acd6540-1 (x86/x86_64)

Version 2.24.0.1.acd6540-1 of mingw64-*-binutils have been uploaded. This is a bug fix release from git. *** 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 mess

Re: [ANNOUNCEMENT] Updated: mingw64-*-binutils-2.24.0.1.acd6540-1 (x86/x86_64)

On 4/2/2014 01:13, Denis Excoffier wrote: > On 2014-03-30 16:58, JonY wrote: > >> >> Version 2.24.0.1.acd6540-1 of mingw64-*-binutils have been uploaded. >> >> This is a bug fix release from git. >> > This must be more than a simple bug fix release. >

Re: [ANNOUNCEMENT] Updated: mingw64-*-binutils-2.24.0.1.acd6540-1 (x86/x86_64)

On 4/2/2014 06:10, JonY wrote: > On 4/2/2014 01:13, Denis Excoffier wrote: >> On 2014-03-30 16:58, JonY wrote: >> >>> >>> Version 2.24.0.1.acd6540-1 of mingw64-*-binutils have been uploaded. >>> >>> This is a bug fix release from git. >

Re: [ANNOUNCEMENT] Updated: mingw64-*-binutils-2.24.0.1.acd6540-1 (x86/x86_64)

On 4/2/2014 18:04, Corinna Vinschen wrote: >> >> I am told that this is happening due to a bug in an earlier binutils >> release, though it still seems to be happening with -2. >> >> The error, for reference when linking ld.exe: >> default-manifest.o: file not recognized: File format not recognized

Re: [ANNOUNCEMENT] Updated: mingw64-*-binutils-2.24.0.1.acd6540-1 (x86/x86_64)

On 4/7/2014 06:11, m0viefreak wrote: > > Looks like it's not searching for the default-manifest.o in the correct > include paths. > > The mingw file resides in > /usr/{x86_64,i686}-w64-mingw32/lib/ > > Maybe it should be in > /usr/{x86_64,i686}-w64-mingw32/sys-root/mingw/lib/ > Yes, this is ap

[ANNOUNCEMENT] Updated: mingw64-*-binutils-2.24.0.3.85cf705-1 (x86/x86_64)

Version 2.24.0.3.85cf705-1 of mingw64-*-binutils have been uploaded. This removes the previously included default-manifest.o file support. It is now in its own package. Support for automatically linking it is being moved into GCC instead. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** I

Re: GIT (was: Coverity Scan)

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

ioctl crash in mpg123

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;

Re: ioctl crash in mpg123

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, >>

Re: gcc-4.9.0 patch status

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,

Re: gcc-4.9.0 patch status

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 k

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

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

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

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: "

Re: Default manifest

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)

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.

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

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

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

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/bi

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

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)

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 u

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

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:

Re: Question on gcc install

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 (opt

Re: Question on gcc install

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

Re: Question on gcc install

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

Re: Question on gcc install

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 specifi

Re: Question on gcc install

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) >> > > Yo

Re: Question on gcc install

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. >

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

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

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

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 > * cygche

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

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 ha

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

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 pr

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

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

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

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, in

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

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)

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

Re: New Git v2.0.4 build to test

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 th

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

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 cygwi

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

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

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

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 Descrip

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

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

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

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 den

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

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 toolchai

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

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

Re: old install instructions? -mnomingw being removed?

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 gre

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

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

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

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

[ANNOUNCEMENT] Updated: lzip-1.9-1

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:

Re: ./configure on cygwin in window platform

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-trun

[ANNOUNCEMENT] Updated: lzip-1.10-1

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

[ANNOUNCEMENT] New package: lzip-1.8-1

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 -

Re: New package: lzip-1.8-1

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. I

Re: New package: lzip-1.8-1

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 o

[1.7] .exe append weirdness

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 altogethe

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

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 305

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

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

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

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 con

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

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 ver

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

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

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

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

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

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

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

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

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

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 __

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

binxs4f60pc5A.bin Description: PGP/MIME version identification encrypted.asc Description: OpenPGP encrypted message

  1   2   3   4   5   6   >