Re: [ITP, take 2] Re: [ITP] libelf

2009-12-30 Thread Dave Korn
Dave Korn wrote:
 send me the
 libelf0-0.8.13-1-compile.log offlist and I'll see how it compares to one of
 mine.  Also if you could dump a list of the imports from your version of the
 dll, I'd like to see which symbols its pulling in.

  Nevermind; I figured it out.  I have a local patch in my binutils (which I'm
about to send upstream) that accounts for the difference.  I'll upload libelf
without libgcc1 in the requires: line, since the DLL that I build won't have
the import.  (DLLs built using unpatched binutils will continue to pull in
this redundant dependency, but that's not a problem for me, only for anyone
who for whatever reason decides they want to repackage it themselves.)

cheers,
  DaveK



singular-icons: possible packaging error?

2009-12-30 Thread Buchbinder, Barry (NIH/NIAID) [E]
The singular-icons package contains the following file in both versions 3.0.3-1 
and 3.1.0-1.
/usr/lib/Singular/cygwin-setup.exe

I point this out since it seems strange to me and I wonder whether it might be 
a mistake.

I apologized for wasting bandwidth if it is not an error.

Thanks,

- Barry
  Disclaimer: Statements made herein are not made on behalf of NIAID.



Re: [ITP, take 2] Re: [ITP] libelf

2009-12-30 Thread Yaakov (Cygwin/X)

On 30/12/2009 11:38, Dave Korn wrote:

   Nevermind; I figured it out.  I have a local patch in my binutils (which I'm
about to send upstream) that accounts for the difference.  I'll upload libelf
without libgcc1 in the requires: line, since the DLL that I build won't have
the import.  (DLLs built using unpatched binutils will continue to pull in
this redundant dependency, but that's not a problem for me, only for anyone
who for whatever reason decides they want to repackage it themselves.)


Why is a dependency on libgcc1 redundant?


Yaakov


Re: [ITP, take 2] Re: [ITP] libelf

2009-12-30 Thread Dave Korn
Yaakov (Cygwin/X) wrote:
 On 30/12/2009 11:38, Dave Korn wrote:
 Nevermind; I figured it out.  I have a local patch in my binutils (which
 I'm about to send upstream) that accounts for the difference.  I'll
 upload libelf without libgcc1 in the requires: line, since the DLL that I
 build won't have the import.  (DLLs built using unpatched binutils will
 continue to pull in this redundant dependency, but that's not a problem
 for me, only for anyone who for whatever reason decides they want to
 repackage it themselves.)
 
 Why is a dependency on libgcc1 redundant?

  Because it doesn't actually need anything from libgcc1.  It gets pulled in
by the weak reference here in gcc/config/i386/cygming-crtbegin.c:

---
extern void __register_frame_info (const void *, struct object *)
   TARGET_ATTRIBUTE_WEAK;
extern void *__deregister_frame_info (const void *)
  TARGET_ATTRIBUTE_WEAK;
[ ... ]
  if (h)
register_frame_fn = (void (*) (const void *, struct object *))
GetProcAddress (h, __register_frame_info);
  else
register_frame_fn = __register_frame_info;
  if (register_frame_fn)
 register_frame_fn (__EH_FRAME_BEGIN__, obj);
---

  This is a PE weak external, and if there aren't any strong definitions
elsewhere in the program, it should fall back to the default value (zero); in
particular it should not cause the import stub to be pulled in from the libgcc
import library.  The bug in binutils causes the weakness of the symbol to be
forgotten, causing the reference to be pulled in; the result is that at
startup the program unnecessarily calls into the libgcc dll to register empty
EH frame tables.  Harmless but wasteful.

  The reason this only happens sometimes when linking a DLL is because it
depends on the order in which LD encounters the weak reference and other
undefined references to the same symbol; the weakness can get lost.  It's
another side of the same bug as here,

http://cygwin.com/ml/cygwin/2009-12/threads.html#00583

where it resulted in a weak reference giving an undefined symbol error; here,
there is a version of the symbol in question available, so it just ends up
pulling the symbol in when it wasn't wanted.

  (I'll post the fix to the binutils list shortly, I'm writing it up now.)

cheers,
  DaveK




Can't start xterm from Cygwin/X icon in system tray

2009-12-30 Thread Jim Reisert AD1C
I have a very strange situation.

At work, I am running Win XP SP3.  I installed all the latest Cygwin
(1.7.1) + Xorg updates, including startxwin.exe.  Everything works
perfectly.

At home, I am running Windows 7 Professional, 64-bit.  I am unable to
start an xterm from the Cygwin/X icon in the system tray (right-click,
select xterm).  Both setups have the same line in .XWinrc:

xterm  EXEC  xterm

I am starting the X server the same way:

D:\Cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe

I do not have a ~/.startxwinrc file.  The xterm that is supposed to be
created when the server starts doesn't start either.

The symptom is that xterm.exe is shown running in the task manager,
but there is no Xterm window on the desktop.

As  a work-around, I created a shortcut on my desktop to start an xterm:

D:\Cygwin\bin\run.exe /usr/bin/xterm -display localhost:0

That works perfectly, but is not an optimum solution (I try to have as
few desktop icons as possible).

There is nothing in the /var/log/Xwin log that indicates why an xterm
would start but not open a window.

Any ideas?


-- 
Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



xinit-1.2.0-2 and Xwin Fatal error (xorg-server1.7.3-1)

2009-12-30 Thread ERIC HO
Hi there, I'm running cygwin 1.7.1. I entered xinit and it brought up
the x server and the xterm. I then entered exit on the xterm to
terminate the xterm. I got Xwin Fatal error. The last few messages in
Xwin.0.log are as follows:
2009-12-30 12:45:31 DetectUnicodeSupport - Windows NT/2000/XP
2009-12-30 12:45:31 winGetDisplay: DISPLAY=:0.0
2009-12-30 12:45:31 winClipboardProc - DISPLAY=:0.0
2009-12-30 12:45:31 winClipboardProc - XOpenDisplay () returned and
successfully opened the display.
2009-12-30 12:45:37 winClipboardProc -
winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting
main loop.
2009-12-30 12:45:37 winClipboardProc - XDestroyWindow succeeded.
2009-12-30 12:45:37 Segmentation fault at address 0x268
2009-12-30 12:45:37
Fatal server error:
2009-12-30 12:45:37 Caught signal 11 (Segmentation fault). Server
aborting

Does anyone gets the similar messages? Thanks.


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



Re: xinit-1.2.0-2 and Xwin Fatal error (xorg-server1.7.3-1)

2009-12-30 Thread Yaakov (Cygwin/X)

On 30/12/2009 13:57, ERIC HO wrote:

Hi there, I'm running cygwin 1.7.1. I entered xinit and it brought up
the x server and the xterm. I then entered exit on the xterm to
terminate the xterm. I got Xwin Fatal error.



Problem reports:   http://cygwin.com/problems.html

 ^^^

Yaakov
Cygwin/X

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



X11 assertion fails

2009-12-30 Thread Carl R. Crawford
I just upgraded to the latest version of X11. A program that previously
worked fine now reports the following error:

assertion ret != inval_id failed: file
/usr/src/ports/xorg/libX11/libX11-1.3.2-2/src/libX11-1.3.2/src/xcb_io.c,
line 385, function: _XAllocID
Aborted (core dumped)

How do I fix this?

Thanks,

--Carl


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



Fwd: xinit-1.2.0-2 and Xwin Fatal error (xorg-server1.7.3-1)

2009-12-30 Thread ERIC HO
Please see the attahced files for problem doc. Thanks.

Cygwin Configuration Diagnostics
Current System Time: Wed Dec 30 21:03:30 2009

Windows Vista Home Premium Ver 6.0 Build 6002 Service Pack 2

Path:   C:\cygwin\usr\local\bin
C:\cygwin\bin
C:\cygwin\bin
C:\Windows\system32
C:\Windows
C:\Windows\System32\Wbem
C:\hp\bin\Python
C:\Program Files\Common Files\Roxio Shared\DLLShared\
C:\Program Files\Common Files\Roxio Shared\DLLShared\
C:\Program Files\Common Files\Roxio Shared\9.0\DLLShared\

Output from C:\cygwin\bin\id.exe
UID: 1000(eho) GID: 513(None)
545(Users) 513(None)

SysDir: C:\Windows\system32
WinDir: C:\Windows

USER = 'eho'
PWD = '/home/eho'
HOME = '/home/eho'

HOMEPATH = '\Users\eho'
MANPATH = '/usr/local/man:/usr/share/man:/usr/man::/usr/ssl/man'
APPDATA = 'C:\Users\eho\AppData\Roaming'
HOSTNAME = 'eho-PC'
OnlineServices = 'Online Services'
TERM = 'cygwin'
RoxioCentral = 'c:\Program Files\Common Files\Roxio Shared\9.0\Roxio Central33\'
PROCESSOR_IDENTIFIER = 'x86 Family 15 Model 67 Stepping 3, AuthenticAMD'
WINDIR = 'C:\Windows'
PUBLIC = 'C:\Users\Public'
OLDPWD = '/usr/bin'
USERDOMAIN = 'eho-PC'
OS = 'Windows_NT'
ALLUSERSPROFILE = 'C:\ProgramData'
!:: = '::\'
TEMP = '/cygdrive/c/Users/eho/AppData/Local/Temp'
COMMONPROGRAMFILES = 'C:\Program Files\Common Files'
PCBRAND = 'Pavilion'
USERNAME = 'eho'
PROCESSOR_LEVEL = '15'
FP_NO_HOST_CHECK = 'NO'
SYSTEMDRIVE = 'C:'
LANG = 'C.UTF-8'
USERPROFILE = 'C:\Users\eho'
PS1 = '\[\e]0;\w\a\]\n\[\e[32m\...@\h \[\e[33m\]\w\[\e[0m\]\n\$ '
LOGONSERVER = '\\EHO-PC'
PLATFORM = 'HPD'
PROCESSOR_ARCHITECTURE = 'x86'
LOCALAPPDATA = 'C:\Users\eho\AppData\Local'
!C: = 'C:\cygwin\bin'
ProgramData = 'C:\ProgramData'
SHLVL = '1'
PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC'
HOMEDRIVE = 'C:'
PROMPT = '$P$G'
COMSPEC = 'C:\Windows\system32\cmd.exe'
TMP = '/cygdrive/c/Users/eho/AppData/Local/Temp'
SYSTEMROOT = 'C:\Windows'
PRINTER = 'Lexmark 6500 Series'
CVS_RSH = '/bin/ssh'
PROCESSOR_REVISION = '4303'
INFOPATH = '/usr/local/info:/usr/share/info:/usr/info:'
PROGRAMFILES = 'C:\Program Files'
NUMBER_OF_PROCESSORS = '2'
SESSIONNAME = 'Console'
COMPUTERNAME = 'EHO-PC'
_ = '/usr/bin/cygcheck'

