Charles Wilson wrote:
So, in short: auto-import has been available for 7.5 years, and has been
the default (but whines with info message) on all pe platforms for
just under 7 years.
I don't think anyone will complain about no longer whining. It's an
established tool in the gcc/ld-on-pe
Charles Wilson wrote:
cygwin-1.5:
http://cygwin.cwilson.fastmail.fm/ITP/tack-1.06-1-src.tar.bz2
http://cygwin.cwilson.fastmail.fm/ITP/tack-1.06-1.tar.bz2
Has the correct version of 'tack' been built and packaged? It appears
that version 1.05
was built and packaged as version 1.06-1.
$
km4hr schrieb:
Phil,
Thanks for hanging in there and trying your best to help identify my
problem.
If I ever find the solution I will shout it from the mountain top!
I'd like to try cygwin-x on another Windows PC with less software installed
but my company's network is configured to block
From: cygwin-xfree-ow...@cygwin.com
[mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Jon TURNEY
Sent: Wednesday, February 25, 2009 2:52 PM
I've built a version of 1.5.3-7, with this patch reverted and
lots more
clipboard debugging added. You can download it from [2]
It would be
Dirk,
Thanks for the recommendation. I gave it a try. Still no luck.
Dirk Fassbender wrote:
km4hr schrieb:
Phil,
Thanks for hanging in there and trying your best to help identify my
problem.
If I ever find the solution I will shout it from the mountain top!
I'd like to try
On Wed, Feb 25, 2009 at 5:51 PM, Jon TURNEY jon.tur...@dronecode.org.uk wrote:
I've built a version of 1.5.3-7, with this patch reverted and lots more
clipboard debugging added. You can download it from [2]
It would be most helpful if you could try this and see if the clipboard
problems you
Thought I'd reply to the list about the resolution to this, since
somebody just asked me about this off-list:
'startxwin.sh' from a bash window works whereas 'startx' doesn't (also
works: 'startxwin.bat' from a windows cmd line). It seems startx is
broken on cygwin.
Andrew
On Sat, Dec 6, 2008
From: cygwin-xfree-ow...@cygwin.com
[mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Andrew Allen
Sent: Thursday, February 26, 2009 5:07 PM
Thought I'd reply to the list about the resolution to this, since
somebody just asked me about this off-list:
'startxwin.sh' from a bash window
CVSROOT:/cvs/uberbaum
Module name:winsup
Changes by: c...@sourceware.org 2009-02-27 00:34:40
Modified files:
cygwin : ChangeLog dtable.cc fhandler.h select.cc
shared_info.h
Log message:
* dtable.cc (dtable::select_read): Add
At 04:52 AM 2/26/2009, Corinna Vinschen wrote:
| On Feb 25 23:03, Pierre A. Humblet wrote:
| I tried to compile Exim with IPv6 enabled and Cygwin 1.7, but it needs
| gethostbyname2.
| Here is an implementation of that function.
| In attachment I am including the same patch as well as a
On Feb 26 10:29, Pierre A. Humblet wrote:
At 04:52 AM 2/26/2009, Corinna Vinschen wrote:
| On Feb 25 23:03, Pierre A. Humblet wrote:
| I tried to compile Exim with IPv6 enabled and Cygwin 1.7, but it needs
| gethostbyname2.
| Here is an implementation of that function.
| In
Pierre A. Humblet wrote:
I am still fighting one issue with Windows. On XP, when using the native
gethostbyname I can resolve computers on my local net (through NetBIOS or
such). But I can't get them with DnsQuery, except my own computer, despite
what I think the doc says. Any insight?
Are
On Feb 26 00:28, Paul McFerrin wrote:
Corinnia:
I finally got cygwin 1.7 swapped-in to try to reproduce my problem.
Good news, after a few hours of pinging a website, ZERO ERRORS for now.
Since it is an intermittent error, I'll let it run at 6 seconds interval
until tomorrow.
Now
On Feb 25 19:20, Greg Freemyer wrote:
On Wed, Feb 25, 2009 at 6:01 PM, Larry Hall (Cygwin)
reply-to-list-only...@cygwin.com wrote:
Greg Freemyer wrote:
snip
Time to experiment with Cygwin 1.7
I know the whole package is still considered test. How stable is the
actual dll(s).
On Feb 25 16:12, Frank Fesevur wrote:
2009/2/25 Corinna Vinschen:
I've just updated the Cygwin 1.7 version of OpenSSH to 5.2p1-1.
This is a new major upstream release. It fixes a security related issue
and introdues a lot of new features. The Cygwin release is created
from the vanilla
On Feb 25 18:58, Greg Freemyer wrote:
I just read the release email for 1.7.0
In part it says:
- Fallout from the long path names: If the current working directory is
longer than 260 bytes, or if the current working directory is a virtual
path (like /proc, /cygdrive, //server), don't
2009/2/26 Corinna Vinschen:
On Feb 25 16:12, Frank Fesevur wrote:
Since this is a security fix, will there be a 1.5 update as well?
Well, actually I have no intention to update 1.5.x packages anymore.
I understand you want us to start using 1.7, but in the announcement
of 1.7.0-41 you write
On Feb 26 10:39, Frank Fesevur wrote:
2009/2/26 Corinna Vinschen:
On Feb 25 16:12, Frank Fesevur wrote:
Since this is a security fix, will there be a 1.5 update as well?
Well, actually I have no intention to update 1.5.x packages anymore.
I understand you want us to start using 1.7,
On Feb 26 10:10, Corinna Vinschen wrote:
On Feb 25 19:20, Greg Freemyer wrote:
On Wed, Feb 25, 2009 at 6:01 PM, Larry Hall (Cygwin)
reply-to-list-only...@cygwin.com wrote:
Greg Freemyer wrote:
snip
Time to experiment with Cygwin 1.7
I know the whole package is still
Has the correct version of 'tack' been built and packaged? It appears that
version 1.05
was built and packaged as version 1.06-1.
$ cygcheck -c tack
Cygwin Package Information
Package VersionStatus
tack 1.06-1 OK
$ tack -V
tack version 1.05
Larry Hall (Cygwin) reply-to-list-only...@cygwin.com writes:
Morten Kjærulff wrote:
On Thu, Feb 26, 2009 at 12:10 AM, Larry Hall (Cygwin)
reply-to-list-only...@cygwin.com wrote:
Morten Kjærulff wrote:
Hi,
On my machine#2 I just installed lynx, but it just exit without
telling anything.
Hi there,
I would like to first thank the entire cygwin team for providing such
a great tool that saved me countless times in corporate hell.
Now, I compiled large application that I am working on from another platform
with gcc on cygwin in vista, and I found that it does not even startup
On 2/26/2009 9:55 AM, Sivaram Neelakantan wrote:
Larry Hall (Cygwin) reply-to-list-only...@cygwin.com writes:
Morten Kjærulff wrote:
On Thu, Feb 26, 2009 at 12:10 AM, Larry Hall (Cygwin)
reply-to-list-only...@cygwin.com wrote:
Morten Kjærulff wrote:
Hi,
On my machine#2 I just installed
On Thu, Feb 26, 2009 at 4:19 AM, Corinna Vinschen
corinna-cyg...@cygwin.com wrote:
On Feb 25 18:58, Greg Freemyer wrote:
I just read the release email for 1.7.0
In part it says:
- Fallout from the long path names: If the current working directory is
longer than 260 bytes, or if the
Dave Korn wrote:
you should definitely see if it reproduces under 1.7
I tried the latest 1.7 and it hangs instead of segfaulting (less than 500k
iterations).
This seems like a pretty major problem for any intensive multithreaded
application. Though infrequent, it has produced a rather large
Simple test case. This application uses the C locale (by virtue of the fact
that we did not use setlocale(), and evidenced by mb_cur_max of 1). On Linux,
this correctly shows wctomb rejecting the conversion (0x100 is too big to fit
in a 1-byte sequence) with EILSEQ, but newlib currently
OKAY, I have some passwd questions problems associated with cygwin 1.7.
PRIOR to 1.7, my UID/GID for Paul account was 501/401 and all of my
files have correct ownership. When I created /etc/passwd via:
cd /etc
mkpasswk -l -p $HOME x
vim x { changed: UID/GID to 501/401
jamesmikedup...@googlemail.com wrote:
snip
I am not able to really see what is going on, process explorer says
cygwin1!aclcheck
Otherwise, I have seen it hang in some function that I cannot remember
exactly ascii convert or something and other vista kernel functions.
Basically, I would like
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
On Thu, Feb 26, 2009 at 02:29:57PM -0500, Greg Freemyer wrote:
If the path is short, it uses the full long directory name as
expected. If the path exceeds 260, it reverts to using the 8.3 names,
thus giving a workaround that will allow you to descend deeper into a
directory structure.
On Thu, Feb 19, 2009 at 09:27:34AM -0500, Christopher Faylor wrote:
On Thu, Feb 19, 2009 at 09:16:50AM -0500, Andrew Schulman wrote:
I'm compiling screen for 1.7. The configure script has a test for a usable
pipe implementation, which passes, and another one for a working pipe
implementation,
-Original Message-
From: cygwin-ow...@cygwin.com
[mailto:cygwin-ow...@cygwin.com] On Behalf Of Christopher Faylor
Sent: Thursday, February 26, 2009 18:36
To: cygwin@cygwin.com
Subject: Re: Another long pathname question
On Thu, Feb 26, 2009 at 02:29:57PM -0500, Greg Freemyer
On Thu, Feb 26, 2009 at 09:33:07PM -0500, Jason Pyeron wrote:
From: cygwin-ownerX
Oh! Is that who it came from?
[mailto:cygwin-ownerX
Yes. Got that the first time.
Sent: Thursday, February 26, 2009 18:36
Hmm. It's 10:18PM here.
To: cygwinX
What? You're responding to email to the
David Rothenberger wrote:
Rolling back libncurses8 and terminfo to the previous release solves the
problem for me. Recompiling lynx from source with the new libncurses8
and terminfo packages also fixes the problem.
Confirmed bug. I've pulled the release.
Upstream has silently changed the
There was an unintended API change in this release, which caused the
cygncurses-8.dll to not be backwards compatible with previous DLLs of
the same name.
Sorry for the inconvenience.
--
Charles Wilson
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports:
There was an unintended API change in the associated ncurses release. As
part of rolling back to the earlier known-good ncurses package, the
updated terminfo must also be rolled back.
Sorry for the inconvenience.
--
Charles Wilson
--
Unsubscribe info:
There was an unintended API change in this release, which caused the
cygncurses-8.dll to not be backwards compatible with previous DLLs of
the same name.
Sorry for the inconvenience.
--
Charles Wilson
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports:
There was an unintended API change in this release, which caused the
cygncurses-8.dll to not be backwards compatible with previous DLLs of
the same name.
Sorry for the inconvenience.
--
Charles Wilson
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports:
The upcoming Cygwin 1.7.0 release adds so many APIs and improves so much
functionality that it probably deserves a separate designation in
config.guess. For reference, notice the size of the most recent beta
announcement: http://cygwin.com/ml/cygwin-announce/2009-02/msg00018.html
For an example
Setup stalled:
Fatal Error: Uncaught Exception
Thread: DialogProc
Type: 9Exception
Message: Package validation failure for
release/gdbm/gdbm-1.8.3-9-src.tar.bz2
AppErrNo: 1
Incidentally gdbm-1.8.3-20 installed perfectly well into [1.7].
Fergus
--
Unsubscribe info:
Fergus wrote:
Setup stalled:
Fatal Error: Uncaught Exception
Thread: DialogProc
Type: 9Exception
Message: Package validation failure for
release/gdbm/gdbm-1.8.3-9-src.tar.bz2
AppErrNo: 1
Incidentally gdbm-1.8.3-20 installed perfectly well into [1.7].
Try a different mirror. I just
There was an unintended API change in the associated ncurses release. As
part of rolling back to the earlier known-good ncurses package, the
updated terminfo must also be rolled back.
Sorry for the inconvenience.
--
Charles Wilson
There was an unintended API change in this release, which caused the
cygncurses-8.dll to not be backwards compatible with previous DLLs of
the same name.
Sorry for the inconvenience.
--
Charles Wilson
43 matches
Mail list logo
