[1.7] does LD_PRELOAD support more than 1 dll ?

2009-05-29 Thread Marco Atzeri
Hi All, I was trying to understand why LD_PRELOAD does not work for octave, that have 3 dlls specified on LD_PRELOAD and I discovered that it seems to handle only 1 dll and not more. If I specify 2 or more dlls, LD_PRELOAD stop to work $uname -a CYGWIN_NT-5.1 ITQMOZCAS2NB007 1.7.0(0.210/5/3) 20

Re: [1.7] does LD_PRELOAD support more than 1 dll ?

2009-05-29 Thread Julio Costa
On Fri, May 29, 2009 at 09:10, Marco Atzeri wrote: > > the outcome is: >  $ LD_PRELOAD="/tmp/prova/cygjpeg-62.dll /tmp/prova/cygpng12.dll" sudoku >      3 [main] bash 12924 C:\cygwin2\bin\bash.exe: *** fatal error - error > while loading shared libraries: /tmp/prova/cygjpeg-62.dll > /tmp/prova/c

R: [1.7] does LD_PRELOAD support more than 1 dll ?

2009-05-29 Thread Marco Atzeri
--- Ven 29/5/09, Marco Atzeri ha scritto: > Da: Marco Atzeri > Oggetto: [1.7] does LD_PRELOAD support more than 1 dll ? > A: cygwin@cygwin.com > Data: Venerdì 29 maggio 2009, 10:10 > > Hi All, > I was trying to understand why LD_PRELOAD does not work > for octave, that have 3 dlls specified on

Re: emacs -nw keypad, tpu-edt.el, and C-h

2009-05-29 Thread Eli Zaretskii
> Date: Thu, 28 May 2009 18:10:51 +0100 > From: Andy Koppe > > rxvt: invoke with -backspacekey DEC > xterm: invoke with -xrm "*backarrowKey:false" (or untick "Backarrow > Key" in the "Main Options" menu) > mintty: Choose ^? as backspace keycode on the "Keys" page of the options > > As far as I k

Re: limited connection numbers to X?

2009-05-29 Thread jean-luc malet
On Thu, May 28, 2009 at 7:14 PM, Larry Hall (Cygwin) wrote: > jean-luc malet wrote: >> >> Hi, >> after opening about 15 to 20 connection to X, all further connection >> will end with an error "can't connect to X server" >> since I have lot of vim and xterm opened I must close some to open new >> o

Re: emacs -nw keypad, tpu-edt.el, and C-h

2009-05-29 Thread Eli Zaretskii
> Date: Thu, 28 May 2009 15:02:35 +0100 > From: Andy Koppe > > Ken Brown: > > A separate issue that has arisen in this thread is that when emacs runs > > in a cygwin terminal [*], it sees C-h as DEL instead of as the help key. > > Can someone familiar with cygwin terminals help with this?  I'm sp

Re: emacs -nw keypad, tpu-edt.el, and C-h

2009-05-29 Thread Ken Brown
On 5/29/2009 6:35 AM, Eli Zaretskii wrote: Date: Thu, 28 May 2009 15:02:35 +0100 From: Andy Koppe There's an ancient and pointless argument about whether the Backspace key should send ^H (0x08) or ^? (0x7F). Actually, this holy war can be bypassed, without sacrificing Emacs correctly working o

Re: emacs -nw keypad, tpu-edt.el, and C-h

2009-05-29 Thread Andy Koppe
>> Actually, this holy war can be bypassed, without sacrificing Emacs >> correctly working on a console.  What the console should send for that >> is the function key. > > Makes sense to me.  Andy, is there any reason all cygwin terminals shouldn't > do this (including mintty)?  This already happe

Re: Upgrade to cygwin 1.7 seemed to trash bash profile, path

2009-05-29 Thread Ken Brown
On 5/28/2009 7:03 PM, Christopher Faylor wrote: I'm not really following this discussion closely but there should not, by default, be any entries for /usr/lib or /usr/bin in your /etc/fstab file. I've actually come across one situation where things don't work right if those lines are missing.

Re: 1.7.0-48: [BUG] Passing characters above 128 from bash command line

2009-05-29 Thread IWAMURO Motonori
Hi. The encoding of C locale is ASCII, and not ISO-8859-1. I don't think ASCII is the same as ISO-8859-1. Does it work on LANG=en_US.ISO-8859-1? 2009/5/29 Edward Lam : > Alexey Borzenkov wrote: >> >> On Thu, May 28, 2009 at 7:28 PM, Edward Lam wrote: >>> >>> PS. In case you haven't noticed, copy

Re: Upgrade to cygwin 1.7 seemed to trash bash profile, path