HKEY_CURRENT_USER\Software\Cygwin
HKEY_CURRENT_USER\Software\Cygwin\Program Options
HKEY_CURRENT_USER\Software\Cygwin\setup
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Installations
  (default) = '\??\C:\cygwin'
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Program Options
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\setup
  (default) = 'C:\cygwin'

obcaseinsensitive set to 1

Cygwin installations found in the registry:
  System: Key: c5e39b7a9d22bafb Path: C:\cygwin

c:  hd  NTFS312483Mb  10% CP CS UN PA FC HP
d:  hd  NTFS  9067Mb  89% CP CS UN PA FC Recovery
e:  cd N/AN/A
g:  fd N/AN/A
h:  fd N/AN/A
i:  fd N/AN/A
j:  fd N/AN/A

C:\cygwin/  system  binary,auto
C:/cygwin/bin/usr/bin   system  binary
C:/cygwin/lib/usr/lib   system  binary
cygdrive prefix  /cygdrive  userbinary,auto

Found: C:\cygwin\bin\awk.exe
Found: C:\cygwin\bin\awk.exe
 - C:\cygwin\bin\gawk.exe
Found: C:\cygwin\bin\bash.exe
Found: C:\cygwin\bin\bash.exe
Found: C:\cygwin\bin\cat.exe
Found: C:\cygwin\bin\cat.exe
Found: C:\cygwin\bin\cp.exe
Found: C:\cygwin\bin\cp.exe
Found: C:\cygwin\bin\cpp.exe
Found: C:\cygwin\bin\cpp.exe
 - C:\cygwin\etc\alternatives\cpp
 - C:\cygwin\bin\cpp-3.exe
Not Found: crontab
Found: C:\cygwin\bin\find.exe
Found: C:\cygwin\bin\find.exe
Found: C:\Windows\system32\find.exe
Warning: C:\cygwin\bin\find.exe hides C:\Windows\system32\find.exe
Found: C:\cygwin\bin\gcc.exe
Found: C:\cygwin\bin\gcc.exe
 - C:\cygwin\etc\alternatives\gcc
 - C:\cygwin\bin\gcc-3.exe
Not Found: gdb
Found: C:\cygwin\bin\grep.exe
Found: C:\cygwin\bin\grep.exe
Found: C:\cygwin\bin\kill.exe
Found: C:\cygwin\bin\kill.exe
Found: C:\cygwin\bin\ld.exe
Found: C:\cygwin\bin\ld.exe
Found: C:\cygwin\bin\ls.exe
Found: C:\cygwin\bin\ls.exe
Found: C:\cygwin\bin\make.exe
Found: C:\cygwin\bin\make.exe
Found: C:\cygwin\bin\mv.exe
Found: C:\cygwin\bin\mv.exe
Not Found: patch
Found: C:\cygwin\bin\perl.exe
Found: C:\cygwin\bin\perl.exe
Found: C:\cygwin\bin\rm.exe
Found: C:\cygwin\bin\rm.exe
Found: C:\cygwin\bin\sed.exe
Found: C:\cygwin\bin\sed.exe
Found: C:\cygwin\bin\ssh.exe
Found: C:\cygwin\bin\ssh.exe
Found: C:\cygwin\bin\sh.exe
Found: C:\cygwin\bin\sh.exe
Found: C:\cygwin\bin\tar.exe
Found: C:\cygwin\bin\tar.exe
Found: C:\cygwin\bin\test.exe
Found: C:\cygwin\bin\test.exe
Found: C:\cygwin\bin\vi
Found: C:\cygwin\bin\vi
 - C:\cygwin\bin\vim-nox.exe
Found: C:\cygwin\bin\vim
Found: C:\cygwin\bin\vim
 - C:\cygwin\etc\alternatives\vim
 - C:\cygwin\bin\vim-nox.exe

   61k 2009/03/02 C:\cygwin\bin\cygbz2-1.dll - os=4.0 img=1.0 

Is there anyway to reduce cygwin perl's String memory usage?

2009-12-30 Thread Zhao, Dong
Dear All:
Recently our Perl project run into the Out of memory issue on Windows Cygwin, 
while it works well on Linux, after optimized the code ,it still didn't work on 
Windows Cygwin perl(Because we do a lot of analysis bases on string arrays and 
hashes) . We found the reason is Cygwin perl uses much more memory than Linux 
perl or Windows As perl.
We did a lot searches over the internet but didn't found a solution yet.
I did tune the  heap_chunk_in_mb flag to 2048  in registry Software/Cygnus 
Solutions/Cygwin/. But our Perl script still exhausted over 1GB memory and 
crashes on Cygwin perl.

Then I compared the memory usage difference between Cygwin perl, Windows AS 
perl, and Linux Perl use this simple script:

    my @array = ();
    my $str = A x 1024;  #A string with 1024 len
    for(my $i=0;$i100*1024;$i++){
    push @array,$str;
    }
    STDIN; #No we can take a look at memory.

I expected it to use about 100M memory for all platforms. But Windows cygwin 
perl use about 200M, while AS perl and Linux perl only used 100M.
Our current cygwin perl version is v5.10.0. And cygwin version is 1.7.1.
I also tried the latest cygwin perl version : v5.10.1. But still the same 
result.

Can anyone explain to me?  It there a simple way to reduce the cygwin perl's 
memory usage(Set some flag?Or recomple cygwin perl code)
Thanks for any answer!

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Defeated by alternatives: unison

2009-12-30 Thread Csaba Raduly
On Wed, Dec 30, 2009 at 4:28 AM, Steven E. Harris  wrote:
 Since updating my Cygwin installation to version 1.7, I can no longer
 run unison from the command line. Unison uses the alternatives
 facility to select among multiple installed versions. The symbolic links
 all look to be set up properly, but the program can't be invoked in the
 normal ways.
..
 | % ls -l /usr/bin/unison*
 | -rwxr-xr-x 1 seh root 1076224 2009-10-01 11:27 /usr/bin/unison-2.27.exe
 | -rwxr-xr-x 1 seh root 1123840 2009-10-01 11:31 /usr/bin/unison-2.32.exe
 | lrwxrwxrwx 1 seh None      28 2005-03-24 22:09 /usr/bin/unison.exe -
 |                                                /etc/alternatives/unison.exe
 |

What is the output of

ls -l /etc/alternatives/unison*

Can you run /etc/alternatives/unison.exe ?

You can try reinstalling unison; maybe one of the components of the
symlink chain got lost

-- 
Life is complex, with real and imaginary parts

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Can't use key authentication on x64 Server 2003 R2

2009-12-30 Thread Csaba Raduly
On Wed, Dec 30, 2009 at 4:56 AM, Gordon Messmer  wrote:
 Since upgrading to Cygwin 1.7, I'm no longer able to use key authentication
 on one of several Windows systems.  All of the working systems are 32 bit
 installs, the one which isn't working is 64 bit.
.
 When the client connects, I get this error:

   # ssh -i id_rsa gor...@exch64.xxx.local
   Last login: Tue Dec 29 13:17:34 2009 from backup.xxx.local
          1 [main] -bash 6832 C:\cygwin\bin\bash.exe: *** fatal error -
   couldn't dynamically determine load address for 'WSAGetLastError'
   (handle 0x), Win32 error 126
   Connection to exch64.xxx.local closed.

If I understand this correctly, it is the ssh client which quits
abruptly. Error 126 is The notorious error 126 (ERROR_MOD_NOT_FOUND)
when loading DLL/DSO's in Win32 (first hit when googling Win32 error
126). However, WSAGetLastError is in ws2_32.dll, which is part of
Windows. But, being a 32-bit dll in a 64-bit Windows, maybe it's in
another directory which is not on the path. Check the folder of
ws2_32.dll

Were you connecting from exch64 to exch64 ?

Hope this helps,
Csaba
-- 
Life is complex, with real and imaginary parts

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: 1.7.1: Does 'chere' work with Vista 64b? Can't tell by me.

2009-12-30 Thread Dave
Larry Hall (Cygwin) wrote:
 On 12/28/2009 06:23 PM, Lee D. Rothstein wrote:
 Larry Hall (Cygwin) wrote:
 Lee D. Rothstein wrote:
 Are you running Vista 64bit? If not, I suspect the registry keys set in
 Vista 64 are not correct as set by 'chere'.

 No, actually I'm not, so if you're sure it's a Vista 64bit thing, then
 that narrows the focus and those affected. The closest I have is
 Windows 7 x64 but I can't experiment at the moment with it since
 it requires a reboot.

 I had no problems with Vista 32 bit, that's my only evidence.
 
 OK, I've installed Cygwin 1.7.1 on a Windows 7 x64 system.  The
 system didn't have a previous version of Cygwin.  I installed just
 the default packages plus chere.  Once the installation was done,
 I invoked 'chere -i' from a command prompt started as Administrator
 and running 'bash -li'.  The configuration of chere succeeded
 and I found Bash Prompt Here was available in the context menu
 for directories.  I find the same is true on Windows 7 x86.  So I
 guess this isn't allot of help beyond the information that this does
 work on systems running Windows 7.  Perhaps someone with Vista
 x64 will be able to answer your original question.

It's been a while since I've had to look at chere. Bottom line - there
haven't been any previous reports of failures on Vista 64 bit (and I
don't have a 64-bit system available to me).

Can you provide the output of `chere -r`, and the chere command you've
run most recently. That'll allow me to diagnose what it's tried to do.

Also, do you know where the  Shell defaulting to bash defined for lr
is coming from?



Cheers,

Dave
chere maintainer.

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: [Patch] chere-1.1-1: fix uninstall from Control Panel

2009-12-30 Thread Dave
Christian Franke wrote:
 Uninstalling a chere item from Control Panel does not work if 
 C:\cygwin\bin is not in Windows default PATH.
 The attached patch fixes this.

Thanks, I'll apply this.

I'm wondering whether I should just nuke that option...



Regards,

Dave.
chere maintainer.

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple




Re: Goldstar please (Re: [ANNOUNCEMENT] Updated: xinit-1.2.0-2)

