How can I automatically convert all symlinks on my Cygwin filesystem from
the !symlink format to windows shortcuts? Samba doesn't seem to
maintain the correct permissions for the Cygwin DLL to detect the
!symlink files as symlinks, so they are treated as regular files
(hence the errors with gcc,
On Tue, Feb 11, 2003 at 01:05:06PM -, Christopher January wrote:
How can I automatically convert all symlinks on my Cygwin filesystem
from
the !symlink format to windows shortcuts? Samba doesn't seem to
maintain the correct permissions for the Cygwin DLL to detect the
!symlink files
I'm having trouble compiling this test program:
void f(){}
using the command line:
gcc test.c -c -o test.o
using 1.3.19 or latest Cygwin snapshot (2003-Feb-07) (same error with
both) and gcc-3.2-3.
The error I see is:
16 bit MS-DOS Subsystem
/usr/src/cygwin-cvs/obj
The NTVDM CPU has
procps reports the effective user id, not the real user id (by design).
The /proc fhandler returns the wrong effective user id (see for yourself by
cat'ing /proc/status, the effective user id is the second number after Uid:).
Therefore the bug is in the /proc fhandler.
Chris
Between 1.1.3 and 1.3.0 a huge change occurred in the pthreads code
base, so this assumption is not safe. (It's not necessarily wrong
either.) I'd definitely be using 1.3.10 though.
#include pthread.h
#include iostream
The cygwin c++ libgcc, stdlibc++ and gcc are not built with thread
Using Cygwin DLL 1.3.10.
Likewise. (On Win2K.)
1. Close all Cygwin programs
2. Open bash
3. Type: cd /cygdrive
4. Type ls
I get a listing of C:\ instead
5. Type bash
6. Type: cd /cygdrive
7. Type ls
I get a listing of available drives
When looking at XP's CreateProcessW (or rather, CreateProcessInternalW) I
noticed something strange about the way it creates a process. It seems
that NT is sort of capable of a fork() command. The function
NtCreateProcess appears to create a blank process, into which you can put
anything
7 matches
Mail list logo