2009-05-29 Thread Larry Hall (Cygwin)
Aaron Humphrey wrote: So, in the end, reinstalling didn't do much. And I got a bunch of "Cannot open (null) for reading" (error not guaranteed to be accurate), usually when it was trying to install gzipped man pages or something. (Times like these I wonder why I persist in downloading every cyg

RE: Upgrade to cygwin 1.7 seemed to trash bash profile, path

2009-05-29 Thread Karl M
> Date: Fri, 29 May 2009 10:56:03 -0400 > From: kbrown > Subject: Re: Upgrade to cygwin 1.7 seemed to trash bash profile, path > > On 5/28/2009 7:03 PM, Christopher Faylor wrote: >> I'm not really following this discussion closely but there should not, >> by default, be any entries for /usr/lib or

Re: R: [1.7] does LD_PRELOAD support more than 1 dll ?

2009-05-29 Thread Christopher Faylor
On Fri, May 29, 2009 at 09:34:36AM +, Marco Atzeri wrote: >It seems that cygwin does not accept the space as separator in >LD_PRELOAD as other systems And lets just all take a moment of silence for a second to see if we can discern why that might be. cgf -- Unsubscribe info: http://cygw

Re: 1.7.0-48: [BUG] Passing characters above 128 from bash command line

2009-05-29 Thread Edward Lam
IWAMURO Motonori wrote: The encoding of C locale is ASCII, and not ISO-8859-1. I don't think ASCII is the same as ISO-8859-1. Does it work on LANG=en_US.ISO-8859-1? No, it doesn't. Mind you though, I haven't managed to get piconv to recognize any of my LANG settings other than C in cygwin 1.7.

Re: R: [1.7] does LD_PRELOAD support more than 1 dll ?

2009-05-29 Thread Dave Korn
Christopher Faylor wrote: > On Fri, May 29, 2009 at 09:34:36AM +, Marco Atzeri wrote: >> It seems that cygwin does not accept the space as separator in >> LD_PRELOAD as other systems > > And lets just all take a moment of silence for a second to see if we can > discern why that might be. Th

Re: 1.7.0-48: [BUG] Passing characters above 128 from bash command line

2009-05-29 Thread IWAMURO Motonori
I think that you should set "export LANG=en_US.ISO-8859-1" instead of "export LANG=LANG=en_US.ISO-8859-1". 2009/5/30 Edward Lam : > IWAMURO Motonori wrote: >> >> The encoding of C locale is ASCII, and not ISO-8859-1. >> I don't think ASCII is the same as ISO-8859-1. >> Does it work on LANG=en_US.I

Re: R: [1.7] does LD_PRELOAD support more than 1 dll ?

2009-05-29 Thread Christopher Faylor
On Fri, May 29, 2009 at 05:02:01PM +0100, Dave Korn wrote: >Christopher Faylor wrote: >>On Fri, May 29, 2009 at 09:34:36AM +, Marco Atzeri wrote: >>>It seems that cygwin does not accept the space as separator in >>>LD_PRELOAD as other systems >> >>And lets just all take a moment of silence for

Re: 1.7.0-48: [BUG] Passing characters above 128 from bash command line

2009-05-29 Thread Edward Lam
IWAMURO Motonori wrote: I think that you should set "export LANG=en_US.ISO-8859-1" instead of "export LANG=LANG=en_US.ISO-8859-1". Ah, sorry, copy/paste error. Yes, that finally works. Thank you! I think there is still a bug here? I set LANG=C, then shouldn't be just NOT doing any encoding, t

Re: Long file names not working in cygwin-1.7.0-48

2009-05-29 Thread jpa
"Christopher Faylor" wrote in message news:20090528051242.ga13...@ednor.casa.cgf.cx... > On Wed, May 27, 2009 at 05:11:55PM -0700, jpa wrote: >># Create long directory path fails (255 a's/255 b's >>mkdir -p >>/tmp/[SNIP long dir name]> > Thanks for the test case. This should be fixed in the nex

Re: Upgrade to cygwin 1.7 seemed to trash bash profile, path

2009-05-29 Thread Aaron Humphrey
On Fri, May 29, 2009 at 9:16 AM, Larry Hall wrote: > Aaron Humphrey wrote: >> >> So, in the end, reinstalling didn't do much.  And I got a bunch of >> "Cannot open (null) for reading" (error not guaranteed to be >> accurate), usually when it was trying to install gzipped man pages or >> something.

Re: Long file names not working in cygwin-1.7.0-48

2009-05-29 Thread Christopher Faylor
On Fri, May 29, 2009 at 09:39:23AM -0700, jpa wrote: >"Christopher Faylor" wrote: >>On Wed, May 27, 2009 at 05:11:55PM -0700, jpa wrote: >>># Create long directory path fails (255 a's/255 b's mkdir -p /tmp/[SNIP >>>long dir name]> >>Thanks for the test case. This should be fixed in the next snapsh