2009-12-30 Thread Andrew Schulman
 On Tue, Dec 29, 2009 at 07:31:07PM -0500, Charles Wilson wrote:
 Yaakov (Cygwin/X) wrote:
  On 29/12/2009 16:27, Charles Wilson wrote:
  Sounds like a good idea, but I wish I'd known this was coming before
  wasting time on:
 
   * Improve checkX behavior when used as 'barrier' in startxwin.
  
  Sorry about that, Chuck, but this was just the latest of a long string
  of issues involving these scripts.  We've been talking about replacing
  them for a while, and the recent traffic on the list was enough of an
  impetus to make me finally stop bandaging the scripts and find a better
  solution.  Plus, we gain argument handling and .startxwinrc, something
  the scripts would likely never do.
 
 Like I said, it sounds to me like a good idea; there's just so many
 issues that can go (and have gone) wrong in these scripts -- PLUS, whose
 idea was it to have TWO, one .sh and one .bat?!!?  Yeeesh.  We're well
 rid of them.
 
 Yes, in fact, I think this deserves a gold star.  These things have been
 a pain in the neck for years.

Awarded.  http://cygwin.com/goldstars/#YS


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: mount -a has no effect on the cygdrive prefix

2009-12-30 Thread Corinna Vinschen
On Dec 29 16:27, Karl M wrote:
 
  Date: Thu, 24 Dec 2009 12:10:47 +0100
  From: corinna-cygwin
  Subject: Re: mount -a has no effect on the cygdrive prefix
 
  On Dec 23 08:32, Karl M wrote:
  Hi All...
 
  With the last 1.7.0 version and with a clean 1.7.1 install on an XP Pro 
  SP3 machine,
  if I edit my fstab to change my cygdrive prefix and then do a mount -a, 
  my mounts
  as shown by the mount command or catting mtab are not updated. I only 
  tried it with
  the cygdrive prefix, not with other mounts.
 
  The cygdrive prefix is explicitely ignored when calling mount -a.
  The problem is, I'm not sure anymore *why* I did it that way.
  I added it to my TODO list, at least to figure out the reason...
 
 
  Thanks,
  Corinna
 
 Hi Corinna...
  
 Did you figure out the reason?

I know the reason, I just don't work on it yet.  It's on the TODO list
for the new year.

 When you look at it, could you remove the inconsistant posix=0 from mount and 
 mount -m
 output for the prefix where posix=0 is the default.

No, I don't think so.  posix=1 is the generic default, posix=0 gets
noted explicitely.  That should be kept for consistency.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: cygpath and spaces in filenames when reading from a file

2009-12-30 Thread Corinna Vinschen
On Dec 29 17:11, Jon Beniston wrote:
 Hi,
 
 cygpath can read a list of paths to convert from a file, when started with
 -file. However, how do you specify paths with spaces in them in this mode?
 It seems quoting the path or using \ doesn't seem to work. E.g:

No, it doesn't.  Space is used as the field separator in the file.  I
assume we need an extension like allowing to specify another separator.
Another one for next year...


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



/var/lib/alternatives/gcc missing for alternatives 1.3.30c

2009-12-30 Thread Neil.Mowbray
Dear Folks,

The scripts /bin/set-gcc-default-[34].sh are written to use alternatives to
install gcc-3 and gcc-4.  But /var/lib/alternatives/gcc is missing.

I tried to create it using g++ as an example but all functions failed with
an
error failed to read link /usr/bin/gcc.exe (which is the orginal problem).

I look for the source but the cygwin alternatives src tar ball doesn't
contain
the source nor can I find it on cygwin.com or with a quick google search.

So I write this message.

Can someone please provide a valid /var/lib/alternatives/gcc file or link
me to either it's syntax or the programs source?

Regards, Neil


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: cygpath and spaces in filenames when reading from a file

2009-12-30 Thread Mark J. Reed
On Wed, Dec 30, 2009 at 7:01 AM, Corinna Vinschen  wrote:
 No, it doesn't.  Space is used as the field separator in the file.  I
 assume we need an extension like allowing to specify another separator.
 Another one for next year...

As a first step, maybe just adding an xargs-style --null/-0 to treat
input as NUL-separated instead of whitespace-separated would be
worthwhile?

The options list is kinda full, single-letter-alias-wise; I see no
obvious place to put a more general '--delimiter' (-d and -D and -f
and -F and -s and -S are all taken).  Also, allowing specification of
an arbitrary delimiter would seem to open up another can of
character-encoding worms.

-- 
Mark J. Reed markjr...@gmail.com

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



RE: Bash v4.0 does not respect $PATH

2009-12-30 Thread Neil.Mowbray
Yes I'm certain.  Below is a log of the following script

#--- script

$ echo bash version = ${BASH_VERSINFO[0]}
$ for i in $(echo $PATH | sed -r -e s/:/ /g); do echo $i; done
$ which perl
$ perl --version

$ /bin/bash
$ echo bash version = ${BASH_VERSINFO[0]}
$ for i in $(echo $PATH | sed -r -e s/:/ /g); do echo $i; done
$ which perl
$ perl --version
$ exit

$ echo bash version = ${BASH_VERSINFO[0]}
$ for i in $(echo $PATH | sed -r -e s/:/ /g); do echo $i; done
$ which perl
$ perl --version

#-- output

bash version = 4

/opt/site/bin
/opt/ms-vs-10.0/VC/bin
/opt/perl/bin
/usr/local/bin
/bin
/usr/bin
/work/solon/neilmowbray/alexandra/basic/Asc/finis/bin
/opt/java/groovy-1.5.6/bin
/windows/Microsoft.NET/Framework/v3.5
/opt/ms-windows-sdk/v6.1/bin
/opt/ms-windows-dbg-tools
/opt/ms-vs-10.0/Common7/Tools
/opt/ms-vs-10.0/Common7/IDE
/opt/ms-vs-10.0/Common7/Tools/bin
/opt/java/jdk1.6.0_17/bin
/opt/java/jdk1.6.0_17/jre/bin
/opt/java/scala-2.7.6.final/bin
/opt/java/maven-2.2.1/bin
/windows/system32
/windows
/windows/System32/Wbem
.
/opt/perl/bin/perl  #-- from which ActiveSate perl

This is perl, v5.10.1 (*) built for i686-cygwin-thread-multi-64int
(with 12 registered patches, see perl -V for more detail)
Copyright 1987-2009, Larry Wall
Perl may be copied only under the terms of either the Artistic License or
the
GNU General Public License, which may be found in the Perl 5 source kit.
Complete documentation for Perl, including FAQ lists, should be found on
this system using man perl or perldoc perl.  If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.
erl.  If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.

bash version = 3

/opt/site/bin
/opt/ms-vs-10.0/VC/bin
/opt/perl/bin
/usr/local/bin
/bin
/usr/bin
/work/solon/neilmowbray/alexandra/basic/Asc/finis/bin
/opt/java/groovy-1.5.6/bin
/windows/Microsoft.NET/Framework/v3.5
/opt/ms-windows-sdk/v6.1/bin
/opt/ms-windows-dbg-tools
/opt/ms-vs-10.0/Common7/Tools
/opt/ms-vs-10.0/Common7/IDE
/opt/ms-vs-10.0/Common7/Tools/bin
/opt/java/jdk1.6.0_17/bin
/opt/java/jdk1.6.0_17/jre/bin
/opt/java/scala-2.7.6.final/bin
/opt/java/maven-2.2.1/bin
/windows/system32
/windows
/windows/System32/Wbem
.
/opt/perl/bin/perl  #-- which agains

This is perl, v5.10.1 built for MSWin32-x86-multi-thread#--
ActiveState perl this time
(with 2 registered patches, see perl -V for more detail)
Copyright 1987-2009, Larry Wall
Binary build 1006 [291086] provided by ActiveState
http://www.ActiveState.com
Built Aug 24 2009 13:48:26
Perl may be copied only under the terms of either the Artistic License or
the
GNU General Public License, which may be found in the Perl 5 source kit.
Complete documentation for Perl, including FAQ lists, should be found on
this system using man perl or perldoc perl.  If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.

bash version = 4

/opt/site/bin
/opt/ms-vs-10.0/VC/bin
/opt/perl/bin
/usr/local/bin
/bin
/usr/bin
/work/solon/neilmowbray/alexandra/basic/Asc/finis/bin
/opt/java/groovy-1.5.6/bin
/windows/Microsoft.NET/Framework/v3.5
/opt/ms-windows-sdk/v6.1/bin
/opt/ms-windows-dbg-tools
/opt/ms-vs-10.0/Common7/Tools
/opt/ms-vs-10.0/Common7/IDE
/opt/ms-vs-10.0/Common7/Tools/bin
/opt/java/jdk1.6.0_17/bin
/opt/java/jdk1.6.0_17/jre/bin
/opt/java/scala-2.7.6.final/bin
/opt/java/maven-2.2.1/bin
/windows/system32
/windows
/windows/System32/Wbem
.
/opt/perl/bin/perl

This is perl, v5.10.1 (*) built for i686-cygwin-thread-multi-64int
(with 12 registered patches, see perl -V for more detail)
Copyright 1987-2009, Larry Wall
Perl may be copied only under the terms of either the Artistic License or
the
GNU General Public License, which may be found in the Perl 5 source kit.
Complete documentation for Perl, including FAQ lists, should be found on
this system using man perl or perldoc perl.  If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.








#- end





-Original Message-
From: Csaba Raduly [mailto:rcs...@gmail.com] 
Sent: 30 December 2009 08:52
To: cygwin@cygwin.com; neil.mowb...@calgacus.com
Subject: Re: Bash v4.0 does not respect $PATH

On Tue, Dec 29, 2009 at 11:21 PM,  Neil Mowbray wrote:
 Folks,

 I need associative arrays so I got the bash 4.0 source, compiled it 
 under cygwin and installed it in /usr/local/bin.

 I have ActiveState perl installed in /opt/perl which preceeds 
 /usr/local/bin:/bin:/usr/bin on my path.  Using bash 4.0, 'which' says 
 I should get ActiveState perl, but actual execution gives cygwin perl 
 in /bin

Are you sure PATH is the same in bash 3 and 4? You only showed the PATH from
bash 4.
Just out of curiosity, what does

perl -e 'print $^X'

print in those two situations? Also, try running

for i in $(echo $PATH | sed -r -e s/:/ /g); do ls -l $i/perl; done

in both shells.



Re: Defeated by alternatives: unison

2009-12-30 Thread Steven E. Harris
Csaba Raduly rcs...@gmail.com writes:

 You can try reinstalling unison; maybe one of the components of the
 symlink chain got lost

Reinstalling solved the problem. Thanks for the suggestion.

