On Jul 6 10:24, David Rothenberger wrote:
Please delete 1.1.3-1 and leave 1.1.4-1 as the previous version.
wget -x -nH --cut-dirs=2 \
http://home.comcast.net/~david.rothenberger/cygwin/libogg/setup.hint \
http://home.comcast.net/~david.rothenberger/cygwin/libogg/libogg0/setup.hint \
On Jul 6 10:41, David Rothenberger wrote:
Please remove 1.2.0-2 and leave 1.2.3-1 as the previous version.
wget -x -nH --cut-dirs=2 \
http://home.comcast.net/~david.rothenberger/cygwin/libvorbis/setup.hint \
On Jul 6 10:59, David Rothenberger wrote:
Please leave 0.8.8-1 as previous.
The new version introduces libao4, so please move the libao2 package
to the _obsolete category.
Done.
wget -x -nH --cut-dirs=2 \
http://home.comcast.net/~david.rothenberger/cygwin/libao/setup.hint \
On Jul 6 21:35, Yaakov S wrote:
On Tue, 2010-07-06 at 22:07 -0400, Christopher Faylor wrote:
I'd want to check with Corinna on this but I am mildly opposed to putting
this in /opt. I don't think it makes sense there. But I haven't been
following closely, though. Where does Debian put
On Jul 6 15:41, David Rothenberger wrote:
On 7/6/2010 2:55 PM, Yaakov (Cygwin/X) wrote:
On Tue, 2010-07-06 at 11:19 -0700, David Rothenberger wrote:
I'd like to package libkate[1] in preparation for packaging the
newest version of vorbis-tools.
libkate is included in Fedora[2].
[accidentally posted to the main list; re-sent here]
On 7/6/2010 10:35 PM, Yaakov (Cygwin/X) wrote:
On Tue, 2010-07-06 at 22:07 -0400, Christopher Faylor wrote:
I'd want to check with Corinna on this but I am mildly opposed to putting
this in /opt. I don't think it makes sense there. But I
On Jul 7 08:08, Charles Wilson wrote:
[accidentally posted to the main list; re-sent here]
On 7/6/2010 10:35 PM, Yaakov (Cygwin/X) wrote:
On Tue, 2010-07-06 at 22:07 -0400, Christopher Faylor wrote:
I'd want to check with Corinna on this but I am mildly opposed to putting
this in /opt.
On Wed, Jul 07, 2010 at 02:39:19PM +0200, Corinna Vinschen wrote:
Oh, and, talking about /opt or /usr, I'd prefer the above /usr/mingw*
sysroot idea. However, I don't like the idea in the least to keep
two different versions of w32api around. It's one target, so we should
have one set of headers
On 7/7/2010 20:58, Christopher Faylor wrote:
On Wed, Jul 07, 2010 at 02:39:19PM +0200, Corinna Vinschen wrote:
Oh, and, talking about /opt or /usr, I'd prefer the above /usr/mingw*
sysroot idea. However, I don't like the idea in the least to keep
two different versions of w32api around. It's
On Jul 7 08:58, Christopher Faylor wrote:
On Wed, Jul 07, 2010 at 02:39:19PM +0200, Corinna Vinschen wrote:
Oh, and, talking about /opt or /usr, I'd prefer the above /usr/mingw*
sysroot idea. However, I don't like the idea in the least to keep
two different versions of w32api around. It's
On Jul 7 21:19, JonY wrote:
On 7/7/2010 20:58, Christopher Faylor wrote:
On Wed, Jul 07, 2010 at 02:39:19PM +0200, Corinna Vinschen wrote:
Oh, and, talking about /opt or /usr, I'd prefer the above /usr/mingw*
sysroot idea. However, I don't like the idea in the least to keep
two different
2010/7/7 Corinna Vinschen corinna-cyg...@cygwin.com:
On Jul 7 21:19, JonY wrote:
On 7/7/2010 20:58, Christopher Faylor wrote:
On Wed, Jul 07, 2010 at 02:39:19PM +0200, Corinna Vinschen wrote:
Oh, and, talking about /opt or /usr, I'd prefer the above /usr/mingw*
sysroot idea. However, I
On 7/7/2010 21:59, Corinna Vinschen wrote:
On Jul 7 21:19, JonY wrote:
On 7/7/2010 20:58, Christopher Faylor wrote:
On Wed, Jul 07, 2010 at 02:39:19PM +0200, Corinna Vinschen wrote:
Oh, and, talking about /opt or /usr, I'd prefer the above /usr/mingw*
sysroot idea. However, I don't like the
On Jul 7 22:04, JonY wrote:
On 7/7/2010 21:59, Corinna Vinschen wrote:
On Jul 7 21:19, JonY wrote:
On 7/7/2010 20:58, Christopher Faylor wrote:
On Wed, Jul 07, 2010 at 02:39:19PM +0200, Corinna Vinschen wrote:
Oh, and, talking about /opt or /usr, I'd prefer the above /usr/mingw*
sysroot
On Wed, 2010-07-07 at 10:19 +0200, Corinna Vinschen wrote:
So, is that ok to upload or are you going to change that first?
It's not wrong, just cleaner for the maintainer, that's all.
Yaakov
On Wed, Jul 07, 2010 at 04:43:49PM +0200, Corinna Vinschen wrote:
Ok, that's something I can live with. I don't understand the notion to
keep _WIN32_WINNT at 0x0400 anyway. The idea of this value is to be set
manually if I *don't* want modern functions, but the default should be
to allow *all*
On Jul 7 10:49, Christopher Faylor wrote:
On Wed, Jul 07, 2010 at 04:43:49PM +0200, Corinna Vinschen wrote:
Ok, that's something I can live with. I don't understand the notion to
keep _WIN32_WINNT at 0x0400 anyway. The idea of this value is to be set
manually if I *don't* want modern
On Jul 7 09:44, Yaakov S wrote:
On Wed, 2010-07-07 at 10:19 +0200, Corinna Vinschen wrote:
So, is that ok to upload or are you going to change that first?
It's not wrong, just cleaner for the maintainer, that's all.
Thanks, yes, that's how I understood it. I'm just asking if David wants
On Wed, 2010-07-07 at 08:58 -0400, Christopher Faylor wrote:
Unfortunately, it sounds like we've stepped into the middle of a dispute
between the mingw folks and the mingw64 folks. Maybe the best thing for
us to do would be to decide to use only one or the other but not both.
It does seem
On Wed, Jul 07, 2010 at 10:22:17AM -0500, Yaakov (Cygwin/X) wrote:
On Wed, 2010-07-07 at 08:58 -0400, Christopher Faylor wrote:
Unfortunately, it sounds like we've stepped into the middle of a dispute
between the mingw folks and the mingw64 folks. Maybe the best thing for
us to do would be to
On 7/7/2010 1:19 AM, Corinna Vinschen wrote:
On Jul 6 15:41, David Rothenberger wrote:
On 7/6/2010 2:55 PM, Yaakov (Cygwin/X) wrote:
On Tue, 2010-07-06 at 11:19 -0700, David Rothenberger wrote:
I'd like to package libkate[1] in preparation for packaging the
newest version of vorbis-tools.
On Wed, 2010-07-07 at 11:33 -0400, Christopher Faylor wrote:
Here's my question, though: given the incompatibilities mentioned, would
a cygwin1.dll built with i686-w64-cygwin (mingw-w64) toolchain be 100%
compatible with current and past releases built with i686-pc-cygwin
(mingw.org)
On Wed, Jul 07, 2010 at 11:16:54AM -0500, Yaakov (Cygwin/X) wrote:
On Wed, 2010-07-07 at 11:33 -0400, Christopher Faylor wrote:
Here's my question, though: given the incompatibilities mentioned, would
a cygwin1.dll built with i686-w64-cygwin (mingw-w64) toolchain be 100%
compatible with current
On Jul 7 08:34, David Rothenberger wrote:
On 7/7/2010 1:19 AM, Corinna Vinschen wrote:
On Jul 6 15:41, David Rothenberger wrote:
On 7/6/2010 2:55 PM, Yaakov (Cygwin/X) wrote:
On Tue, 2010-07-06 at 11:19 -0700, David Rothenberger wrote:
I'd like to package libkate[1] in preparation for
On Wed, Jul 7, 2010 at 12:53 PM, Christopher Faylor
cgf-use-the-mailinglist-ple...@cygwin.com wrote:
On Wed, Jul 07, 2010 at 11:16:54AM -0500, Yaakov (Cygwin/X) wrote:
On Wed, 2010-07-07 at 11:33 -0400, Christopher Faylor wrote:
Here's my question, though: given the incompatibilities mentioned,
On 7/7/2010 9:48 AM, Corinna Vinschen wrote:
On Jul 7 08:58, Christopher Faylor wrote:
On Wed, Jul 07, 2010 at 02:39:19PM +0200, Corinna Vinschen wrote:
Oh, and, talking about /opt or /usr, I'd prefer the above /usr/mingw*
sysroot idea. However, I don't like the idea in the least to keep
two
On 7 July 2010 18:27, NightStrike wrote:
I suppose you could build cygwin with a mingw compiler but that's not
how it's built now so I don't see why it makes a difference.
cgf
How's it built now?
With Cygwin gcc and the -mno-cygwin option, using mingw.org's w32api.
Andy
On 7/7/2010 11:12 AM, Corinna Vinschen wrote:
The important question for me is, can Cygwin be built using the w32api
based on the mingw64 sources?
Is it possible? Maybe; we'll just have to try it.
Is it legally permissible, given (possibly overblown?) concerns about
provenance of the changes
On 7 July 2010 22:03, Christopher Faylor wrote:
On Wed, Jul 07, 2010 at 09:44:14PM +0100, Andy Koppe wrote:
On 7 July 2010 18:27, NightStrike wrote:
I suppose you could build cygwin with a mingw compiler but that's not
how it's built now so I don't see why it makes a difference.
cgf
How's
On 7/7/2010 5:03 PM, Christopher Faylor wrote:
On Wed, Jul 07, 2010 at 09:44:14PM +0100, Andy Koppe wrote:
On 7 July 2010 18:27, NightStrike wrote:
How's it built now?
With Cygwin gcc and the -mno-cygwin option, using mingw.org's w32api.
It doesn't use -mno-cygwin. How could it? The
On Wed, Jul 7, 2010 at 6:12 PM, Charles Wilson
cyg...@cwilson.fastmail.fm wrote:
On 7/7/2010 5:03 PM, Christopher Faylor wrote:
On Wed, Jul 07, 2010 at 09:44:14PM +0100, Andy Koppe wrote:
On 7 July 2010 18:27, NightStrike wrote:
How's it built now?
With Cygwin gcc and the -mno-cygwin
On Wed, Jul 07, 2010 at 06:12:23PM -0400, Charles Wilson wrote:
On 7/7/2010 5:03 PM, Christopher Faylor wrote:
On Wed, Jul 07, 2010 at 09:44:14PM +0100, Andy Koppe wrote:
On 7 July 2010 18:27, NightStrike wrote:
How's it built now?
With Cygwin gcc and the -mno-cygwin option, using mingw.org's
On Wed, Jul 07, 2010 at 06:22:30PM -0400, NightStrike wrote:
On Wed, Jul 7, 2010 at 6:12 PM, Charles Wilson
cyg...@cwilson.fastmail.fm wrote:
On 7/7/2010 5:03 PM, Christopher Faylor wrote:
On Wed, Jul 07, 2010 at 09:44:14PM +0100, Andy Koppe wrote:
On 7 July 2010 18:27, NightStrike wrote:
On 7/7/2010 8:39 AM, Corinna Vinschen wrote:
On Jul 7 08:08, Charles Wilson wrote:
I hope I have summed up the various competing proposals fairly, and that
this edition of my patented War and Peace emails helps move the
discussion along to a conclusion.
Ok, I'm sufficiently confused now.
Michael chaozhan at hotmail.com writes:
Hello,
I got the same problem.
My settings:
Windows 7 64 bit Home Premium
CYGWIN_NT-6.1-WOW64 my_machine 1.7.5(0.225/5/3) 2010-04-12 19:07 i686 Cygwin
And I use cygwin 1.7.5 on windows XP has NO problem at all.
But after I completed June
Eric Blake wrote:
As is, your question didn't make much sense to me; please
show a transcript of exact command line sequences showing what you
are trying to accomplish and why you think that cygwin isn't
doing the right thing, rather than just describing it in words.
---
Will do --- I may have
I made separate iso files (setup*exe + setup*ini + release*/) for the
Legacy version [1.5] and current version [1.7]. At 4335495168 and
5039841280 respectively they are both too large to reside on a FAT32
file system, and the larger one can't be burned to an installation DVD.
I put both on a 16G
On Tue, Jul 6, 2010 at 9:59 PM, Christopher Faylor wrote:
On Tue, Jul 06, 2010 at 07:41:03PM +, Peter Waltman wrote:
This is a weird one. I just updated cygwin on my windows 7 machine, and now
my
'x' (lowercase 'x') key isn't working.
The key works outside of cygwin, and when I type the
On Tue, Jul 6, 2010 at 11:22 PM, philippe wrote:
so where should i place the /etc/bashrc
In the file /etc/bash.bashrc
--
Life is complex, with real and imaginary parts.
Ok, it boots. Which means it must be bug-free and perfect. -- Linus Torvalds
People disagree with me. I just ignore them. --
On Wed, Jul 7, 2010 at 8:04 AM, Linda Walsh wrote:
my world is unstable!
Reboot it :)
--
Life is complex, with real and imaginary parts.
Ok, it boots. Which means it must be bug-free and perfect. -- Linus Torvalds
People disagree with me. I just ignore them. -- Linus Torvalds
--
Problem
On Jul 7 09:37, Csaba Raduly wrote:
On Tue, Jul 6, 2010 at 9:59 PM, Christopher Faylor wrote:
On Tue, Jul 06, 2010 at 07:41:03PM +, Peter Waltman wrote:
This is a weird one. I just updated cygwin on my windows 7 machine, and
now my
'x' (lowercase 'x') key isn't working.
The key
On Jul 7 00:22, Charles Wilson wrote:
On 7/6/2010 10:35 PM, Yaakov (Cygwin/X) wrote:
On Tue, 2010-07-06 at 22:07 -0400, Christopher Faylor wrote:
I'd want to check with Corinna on this but I am mildly opposed to putting
this in /opt. I don't think it makes sense there. But I haven't been
On Jul 7 08:03, Fergus wrote:
I made separate iso files (setup*exe + setup*ini + release*/) for the
Legacy version [1.5] and current version [1.7]. At 4335495168 and
5039841280 respectively they are both too large to reside on a FAT32
file system, and the larger one can't be burned to an
On Jul 6 06:41, Slide wrote:
On Tue, Jul 6, 2010 at 1:02 AM, Corinna Vinschen
corinna-cyg...@cygwin.com wrote:
On Jul 5 23:00, Slide wrote:
snip
This funtionality wasn't available in 1.5, so, yes, this would only
have started with 1.7.
So it seems that these netapp drives
Hi all,
I just did a periodic update of my cygwin installation, and now I can't
build applications using fltk. The fltk packages seem to have been split
into a new set for X11 and a set similar to the old packages for native
windows graphics. However, the X11 set consists of source, library,
snip
Thanks for your help. This problem should be fixed now in CVS.
I switched off the entire mechanism which tries to resolve sharing
violations for netapp drives.
What happens is this:
The netapp drive is thoroughly confused when trying to move-and-delete
a file or directory using a
On Wed, Jul 07, 2010 at 10:20:54AM +0200, Corinna Vinschen wrote:
On Jul 7 09:37, Csaba Raduly wrote:
On Tue, Jul 6, 2010 at 9:59 PM, Christopher Faylor wrote:
On Tue, Jul 06, 2010 at 07:41:03PM +, Peter Waltman wrote:
This is a weird one. ??I just updated cygwin on my windows 7 machine,
On Wed, Jul 07, 2010 at 05:56:30AM -0700, Slide wrote:
snip
Thanks for your help. ?This problem should be fixed now in CVS.
I switched off the entire mechanism which tries to resolve sharing
violations for netapp drives.
What happens is this:
The netapp drive is thoroughly confused when
On Wed, Jul 7, 2010 at 6:04 AM, Christopher Faylor
cgf-use-the-mailinglist-ple...@cygwin.com wrote:
On Wed, Jul 07, 2010 at 05:56:30AM -0700, Slide wrote:
snip
Thanks for your help. ?This problem should be fixed now in CVS.
I switched off the entire mechanism which tries to resolve sharing
Have you tried rebaseall yet?
Ken
Hello,
I haven't. From how I understood it, that's something one does to
update or repair an older installation.
Should I just run it on my fresh installation? The documentation of
rebaseall confused me a little bit, all those base- and
On Wed, Jul 07, 2010 at 03:48:09PM +0200, P. Goldmann wrote:
Just out of curiosity: The whole rebase-stuff, was it introduced
because of MS's Windows 7 or with cygwin 1.7.x? On XP I never heard
anything about it, neither was it necessary to do someting like this to
get a cygwin 1.5.x installation
On Jul 7 15:48, P. Goldmann wrote:
Have you tried rebaseall yet?
Ken
Hello,
I haven't. From how I understood it, that's something one does to
update or repair an older installation.
Should I just run it on my fresh installation? The documentation of
rebaseall confused me a little
None, usually. Just call `rebaseall' from a dash(!) shell, with no
other process running.
That's what I did. Still no luck running top.
In a plain bash I still get:
u...@box ~
$ top
5 [main] top 5780 sig_send: wait for sig_complete event failed,
signal 6,
rc 258, Win32 error 0
On Wed, 2010-07-07 at 17:38 +0800, Steve Underwood wrote:
I just did a periodic update of my cygwin installation, and now I can't
build applications using fltk. The fltk packages seem to have been split
into a new set for X11 and a set similar to the old packages for native
windows
A new version the libogg, libogg-devel, and libogg0 packages are now
available for download.
NEWS:
=
This is a new upstream release, with upstream changes listed
below.
DESCRIPTION:
Ogg project codecs use the Ogg bitstream format to arrange the raw,
compressed bitstream into a
A new version of the libvorbis, libvorbis-devel, libvorbis0,
libvorbisenc2, and libvorbisfile3 packages are now available for
download.
DESCRIPTION:
Vorbis is a general purpose audio and music encoding format
contemporary to MPEG-4's AAC and TwinVQ, the next generation beyond
MPEG
A new version the libao packages is now available for download.
NEWS:
=
This is a new upstream release, with upstream changes listed below. See
also the package documentation in /usr/share/doc/libao.
The new release includes a new versioned DLL package: libao4. The
old package, libao2, is
On Tue, 2010-07-06 at 23:04 -0400, Charles Wilson wrote:
[massive snip]
OK, so the next question is, if they going to go multilib, why provide
TWO different toolchains -- basically identical, both supporting both
-m32 and -m64, different only in the default bitmode?
Well...that's up to them.
New packages providing the Kate codec are now available.
libkate is part of the Cygwin Ports project. The current version
there is 0.3.7-2, which is why these package are
0.3.7-3. The Cygwin Ports packages also include
KateDJ. KateDJ relies on python-wx, which is not available outside
of Cygwin
On 7/7/2010 12:10 PM, Yaakov (Cygwin/X) wrote:
On Tue, 2010-07-06 at 23:04 -0400, Charles Wilson wrote:
[massive snip]
OK, so the next question is, if they going to go multilib, why provide
TWO different toolchains -- basically identical, both supporting both
-m32 and -m64, different only in
Csaba Raduly a écrit :
On Tue, Jul 6, 2010 at 11:22 PM, philippe wrote:
so where should i place the /etc/bashrc
In the file /etc/bash.bashrc
the change bashrc-basch.barchrc doesn't solve the problem.
Philippe.
--
Problem reports: http://cygwin.com/problems.html
FAQ:
On 6 July 2010 22:22, philippe wrote:
- /cygwin.bat to replace basic console by rxvt with the line
rxvt -fn -*-Courier-medium-r-*-18-*-*-*-*-iso8859-1 -geometry 80x30
-sr -bg #d5 -fg black -sl 2000 -termName xterm -e /usr/bin/bash
--login -i
Setting termName to xterm in rxvt is a bad
On Wed, 2010-07-07 at 15:21 -0400, Charles Wilson wrote:
Really? Other than the packaging issues, I had no problem with JonY's
src snapshot, compiling a 64bit-default, but multilib enabled, gcc. did
something break upstream between when JonY took his snapshot and today,
or are you
[Please:
http://www.cygwin.com/acronyms/#PCYMTWLL
Thanks.]
On 2010-07-08 01:30Z, Shalomov, Inessa A (US SSA) wrote:
I am trying to get the system() call working in my driver which I am
running in a DOS terminal. For the sake of not porting out all of
cygwin libraries and executables, I am
On 7/7/2010 8:14 PM, Yaakov (Cygwin/X) wrote:
On Wed, 2010-07-07 at 15:21 -0400, Charles Wilson wrote:
Really? Other than the packaging issues, I had no problem with JonY's
src snapshot, compiling a 64bit-default, but multilib enabled, gcc. did
something break upstream between when JonY
On Wed, Jul 7, 2010 at 10:16 PM, Charles Wilson
cyg...@cwilson.fastmail.fm wrote:
OOTB gcc multilib does not build, nor AFAICS do clear-cut patches exist
to fix it. Others in #mingw-w64 seem to think that multilib isn't worth
the headache, at least not yet. We'll see what I come up with over
On Wed, 2010-07-07 at 22:16 -0400, Charles Wilson wrote:
Hmm. That's what I *was* doing: JonY's -src provides a cygport that
appears to work. You have to impose some workarounds, like:
RESTRICT=strip
and manually use the target strip tool within src_install, but...it
*works*. (E.g. how
A new version the libogg, libogg-devel, and libogg0 packages are now
available for download.
NEWS:
=
This is a new upstream release, with upstream changes listed
below.
DESCRIPTION:
Ogg project codecs use the Ogg bitstream format to arrange the raw,
compressed bitstream into a
A new version the libao packages is now available for download.
NEWS:
=
This is a new upstream release, with upstream changes listed below. See
also the package documentation in /usr/share/doc/libao.
The new release includes a new versioned DLL package: libao4. The
old package, libao2, is
New packages providing the Kate codec are now available.
libkate is part of the Cygwin Ports project. The current version
there is 0.3.7-2, which is why these package are
0.3.7-3. The Cygwin Ports packages also include
KateDJ. KateDJ relies on python-wx, which is not available outside
of Cygwin
70 matches
Mail list logo