Re: 1.7.0-48: [BUG] Passing characters above 128 from bash command line

2009-05-29 Thread Alexey Borzenkov
On Fri, May 29, 2009 at 8:22 PM, Edward Lam wrote: > I think there is still a bug here? I set LANG=C, then shouldn't be just NOT > doing any encoding, thus work? If I do this on Linux, it works. If I use a > cygwin compiled app, it also works. On Linux, internally, system uses multibyte strings (

cygpath -a anomaly

2009-05-29 Thread Buchbinder, Barry (NIH/NIAID) [E]
With cygdrive prefix = /, from the root directory of a drive (e.g., /c = c:\ or /h = h:\), when asking for the absolute unix path with -au, cygpath doubles the / between the drive letter and the first directory of the path. /h> echo Home | cygpath -au -f - /h//Home /h> echo Home | cygpath -a

Re: Long file names not working in cygwin-1.7.0-48

2009-05-29 Thread jpa
"Christopher Faylor" wrote in message news:20090529183702.ga28...@ednor.casa.cgf.cx... > On Fri, May 29, 2009 at 09:39:23AM -0700, jpa wrote: >>"Christopher Faylor" wrote: >>>On Wed, May 27, 2009 at 05:11:55PM -0700, jpa wrote: # Create long directory path fails (255 a's/255 b's mkdir -p /tmp

Re: cygpath -a anomaly

2009-05-29 Thread Christopher Faylor
On Fri, May 29, 2009 at 03:20:28PM -0400, Buchbinder, Barry (NIH/NIAID) [E] wrote: >With cygdrive prefix = /, from the root directory of a drive (e.g., >/c = c:\ or /h = h:\), when asking for the absolute unix path with -au, >cygpath doubles the / between the drive letter and the first directory >

Re: Long file names not working in cygwin-1.7.0-48

2009-05-29 Thread Christopher Faylor
On Fri, May 29, 2009 at 12:27:57PM -0700, jpa wrote: >Thanks for testing. I can't tell what's different about my cwrsync >config so I strace'd a test mkdir with a period using a 1.7.0-48 and >snapshot cygwin dll and looked for differences. I found several >differences where a \ was at the end of

Re: 1.7.0-48: [BUG] Passing characters above 128 from bash command line

2009-05-29 Thread Edward Lam
Hi Alexey, Thanks for explaining the UTF8 changes in cygwin 1.7. However, the decision to use UTF-8 for the C locale is questionable. It seems to me that it would be much safer to use the SYSTEM DEFAULT code page (ie. the return value of the system GetACP() function) for CYGWIN instead, ensu

Re: Long file names not working in cygwin-1.7.0-48

2009-05-29 Thread jpa
"Christopher Faylor" wrote in message news:20090529194839.gc28...@ednor.casa.cgf.cx... > On Fri, May 29, 2009 at 12:27:57PM -0700, jpa wrote: >>Thanks for testing. I can't tell what's different about my cwrsync >>config so I strace'd a test mkdir with a period using a 1.7.0-48 and >>snapshot cyg

Re: Long file names not working in cygwin-1.7.0-48

2009-05-29 Thread Christopher Faylor
On Fri, May 29, 2009 at 03:48:39PM -0400, Christopher Faylor wrote: >On Fri, May 29, 2009 at 12:27:57PM -0700, jpa wrote: >>Thanks for testing. I can't tell what's different about my cwrsync >>config so I strace'd a test mkdir with a period using a 1.7.0-48 and >>snapshot cygwin dll and looked for

Re: 1.7.0-48: [BUG] Passing characters above 128 from bash command line

2009-05-29 Thread Alexey Borzenkov
On Sat, May 30, 2009 at 12:10 AM, Edward Lam wrote: > Thanks for explaining the UTF8 changes in cygwin 1.7. However, the decision > to use UTF-8 for the C locale is questionable. Not at all, because utf-8, as far as I understand, is used for communication with the system in this context, and does

Re: Long file names not working in cygwin-1.7.0-48

2009-05-29 Thread jpa
ot. > > Please let me know if that works any better. I still can't duplicate > your reported behavior however. > > cgf > Thank you so much for working through this with me as it now works with the 20090529 snapshot. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/

Re: R: [1.7] does LD_PRELOAD support more than 1 dll ?

2009-05-29 Thread Marco Atzeri
--- Ven 29/5/09, Christopher Faylor ha scritto: > Da: Christopher Faylor > Oggetto: Re: R: [1.7] does LD_PRELOAD support more than 1 dll ? > A: cygwin > Data: Venerdì 29 maggio 2009, 18:01 > On Fri, May 29, 2009 at 05:02:01PM > +0100, Dave Korn wrote: > >Christopher Faylor wrote: > >>On Fri, Ma