-- 
Steven E. Harris


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Symbolic links problem with cygwin 1.7.1 in 64-bit Win7 Command Prompt

2009-12-30 Thread tuli tanssi
Hi,

I've been using gcc and other tools in older versions of cygwin with
32-bit Windows XP and Vista from windows command prompt (cmd.exe)
without problems. But now I'm using 64-bit Windows 7, and some command
line tools like gcc.exe do not work anymore (from cmd.exe). They do
work ok from Cygwin's bash.

The message I get when trying to run gcc in cmd.exe is: Access is denied.

Anyway, only some tools don't work, e.g. 'ls' works ok from cmd.exe.

I noticed that all cygwin tools that are actually symbolic links to
somehere else (just like /bin/gcc.exe and some others) are the
problematic tools.
Also /bin/gcc.exe has System rights (as seen by Attrib command of
windows), while tools that do work have only Archive rights.

So the I guess the problem is related to how symbolic links are
created and with what rights.

Anyone else tried this? Any solutions?

Cheers,
Tuli

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



RE: cygpath and spaces in filenames when reading from a file

2009-12-30 Thread Jason Pyeron
 

 -Original Message-
 From: Behalf Of Mark J. Reed
 Sent: Wednesday, December 30, 2009 8:12
 Subject: Re: cygpath and spaces in filenames when reading from a file
 
 On Wed, Dec 30, 2009 at 7:01 AM, Corinna Vinschen  wrote:
  No, it doesn't.  Space is used as the field separator in 
 the file.  I 
  assume we need an extension like allowing to specify 
 another separator.
  Another one for next year...
 
 As a first step, maybe just adding an xargs-style --null/-0 
 to treat input as NUL-separated instead of 
 whitespace-separated would be worthwhile?
 
 The options list is kinda full, single-letter-alias-wise; I 
 see no obvious place to put a more general '--delimiter' (-d 
 and -D and -f and -F and -s and -S are all taken).  Also, 
 allowing specification of an arbitrary delimiter would seem 
 to open up another can of character-encoding worms.

You could even treat the -0 in the future just like the perl record seperator
option syntax.

From man perl-opt:

-0digits 
specifies the record separator ($/) as an octal number. If there are no digits,
the null character is the separator. Other switches may precede or follow the
digits. For example, if you have a version of find which can print filenames
terminated by the null character, you can say this: 
find . -name '*.bak' -print0 | perl -n0e unlink

The special value 00 will cause Perl to slurp files in paragraph mode. The value
0777 will cause Perl to slurp files whole since there is no legal character with
that value. 




 
 --
 Mark J. Reed markjr...@gmail.com
 
 --
 Problem reports:   http://cygwin.com/problems.html
 FAQ:   http://cygwin.com/faq/
 Documentation: http://cygwin.com/docs.html
 Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
 
 


--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-   -
- Jason Pyeron  PD Inc. http://www.pdinc.us -
- Principal Consultant  10 West 24th Street #100-
- +1 (443) 269-1555 x333Baltimore, Maryland 21218   -
-   -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: gcc4[1.7] printf treats differently a string constant and a character array

2009-12-30 Thread Rodrigo Medina
Hi,
Eric Blake on Dec 2009 06:41:33 wrote:

According to Andy Koppe on 12/29/2009 6:30 AM:
 Remember, POSIX states that any use in a character context of bytes with
 the 8th-bit set is specifically undefined in the C locale (whether that
be
 C.ASCII or C.UTF-8).
 
 I very much disagree with that. C.ASCII and C.UTF-8 are different
 locales from plain C, and the whole point of the explicitly stated
 charset is to define the meaning of bytes beyond 7-bit ASCII.

Point taken: an explicit C.UTF-8 is a request of a specific charset
along with C semantics (such as no translation of output messages,
posix-mandated formatting for time and money, ...), but because the
charset is explicit, the use of 8-bit bytes is well-defined in our
implementation (and since POSIX does not specify C.UTF-8, you've already
left the realm of portability and gone into implementation-defined).

But my point remains: an explicit C is specified to be charset-agnostic,
so a portable program requesting C should not be expecting any
particular behavior of 8-bit bytes in character contexts.  Programs that
use LC_ALL=C to try to get 8-bit transparency from character contexts are
flat-out non-portable.  They get other well-defined benefits on 8-bit
bytes (such as sorting by strcmp instead of strcoll, fixed-format
messages, ...), but only insofar as those 8-bit bytes are in byte contexts
rather than character contexts.

Some comments:
1- I think that printf(string_constant) and printf(char_array) should give
the same
output in any circumstance.
2- In absence of a call to setlocale printf((string_constant) writes
according to 
the locale of the environment, but  printf(char_array)  does not, even
though  it is
 affected by the locale of the environment.
3- I think that a program that was written for locale=C should work without
modification
if the locale in the environment is any of the one-byte characters ones.
4- I think that a plain C (8-bit transparent) locale should be available,
even if it
is not the default one.

RM


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



RE: Bash v4.0 does not respect $PATH

2009-12-30 Thread Neil.Mowbray
As requested the output from perl -e print $^X;

Bash 3 = c:\opt\perl\bin\perl.exe

Bash 4 = /usr/bin/perl

As you would expect the program that is actually running.
But again Bash 4 is incorrectly getting /usr/bin/perl rather
than /opt/perl/bin/perl

-Original Message-
From: Csaba Raduly [mailto:rcs...@gmail.com] 
Sent: 30 December 2009 08:52
To: cygwin@cygwin.com; neil.mowb...@calgacus.com
Subject: Re: Bash v4.0 does not respect $PATH

On Tue, Dec 29, 2009 at 11:21 PM,  Neil Mowbray wrote:
 Folks,

 I need associative arrays so I got the bash 4.0 source, compiled it 
 under cygwin and installed it in /usr/local/bin.

 I have ActiveState perl installed in /opt/perl which preceeds 
 /usr/local/bin:/bin:/usr/bin on my path.  Using bash 4.0, 'which' says 
 I should get ActiveState perl, but actual execution gives cygwin perl 
 in /bin

Are you sure PATH is the same in bash 3 and 4? You only showed the PATH from
bash 4.
Just out of curiosity, what does

perl -e 'print $^X'

print in those two situations? Also, try running

for i in $(echo $PATH | sed -r -e s/:/ /g); do ls -l $i/perl; done

in both shells.


--
Life is complex, with real and imaginary parts


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: setup 1.7.1 hangs on 000-cygwin-post-install.sh

2009-12-30 Thread Brian Wilson
I had the same problem and have written up the detailed solution on my own 
problem thread; but will share it again here.  It looks like the issue is the 
shell is not starting (heap space error) so the installation won't complete 
it's last steps (which require running shell scripts).  Don't know why.

Basically boot in Safe Mode with Networking and run setup then select 
reinstall on all the base files.  For me this got me to the point where I 
could get basic Cygwin working again and I could get a command shell running 
(sometimes).  While this didn't eliminate the heap space error, I was able to 
manage it's impact for the time being.

You might also want to run the cygcheck -s -v -r  cygcheck.out command from 
the C:/cygwin/bin is a DOS or shell window and attach the cygcheck.out file to 
your email.  It can help with the diagnosis.

Sincerely,

Brian S. Wilson
===
Home: (678) 376-9258   Cell: (678) 232-9357 wil...@ds.net
===


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



RE: Bash v4.0 does not respect $PATH

2009-12-30 Thread Jason Pyeron
 

 -Original Message-
 From: cygwin-ow...@cygwin.com 
 [mailto:cygwin-ow...@cygwin.com] On Behalf Of 
 neil.mowb...@calgacus.com
 Sent: Wednesday, December 30, 2009 8:38
 To: 'Csaba Raduly'; cygwin@cygwin.com
 Subject: RE: Bash v4.0 does not respect $PATH
 
 As requested the output from perl -e print $^X;
 
 Bash 3 = c:\opt\perl\bin\perl.exe
 
 Bash 4 = /usr/bin/perl
 

In bash4 can I see, every thing else is a bit noisy for me.

$ set  echo  alias  echo  uname -a


 As you would expect the program that is actually running.
 But again Bash 4 is incorrectly getting /usr/bin/perl rather 
 than /opt/perl/bin/perl
 
 -Original Message-
 From: Csaba Raduly [mailto:rcs...@gmail.com]
 Sent: 30 December 2009 08:52
 To: cygwin@cygwin.com; neil.mowb...@calgacus.com
 Subject: Re: Bash v4.0 does not respect $PATH
 
 On Tue, Dec 29, 2009 at 11:21 PM,  Neil Mowbray wrote:
  Folks,
 
  I need associative arrays so I got the bash 4.0 source, compiled it 
  under cygwin and installed it in /usr/local/bin.
 
  I have ActiveState perl installed in /opt/perl which preceeds 
  /usr/local/bin:/bin:/usr/bin on my path.  Using bash 4.0, 
 'which' says 
  I should get ActiveState perl, but actual execution gives 
 cygwin perl 
  in /bin
 
 Are you sure PATH is the same in bash 3 and 4? You only 
 showed the PATH from bash 4.
 Just out of curiosity, what does
 
 perl -e 'print $^X'
 
 print in those two situations? Also, try running
 
 for i in $(echo $PATH | sed -r -e s/:/ /g); do ls -l $i/perl; done
 
 in both shells.
 

Thanks

--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-   -
- Jason Pyeron  PD Inc. http://www.pdinc.us -
- Principal Consultant  10 West 24th Street #100-
- +1 (443) 269-1555 x333Baltimore, Maryland 21218   -
-   -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



[OT] RE: Bash v4.0 does not respect $PATH

2009-12-30 Thread Jason Pyeron


Forgot to strip the email addresses, my apologies.


--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-   -
- Jason Pyeron  PD Inc. http://www.pdinc.us -
- Principal Consultant  10 West 24th Street #100-
- +1 (443) 269-1555 x333Baltimore, Maryland 21218   -
-   -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.

 


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



RE: Bash v4.0 does not respect $PATH

2009-12-30 Thread Neil.Mowbray
Sorry I missing the last question.  To answer it: yes perl really is visible
as /opt/perl/bin/perl which bash fails to execute it as the third line
below shows.  In this shell bash execute cygwin perl on line 5.

ls: cannot access /opt/site/bin/perl: No such file or directory
ls: cannot access /opt/ms-vs-10.0/VC/bin/perl: No such file or directory
-rwx--+ 1 SYSTEM SYSTEM 45137 2009-08-25 05:49 /opt/perl/bin/perl
ls: cannot access /usr/local/bin/perl: No such file or directory
-rwxr-xr-x 2 neilmowbray Administrators 34883 2009-12-20 00:20 /bin/perl
-rwxr-xr-x 2 neilmowbray Administrators 34883 2009-12-20 00:20 /usr/bin/perl
ls: cannot access
/work/solon/neilmowbray/alexandra/basic/Asc/finis/bin/perl: No such file or
directory
ls: cannot access /opt/java/groovy-1.5.6/bin/perl: No such file or directory
ls: cannot access /windows/Microsoft.NET/Framework/v3.5/perl: No such file
or directory
ls: cannot access /opt/ms-windows-sdk/v6.1/bin/perl: No such file or
directory
ls: cannot access /opt/ms-windows-dbg-tools/perl: No such file or directory
ls: cannot access /opt/ms-vs-10.0/Common7/Tools/perl: No such file or
directory
ls: cannot access /opt/ms-vs-10.0/Common7/IDE/perl: No such file or
directory
ls: cannot access /opt/ms-vs-10.0/Common7/Tools/bin/perl: No such file or
directory
ls: cannot access /opt/java/jdk1.6.0_17/bin/perl: No such file or directory
ls: cannot access /opt/java/jdk1.6.0_17/jre/bin/perl: No such file or
directory
ls: cannot access /opt/java/scala-2.7.6.final/bin/perl: No such file or
directory
ls: cannot access /opt/java/maven-2.2.1/bin/perl: No such file or directory
ls: cannot access /windows/system32/perl: No such file or directory
ls: cannot access /windows/perl: No such file or directory
ls: cannot access /windows/System32/Wbem/perl: No such file or directory
ls: cannot access ./perl: No such file or directory


-Original Message-
From: Csaba Raduly [mailto:rcs...@gmail.com] 
Sent: 30 December 2009 08:52
To: cygwin@cygwin.com; neil.mowb...@calgacus.com
Subject: Re: Bash v4.0 does not respect $PATH

On Tue, Dec 29, 2009 at 11:21 PM,  Neil Mowbray wrote:
 Folks,

 I need associative arrays so I got the bash 4.0 source, compiled it 
 under cygwin and installed it in /usr/local/bin.

 I have ActiveState perl installed in /opt/perl which preceeds 
 /usr/local/bin:/bin:/usr/bin on my path.  Using bash 4.0, 'which' says 
 I should get ActiveState perl, but actual execution gives cygwin perl 
 in /bin

Are you sure PATH is the same in bash 3 and 4? You only showed the PATH from
bash 4.
Just out of curiosity, what does

perl -e 'print $^X'

print in those two situations? Also, try running

for i in $(echo $PATH | sed -r -e s/:/ /g); do ls -l $i/perl; done

in both shells.


--
Life is complex, with real and imaginary parts


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: 1.7.1 Install freeze of Cygwin post install.sh

2009-12-30 Thread Dave Korn
Brian Wilson wrote:
 Okay here's what worked for me on my home PC. [ ... snip ... ]

  You don't mention anything about the Cisco VPN client, but according to your
cygcheck output it's still installed and (probably) running.  That's the
reason why cygcheck detects ZoneAlarm; it contains a bundled version of the
same firewall engine, and ZA in general has been known to cause problems of
this kind.  I can't guarantee it's the cause of the problem but it's a
significant possibility worth investigating.

  OTOH it could be your McAfee.  You should try disabling all the advanced
features in that - behaviour blocking, heuristics, any kind of buffer overflow
or other anti-malware protection, and see if that makes a difference.

cheers,
  DaveK

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: setup 1.7.1 hangs on 000-cygwin-post-install.sh

2009-12-30 Thread Dave Korn
Brian Wilson wrote:

 Basically boot in Safe Mode with Networking and run setup then select 
 reinstall on all the base files.  For me this got me to the point where I 
 could get basic Cygwin working again and I could get a command shell
 running (sometimes).  While this didn't eliminate the heap space error, I
 was able to manage it's impact for the time being.

  If this works, of course, it pretty much proves that there is something
installed on your system that is interfering.  (It would be possible to
extract the list of services from the registry and compare which ones are
started in safe mode against which are started normally and get a list of
suspects, although I don't know off the top of my head of any utility that
does this in a straightforward and direct fashion.)  Security software is
always the most likely culprit, and sometimes just disabling it isn't enough;
sometimes you actually have to uninstall it to stop it interfering.

 You might also want to run the cygcheck -s -v -r  cygcheck.out command
 from the C:/cygwin/bin is a DOS or shell window and attach the cygcheck.out
 file to your email.  It can help with the diagnosis.

  Yes, please do; it might provide a vital clue.

cheers,
  DaveK

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Cygwin Apache installation problem

2009-12-30 Thread mtuma

Hi,

I've downloaded last apache stable version (2.0.63) and when I tried to
install it on my cygwin is giving me this error:

$ ./configure --prefix=/usr/local/apache2
checking for chosen layout... Apache
checking for working mkdir -p... yes
checking build system type... i686-pc-cygwin
checking host system type... i686-pc-cygwin
checking target system type... i686-pc-cygwin

Configuring Apache Portable Runtime library ...

checking for APR... reconfig
configuring package in srclib/apr now
/bin/sh: /cygdrive/c/Documents: No such file or directory
configure failed for srclib/apr


I looked over the web but with no luck, can anybody help me on this?

Thanks.
-- 
View this message in context: 
http://old.nabble.com/Cygwin-Apache-installation-problem-tp26968571p26968571.html
Sent from the Cygwin list mailing list archive at Nabble.com.


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Can't use key authentication on x64 Server 2003 R2

2009-12-30 Thread Gordon Messmer

On 12/30/2009 12:56 AM, Csaba Raduly wrote:


If I understand this correctly, it is the ssh client which quits
abruptly. Error 126 is The notorious error 126 (ERROR_MOD_NOT_FOUND)
when loading DLL/DSO's in Win32 (first hit when googling Win32 error
126). However, WSAGetLastError is in ws2_32.dll, which is part of
Windows. But, being a 32-bit dll in a 64-bit Windows, maybe it's in
another directory which is not on the path. Check the folder of
ws2_32.dll

