On Mon, 25 Mar 2013 17:38:09 +0100, adam kisiel wrote:
ftp://cygwin.com/pub/cygwin/64bit/release/X.Org/printproto/
no packages
I'm not sure how that happened, but in any case, printproto was only in
the 32bit distro due to lesstif's headers' use thereof (even though it
was compiled without
On Mar 28 04:00, Yaakov wrote:
On Mon, 25 Mar 2013 17:38:09 +0100, adam kisiel wrote:
ftp://cygwin.com/pub/cygwin/64bit/release/X.Org/printproto/
no packages
I'm not sure how that happened, but in any case, printproto was only in
the 32bit distro due to lesstif's headers' use thereof
On 26/03/2013 11:20, Corinna Vinschen wrote:
Hi Dave,
On Mar 12 23:50, Dave Korn wrote:
On 12/03/2013 22:15, Achim Gratz wrote:
Achim Gratz writes:
Yaakov (Cygwin/X) writes:
OK. I won't be able to run the tests for some packages this way, but it
sounds like this should provide a workable
Hi guys,
right now it's only possible to build a 64 bit package using the native
toolchain. Yaakov is working on a 32 bit cross toolchain, but this
may take another couple of days.
Anyway, the latest 64 bit Cygwin DLL seems to be stable enough to call
it post-alpha or pre-beta or something
On Mar 28 13:25, Dave Korn wrote:
On 26/03/2013 11:20, Corinna Vinschen wrote:
Hi Dave,
On Mar 12 23:50, Dave Korn wrote:
On 12/03/2013 22:15, Achim Gratz wrote:
Achim Gratz writes:
Yaakov (Cygwin/X) writes:
OK. I won't be able to run the tests for some packages this way, but it
On 28/03/2013 13:39, Corinna Vinschen wrote:
On Mar 28 13:25, Dave Korn wrote:
I've realised that I should re-roll the release after updating to the
latest
cygport, as I don't yet have the version with the debuginfo changes, which I
assume are desirable?
Just run setup ;)
If
On 28 March 2013 13:36, Corinna Vinschen wrote:
Hi guys,
right now it's only possible to build a 64 bit package using the native
toolchain. Yaakov is working on a 32 bit cross toolchain, but this
may take another couple of days.
Anyway, the latest 64 bit Cygwin DLL seems to be stable
On Mar 28 14:05, Andy Koppe wrote:
On 28 March 2013 13:36, Corinna Vinschen wrote:
Hi guys,
right now it's only possible to build a 64 bit package using the native
toolchain. Yaakov is working on a 32 bit cross toolchain, but this
may take another couple of days.
Anyway, the
On Mar 28 15:09, Corinna Vinschen wrote:
On Mar 28 14:05, Andy Koppe wrote:
On 28 March 2013 13:36, Corinna Vinschen wrote:
Hi guys,
right now it's only possible to build a 64 bit package using the native
toolchain. Yaakov is working on a 32 bit cross toolchain, but this
may
On 28/03/2013 14:05, Dave Korn wrote:
Righto. Will upload as soon as I've finished running setup ;)
Argh. Gotta re-roll the packaging step as I forgot to commit some of the
setup.hint reversions to my local svn. D'oh, but at least I spotted it before
uploading.
cheers,
DaveK
On Thu, Mar 28, 2013 at 9:36 AM, Corinna Vinschen
corinna-cyg...@cygwin.com wrote:
Hi guys,
Hi!
Obviously I can't force you to switch to cygport.
Why not? Honestly, can't you just make it a cygwin policy?
We're still mulling over setting up a build machine. If we have that,
and if you
I've tried to build my package (mined) with freshly installed 64-bit
cygwin (default + gcc + make).
When I try it with make, nothing happens, make simply hangs.
When I try it without make, it fails with:
linking mined
/usr/lib/gcc/x86_64-pc-cygwin/4.8.0/../../../../x86_64-pc-cygwin/bin/ld:
W dniu 28.03.2013 o 19:45 Thomas Wolff t...@towo.net pisze:
I've tried to build my package (mined) with freshly installed 64-bit
cygwin (default + gcc + make).
When I try it with make, nothing happens, make simply hangs.
When I try it without make, it fails with:
linking mined
On Mar 28 19:45, Thomas Wolff wrote:
I've tried to build my package (mined) with freshly installed 64-bit
cygwin (default + gcc + make).
When I try it with make, nothing happens, make simply hangs.
When I try it without make, it fails with:
linking mined
W dniu 28.03.2013 o 20:51 Corinna Vinschen corinna-cyg...@cygwin.com
pisze:
On Mar 28 19:45, Thomas Wolff wrote:
I've tried to build my package (mined) with freshly installed 64-bit
cygwin (default + gcc + make).
When I try it with make, nothing happens, make simply hangs.
When I try it
On Mar 28 13:44, NightStrike wrote:
On Thu, Mar 28, 2013 at 9:36 AM, Corinna Vinschen
corinna-cyg...@cygwin.com wrote:
Hi guys,
Hi!
Obviously I can't force you to switch to cygport.
Why not? Honestly, can't you just make it a cygwin policy?
I would like to, but I would also like to
On Mar 28 21:32, adam kisiel wrote:
W dniu 28.03.2013 o 20:51 Corinna Vinschen
corinna-cyg...@cygwin.com pisze:
On Mar 28 19:45, Thomas Wolff wrote:
I've tried to build my package (mined) with freshly installed 64-bit
cygwin (default + gcc + make).
When I try it with make, nothing happens,
On 28 March 2013 14:12, Corinna Vinschen wrote:
On Mar 28 15:09, Corinna Vinschen wrote:
On Mar 28 14:05, Andy Koppe wrote:
On 28 March 2013 13:36, Corinna Vinschen wrote:
Hi guys,
right now it's only possible to build a 64 bit package using the native
toolchain. Yaakov is
On Mar 28 20:51, Andy Koppe wrote:
On 28 March 2013 14:12, Corinna Vinschen wrote:
On Mar 28 15:09, Corinna Vinschen wrote:
On Mar 28 14:05, Andy Koppe wrote:
On 28 March 2013 13:36, Corinna Vinschen wrote:
Hi guys,
right now it's only possible to build a 64 bit package
Hi guys,
I just uploaded a new 64 bit Cygwin DLL, 1.7.18-14. It fixes two
problems:
- getline and getdelim functions were not exported accidentally.
- The gets function crashed immediately after being called. The reason
was a piece of badly arranged inline assembler, which was ripped
20 matches
Mail list logo