Re: 1.7.0-48: [BUG] Passing characters above 128 from bash command line

2009-05-29 Thread Edward Lam
Alexey Borzenkov wrote: > It might be safe for you, but not for other people. If you have a > Russian default codepage and ever need to work with chineese/japanese > filenames and cygwin uses default codepage for filesystem operations > (as in 1.5 right now), then you are really screwed. In my opi

Re: 1.7.0-48: [BUG] Passing characters above 128 from bash command line

2009-05-29 Thread Edward Lam
Alexey Borzenkov wrote: > No, the bug is not that it gets wrong number of arguments. In fact, > Windows has no concept of arguments, only C runtime does, which parses > the command line. If command line is truncated, then C runtime will > have missing arguments when it tries to parse it. Sorry,

Re: 1.7.0-48: [BUG] Passing characters above 128 from bash command line

2009-05-29 Thread Alexey Borzenkov
On Sat, May 30, 2009 at 1:04 AM, Edward Lam wrote: > Alexey Borzenkov wrote: >> It might be safe for you, but not for other people. If you have a >> Russian default codepage and ever need to work with chineese/japanese >> filenames and cygwin uses default codepage for filesystem operations >> (as

Re: 1.7.0-48: [BUG] Passing characters above 128 from bash command line

2009-05-29 Thread Alexey Borzenkov
On Sat, May 30, 2009 at 1:21 AM, Edward Lam wrote: > Here's some more investigation: [...] > So note that even when I'm seems to be an UNICODE-AWARE child process, I'm > still getting a truncated command line. In fact, call GetCommandLineW() > directly seems to give a truncated command line > as w

Re: emacs -nw keypad, tpu-edt.el, and C-h

2009-05-29 Thread Andy Koppe
>>> Actually, this holy war can be bypassed, without sacrificing Emacs >>> correctly working on a console.  What the console should send for that >>> is the function key. >> >> Makes sense to me.  Andy, is there any reason all cygwin terminals shouldn't >> do this (including mintty)?  This already

Re: R: [1.7] does LD_PRELOAD support more than 1 dll ?

2009-05-29 Thread Dave Korn
Marco Atzeri wrote: > May I suggest a small note in the documentation ? > Just to help the next one to not fall in the same problem. > :-) PTC and all that... if you want a hand with the English grammar/spelling, ask me offlist. > so it seems that the LD_PRELOAD is not working well > in case

Re: emacs -nw keypad, tpu-edt.el, and C-h

2009-05-29 Thread Ken Brown
On 5/29/2009 5:59 PM, Andy Koppe wrote: Now of course if emacs can translate low-level console I/O as it sees fit, then the Cygwin DLL could also be able to translate Backspace into ^? characters rather than ^H, in CYGWIN=tty mode anyway. So I had a look at fhandler_console.cc. It already uses Re

[ANNOUNCEMENT] [1.7] Updated: git-1.6.3.1-1, git{k,-gui,-completion,-svn}-1.6.3.1-1

2009-05-29 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new release of git, 1.6.3.1-1, has been uploaded to the cygwin 1.7 release area. This replaces 1.6.2.4-2 as current. NEWS: = This is a new upstream major release. I'm attaching the release notes; see also the package documentation in /usr/shar

Re: R: [1.7] does LD_PRELOAD support more than 1 dll ?

2009-05-29 Thread Marco Atzeri
--- Sab 30/5/09, Dave Korn ha scritto: > Da: Dave Korn > Oggetto: Re: R: [1.7] does LD_PRELOAD support more than 1 dll ? > A: cygwin@cygwin.com > Data: Sabato 30 maggio 2009, 03:07 > Marco Atzeri wrote: > > > May I suggest a small note in the documentation ? > > Just to help the next one to no

Re: R: [1.7] does LD_PRELOAD support more than 1 dll ?

2009-05-29 Thread Christopher Faylor
On Sat, May 30, 2009 at 04:55:12AM +, Marco Atzeri wrote: > >--- Sab 30/5/09, Dave Korn ha scritto: > >> Da: Dave Korn >> Oggetto: Re: R: [1.7] does LD_PRELOAD support more than 1 dll ? >> A: cygwin@cygwin.com >> Data: Sabato 30 maggio 2009, 03:07 >> Marco Atzeri wrote: >> >> > May I suggest

Re: emacs -nw keypad, tpu-edt.el, and C-h

2009-05-29 Thread Christopher Faylor
On Fri, May 29, 2009 at 10:59:21PM +0100, Andy Koppe wrote: >Now of course if emacs can translate low-level console I/O as it sees >fit, then the Cygwin DLL could also be able to translate Backspace into >^? characters rather than ^H, in CYGWIN=tty mode anyway. So I had a >look at fhandler_consol