Were you connecting from exch64 to exch64 ?
   


I'd also seen one list member draw that conclusion, but for the life of 
me I can't see why.  I'm connecting from a Linux host, and the error 
appears to be printed by Cygwin's bash.exe.


bash.exe doesn't appear to be linked to that dll on either host.  I do 
notice that /cygdrive/c/WINDOWS/system32 appears before  
/cygdrive/c/WINDOWS/sysWOW64 in the PATH.  I know nothing about Windows' 
linker or loader, so I don't know if that could be a problem.  Is there 
any way to change it system-wide for Cygwin?  On the broken 64 bit host:


$ ldd /bin/bash.exe
kernel32.dll = /cygdrive/c/WINDOWS/syswow64/kernel32.dll (0x7d4c)
ntdll.dll = /cygdrive/c/WINDOWS/system32/ntdll.dll (0x7d60)
kernel32.dll = /cygdrive/c/WINDOWS/syswow64/kernel32.dll (0x7d4c)
cygwin1.dll = /usr/bin/cygwin1.dll (0x6100)
ADVAPI32.DLL = /cygdrive/c/WINDOWS/syswow64/ADVAPI32.DLL (0x7d1e)
RPCRT4.dll = /cygdrive/c/WINDOWS/syswow64/RPCRT4.dll (0x7da2)
Secur32.dll = /cygdrive/c/WINDOWS/syswow64/Secur32.dll (0x7d8d)
cygintl-8.dll = /usr/bin/cygintl-8.dll (0x6f5c)
cygiconv-2.dll = /usr/bin/cygiconv-2.dll (0x674c)
cyggcc_s-1.dll = /usr/bin/cyggcc_s-1.dll (0x67f0)
cygreadline7.dll = /usr/bin/cygreadline7.dll (0x6afc)
cygncurses-9.dll = /usr/bin/cygncurses-9.dll (0x6db8)
USER32.dll = /cygdrive/c/WINDOWS/syswow64/USER32.dll (0x7d93)
GDI32.dll = /cygdrive/c/WINDOWS/syswow64/GDI32.dll (0x7d80)
$ ls -l /cygdrive/c/WINDOWS/system32/ws2_32.dll
-rwxrwx---+ 1 Administrators SYSTEM 83456 2007-02-18 04:00 
/cygdrive/c/WINDOWS/system32/ws2_32.dll

$ ls -l /cygdrive/c/WINDOWS/syswow64/ws2_32.dll
-rwxrwx---+ 1 Administrators SYSTEM 83456 2007-02-18 04:00 
/cygdrive/c/WINDOWS/syswow64/ws2_32.dll

$ echo $PATH
/usr/local/bin:/usr/bin:/bin:/cygdrive/c/Program Files/Support 
Tools/:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/System32/Wbem:/cygdrive/c/Program 
Files/ATI Technologies/ATI Control 
Panel/:/cygdrive/c/WINDOWS/system32/WindowsPowerShell/v1.0:/cygdrive/c/Program 
Files/Microsoft/Exchange Server/bin:/cygdrive/c/Program 
Files/Microsoft/Exchange 
Server/Scripts:/cygdrive/c/WINDOWS/sysWOW64:/cygdrive/c/Program Files 
(x86)/ExchangeMapi/:/bin



On a working 32 bit host:

$ ldd /bin/bash
ntdll.dll = /cygdrive/c/WINDOWS/system32/ntdll.dll (0x7c80)
kernel32.dll = /cygdrive/c/WINDOWS/system32/kernel32.dll (0x77e4)
cygwin1.dll = /usr/bin/cygwin1.dll (0x6100)
ADVAPI32.DLL = /cygdrive/c/WINDOWS/system32/ADVAPI32.DLL (0x7d1e)
RPCRT4.dll = /cygdrive/c/WINDOWS/system32/RPCRT4.dll (0x77c5)
Secur32.dll = /cygdrive/c/WINDOWS/system32/Secur32.dll (0x76f5)
cygintl-8.dll = /usr/bin/cygintl-8.dll (0x6f5c)
cygiconv-2.dll = /usr/bin/cygiconv-2.dll (0x674c)
cyggcc_s-1.dll = /usr/bin/cyggcc_s-1.dll (0x67f0)
cygreadline7.dll = /usr/bin/cygreadline7.dll (0x6afc)
cygncurses-9.dll = /usr/bin/cygncurses-9.dll (0x6db8)
USER32.dll = /cygdrive/c/WINDOWS/system32/USER32.dll (0x7738)
GDI32.dll = /cygdrive/c/WINDOWS/system32/GDI32.dll (0x77c0)
$ ls -l /cygdrive/c/WINDOWS/system32/ws2_32.dll
-rwxrwx---+ 1 Administrators SYSTEM 83456 2007-02-17 06:03 
/cygdrive/c/WINDOWS/system32/ws2_32.dll




