On 2/6/06, Brian Dessent <[EMAIL PROTECTED]> wrote:
> The actual source of the problem is the SECT_OFF_DATA macro around line
> 910 in coffread.c. I'm not sure exactly what's broken here, but it
> seems like it might be related to the fact that (at least on my system)
> the DLL gets assigned the d
> > > >
> > > > Basically, when I hit [ESC] then fwd slash (/) to search through the
> > > > history, it throws my cursor back to get beginning of the line (on top
> > > > of the prompt) and acts weird. This is in mrxvt, now if I do the same
> > > > in the basic cygwin bash shell i get this:
> > >
The solution to my variant of this problem ended up being pretty simple.
I was running the Norton utility that guards the trash bin (Norton
Protected Trash Bin).
For this use, it's toxic.
The solution was to add the entire cygwin directory to the exclusion
list (in the trash bin's Properties
Yu Lianqing wrote:
> I've post the message below to cygwin-xfree@cygwin.com but got no reply
> yet. I post this message to this list since I need your help urgently.
> Sorry for this.
>
> I successfully download and install cgywin on my windows xp profesional
> system. I choose to install everyth
Yu Lianqing wrote:
> Hi,
>
> I've post the message below to cygwin-xfree cygwin [dot] com but got no
> reply
^
Please don't send plain-text email addresses in the body of email.
It just feeds the spammers.
> yet.
Hi,
I've post the message below to cygwin-xfree@cygwin.com but got no reply
yet. I post this message to this list since I need your help urgently.
Sorry for this.
I successfully download and install cgywin on my windows xp profesional
system. I choose to install everything (at select package
> > $ uname -a
> > CYGWIN_98-4.10 bedroom 1.5.19(0.150/4/2) 2006-01-20 13:28 i686 Cygwin
> > $ cd /bin
> > $ cygcheck ./bash
> > .\.\.\.\.\ - Cannot open
> > $ cygcheck ./bash.exe
> > .\bash.exe
> > .\cygwin1.dll
> > ...
>
> FWIW, WFM:
>
> $ cygcheck --version
> cygcheck version 1.74
> System C
Hi all,
I recently set up cygwin on a Windows 2003 box with NTFS file permissions. I
encountered the same problem as mentioned in this thread:
http://www.cygwin.com/ml/cygwin/2005-07/msg00732.html
To sum up the issue: Upon ssh login I received the following error message:
-bash: cannot create
On Tue, 7 Feb 2006, Eric Blake wrote:
> $ uname -a
> CYGWIN_98-4.10 bedroom 1.5.19(0.150/4/2) 2006-01-20 13:28 i686 Cygwin
> $ cd /bin
> $ cygcheck ./bash
> .\.\.\.\.\ - Cannot open
> $ cygcheck ./bash.exe
> .\bash.exe
> .\cygwin1.dll
> ...
FWIW, WFM:
$ uname -svr
CYGWIN_NT-5.1 1.5.20(0.153/4/
$ uname -a
CYGWIN_98-4.10 bedroom 1.5.19(0.150/4/2) 2006-01-20 13:28 i686 Cygwin
$ cd /bin
$ cygcheck ./bash
.\.\.\.\.\ - Cannot open
$ cygcheck ./bash.exe
.\bash.exe
.\cygwin1.dll
...
--
Eric Blake
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http:
1. Run bash in rxvt.
2. Run "strace sleep 10".
3. Press Ctrl+C.
Nothing seems to receive the ^C at all (both strace and sleep run to
completion). I cannot reproduce this problem using bash in a windows
console.
This is not a regression from 1.5.19. But I recall it working a while
ago (what
Zach Gelnett gmail.com> writes:
> > >
> > > Basically, when I hit [ESC] then fwd slash (/) to search through the
> > > history, it throws my cursor back to get beginning of the line (on top
> > > of the prompt) and acts weird. This is in mrxvt, now if I do the same
> > > in the basic cygwin bash
On Tue, 7 Feb 2006, Christopher Faylor wrote:
> I believe that Brian Ford is looking into modifying the new CW_SETUP_WINENV
> code to perform the proper conversion of POSIX style to Windows style.
We're still debating aproaches for solving our problem, so it is possible
I won't get to it. If som
On Tue, Feb 07, 2006 at 06:59:43PM +0100, Michael Schaap wrote:
>On 7-Feb-2006 3:31, Yitzchak Scott-Thoennes wrote:
>> On Mon, Feb 06, 2006 at 11:40:22PM +0100, Michael Schaap wrote:
>>
>>> What we basically need to do, is copy the Cygwin environment to the
>>> Windows environment, taking care o
On 7-Feb-2006 3:31, Yitzchak Scott-Thoennes wrote:
> On Mon, Feb 06, 2006 at 11:40:22PM +0100, Michael Schaap wrote:
>
>> What we basically need to do, is copy the Cygwin environment to the
>> Windows environment, taking care of path conversion for all the
>> appropriate variables.
>>
>
> M
Corinna Vinschen <[EMAIL PROTECTED]> wrote:
>> On Feb 6 14:49, Kevin Layer wrote:
>> > I'm running the latest cygwin (1.5.19, see cygcheck below).
>> >
>> > My application is a native Windows app (64 and 32-bit). It includes
>> > no cygwin libraries and is not compiled with cygwin's gcc. When
On Feb 8 00:06, HASHI Hiroaki wrote:
> > Thanks, but the patch isn't exactly "trivial", so we would need a
> > copyright assignment from you and, possibly, from your employer.
> > See http://cygwin.com/contrib.html.
>
> Oh.
>
> I regard my employer as not agreeing.
>
> I hope, anyone re-write
> Thanks, but the patch isn't exactly "trivial", so we would need a
> copyright assignment from you and, possibly, from your employer.
> See http://cygwin.com/contrib.html.
Oh.
I regard my employer as not agreeing.
I hope, anyone re-write a patch and appling it.
> Why isn't it sufficient just
On Feb 7 22:55, HASHI Hiroaki wrote:
> Hello!
>
> In cvs head.
>
> A 'readdir' function cannot listing filename that using multi-byte
> charctor. (corrupt filename)
>
> Because, newlib's wcstombs do not support 'true' multi-byte charactor
> conversion.
>
> I made a patch for cvs head.
Thanks
Hello!
In cvs head.
A 'readdir' function cannot listing filename that using multi-byte
charctor. (corrupt filename)
Because, newlib's wcstombs do not support 'true' multi-byte charactor
conversion.
I made a patch for cvs head.
That using W32API's WideCharToMultiByte instead of newlib's wcstom
On 2/3/06, Igor Peshansky <[EMAIL PROTECTED]> wrote:
> On Fri, 3 Feb 2006, David Picton wrote:
>
> > I have encountered a strange bug when starting Microsoft Word when it is
> > started by the cygstart command, e.g. "cygstart Index.doc", with the
> > current version of the Cygwin dll.
> >
> > The s
On Feb 7 11:01, Corinna Vinschen wrote:
> On Feb 6 14:49, Kevin Layer wrote:
> > I'm running the latest cygwin (1.5.19, see cygcheck below).
> >
> > My application is a native Windows app (64 and 32-bit). It includes
> > no cygwin libraries and is not compiled with cygwin's gcc. When I
> > exe
On Feb 6 14:49, Kevin Layer wrote:
> I'm running the latest cygwin (1.5.19, see cygcheck below).
>
> My application is a native Windows app (64 and 32-bit). It includes
> no cygwin libraries and is not compiled with cygwin's gcc. When I
> execute cygwin programs from my app, however, the return
David Arnstein wrote:
I use the usual setup.exe to keep my Cygwin packages up to date.
Recently, this executable has been giving me Dr. Watson crashes left and
right. I think I isolated the problem.
There is a cygwin package xorg-x11-f11. I attempted to re-install it
from setup.exe. Setup.exe
I use the usual setup.exe to keep my Cygwin packages up to date.
Recently, this executable has been giving me Dr. Watson crashes left and
right. I think I isolated the problem.
There is a cygwin package xorg-x11-f11. I attempted to re-install it
from setup.exe. Setup.exe told me that the packa
Thanks for the informative and helpful response.
Darel
---
Tim Prince wrote:
djh wrote:
My current version of gcc that setup.exe downloaded for me is:
gcc (GCC) 3.4.4 (cygming special) (gdc 0.12, using dmd 0.125)
The other day I downloaded gcc 4.0.2
filena
26 matches
Mail list logo