--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Problem with wildcard from Windows

2009-12-30 Thread Bengt Larsson
I seem to have a problem with wildcards from the Windows command line
when there are high-bit characters in a filename.

A directory contains only the two files user and användare
(användare being user in Swedish):

  C:\Documents and Settings\Bengt2\Desktop\test\tttls -l
  total 0
  -rw-r--r-- 1 Bengt2 Users 0 2009-12-30 02:23 användare
  -rw-r--r-- 1 Bengt2 Users 0 2009-12-30 02:23 user
  
  C:\Documents and Settings\Bengt2\Desktop\test\tttls u*
  user
  
  C:\Documents and Settings\Bengt2\Desktop\test\tttls a*
  ls: cannot access a*: No such file or directory
  
  C:\Documents and Settings\Bengt2\Desktop\test\tttls *
  ls: cannot access *: No such file or directory

It works in bash and dash:
  
  C:\Documents and Settings\Bengt2\Desktop\test\tttbash
  /users/Bengt2/Desktop/test/ttt: ls u*
  user
  /users/Bengt2/Desktop/test/ttt: ls a*
  användare
  /users/Bengt2/Desktop/test/ttt: ls *
  användare  user

I have LANG and CYGWIN set, but not having them set doesn't change the
outcome.


cygcheck.out
Description: Binary data
--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Problem with wildcard from Windows

2009-12-30 Thread Larry Hall (Cygwin)

On 12/30/2009 11:36 AM, Bengt Larsson wrote:

I seem to have a problem with wildcards from the Windows command line
when there are high-bit characters in a filename.

A directory contains only the two files user and användare
(användare being user in Swedish):

   C:\Documents and Settings\Bengt2\Desktop\test\tttls -l
   total 0
   -rw-r--r-- 1 Bengt2 Users 0 2009-12-30 02:23 användare
   -rw-r--r-- 1 Bengt2 Users 0 2009-12-30 02:23 user

   C:\Documents and Settings\Bengt2\Desktop\test\tttls u*
   user

   C:\Documents and Settings\Bengt2\Desktop\test\tttls a*
   ls: cannot access a*: No such file or directory

   C:\Documents and Settings\Bengt2\Desktop\test\tttls *
   ls: cannot access *: No such file or directory

It works in bash and dash:

   C:\Documents and Settings\Bengt2\Desktop\test\tttbash
   /users/Bengt2/Desktop/test/ttt: ls u*
   user
   /users/Bengt2/Desktop/test/ttt: ls a*
   användare
   /users/Bengt2/Desktop/test/ttt: ls *
   användare  user

I have LANG and CYGWIN set, but not having them set doesn't change the
outcome.


Try noglob if your shell is not Cygwin-aware.

--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 893-9889 - FAX
Holliston, MA 01746

_

A: Yes.
 Q: Are you sure?
 A: Because it reverses the logical flow of conversation.
 Q: Why is top posting annoying in email?

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Cygwin Apache installation problem

2009-12-30 Thread Warren Young

On 12/30/2009 8:23 AM, mtuma wrote:


checking for APR... reconfig
configuring package in srclib/apr now
/bin/sh: /cygdrive/c/Documents: No such file or directory
configure failed for srclib/apr


It's clearly barfing on the space in c:\Documents and Settings.  The 
question is why it thinks it needs to be looking in that part of your 
hard disk.  You can find out by looking at the config.log for APR.  Use 
keywords from the above four lines to find the appropriate section of 
the log; it won't be super-easy to find, due to the verbosity of 
autoconf logs.


Incidentally, why can't you just use the native Windows version of 
Apache?  It'll be a lot faster than a Cygwin build, and it's fully 
supported.  I imagine this is the main reason the last Cygwin package 
for Apache is still 1.3, those being the days when the native Windows 
port of Apache was still a bit weak.


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Problem with wildcard from Windows

2009-12-30 Thread Bengt Larsson
Try noglob if your shell is not Cygwin-aware.

Eh? The problem is that it doesn't glob when it should. The shell is
standard CMD.EXE, ie Windows console.

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: /var/lib/alternatives/gcc missing for alternatives 1.3.30c

2009-12-30 Thread Larry Hall (Cygwin)

On 12/30/2009 08:07 AM, neil.mowb...@calgacus.com wrote:

Can someone please provide a valid /var/lib/alternatives/gcc file or link
me to either it's syntax or the programs source?


This is created when alternatives runs for gcc.  If you're missing it, it 
suggests

to me that alternatives wasn't run.  Check '/etc/postinstall/gcc.sh* and
/etc/postinstall/gcc-g++.sh*.  If there is no done suffix, these didn't 
run,

which is why you don't have the alternatives files you're looking for.  If there
is a done suffix, these did run but apparently didn't do so successfully.  Try
running them again by hand and see what errors, if any, pop up.

--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 893-9889 - FAX
Holliston, MA 01746

_

A: Yes.
 Q: Are you sure?
 A: Because it reverses the logical flow of conversation.
 Q: Why is top posting annoying in email?

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Symbolic links problem with cygwin 1.7.1 in 64-bit Win7 Command Prompt

2009-12-30 Thread Larry Hall (Cygwin)

On 12/30/2009 08:30 AM, tuli tanssi wrote:

Hi,

I've been using gcc and other tools in older versions of cygwin with
32-bit Windows XP and Vista from windows command prompt (cmd.exe)
without problems. But now I'm using 64-bit Windows 7, and some command
line tools like gcc.exe do not work anymore (from cmd.exe). They do
work ok from Cygwin's bash.

The message I get when trying to run gcc in cmd.exe is: Access is denied.

Anyway, only some tools don't work, e.g. 'ls' works ok from cmd.exe.

I noticed that all cygwin tools that are actually symbolic links to
somehere else (just like /bin/gcc.exe and some others) are the
problematic tools.
Also /bin/gcc.exe has System rights (as seen by Attrib command of
windows), while tools that do work have only Archive rights.

So the I guess the problem is related to how symbolic links are
created and with what rights.

Anyone else tried this? Any solutions?


This is a known limitation of the symbolic links in Cygwin 1.7.  The solution
is to invoke the command directly ('gcc-3.exe' or 'gcc-4.exe' in this case) or
create your own batch file wrappers or DOS aliases to point to the proper
alternative.  Another might be to set winsymlinks in the CYGWIN environment
variable http://cygwin.com/cygwin-ug-net/using-cygwinenv.html and recreate
the symlinks you want that way.  The clear downside to this approach is that
it won't handle international characters in file names/paths properly.  As a 
result

one might guess this is not the recommended solution.  And one would be
right! ;-)

--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 893-9889 - FAX
Holliston, MA 01746

_

A: Yes.
 Q: Are you sure?
 A: Because it reverses the logical flow of conversation.
 Q: Why is top posting annoying in email?

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: High CPU consumption with git tab completion in zsh

2009-12-30 Thread Thorsten Kampe
* Steven E. Harris (Tue, 29 Dec 2009 21:21:13 -0500)
 
 I've noticed that using tab completion with git in zsh often causes zsh
 to consume 100% of my CPU for around ten minutes before the completion
 request completes. The zsh completion commands look rather old:
 
 ,
 | % ls -l /usr/share/zsh/4.3.9/functions | egrep git
 | -rwxr-x---+ 1 seh Users618 2008-11-25 19:45 VCS_INFO_detect_git
 | -rwxr-x---+ 1 seh Users   2959 2008-11-25 19:45 VCS_INFO_get_data_git
 | -rwxr-x---+ 1 seh Users 163034 2008-11-25 19:45 _git
 | -rwxr-x---+ 1 seh Users   2301 2008-11-25 19:45 _stgit
 | -rwxr-x---+ 1 seh Users144 2008-11-25 19:45 run-help-git
 `
 
 Is this the right place to report such a problem in more detail, or do I
 need to contact the git mailing list, or maybe the zsh mailing list?

In general the Zsh mailing list...

Thorsten


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Problem with wildcard from Windows

2009-12-30 Thread Thorsten Kampe
* Bengt Larsson (Wed, 30 Dec 2009 18:18:21 +0100)
 Try noglob if your shell is not Cygwin-aware.
 
 Eh? The problem is that it doesn't glob when it should. The shell is
 standard CMD.EXE, ie Windows console.

The shell (Cmd) does the globbing. Describe your problem in a Microsoft 
newsgroup.

Thorsten


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Cygwin Apache installation problem

2009-12-30 Thread Dave Korn
Warren Young wrote:
 On 12/30/2009 8:23 AM, mtuma wrote:

 checking for APR... reconfig
 configuring package in srclib/apr now
 /bin/sh: /cygdrive/c/Documents: No such file or directory
 configure failed for srclib/apr
 
 It's clearly barfing on the space in c:\Documents and Settings.  The
 question is why it thinks it needs to be looking in that part of your
 hard disk.  

  Presumably because that is where the build is taking place; OP's home dir
must be under the Docs'n'Settings user dir.  Trying the build in a subdir off
/tmp might be an instant and easy workaround.  Otherwise check the FAQ on the
location of the home dir is decided; specifying a new home dir path (under
/home, for example) without spaces in the /etc/passwd entry might be best, as
this kind of problem could happen again with other software.

cheers,
  DaveK

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Cygwin Apache installation problem

2009-12-30 Thread mtuma

Thank you for your relpy.

You were right. I've extracted the tar file onto a different directory and
it did worked like a charm. This is a COE system so I might have space
issues in the previous folder, as you said.

The reason I want to use apache for cygwin is because I need to use cygwin's
perl in some cgi pages.

Thanks again.


Warren Young wrote:
 
 On 12/30/2009 8:23 AM, mtuma wrote:

 checking for APR... reconfig
 configuring package in srclib/apr now
 /bin/sh: /cygdrive/c/Documents: No such file or directory
 configure failed for srclib/apr
 
 It's clearly barfing on the space in c:\Documents and Settings.  The 
 question is why it thinks it needs to be looking in that part of your 
 hard disk.  You can find out by looking at the config.log for APR.  Use 
 keywords from the above four lines to find the appropriate section of 
 the log; it won't be super-easy to find, due to the verbosity of 
 autoconf logs.
 
 Incidentally, why can't you just use the native Windows version of 
 Apache?  It'll be a lot faster than a Cygwin build, and it's fully 
 supported.  I imagine this is the main reason the last Cygwin package 
 for Apache is still 1.3, those being the days when the native Windows 
 port of Apache was still a bit weak.
 
 --
 Problem reports:   http://cygwin.com/problems.html
 FAQ:   http://cygwin.com/faq/
 Documentation: http://cygwin.com/docs.html
 Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
 
 
 

-- 
View this message in context: 
http://old.nabble.com/Cygwin-Apache-installation-problem-tp26968571p26970430.html
Sent from the Cygwin list mailing list archive at Nabble.com.


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Problem with wildcard from Windows

2009-12-30 Thread Dave Korn
Thorsten Kampe wrote:
 * Bengt Larsson (Wed, 30 Dec 2009 18:18:21 +0100)
 Try noglob if your shell is not Cygwin-aware.
 Eh? The problem is that it doesn't glob when it should. The shell is
 standard CMD.EXE, ie Windows console.
 
 The shell (Cmd) does the globbing. Describe your problem in a Microsoft 
 newsgroup.

  Hang on though, isn't there some code in the cygwin dll to do globbing for
just this situation, when you want to launch a cygwin executable from a
non-cygwin context?  Perhaps that code has a problem with multi-byte chars or
something; this could be a cygwin bug, couldn't it?

cheers,
  DaveK

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: /var/lib/alternatives/gcc missing for alternatives 1.3.30c

2009-12-30 Thread Dave Korn
Larry Hall (Cygwin) wrote:
 On 12/30/2009 08:07 AM, neil.mowb...@calgacus wrote:
 Can someone please provide a valid /var/lib/alternatives/gcc file or link
  me to either it's syntax or the programs source?
 
 This is created when alternatives runs for gcc.  If you're missing it, it
 suggests to me that alternatives wasn't run.  Check
 '/etc/postinstall/gcc.sh* and /etc/postinstall/gcc-g++.sh*.  If there is
 no done suffix, these didn't run, which is why you don't have the
 alternatives files you're looking for. If there is a done suffix, these
 did run but apparently didn't do so successfully.  Try running them again
 by hand and see what errors, if any, pop up.

  Also, apologies: there was a packaging hiccup in the latest version, and the
execute permissions got lost.  If you try to just run set-gcc-default-[34].sh
at the shell, you'll get a Permission denied error; you can either chmod a+x
them, or use the . name (aka bash source builtin) syntax to invoke them.

cheers,
  DaveK


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Problem with wildcard from Windows

2009-12-30 Thread Warren Young

On 12/30/2009 10:18 AM, Bengt Larsson wrote:

Try noglob if your shell is not Cygwin-aware.


Eh? The problem is that it doesn't glob when it should. The shell is
standard CMD.EXE, ie Windows console.


The behavior you're relying on is a nonstandard Cygwin extension which 
most Cygwin users, I dare say, don't even use themselves.  It's an 
emulation of a feature all POSIX shells have, internal globbing. 
cmd.exe doesn't provide globbing services to programs it runs, so Cygwin 
by default (CYGWIN=glob) tries to do this for you, but it appears 
there are weaknesses.


Another thing that doesn't work:

c:\ echo W*

This should give Windows at least.

What I'm having trouble understanding is why you've installed Cygwin but 
then insist on sticking with the primitive cmd.exe shell.  Your globbing 
problem will go away if you switch to one of the many shells in the 
Cygwin package repository.


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Problem with wildcard from Windows

2009-12-30 Thread Larry Hall (Cygwin)

On 12/30/2009 01:20 PM, Dave Korn wrote:

Thorsten Kampe wrote:

* Bengt Larsson (Wed, 30 Dec 2009 18:18:21 +0100)

Try noglob if your shell is not Cygwin-aware.

Eh? The problem is that it doesn't glob when it should. The shell is
standard CMD.EXE, ie Windows console.


The shell (Cmd) does the globbing. Describe your problem in a Microsoft
newsgroup.


   Hang on though, isn't there some code in the cygwin dll to do globbing for
just this situation, when you want to launch a cygwin executable from a
non-cygwin context?  Perhaps that code has a problem with multi-byte chars or
something; this could be a cygwin bug, couldn't it?


Yep.  That's why I made my suggestion.  If that works, then it's a work-around
and a confirmation of a bug in Cygwin.  If it doesn't, then it suggests (to me)
some issue in 'ls'.

--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 893-9889 - FAX
Holliston, MA 01746

_

A: Yes.
 Q: Are you sure?
 A: Because it reverses the logical flow of conversation.
 Q: Why is top posting annoying in email?

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: cygpath and spaces in filenames when reading from a file

2009-12-30 Thread Christopher Faylor
On Wed, Dec 30, 2009 at 01:01:29PM +0100, Corinna Vinschen wrote:
On Dec 29 17:11, Jon Beniston wrote:
 Hi,
 
 cygpath can read a list of paths to convert from a file, when started with
 -file. However, how do you specify paths with spaces in them in this mode?
 It seems quoting the path or using \ doesn't seem to work. E.g:

No, it doesn't.  Space is used as the field separator in the file.  I
assume we need an extension like allowing to specify another separator.
Another one for next year...

That's an option that I added.  I am surprised that it is space delimited since
I thought I intended to make it newline delimited.

I'll take a look at it.

cgf

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Problem with wildcard from Windows

2009-12-30 Thread Christopher Faylor
On Wed, Dec 30, 2009 at 06:20:32PM +, Dave Korn wrote:
Hang on though, isn't there some code in the cygwin dll to do globbing
for just this situation, when you want to launch a cygwin executable
from a non-cygwin context?

Yes.

cgf

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Problem with wildcard from Windows

2009-12-30 Thread Larry Hall (Cygwin)

On 12/30/2009 01:08 PM, Warren Young wrote:

Another thing that doesn't work:

 c:\ echo W*


Ah, right.  So my idea doesn't make sense.  Never mind. ;-)

--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 893-9889 - FAX
Holliston, MA 01746

_

A: Yes.
 Q: Are you sure?
 A: Because it reverses the logical flow of conversation.
 Q: Why is top posting annoying in email?

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Problem with wildcard from Windows

2009-12-30 Thread Warren Young

On 12/30/2009 11:16 AM, Larry Hall (Cygwin) wrote:

On 12/30/2009 01:08 PM, Warren Young wrote:

Another thing that doesn't work:

c:\ echo W*


Ah, right. So my idea doesn't make sense. Never mind. ;-)


I think we're looking at two bugs, though.  The original post appears to 
be about a Unicode or wide character issue.  My example shows some kind 
of weird discrimination: it works fine for ls.exe, but not echo.exe.


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Problem with wildcard from Windows

2009-12-30 Thread Bengt Larsson
 Warren Young wrote:
On 12/30/2009 10:18 AM, Bengt Larsson wrote:
 Try noglob if your shell is not Cygwin-aware.

 Eh? The problem is that it doesn't glob when it should. The shell is
 standard CMD.EXE, ie Windows console.

The behavior you're relying on is a nonstandard Cygwin extension which 
most Cygwin users, I dare say, don't even use themselves.  It's an 
emulation of a feature all POSIX shells have, internal globbing. 
cmd.exe doesn't provide globbing services to programs it runs, so Cygwin 
by default (CYGWIN=glob) tries to do this for you, but it appears 
there are weaknesses.

Another thing that doesn't work:

   c:\ echo W*

This should give Windows at least.

What I'm having trouble understanding is why you've installed Cygwin but 
then insist on sticking with the primitive cmd.exe shell.  Your globbing 
problem will go away if you switch to one of the many shells in the 
Cygwin package repository.

Every port of Unix utilities to Windows such as ls, grep and so forth do
this globbing internally. It's not only Cygwin that does it. The reason
is, it can be useful to use Unix command line utilities from the Windows
command line. ls, for example, has a handy way of seeing the whole
precision of a file timestamp. grep is a better grepper.

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Problem with wildcard from Windows

2009-12-30 Thread Christopher Faylor
On Wed, Dec 30, 2009 at 05:36:05PM +0100, Bengt Larsson wrote:
I seem to have a problem with wildcards from the Windows command line
when there are high-bit characters in a filename.

A directory contains only the two files user and anv?ndare
(anv?ndare being user in Swedish):

  C:\Documents and Settings\Bengt2\Desktop\test\tttls -l
  total 0
  -rw-r--r-- 1 Bengt2 Users 0 2009-12-30 02:23 anv?ndare
  -rw-r--r-- 1 Bengt2 Users 0 2009-12-30 02:23 user
  
  C:\Documents and Settings\Bengt2\Desktop\test\tttls u*
  user
  
  C:\Documents and Settings\Bengt2\Desktop\test\tttls a*
  ls: cannot access a*: No such file or directory

I get a different (and slightly more understandable) error
(not sure how this will translate to my email client from vnc):

c:\tmp ls a*
ls: cannot access anvA?ndare: No such file or directory
autoruns.chm  autoruns.exe  autorunsc.exe

I'm not really familiar with all of the changes that Corinna made
for this but I'll take a look to see if this is easy to fix.

cgf

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Problem with wildcard from Windows

2009-12-30 Thread Bengt Larsson
Warren Young wrote:
On 12/30/2009 11:16 AM, Larry Hall (Cygwin) wrote:
 On 12/30/2009 01:08 PM, Warren Young wrote:
 Another thing that doesn't work:

 c:\ echo W*

 Ah, right. So my idea doesn't make sense. Never mind. ;-)

I think we're looking at two bugs, though.  The original post appears to 
be about a Unicode or wide character issue.  My example shows some kind 
of weird discrimination: it works fine for ls.exe, but not echo.exe.

It doesn't work for echo because echo is a builtin in the Windows
shell.

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Problem with wildcard from Windows

2009-12-30 Thread Warren Young

On 12/30/2009 11:33 AM, Bengt Larsson wrote:


It doesn't work for echo because echo is a builtin in the Windows
shell.


Okay, imatwit, of course it is.  One bug, then. :)

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Problem with wildcard from Windows

2009-12-30 Thread Dave Korn
Bengt Larsson wrote:

 Every port of Unix utilities to Windows such as ls, grep and so forth do
 this globbing internally.

  No.  Not every port.  Specifically, not Cygwin ones: they get it done for
them, by the shell that launches them, or in fallback cases by the Cygwin DLL.

  They don't have any code in them to do globbing internally on Unix and they
still don't have any code in them to do globbing internally when compiled for
Cygwin.  They may have /optional/ globbing code to support MinGW or VC builds,
stuff like GnuWin32 will use that, but it won't be compiled or invoked under
Cygwin.

cheers,
  DaveK

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: cygpath and spaces in filenames when reading from a file

2009-12-30 Thread Mark J. Reed
On Wed, Dec 30, 2009 at 1:18 PM, Christopher Faylor wrote:
 That's an option that I added.  I am surprised that it is space delimited 
 since
 I thought I intended to make it newline delimited.

It looks pretty intentional - it reads through the input line by line
using fgets, but then calls argz_create_sep() to split each line on
spaces.

-- 
Mark J. Reed markjr...@gmail.com

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Problem with wildcard from Windows

2009-12-30 Thread Bengt Larsson
Dave Korn wrote:
Bengt Larsson wrote:

 Every port of Unix utilities to Windows such as ls, grep and so forth do
 this globbing internally.

  No.  Not every port.  Specifically, not Cygwin ones: they get it done for
them, by the shell that launches them, or in fallback cases by the Cygwin DLL.

It depends on what you mean by internally. I didn't mean it's in the
source code for ls(1) etc. I mean it from a users viewpoint, ie it isn't
already done by the shell for the application when it starts up. 

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Problem with wildcard from Windows

2009-12-30 Thread Bengt Larsson
Christopher Faylor wrote:
On Wed, Dec 30, 2009 at 05:36:05PM +0100, Bengt Larsson wrote:
I seem to have a problem with wildcards from the Windows command line
when there are high-bit characters in a filename.

A directory contains only the two files user and anv?ndare
(anv?ndare being user in Swedish):

  C:\Documents and Settings\Bengt2\Desktop\test\tttls -l
  total 0
  -rw-r--r-- 1 Bengt2 Users 0 2009-12-30 02:23 anv?ndare
  -rw-r--r-- 1 Bengt2 Users 0 2009-12-30 02:23 user
  
  C:\Documents and Settings\Bengt2\Desktop\test\tttls u*
  user
  
  C:\Documents and Settings\Bengt2\Desktop\test\tttls a*
  ls: cannot access a*: No such file or directory

I get a different (and slightly more understandable) error
(not sure how this will translate to my email client from vnc):

c:\tmp ls a*
ls: cannot access anvA¤ndare: No such file or directory
autoruns.chm  autoruns.exe  autorunsc.exe

You mail is a bit garbled, the ? in användare should be U+00E4 LATIN
SMALL LETTER A WITH DIAERESIS. But probably any non-7-bit letter will
do.

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Problem with wildcard from Windows

2009-12-30 Thread Christopher Faylor
On Wed, Dec 30, 2009 at 08:17:21PM +0100, Bengt Larsson wrote:
Dave Korn wrote:
Bengt Larsson wrote:

 Every port of Unix utilities to Windows such as ls, grep and so forth do
 this globbing internally.

  No.  Not every port.  Specifically, not Cygwin ones: they get it done for
them, by the shell that launches them, or in fallback cases by the Cygwin DLL.

It depends on what you mean by internally. I didn't mean it's in the
source code for ls(1) etc. I mean it from a users viewpoint, ie it isn't
already done by the shell for the application when it starts up. 

Why is this particular point pertinent to the cygwin mailing list?

There's a bug in the DLL.  It needs to be fixed.  End of story.

cgf

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: cygpath and spaces in filenames when reading from a file

2009-12-30 Thread Christopher Faylor
On Wed, Dec 30, 2009 at 01:18:50PM -0500, Christopher Faylor wrote:
On Wed, Dec 30, 2009 at 01:01:29PM +0100, Corinna Vinschen wrote:
On Dec 29 17:11, Jon Beniston wrote:
cygpath can read a list of paths to convert from a file, when started
with -file.  However, how do you specify paths with spaces in them in
this mode?  It seems quoting the path or using \ doesn't seem to work.
E.g:

No, it doesn't.  Space is used as the field separator in the file.  I
assume we need an extension like allowing to specify another separator.
Another one for next year...

That's an option that I added.  I am surprised that it is space
delimited since I thought I intended to make it newline delimited.

I'll take a look at it.

The option processing was changed from the time I first added it.
AFAICT, at that point it did take one file per line.  Now it breaks on
spaces.

Since Corinna made the change from line to whitespace, I'll defer
on changing this.

cgf

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: C compiler is broken under 1.7.1-1

2009-12-30 Thread Paul McFerrin
Now that's been cleared up, I've reinstalled the default package and the 
C compiler now works.  Should have noticed the ps.exe missing  is a 
clue.  I'm off to getting PHP installed now.


Dave Korn wrote:

Paul McFerrin wrote:
  

Dave Korn wrote:


File crt0.o is missing.  Is it supposed to be?


Nope. It's part of the main cygwin package itself; try reinstalling that 
if it is indeed missing.
  
  
Yes, file crt0.o is missing. What specific package should I reinstall. 



  

Dave Korn wrote:



  

[ ... ] the main cygwin package itself [ ... ]
  


i.e. the cygwin-1.7.1-1 package, which contains the DLL itself along with
supporting headers and libs and utilities.

  

B Default?? ase Devel??



  Those are entire categories, not packages.

cheers,
  DaveK




  


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Problem with wildcard from Windows

2009-12-30 Thread Christopher Faylor
On Wed, Dec 30, 2009 at 01:30:19PM -0500, Christopher Faylor wrote:
On Wed, Dec 30, 2009 at 05:36:05PM +0100, Bengt Larsson wrote:
I seem to have a problem with wildcards from the Windows command line
when there are high-bit characters in a filename.

A directory contains only the two files user and anv?ndare
(anv?ndare being user in Swedish):

  C:\Documents and Settings\Bengt2\Desktop\test\tttls -l
  total 0
  -rw-r--r-- 1 Bengt2 Users 0 2009-12-30 02:23 anv?ndare
  -rw-r--r-- 1 Bengt2 Users 0 2009-12-30 02:23 user
  
  C:\Documents and Settings\Bengt2\Desktop\test\tttls u*
  user
  
  C:\Documents and Settings\Bengt2\Desktop\test\tttls a*
  ls: cannot access a*: No such file or directory

I get a different (and slightly more understandable) error
(not sure how this will translate to my email client from vnc):

c:\tmp ls a*
ls: cannot access anvA?ndare: No such file or directory
autoruns.chm  autoruns.exe  autorunsc.exe

I'm not really familiar with all of the changes that Corinna made
for this but I'll take a look to see if this is easy to fix.

It looks like things should work better if you set LANG appropriately.
For instance, this works for me:

c:\set LANG=en_US.UTF-8
c:\ls a*

What's happening is that cygwin's readdir is converting the on-disk
filename to utf-8 but cygwin's open/stat apparently aren't converting it
back.  As I said, I don't know enough about the labyrinthian multi-byte
character set code that is now in cygwin but I really can't see how this
could be anything other than a bug.  If readdir() returns a filename
then open should be able to open it.

cgf

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: 1.7.1: Mintty/bash window start: -bash: regtool: command not found

2009-12-30 Thread Dave Trollope

Hi,

I too have seen this behaviour on both my work and home systems. Whats 
interesting is I ran cygcheck -c on each when exhibiting this problem 
and it said OK for the cygwin package.


Is there a check that needs to be added to cygcheck which reports this 
as a problem? Or perhaps this is not the type of problem cygcheck is 
designed to detect?


Cheers
Dave

On 12/28/2009 12:07 PM, Warren Young wrote:

On 12/23/2009 3:15 AM, Andy Koppe wrote:


I can reproduce this as follows:

- Leave a Cygwin session open.
- Run setup.exe
- Select reinstall for cygwin-1.7.1-1.
- Click next
- in-use files detected appears
- Click retry.


I saw the same symptom, but by a slightly different path.

On updating from 1.7.0.68 to 1.7.1 this morning, I ran into the 
files-in-use case because sometime last week, Xwin.exe died horribly 
and left a UI-less process running in the background.  When setup.exe 
complained, I investigated with Task Manager, found Xwin.exe still 
hanging around, killed it, and told setup.exe to move along.  It 
completed without complaint, but I still didn't end up with a regtool.


I didn't check for ps or mount, just retried setup with a forced 
Cygwin package reinstall, and that worked.


Point being, it isn't necessary to lie to setup.exe, telling it it's 
okay to try again.  It *was* okay in my case, and it still did the 
wrong thing.



It can be fixed by reinstalling the cygwin package again, this time
without any Cygwin processes running.


Confirmed.

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



--
 David Trollope
  dtroll...@29west.com
   (630) 836-2990x309
 AIM:dstrollope
  29West, Inc.


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



cygport: latest diffutils issues warning

2009-12-30 Thread Charles Wilson
The -u0 syntax has been deprecated, and now causes this message:

 Checking packages for missing or duplicate files
diff: `-0' option is obsolete; use `-U 0'
diff: Try `diff --help' for more information.
diff: `-0' option is obsolete; use `-U 0'
diff: Try `diff --help' for more information.


Fixed as below.

--
Chuck
Index: lib/pkg_pkg.cygpart
===
--- lib/pkg_pkg.cygpart	(revision 8418)
+++ lib/pkg_pkg.cygpart	(working copy)
@@ -112,10 +112,10 @@
 
 	find * -type f -o -type l | sort  ${tmp2}
 
-	if ! diff -u0 ${tmp2} ${tmp1}  /dev/null
+	if ! diff -U 0 ${tmp2} ${tmp1}  /dev/null
 	then
 		# detect duplicates and/or missing files
-		diff -u0 ${tmp2} ${tmp1} | grep -E -v '^@'  ${T}/pkgcheck.diff
+		diff -U 0 ${tmp2} ${tmp1} | grep -E -v '^@'  ${T}/pkgcheck.diff
 
 		if grep -E '^-[^\-]' ${T}/pkgcheck.diff  /dev/null
 		then

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: cygport: latest diffutils issues warning

2009-12-30 Thread Yaakov (Cygwin/X)

On 30/12/2009 20:04, Charles Wilson wrote:

The -u0 syntax has been deprecated, and now causes this message:


Checking packages for missing or duplicate files

diff: `-0' option is obsolete; use `-U 0'
diff: Try `diff --help' for more information.
diff: `-0' option is obsolete; use `-U 0'
diff: Try `diff --help' for more information.


Strange, cgf wrote in the announcement:


This is just a refresh of the diffutils package using more
modern versions of cygwin, gcc, and dependent libraries.  There is no new
functionality.


Apparently it's not quite so simple.


Fixed as below.


Thanks for the patch; committed to trunk, r8419.


Yaakov

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple