Re: bash scripts fail with bash3.1-8

[Thomas Porschberg]

Am Tue, 3 Oct 2006 17:02:29 +0100
schrieb "Dave Korn" :

> On 03 October 2006 16:43, Turly O'Connor wrote:
> 
> 
> > By way of an example as to what broke, note that in the following
> > that  "cleartool" is not a cygwin tool (it's a Windows executable),
> > writing its CRLF-terminated output to Windows' stdout.
> > 
> > CHECKOUTS=`cleartool lsc -all -cvi -s`  # list all my checkouts
> > 
> > I used to be able to do
> > 
> > for one in $CHECKOUTS ; do echo $one Hello ; done
> > 
> > C:/Path/To/file1 Hello
> > C:/Path/To/file2 Hello
> > 
> > Now it seems that "$one" above contains the binary CR, so I get:
> > 
> > Hello h/To/file1
> > Hello h/To/file2
> > 
> > What do I need to do to get this working again?
> 
>   How about
> 
> CHECKOUTS=`cleartool lsc -all -cvi -s | d2u`  # list all my checkouts
> 
> or 
> 
> for one in $((echo $CHECKOUTS | d2u)) ; do echo $one Hello ; done
> 
> depending on how happy cleartool is on piping output to a cygwin
> program.
> 

This is exactly the problem I have with my sqlplus call.
Is there a way to solve it without introducing the d2u filter ?

What I do is:

RESULT=`sqplus -s user/[EMAIL PROTECTED] << EOF
sql-commands here
EOF

and it is easy to change it to 

RESULT=`sqplus -s user/[EMAIL PROTECTED] << EOF | d2u
sql-commands here
EOF

(is working)

For native UNIX systems the "d2u" command is unnecessary.
I could do something like
D2U="| d2u" under Cygwin
and
D2U="" under UNIX
and write
RESULT=`sqplus -s user/[EMAIL PROTECTED] << EOF | $D2U

But this still requires that I touch the scripts.
And we have a lot of such scripts, Cygwin is just one platform and I
have not access to all shell sources.

Best regards,
Thomas






-- 


--
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: Similar Bash 3.1.18 CR/LF Problem

[Ken Wagnitz]

Christopher Faylor  cygwin.com> writes:

> 
> On Mon, Oct 02, 2006 at 01:14:37PM -0700, Wilks, Dan wrote:
> >cgf wrote:
> >>I really am getting a bad feeling that, rather than FIXING THE SCRIPTS,
> >>everyone is reverting to using text mode mounts which are not what we
> >>generally recommend.
> >
...
> 
> If you want to continue to use Cygwin tools, you really should
> investigate converting the generated scripts.
...
> 
...
> People who have not been entirely clear on
> what Cygwin is supposed to be or are not willing/able to adapt might be
> left behind by this and other similar changes.
> 
> cgf
> 
> 

I am another who has been bitten by this change to the behaviour of Cygwin.
Obviously I am one who is being "left behind".
What platform is Cygwin written to run on?  How would the Unix community react
if someone ported a really nifty tool from the DOS/Windows world to Unix, but
its data or script files had to have CR/LF endings for it to work?

Ken.



--
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: shopt igncr not working

[Kazuyuki Hagiwara]

Hi Frank,
all the three methods work fine here.

some points ...

Is the bash version right?
[~/work] bash --version
GNU bash, version 3.1.17(9)-release (i686-pc-cygwin)
Copyright (C) 2005 Free Software Foundation, Inc.
[~/work]

)   - first line of the shell script
# is required In the shopt line like ...
 shopt -s igncr #

)   - $HOME/.bash_profile
.bash_profile is not automatically executed,
at the startup of script.

)   - "-O igncr" at invocation of bash
If your script calls  another bash script, 
you have to  write in main script like ..
bash another_bash_script -O igncr arg1 arg2


) -Original Message-
) From: [EMAIL PROTECTED] 
) [mailto:[EMAIL PROTECTED] On Behalf Of Frank Illenseer
) Sent: Wednesday, October 04, 2006 3:49 PM
) To: cygwin@cygwin.com
) Subject: shopt igncr not working
) 
) Hi all,
) 
) i am experiencing problems with the newly introduced shopt 
) "igncr" to solve 
) the problem with
) CRNL in shell scripts on binary mounts.
) 
) Unfortunately this is not working for me at all: I tried all 
) possible places
)   - first line of the shell script
)   - $HOME/.bash_profile
)   - "-O igncr" at invocation of bash
) but every time I got the well known errors from bash coming 
) from the \r 
) being present in the
) shell script. (I am doing this on a binary mount.)
) 
) Any comments/help is appreciated.
) 
) @Eric: Sorry for bothering again and also sorry that I bring 
) the bad news 
) for your really good solution!
) 
) 
) Best regards
) Frank
) 
-
Kazuyuki  Hagiwara


--
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: shopt igncr not working

[Frank Illenseer]

Hi Kazuyuki,

thanks for pointing this oiut, but

1) bash version is correct, i.e.
   GNU bash, version 3.1.17(9)-release (i686-pc-cygwin)
   as recommended

2) I indeed applied the comment character "#" at the end when using as the 
first line of

   the shell script

3) When trying the option of including the shopt line in my .bash_profile I 
first opened a
   bash login shell (which indeed executes the .bash_profile) and in-there 
then ran the script

   with DOS endings by calling myscript.sh

So shall I provide additional info? - Just state what you need or what I 
shall do to enable you

to debug this further...


Thanks in advance
and best regards
Frank



--
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: [ANNOUNCEMENT] Updated: bash-3.1-9

[Ken Wagnitz]

Wilks, Dan  intuit.com> writes:

> 
> Eric, as one of the complainers :) thanks.  I just wanted to check in
> and
> say that our case of executing a cr/lf script via a DOS path on a text
> mount
> is working as well as it used to.
> 
> 

I echo that sentiment.  Now I don't feel so "left behind". :)

Ken.



--
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/

extending desktop to a second monitor

[Fabrizio Salvatore]

Hi,

I run cygwin on my Windows XP laptop and I now have a second monitor 
that I use to extend my desktop. Although I can use both monitors 
without any problem with Windows, when I run cygwin I noticed the 
following: when I open a new xterm, this will always be open on my 
laptop's monitor and when I move it to the other monitor I can type 
everything without any problem on the login window, but if I launch for 
example xemacs, I can write on the xemacs window only if I put it on the 
laptop's monitor: when I move it to the extenal monitor I can see it, 
but I cannot type on it or for instance close it. I have noticed the 
same also when I launch other applications (ROOT, for example). Is this 
 because cygwin only recognizes my laptop's monitor as the Windows 
terminal ? If so, is there a way to tell cygwin to 'extend' the Windows 
terminal to the external monitor, when this is present ?


Thanks for any help !

Fab

--
#
Dr P-Fabrizio Salvatore| Department of Physics
Phone: +44 (0)1784 44 3479 | Royal Holloway College
Fax: +44 (0)1784 47 2794   | University of London
e-mail: [EMAIL PROTECTED] | Egham, Surrey, TW20 0EX
http://www.pp.rhul.ac.uk/~salvator | United Kingdom (UK)
#

--
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: Bash and CR/LF line-endings

[Christopher Faylor]

On Tue, Oct 03, 2006 at 09:24:12PM -0600, Eric Blake wrote:
>According to Gary R. Van Sickle on 10/3/2006 8:27 PM:
>>What's going to break if igncr is simply always on?
>
>Actually, that might not be a bad idea.  Those who want literal \r
>would edit cygwin.bat or ~/.bash_profile to turn the shopt off, but
>leaving the default on would certainly minimize complaints of new
>users.  Any other opinions on this matter?  I'm not going to make such
>a change without more discussion on this list, first.

I thought the whole point of this change was to make bash faster.  If
skipping \r is a simple solution why are we here at all?

cgf

--
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: Similar Bash 3.1.18 CR/LF Problem

[Christopher Faylor]

On Wed, Oct 04, 2006 at 08:04:55AM +, Ken Wagnitz wrote:
>Christopher Faylor  cygwin.com> writes:
>> On Mon, Oct 02, 2006 at 01:14:37PM -0700, Wilks, Dan wrote:
>> >cgf wrote:
>> >>I really am getting a bad feeling that, rather than FIXING THE SCRIPTS,
>> >>everyone is reverting to using text mode mounts which are not what we
>> >>generally recommend.
>>
>> If you want to continue to use Cygwin tools, you really should
>> investigate converting the generated scripts.
>> 
>>People who have not been entirely clear on what Cygwin is supposed to
>>be or are not willing/able to adapt might be left behind by this and
>>other similar changes.
>
>I am another who has been bitten by this change to the behaviour of
>Cygwin.  Obviously I am one who is being "left behind".  What platform
>is Cygwin written to run on?  How would the Unix community react if
>someone ported a really nifty tool from the DOS/Windows world to Unix,
>but its data or script files had to have CR/LF endings for it to work?

I suspect that people wouldn't use the tool or, if it was really
important, they might investigate how they could help improve it by
looking at sources and providing patches.

However, really for the above analogy to be true, you'd have to throw in
the "Unix community" not being quite clear on what the "really nifty
tool" was supposed to be doing.

The dilemma here is that I read other mailing lists besides cygwin where
people are trying to use Cygwin but are close to giving up because it is
so slow.  So, making bash faster for people who are using it correctly
is very desirable.

In any event, while I'm not particularly interested in hearing case
studies, I have a hard time believing that it is completely impossible
for you or anyone to add a d2u step to whatever is generating your
scripts.  If you did that you would actually benefit from the bash
speedups.

cgf

--
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: shopt igncr not working

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Frank Illenseer on 10/4/2006 2:24 AM:
> 
> 3) When trying the option of including the shopt line in my
> .bash_profile I first opened a
>bash login shell (which indeed executes the .bash_profile) and
> in-there then ran the script
>with DOS endings by calling myscript.sh

Does myscript.sh have a shebang (#!)?  Are you calling it without
mentioning which shell should invoke it (ie. 'myscript.sh' instead of
'bash myscript.sh')?  If so, you are starting yet another bash process
(possibly by the name /bin/sh); the new process for the script starts out
with the default shopt setting, and not the shopt setting of the parent
shell, as bash has no way to communicate that to an unrelated child
process.  On the other hand, you could use BASH_ENV to point to a file
whose contents set the shopt, so that all non-interactive scripts
automatically get the desired igncr behavior:

$ echo 'shopt -s igncr;#' > /etc/bash_env
$ export BASH_ENV=/etc/bash_env

Then you would not have to edit any scripts.

And then there is still the possibility that my next release of bash will
default igncr to enabled.  I'm still debating on that one.

- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD4DBQFFI6VS84KuGfSFAYARAgXlAJjDmc3HIsTkFI1atDukSAojVY3xAJ4k585k
28PwxN9ZdQIRCCQ9SwWJsg==
=sWsw
-END PGP SIGNATURE-

--
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: extending desktop to a second monitor

[Jonathan Arnold]

Fabrizio Salvatore wrote:

Hi,

I run cygwin on my Windows XP laptop and I now have a second monitor 
that I use to extend my desktop. Although I can use both monitors 
without any problem with Windows, when I run cygwin I noticed the 
following: when I open a new xterm, this will always be open on my 
laptop's monitor and when I move it to the other monitor I can type 
everything without any problem on the login window, but if I launch for 
example xemacs, I can write on the xemacs window only if I put it on the 
laptop's monitor: when I move it to the extenal monitor I can see it, 
but I cannot type on it or for instance close it. I have noticed the 
same also when I launch other applications (ROOT, for example). Is this 
 because cygwin only recognizes my laptop's monitor as the Windows 
terminal ? If so, is there a way to tell cygwin to 'extend' the Windows 
terminal to the external monitor, when this is present ?


1] You must be talking about Cygwin/X, so your question might be better
of directed to that mailing list.

2] It worked just fine for me on my dual monitor set up, at least opening
up various X windows. I don't use xemacs but rather GNU emacs, so I'm not sure
what the problem might be.

3] As Cygwin/X is sort of an orphan package, you might look into the Xming 
package,
as found at http://www.straightrunning.com

--
Jonathan Arnold   http://www.buddydog.org

When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl.


--
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: extending desktop to a second monitor

[Fabrizio Salvatore]

Hi,

I've no idea if this is a Cygwin/X issue ! When I run cygwin, I use 
Windows as window terminal:


%RUN% XWin -multiwindow -clipboard -silent-dup-error +bs),

I'm not opening another window terminal on top of Windows (I mean, all 
my windows are being opened on my Windows desktop). It seems to me that 
Windows is capable of handling the multi-screen environment (I can open 
any application on Windows and it works on both monitors), but Cygwin is 
not: if I work on the login xterm that I've moved to the second monitor 
I can type and work on it without any problem, but as soon as I execute 
a program that sends a separate window to my desktop it only works if 
this window runs on my laptop's monitor.


I'll post the same question on the other forum as well, just in case.

Thanks !

Fab

Jonathan Arnold wrote:

Fabrizio Salvatore wrote:

Hi,

I run cygwin on my Windows XP laptop and I now have a second monitor 
that I use to extend my desktop. Although I can use both monitors 
without any problem with Windows, when I run cygwin I noticed the 
following: when I open a new xterm, this will always be open on my 
laptop's monitor and when I move it to the other monitor I can type 
everything without any problem on the login window, but if I launch 
for example xemacs, I can write on the xemacs window only if I put it 
on the laptop's monitor: when I move it to the extenal monitor I can 
see it, but I cannot type on it or for instance close it. I have 
noticed the same also when I launch other applications (ROOT, for 
example). Is this  because cygwin only recognizes my laptop's monitor 
as the Windows terminal ? If so, is there a way to tell cygwin to 
'extend' the Windows terminal to the external monitor, when this is 
present ?


1] You must be talking about Cygwin/X, so your question might be better
of directed to that mailing list.

2] It worked just fine for me on my dual monitor set up, at least opening
up various X windows. I don't use xemacs but rather GNU emacs, so I'm 
not sure

what the problem might be.

3] As Cygwin/X is sort of an orphan package, you might look into the 
Xming package,

as found at http://www.straightrunning.com



--
#
Dr P-Fabrizio Salvatore| Department of Physics
Phone: +44 (0)1784 44 3479 | Royal Holloway College
Fax: +44 (0)1784 47 2794   | University of London
e-mail: [EMAIL PROTECTED] | Egham, Surrey, TW20 0EX
http://www.pp.rhul.ac.uk/~salvator | United Kingdom (UK)
#

--
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: Bash and CR/LF line-endings

[Karl M]

Hi All...

My $0.02...

If you make igncr the default for bash, I would consider removing the 
special handling on the DOS paths.


Thanks for all the work you are doing to speed things up.

Damn the CRs, full speed ahead!

...Karl


From: Eric Blake Subject: Re: Bash and CR/LF line-endings
Date: Tue, 03 Oct 2006 20:13:19 -0600

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Kazuyuki Hagiwara on 10/3/2006 6:23 PM:
> How about  using BASH_ENV variable.
> In the startup script defined by BASH_ENV variable,
> you can put a line "shopt -s igncr".

BASH_ENV already has a defined meaning that conflicts with your
suggestion; read 'man bash' once more.

But bash does have the -O and +O command line option for choosing prior to
script execution what any shopt setting should be.  In other words,

bash -O igncr script_with_cr_lf

will guarantee execution of the script with \r ignored (at least, up until
the script does something to change that shopt).

- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFIxi/84KuGfSFAYARAgzlAKC+h9w9x6Fo1AfzRcZVAeiMpJgLXwCfQ8y6
H5QDRq7V43q7R2MH2qRKENQ=
=EojF
-END PGP SIGNATURE-

--
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/





--
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: extending desktop to a second monitor

[Jonathan Arnold]

Fabrizio Salvatore wrote:

Hi,

I've no idea if this is a Cygwin/X issue ! When I run cygwin, I use 
Windows as window terminal:


%RUN% XWin -multiwindow -clipboard -silent-dup-error +bs),


You need to add the -multiplemonitors flag to the command line. See the
batch file for more info.

--
Jonathan Arnold   http://www.buddydog.org

When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl.


--
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: extending desktop to a second monitor

[Fabrizio Salvatore]

Ah, that's an interesting suggestion, then ! Thank you very much ! By 
adding this flag, I assume cygwin will not complain when I'm using my 
laptop without the additional monitor, will it ?


Thanks again !

> See the batch file for more info.

Where is this file ?

Cheers,

Fab


Jonathan Arnold wrote:

Fabrizio Salvatore wrote:

Hi,

I've no idea if this is a Cygwin/X issue ! When I run cygwin, I use 
Windows as window terminal:


%RUN% XWin -multiwindow -clipboard -silent-dup-error +bs),


You need to add the -multiplemonitors flag to the command line. See the
batch file for more info.



--
#
Dr P-Fabrizio Salvatore| Department of Physics
Phone: +44 (0)1784 44 3479 | Royal Holloway College
Fax: +44 (0)1784 47 2794   | University of London
e-mail: [EMAIL PROTECTED] | Egham, Surrey, TW20 0EX
http://www.pp.rhul.ac.uk/~salvator | United Kingdom (UK)
#

--
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: Un-attended install ALL

[Larry Hall (Cygwin)]

Vinod Gupta wrote:

On 10/3/2006 10:28 PM, Igor Peshansky wrote:

On Tue, 3 Oct 2006, Vinod Gupta wrote:

 

Vinod Gupta wrote:

Vinod K Gupta wrote:

We have a local mirror of selected packages from which we
install cygwin on
user machines. When we perform un-attended installation
using setup.exe -q
-L -l -R... the installer installs only the Base packages.
How can we tell
setup to install ALL available packages?

Lary Hall wrote:
There are many ways but the easiest is to create a 
setup.hint file

with an empty package that's part of the Base category. Then
list all the
packages you want to install as its dependencies. Obviously,
you can leave
out other base packages. Voila! :-)


Thanks Lary,

I am not sure what you mean by "empty package" and how do you make
it known to the installer?
If I create a setup.hint and copy it to, say, release\base-files\,
will that work?
This sounds like fooling the installer. I can't believe that there
is nothing like "--InstallAll" option to the setup.exe installer.


Lary Hall wrote:
Fooling the installer into believing there is another package to 
install?

Yes, that should be outlawed. ;-)

Whatever you want to call it, this is the way to do it. See:



if you haven't already.
  

I tried but failed :(
I create allpackage as per instructions, here are contents:

# cd 
# ls -l release/allpackage/
total 1.0K
-rwxr-xr-x  1 vinod   0 2006-10-03 15:39 allpackage-0.0.1-1-src.tar.bz2
-rwxr-xr-x  1 vinod   0 2006-10-03 15:39 allpackage-0.0.1-1.tar.bz2


  ^^^
This is one thing that's wrong.  You should create an empty tarball and
then bzip2 it.  The size should be 46 bytes.

 

-rwxr-xr-x  1 vinod 650 2006-10-03 15:45 setup.hint

# cat release/allpackage/setup.hint
@ allpackage
sdesc: "Dummy package to include all my non-Base packages"
ldesc: "Dummy package to include all my non-Base packages"
category: Base
requires: X11 _update-info-dir alternatives ash base-files 
base-passwd bash
binutils bzip2 cabextract coreutils crypt cygrunsrv cygutils cygwin 
cygwin-doc
d db diffutils editrights expat file findutils gawk gcc gcc-mingw gdb 
gdbm
gettext grep groff gzip jpeg less libiconv libpng login make man 
mingw-runtime

minires mktemp ncurses openssh openssl pcre perl pine ping pkg-config
pkgconfig popt readline run sed sharutils tar tcltk tcsh termcap 
terminfo

texinfo time tnef unzip w32api wget which zip zlib

# bunzip setup.bz2
# cat setup

# This file is automatically generated.  If you edit it, your
# edits will be discarded next time the file is generated.
# See http://cygwin.com/setup.html for details.
#



This is another.  You should use the genini script to generate setup.ini
(and/or setup.bz2, but setup.ini should suffice).

 

Installer still installs only the Base packages.
I thought genini did not generate good setup. I copied 
release/allpackage to

/release/ and added contents of above setup.hint to
/release/setup.ini

Installer still installs only the Base packages :(

What I am doing wrong?



You need more information in setup.ini than what's in your setup.hint.
Try browsing any of the mirrors for their setup.ini and use that as a
template.
Igor
  


OK, I think I found the problem and a work around, if not the solution.

The following line must be added to setup.ini even if the allpackage is 
empty:

install: release/allpackage/allpackage-0.0.1-1.tar.bz2

The installer is looking at only /release/, and NOT 
mymirror/release/. If I add allpackage folder to /release/ and add 
contents of setup.hint to /setup.ini (including install: line) 
then it works. But this is not a good solution because /setup.ini 
will be overwritten next time I update cygwin.


The local packages folder has two mirrors - the main (http%3a%2f.../) 
and mymirror/ (which has only this empty allpackage). How do I tell 
setup.exe to look inside BOTH mirrors?



Type in the name of your mirror site when you are asked for the mirrors
you wish to use.


All this pain, just because some one did not include "--InstallAll" 
option to setup.exe??



As the saying goes, .  Of course, you
can always look to see if any of your issues with 'setup.exe' are addressed
by a snapshot .


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

--
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: extending desktop to a second monitor

[Larry Hall (Cygwin)]

On 10/04/2006, Fabrizio Salvatore wrote:
I've no idea if this is a Cygwin/X issue ! When I run cygwin, I use Windows 
as window terminal:


%RUN% XWin -multiwindow -clipboard -silent-dup-error +bs), 


XWin is the Cygwin X server.  Therefore, by definition, this is a Cygwin/X
issue for which there is a separate list.  Please use the cygwin-xfree list
for these kinds of issues/reports.

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

--
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: Re: Does 'ar' work with native MS Windows libs?

[Williams, Gerald S \(Jerry\)]

Coatimundi wrote:
> Thank you for bringing this up.  I forgot to mention (a sure
> sign that my multitasking scaling is rolling over) that I also
> tried the P option.
>   While this usually works, I found cases where it did not.
[...]
> Since I see nothing wrong with the source and I am short on
> time, I am going to chalk this up to an unidentified mistake
> on my part, unless I see it again and have time to build
> bintools myself and step through the code in debug.

You've probably already ruled this out, but if you do see it
again, you might want to verify that you're not mixing path
separators (LIB.EXE will use either). I believe you must use
only backslash-style separators if you want to interoperate
with ar.

gsw

--
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/

[ANNOUNCEMENT] Updated [experimental]: readline-5.2-1, libreadline6-5.2-1

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

A new release of readline and libreadline6, 5.2-1, is available for
experimental use.  5.1-5 remains the current version.

NEWS:
=
This is an upstream release candidate, and hence experimental.  It is
possible that there are still bugs that will be fixed between this beta
and the final upstream release of 5.2.  Additionally, this version is not
strictly binary compatible with readline 5.1; it removes a cygwin-specific
entry point that bash 3.0 (but not bash 3.1) depended on.  Now that bash
3.0 is no longer available from the cygwin mirrors, I felt it safe to drop
that cygwin-specific patch.  Although it is unlikely that any other
package depended on this entry point, I need to know now if this decision
was not wise, in which case I will create libreadline7 when promoting
readline 5.2 to current, leaving libreadline6 to preserve the entry point;
but I will only do this if someone can demonstrate why it is needed (hint,
you would have to mention the entry point by name to show you know what
you are talking about).

The upstream maintainer claims that this version fixes some prompt display
bugs when using non-printing escape sequences with a single-line prompt.
I have not verified this, but hope that this is the case.

DESCRIPTION:

The readline library will read a line from the terminal and return it,
allowing the user to edit the line with emacs or vi editing keys.  It also
allows a history feature, for editing previous entries, making command
line interfaces easier-to-use and more intuitive.

libreadline6 provides the .dlls needed for readline and history expansion
for dynamic linking in other programs, including bash and gdb; it is
required for a minimal cygwin installation.  The 6 in libreadline6
distinguishes incompatible API changes made to the prior libreadline4 and
libreadline5 libraries still available on the mirrors. readline provides
the documentation and the static libraries required for static linking;
you should only need it if you plan on compiling an application that links
with -lreadline or -lhistory.

UPDATE:
===
To update your installation, click on the "Install Cygwin now" link on the
http://cygwin.com/ web page.  This downloads setup.exe to your system.
Save it and run setup, answer the questions and pick up 'libreadline6'
from the 'Base' category (it should already be selected), or 'readline' in
the 'Devel' category.  Be sure that you do not have any cygwin programs
running during the upgrade.  You will need to use the 'Exp' radio button
since this release is experimental.

DOWNLOAD:
=
Note that downloads from sources.redhat.com (aka cygwin.com) aren't
allowed due to bandwidth limitations.  This means that you will need to
find a mirror which has this update, please choose the one nearest to you:
http://cygwin.com/mirrors.html

QUESTIONS:
==
If you want to make a point or ask a question the Cygwin mailing list is
the appropriate place.

- --
Eric Blake
volunteer cygwin readline maintainer

CYGWIN-ANNOUNCE UNSUBSCRIBE INFO:
=
To unsubscribe to the cygwin-announce mailing list, look at the
"List-Unsubscribe: " tag in the email header of this message.  Send email
to the address specified there.  It will be in the format:

[EMAIL PROTECTED]

If you need more information on unsubscribing, start reading here:

http://sources.redhat.com/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is available
starting at this URL.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFI7Xb84KuGfSFAYARArogAJwIr9vu3hjWx6UTYvQ30AbfO2zhcACdFnOB
32rd5Y7aWumm8lfJWsvzeP4=
=S/OR
-END PGP SIGNATURE-

--
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: extending desktop to a second monitor

[Fabrizio Salvatore]

OK, I'll do it. In any event, the suggestion I received works, so thanks !

Fab

Larry Hall (Cygwin) wrote:

On 10/04/2006, Fabrizio Salvatore wrote:
I've no idea if this is a Cygwin/X issue ! When I run cygwin, I use 
Windows as window terminal:


%RUN% XWin -multiwindow -clipboard -silent-dup-error +bs), 


XWin is the Cygwin X server.  Therefore, by definition, this is a Cygwin/X
issue for which there is a separate list.  Please use the cygwin-xfree list
for these kinds of issues/reports.



--
#
Dr P-Fabrizio Salvatore| Department of Physics
Phone: +44 (0)1784 44 3479 | Royal Holloway College
Fax: +44 (0)1784 47 2794   | University of London
e-mail: [EMAIL PROTECTED] | Egham, Surrey, TW20 0EX
http://www.pp.rhul.ac.uk/~salvator | United Kingdom (UK)
#

--
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: Bash and CR/LF line-endings

[Williams, Gerald S \(Jerry\)]

Gary R. Van Sickle wrote:
> At the risk of being over-obvious, Linux users... use Linux. In such
> an insular environment, perhaps they have the luxury of only using
> the One True Text File Format (whatever that is).

We're you the one who brought up Unicode earlier? Besides,
there are numerous situations where files get transferred
with  without needing to involve Windows, so stray
 characters occasionally show up here and there. I'm
sure many of us would like support for  endings on
Linux as well.

gsw

--
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/

[ANNOUNCEMENT] New package: lyx-1.4.3-4

[Bo Peng]

Version 1.4.3-4 of "lyx" has been uploaded.

In case you are wondering what LyX is, here is what
http://www.lyx.org/ has to say on the subject:

  LyX is a document processor that encourages an approach to writing
  based on the structure of your documents, not their appearance. It
  is released under a Free Software / Open Source license.

  LyX is for people that write and want their writing to look great,
  right out of the box. No more endless tinkering with formatting
  details, 'finger painting' font attributes or futzing around with page
  boundaries. You just write. In the background, Prof. Knuth's legendary
  TeX typesetting engine makes you look good.

  On screen, LyX looks like any word processor; its printed output -- or
  richly cross-referenced PDF, just as readily produced -- looks like
  nothing else. Gone are the days of industrially bland .docs, all
  looking similarly not-quite-right, yet coming out unpredictably
  different on different printer drivers. Gone are the crashes 'eating'
  your dissertation the evening before going to press.

  LyX is stable and fully featured. It is a multi-platform, fully
  internationalized application running natively on Unix/Linux, the
  Macintosh and modern Windows platforms.

Version 1.4.3-4 is the first official cygwin port of lyx. Compared to
lyx-1.4.2, this version improves stability and MS Windows support.
Please refer to the lyx-announce mailing list (
http://marc.theaimsgroup.com/?l=lyx-announce&r=1&w=2) for a complete
list of features and changes.

If you have questions or comments, please send them to the Cygwin
mailing list at: cygwin@cygwin.com .

 *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there. It will be in the format:

[EMAIL PROTECTED]

If you need more information on unsubscribing, start reading here:

http://sources.redhat.com/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is
available starting at this URL.

--
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: Re: Does 'ar' work with native MS Windows libs?

[Christopher Faylor]

On Wed, Oct 04, 2006 at 09:37:09AM -0400, Williams, Gerald S (Jerry) wrote:
>Coatimundi wrote:
>>Thank you for bringing this up.  I forgot to mention (a sure
>>sign that my multitasking scaling is rolling over) that I also
>>tried the P option.
>>   While this usually works, I found cases where it did not.
>[...]
>>Since I see nothing wrong with the source and I am short on time, I am
>>going to chalk this up to an unidentified mistake on my part, unless I
>>see it again and have time to build bintools myself and step through
>>the code in debug.
>
>You've probably already ruled this out, but if you do see it again, you
>might want to verify that you're not mixing path separators (LIB.EXE
>will use either).  I believe you must use only backslash-style
>separators if you want to interoperate with ar.

If 'ar' insists on backslash separators that is surely a bug.

cgf

--
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: Does 'ar' work with native MS Windows libs?

[Larry Hall (Cygwin)]

Williams, Gerald S (Jerry) wrote:

Coatimundi wrote:

Thank you for bringing this up.  I forgot to mention (a sure
sign that my multitasking scaling is rolling over) that I also
tried the P option.
  While this usually works, I found cases where it did not.

[...]

Since I see nothing wrong with the source and I am short on
time, I am going to chalk this up to an unidentified mistake
on my part, unless I see it again and have time to build
bintools myself and step through the code in debug.


You've probably already ruled this out, but if you do see it
again, you might want to verify that you're not mixing path
separators (LIB.EXE will use either). I believe you must use
only backslash-style separators if you want to interoperate
with ar.



Why is that?  If 'LIB.EXE' will work with either and 'ar' as a Cygwin
app prefers '/', why would working with a .lib produced by 'LIB.EXE'
containing '\' separators make 'ar' work better?


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

--
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/

Subversion 1.4

[Williams, Gerald S \(Jerry\)]

Has anybody successfully built subversion 1.4 (or alternately,
is a release planned soon)? It didn't build OOTB for me, and
I'd rather not duplicate effort.

gsw

--
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/

[ANNOUNCEMENT] Updated: openssl-0.9.8d-1, openssl-devel-0.9.8d-1, openssl097-0.9.7l-1

[Corinna Vinschen]

I've updated the version of OpenSSL to 0.9.8d-1.  This also includes the
openssl-devel package.  The compatibility package openssl097 has been
updated to 0.9.7l-1.

This is an upstream security and bugfix release.  The Cygwin release is the
vanilla version, no additional patches.

Official release message:
===

   OpenSSL version 0.9.8d and 0.9.7l released
   ==

   OpenSSL - The Open Source toolkit for SSL/TLS
   http://www.openssl.org/

   The OpenSSL project team is pleased to announce the release of
   version 0.9.8d of our open source toolkit for SSL/TLS. This new
   OpenSSL version is a security and bugfix release and incorporates
   changes and bugfixes to the toolkit.  For a complete list of
   changes, please see http://www.openssl.org/source/exp/CHANGES.

   This release fixes four security vulnerabilities, CVE-2006-2937,
   CVE-2006-2940, CVE-2006-3738, CVE-2006-4343.  Please see
   http://www.openssl.org/news/secadv_20060928.txt

   We also release 0.9.7l, which contains the security update and
   bugfixes compared to 0.9.7k.

   We consider OpenSSL 0.9.8d to be the best version of OpenSSL
   available and we strongly recommend that users of older versions
   upgrade as soon as possible. OpenSSL 0.9.8d is available for
   download via HTTP and FTP from the following master locations (you
   can find the various FTP mirrors under
   http://www.openssl.org/source/mirror.html):

 * http://www.openssl.org/source/
 * ftp://ftp.openssl.org/source/

   For those who want or have to stay with the 0.9.7 series of
   OpenSSL, we strongly recommend that you upgrade to OpenSSL 0.9.7l
   as soon as possible.  It's available in the same location as
   0.9.8d.

   The distribution file names are:

o openssl-0.9.8d.tar.gz
  MD5 checksum: 8ed1853538e1d05a1f5ada61ebf8bffa
  SHA1 checksum: 4136fba00303a3d319d2052bfa8e1f09a2e12fc2

o openssl-0.9.7l.tar.gz
  MD5 checksum: b21d6e10817ddeccf5fbe1379987333e
  SHA1 checksum: f0e4136639b10cbd1227c4f7350ff7ad406e575d

   The checksums were calculated using the following commands:

openssl md5 openssl-0.9.*.tar.gz
openssl sha1 openssl-0.9.*.tar.gz

   Yours,

   The OpenSSL Project Team...

Mark J. Cox Nils Larsch Ulf M\366ller
Ralf S. Engelschall Ben Laurie  Andy Polyakov
Dr. Stephen Henson  Richard Levitte Geoff Thorpe
Lutz JänickeBodo Möller
===

To update your installation, click on the "Install Cygwin now" link on
the http://cygwin.com/ web page.  This downloads setup.exe to your
system.  Then, run setup and answer all of the questions.


*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there.  It will be in the format:


[EMAIL PROTECTED]

If you need more information on unsubscribing, start reading here:

http://sources.redhat.com/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is available
starting at the above URL.

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

--
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/

[ANNOUNCEMENT] Updated: OpenSSH-4.4p1-1

[Corinna Vinschen]

I've just updated the version of OpenSSH to 4.4p1-1.

This is a new major upstream release.  The Cygwin release is created
from the vanilla sources.

The official release message of 4.4p1:


OpenSSH 4.4 has just been released. It will be available from the
mirrors listed at http://www.openssh.com/ shortly.

OpenSSH is a 100% complete SSH protocol version 1.3, 1.5 and 2.0
implementation and includes sftp client and server support.

Once again, we would like to thank the OpenSSH community for their
continued support of the project, especially those who contributed
code or patches, reported bugs, tested snapshots and purchased
T-shirts or posters.

T-shirt, poster and CD sales directly support the project. Pictures
and more information can be found at:
http://www.openbsd.org/tshirts.html and
http://www.openbsd.org/orders.html

For international orders use http://https.openbsd.org/cgi-bin/order
and for European orders, use http://https.openbsd.org/cgi-bin/order.eu

Changes since OpenSSH 4.3:


Security bugs resolved in this release:

 * Fix a pre-authentication denial of service found by Tavis Ormandy,
   that would cause sshd(8) to spin until the login grace time
   expired.

 * Fix an unsafe signal hander reported by Mark Dowd. The signal
   handler was vulnerable to a race condition that could be exploited
   to perform a pre-authentication denial of service. On portable
   OpenSSH, this vulnerability could theoretically lead to
   pre-authentication remote code execution if GSSAPI authentication
   is enabled, but the likelihood of successful exploitation appears
   remote.

 * On portable OpenSSH, fix a GSSAPI authentication abort that could
   be used to determine the validity of usernames on some platforms.

This release includes the following new functionality and fixes:

 * Implemented conditional configuration in sshd_config(5) using the
   "Match" directive. This allows some configuration options to be
   selectively overridden if specific criteria (based on user, group,
   hostname and/or address) are met. So far a useful subset of post-
   authentication options are supported and more are expected to be
   added in future releases.

 * Add support for Diffie-Hellman group exchange key agreement with a
   final hash of SHA256.

 * Added a "ForceCommand" directive to sshd_config(5). Similar to the
   command="..." option accepted in ~/.ssh/authorized_keys, this forces
   the execution of the specified command regardless of what the user
   requested. This is very useful in conjunction with the new "Match"
   option.

 * Add a "PermitOpen" directive to sshd_config(5). This mirrors the
   permitopen="..." authorized_keys option, allowing fine-grained
   control over the port-forwardings that a user is allowed to
   establish.

 * Add optional logging of transactions to sftp-server(8).

 * ssh(1) will now record port numbers for hosts stored in
   ~/.ssh/authorized_keys when a non-standard port has been requested.

 * Add an "ExitOnForwardFailure" option to cause ssh(1) to exit (with
   a non-zero exit code) when requested port forwardings could not be
   established.

 * Extend sshd_config(5) "SubSystem" declarations to allow the
   specification of command-line arguments.

 * Replacement of all integer overflow susceptible invocations of
   malloc(3) and realloc(3) with overflow-checking equivalents.

 * Many manpage fixes and improvements

 * New portable OpenSSH-specific features:

   - Add optional support for SELinux, controlled using the
 --with-selinux configure option (experimental)

   - Add optional support for Solaris process contracts, enabled
 using the --with-solaris-contracts configure option (experimental)
 This option will also include SMF metadata in Solaris packages
 built using the "make package" target

   - Add optional support for OpenSSL hardware accelerators (engines),
 enabled using the --with-ssl-engine configure option.

 * Bugs from http://bugzilla.mindrot.org fixed:
#482  - readconf doesn't accept paths with spaces in them.
#906  - syslog messages from sshd [net] lost.
#975  - Kerberos authentication timing can leak information
about account validity.
#981  - Flow stop in SSH2.
#1102 - C program 'write' with zero length hangs.
#1129 - sshd hangs for command-only invocations due to
fork/child signals.
#1131 - error "buffer_append_space:alloc not supported"
#1138 - Passphrase asked for (but ignored) if key file permissions
too liberal..
#1156 - Closes connection after C-c is pressed on QNX.
#1157 - ssh-keygen doesn't handle DOS line breaks.
#1159 - %u and %h not handled in IdentityFile.
#1161 - scp -r fails.
#1162 - Inappropriate sequence of syslog messages.
#1166 - openssh-4.3p1 has some issues compiling.
#1171 - configure can't always figure out LL

Re: openssh 3.4p1-4. Error starting sshd service

[Luther Palmer]

Max Bowsher  ukf.net> writes:

> 
> Pablo Milano wrote:
> > I upgraded to openssh 3.4p1-4, and after installing it, I get the
> > following error when trying to start the openssh service:
> > 
> > ***
> > The CYGWIN sshd service is starting.
> > The CYGWIN sshd service could not be started.
> > 
> > The service did not report an error.
> > 
> > More help is available by typing NET HELPMSG 3534
> > ***
> > > 

> You might find a helpful error message in /var/log/sshd.log
> 
> Max.
> 



I had seen the advice to look at /var/log/sshd.log before, but there was 
nothing in the file, then I noticed that no one had write priveleges to that 
file.  Once I ran 

chmod +w /var/log/sshd.log

the ssh server started properly.  Very odd.




--
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: Un-attended install ALL

[Vinod Gupta]

All this pain, just because some one did not include
"--InstallAll" option to setup.exe?? 




As the saying goes, .  Of course, you
can always look to see if any of your issues with 'setup.exe' are addressed
by a snapshot .

  


Thanks Lary.
When I ran the latest "setup-2.551.exe --help" I got no output at all.

Vinod



--
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: bash scripts fail with bash3.1-8

[mwoehlke]

Thomas Porschberg wrote:

Am Tue, 3 Oct 2006 17:02:29 +0100
schrieb "Dave Korn" :

On 03 October 2006 16:43, Turly O'Connor wrote:

By way of an example as to what broke, note that in the following
that  "cleartool" is not a cygwin tool (it's a Windows executable),
writing its CRLF-terminated output to Windows' stdout.

CHECKOUTS=`cleartool lsc -all -cvi -s`  # list all my checkouts

I used to be able to do

for one in $CHECKOUTS ; do echo $one Hello ; done

C:/Path/To/file1 Hello
C:/Path/To/file2 Hello

Now it seems that "$one" above contains the binary CR, so I get:

Hello h/To/file1
Hello h/To/file2

What do I need to do to get this working again?

  How about

CHECKOUTS=`cleartool lsc -all -cvi -s | d2u`  # list all my checkouts

or 


for one in $((echo $CHECKOUTS | d2u)) ; do echo $one Hello ; done

depending on how happy cleartool is on piping output to a cygwin
program.


This is exactly the problem I have with my sqlplus call.
Is there a way to solve it without introducing the d2u filter ?


You could try the new shopt... but have you considered arranging for 
'sqlplus' to point to a shell script that would exec 'sqlplus.exe' and 
pipe it through d2u?


--
Matthew
This message will self destruct in five millennia.


--
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: Bash and CR/LF line-endings

[mwoehlke]

Williams, Gerald S (Jerry) wrote:

Gary R. Van Sickle wrote:

At the risk of being over-obvious, Linux users... use Linux. In such
an insular environment, perhaps they have the luxury of only using
the One True Text File Format (whatever that is).


We're you the one who brought up Unicode earlier? Besides,
there are numerous situations where files get transferred
with  without needing to involve Windows, so stray
 characters occasionally show up here and there. I'm
sure many of us would like support for  endings on
Linux as well.


...which is exactly why I kept pestering Eric to know if he planned on 
submitting upstream. :-)

http://cygwin.com/ml/cygwin/2006-10/msg00101.html (Eric's answer)

--
Matthew
This message will self destruct in five millennia.


--
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: [ANNOUNCEMENT] Updated: monotone-0.30-1

[Dr. Volker Zell]

> Lapo Luchini writes:

> Version 0.30-1 of monotone has been uploaded.

Packaging error: There are two directories under /usr/share/doc

 monotone and monotone-0.30

Shouldn't the file below monotone go to the monotone-0.30 subdirectory ?

Ciao
  Volker


--
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: Un-attended install ALL

[Vinod Gupta]

The local packages folder has two mirrors - the main (http%3a%2f.../) 
and mymirror/ (which has only this empty allpackage). How do I tell 
setup.exe to look inside BOTH mirrors?


Type in the name of your mirror site when you are asked for the mirrors
you wish to use.


I am installing from "local packages" folder containing two mirrors 
having different packages, not from Internet.


I tried:
setup.exe -L -l  -l 
it installed from mirror2_folder only. How do I force it to use BOTH?

Vinod


--
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/

Packaging error in lyx-1.4.3-4

[Dr. Volker Zell]

Hi

Packaging errors in lyx-1.4.3-4:

 o The file /etc/postinstall/lyx.sh/lyx.sh should be /etc/postinstall/lyx.sh

 o The subdirectory /usr/share/doc/lyx should be named /usr/share/doc/lyx-1.4.3
   to be consistent with the other packages

Ciao
  Volker


--
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/

bash shell globbing not working anymore

[Andy Telford]

Has any experienced this?  

- "ls" works but "ls *" returns "ls: *: No such file or directory"
- same if I just use the shell builtin "echo *" just returns "*"

I am up to date with the latest versions of everything.  I had to fix up the 
line endings in my .bash_profile/.bashrc file to follow the unix conventions 
with the recent bash update but otherwise haven't changed anything,

Andrew

Environment:

SHELLOPTS=braceexpand:emacs:hashall:histexpand:history:interactive-comments:monitor
CYGWIN="ntsec binmode"
BASH_VERSION="3.1.17(9)-release"


$ uname -a
CYGWIN_NT-5.0 J3RSF41 1.5.19(0.150/4/2) 2006-01-16 15:01 i686 Cygwin








--
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: bash shell globbing not working anymore

[Markus Schönhaber]

Andy Telford wrote:
> Has any experienced this?
>
> - "ls" works but "ls *" returns "ls: *: No such file or directory"
> - same if I just use the shell builtin "echo *" just returns "*"

I experience this every time when I issue those commands with an empty 
directory as cwd. That's simply the way it's meant to be.

Regards
  mks

--
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: Un-attended install ALL

[Igor Peshansky]

On Wed, 4 Oct 2006, Vinod Gupta wrote:

> > All this pain, just because some one did not include
> > "--InstallAll" option to setup.exe??
> >
> > As the saying goes, .  Of course, you
> > can always look to see if any of your issues with 'setup.exe' are
> > addressed by a snapshot .
>
> Thanks Lary.
> When I ran the latest "setup-2.551.exe --help" I got no output at all.

Check the log file.
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_Igor Peshansky, Ph.D. (name changed!)
 |,4-  ) )-,_. ,\ (  `'-'   old name: Igor Pechtchanski
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

--
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: bash shell globbing not working anymore

[Dave Korn]

On 04 October 2006 16:47, Andy Telford wrote:

> Has any experienced this?
> 
> - "ls" works but "ls *" returns "ls: *: No such file or directory"
> - same if I just use the shell builtin "echo *" just returns "*"

  You are in an empty directory.  There is nothing for the '*' to match.

  As glob expansion is handled by the shell, ls ends up actually seeing "*" as
the argument passed to it, rather than a list of filenames.  Since there is no
file called "*" in the directory, there is nothing for it to list; it returns
the same error as any other non-existent filename.

  Contrast the effect of "ls *" against "ls .*".


cheers,
  DaveK
-- 
Can't think of a witty .sigline today


--
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: [ANNOUNCEMENT] Updated: bash-3.1-9

[David Picton]

From: Eric Blake 
To: cygwin at cygwin dot com
Date: Mon, 02 Oct 2006 21:51:04 -0600
Subject: [ANNOUNCEMENT] Updated: bash-3.1-9
Reply-to: cygwin at cygwin dot com
Reply-to: The Cygwin Mailing List 



-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

A new release of bash, 3.1-9, is now available, replacing 3.1-8 as the
current version.  3.1-6 remains as the previous version.



NEWS:
=
Due to complaints on the mailing list, this version attempts to alleviate
some of the pain of people who have difficulties working around \r\n line
endings in scripts residing on binary mounts.


[snip]


Second, this release adds a new shopt, igncr, which dynamically
tells bash to ignore all \r in the input file when it is set; however, it
defaults to unset.  With this shopt, it is possible to make a bash script
work on binary mounts even if it has \r\n line endings, by adding the
following line as the first non-comment:
 shopt -s igncr;#


[snip]


If you want your script to be
portable to other platforms or shells that don't understand igncr, you can
write it as:
(shopt -s igncr) 2>/dev/null && eval 'shopt -s igncr';#


Alternatively, you can set the environment variable BASH_ENV to the name of a
file containing startup commands for all bash scripts.  If the above command is
issued in the file, the shopt command will be set before the script is
read - and
DOS-format scripts will therefore execute correctly without modification.

--
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: Un-attended install ALL

[Larry Hall (Cygwin)]

Vinod Gupta wrote:


The local packages folder has two mirrors - the main (http%3a%2f.../) 
and mymirror/ (which has only this empty allpackage). How do I tell 
setup.exe to look inside BOTH mirrors?


Type in the name of your mirror site when you are asked for the mirrors
you wish to use.


I am installing from "local packages" folder containing two mirrors 
having different packages, not from Internet.


I tried:
setup.exe -L -l  -l 
it installed from mirror2_folder only. How do I force it to use BOTH?



Sorry, I don't know the answer to this offhand.  I'd need to check the
source.  You might want to beat me to it and take a peek yourself.


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

--
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: Does 'ar' work with native MS Windows libs?

[Williams, Gerald S \(Jerry\)]

Christopher Faylor wrote:
> If 'ar' insists on backslash separators that is surely a bug.

You may be right, but please stop calling me Shirley. :-)

Larry Hall (Cygwin) wrote:
> Why is that?  If 'LIB.EXE' will work with either and 'ar' as a Cygwin
> app prefers '/', why would working with a .lib produced by 'LIB.EXE'
> containing '\' separators make 'ar' work better?

Perhaps ar doesn't prefer either. It strips the directory
name when you add files. It does tolerate directories in
the form that LIB.EXE would normally generate (i.e., with
backslashes).

Yes, it is still arguably a bug if ar cannot handle files
that LIB.EXE can produce, although there may be a reason.
It's been a while since I looked into the internals of
archive files, but I vaguely remember that slashes have a
special meaning when found in archive directories.

gsw

--
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: Subversion 1.4

[David Rothenberger]

On 10/4/2006 7:35 AM, Williams, Gerald S (Jerry) wrote:

Has anybody successfully built subversion 1.4 (or alternately,
is a release planned soon)? It didn't build OOTB for me, and
I'd rather not duplicate effort.


I successfully built it with the attached patch. I haven't actually used 
it yet, since some other tools I use don't yet support 1.4, but it 
passed all tests except the ruby tests. I did some investigation and it 
seemed like a problem with the test infrastructure. Since I don't use 
ruby bindings, I didn't spend a lot of time on it.


I did have trouble building with subversion installed. I had to 
uninstall it to get the build to work correctly.


Also, I did not regenerate the swig bindings, as was done for 1.3.2.

Anyway, I've attached the g-b-s script and patch I used. Maybe it will 
work for you.


--
David Rothenbergerspammer? -> [EMAIL PROTECTED]
GPG/PGP: 0x92D68FD8, DB7C 5146 1AB0 483A 9D27 DFBA FBB9 E328 92D6 8FD8

One possible reason that things aren't going according to plan
is that there never was a plan in the first place.
--- subversion-1.4.0-orig/CYGWIN-PATCHES/README 1969-12-31 16:00:00.0 
-0800
+++ subversion-1.4.0/CYGWIN-PATCHES/README  2006-09-12 11:05:09.0 
-0700
@@ -0,0 +1,54 @@
+Subversion 1.4.0
+--
+The goal of the Subversion project is to build a version control system
+that is a compelling replacement for CVS in the open source community. 
+
+There is very useful and comprehensive documentation in the book
+"Version Control with Subversion", available free online:
+
+  http://svnbook.red-bean.com/
+
+
+
+Runtime requirements:
+  cygwin
+  libapr0
+  libaprutil0
+  libdb4.2
+  expat
+  libneon24
+
+Build requirements:
+  (basic development packages)
+  python
+  autoconf
+  libtool
+  apr
+  apr-util
+  libdb4.2-devel
+  neon
+  libiconv
+  swig
+  apache2-devel
+  perl
+
+Canonical homepage:
+  http://subversion.tigris.org/
+
+Canonical download:
+  http://subversion.tigris.org/tarballs/subversion-1.4.0.tar.bz2
+
+
+
+Build instructions:
+  unpack subversion-1.4.0-1-src.tar.bz2
+if you use setup to install this src package, it will be
+unpacked under /usr/src automatically
+  cd /usr/src
+  ./subversion-1.4.0-1.sh all
+
+Or use './subversion-1.4.0-1.sh prep' to get a patched source directory
+
+---
+
+Cygwin port maintained by: Max Bowsher <[EMAIL PROTECTED]>
--- subversion-1.4.0-orig/CYGWIN-PATCHES/gbs.munge  1969-12-31 
16:00:00.0 -0800
+++ subversion-1.4.0/CYGWIN-PATCHES/gbs.munge   2006-09-12 10:58:32.0 
-0700
@@ -0,0 +1,46 @@
+ConfigureArg --enable-shared
+ConfigureArg --disable-static
+ConfigureArg --with-apr=/usr/bin/apr-1-config
+ConfigureArg --with-apr-util=/usr/bin/apu-1-config
+ConfigureArg --with-neon=/usr
+ConfigureArg --disable-neon-version-check
+ConfigureArg --with-swig=/usr/bin/swig
+ConfigureArg --with-apxs=/usr/sbin/apxs2
+
+SubPackage subversion-devel-$VER-$REL.tar.bz2 usr/include 
usr/lib/libsvn_[a-rt-z]* usr/lib/libsvn_subr*
+SubPackage subversion-python-$VER-$REL.tar.bz2 usr/lib/python* 
usr/bin/cygsvn_swig_py* usr/lib/libsvn_swig_py*
+SubPackage subversion-perl-$VER-$REL.tar.bz2 usr/lib/perl5 
usr/bin/cygsvn_swig_perl* usr/lib/libsvn_swig_perl*
+SubPackage subversion-ruby-$VER-$REL.tar.bz2 usr/lib/ruby 
usr/bin/cygsvn_swig_ruby* usr/lib/libsvn_swig_ruby*
+SubPackage subversion-apache2-$VER-$REL.tar.bz2 usr/lib/apache2
+
+AutoreconfCmd ./autogen.sh
+AutoreconfCmd find . -name "autom4te.cache" | xargs rm -rf
+AutoreconfCmd sed -e 's/relink_command=\\"$relink_command\\""/"/' 
ac-helpers/ltmain.sh > gbs.$$.tmp && mv gbs.$$.tmp ac-helpers/ltmain.sh
+
+MakeTarget extraclean-swig-py EXTRA_CFLAGS=
+MakeTarget extraclean-swig-pl EXTRA_CFLAGS=
+MakeTarget extraclean-swig-rb EXTRA_CFLAGS=
+MakeTarget autogen-swig-py EXTRA_CFLAGS=
+MakeTarget autogen-swig-pl EXTRA_CFLAGS=
+MakeTarget autogen-swig-rb EXTRA_CFLAGS=
+MakeTarget EXTRA_CFLAGS=
+MakeTarget swig-py swig_pydir=/usr/lib/python2.4/site-packages/libsvn 
swig_pydir_extra=/usr/lib/python2.4/site-packages/svn EXTRA_CFLAGS=
+MakeTarget swig-pl EXTRA_CFLAGS=
+MakeTarget swig-rb LIBS=-lruby EXTRA_CFLAGS=
+
+MakeInstallTarget install
+MakeInstallTarget install-swig-py 
swig_pydir=/usr/lib/python2.4/site-packages/libsvn 
swig_pydir_extra=/usr/lib/python2.4/site-packages/svn
+MakeInstallTarget install-swig-pl
+MakeInstallTarget install-swig-rb
+
+# Kill perllocal.pod and containing dirs
+InstallExtraCmd rm ${instdir}/usr/lib/perl5/5.8/cygwin/perllocal.pod
+InstallExtraCmd rmdir ${instdir}/usr/lib/perl5/5.8/cygwin
+InstallExtraCmd rmdir ${instdir}/usr/lib/perl5/5.8
+
+UnpackExclude */apr
+UnpackExclude */apr-util
+UnpackExclude */neon
+
+DiffExclude configure
+DiffExclude build-outputs.mk
--- subversion-1.4.0-orig/CYGWIN-PATCHES/setup.hint 1969-12-31 
16:00:00.0 -0800
+++ subversion-1.4.0/CYGWIN-PATCHES/s

RE: Similar Bash 3.1.18 CR/LF Problem

[Williams, Gerald S \(Jerry\)]

Christopher Faylor wrote:
> The dilemma here is that I read other mailing lists besides
> cygwin where people are trying to use Cygwin but are close
> to giving up because it is so slow.  So, making bash faster
> for people who are using it correctly is very desirable. 

Which is why we need to get the patch in upstream. If you
can't make it faster, you can at least make what you're
comparing against slower. :-)

Seriously, I'd have a hard time believing that supporting
 endings would noticably impact performance if it
were done as part of upstream BASH. Special-casing Cygwin
(especially when you start doing things like checking for
DOS paths, examining the first line, etc.) would impact
performance, surely. So I agree--don't do that.

gsw

--
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: bash shell globbing not working anymore

[Andy Telford]

Nope. The directory was not empty, so * should have been expanded by the shell 
according to the bash "pathname expansion" rules.  I included the SHELLOPTS 
variable in the first email to show that noglob is not set.

$ mkdir newdir
$ cd newdir
$ touch newfile
$ ls
newfile
$ ls *
ls: *: No such file or directory
$ type ls
ls is hashed (/usr/bin/ls)





--
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: Subversion 1.4

[David Rothenberger]

Resending with the g-b-s script compressed so it's not blocked and with 
a valid GPG signature this time.


On 10/4/2006 7:35 AM, Williams, Gerald S (Jerry) wrote:

Has anybody successfully built subversion 1.4 (or alternately,
is a release planned soon)? It didn't build OOTB for me, and
I'd rather not duplicate effort.


I successfully built it with the attached patch. I haven't actually used
it yet, since some other tools I use don't yet support 1.4, but it
passed all tests except the ruby tests. I did some investigation and it
seemed like a problem with the test infrastructure. Since I don't use
ruby bindings, I didn't spend a lot of time on it.

I did have trouble building with subversion installed. I had to
uninstall it to get the build to work correctly.

Also, I did not regenerate the swig bindings, as was done for 1.3.2.

Anyway, I've attached the g-b-s script and patch I used. Maybe it will
work for you.

--
David Rothenbergerspammer? -> [EMAIL PROTECTED]
GPG/PGP: 0x92D68FD8, DB7C 5146 1AB0 483A 9D27 DFBA FBB9 E328 92D6 8FD8

One possible reason that things aren't going according to plan
is that there never was a plan in the first place.

--- subversion-1.4.0-orig/CYGWIN-PATCHES/README 1969-12-31 16:00:00.0 
-0800
+++ subversion-1.4.0/CYGWIN-PATCHES/README  2006-09-12 11:05:09.0 
-0700
@@ -0,0 +1,54 @@
+Subversion 1.4.0
+--
+The goal of the Subversion project is to build a version control system
+that is a compelling replacement for CVS in the open source community. 
+
+There is very useful and comprehensive documentation in the book
+"Version Control with Subversion", available free online:
+
+  http://svnbook.red-bean.com/
+
+
+
+Runtime requirements:
+  cygwin
+  libapr0
+  libaprutil0
+  libdb4.2
+  expat
+  libneon24
+
+Build requirements:
+  (basic development packages)
+  python
+  autoconf
+  libtool
+  apr
+  apr-util
+  libdb4.2-devel
+  neon
+  libiconv
+  swig
+  apache2-devel
+  perl
+
+Canonical homepage:
+  http://subversion.tigris.org/
+
+Canonical download:
+  http://subversion.tigris.org/tarballs/subversion-1.4.0.tar.bz2
+
+
+
+Build instructions:
+  unpack subversion-1.4.0-1-src.tar.bz2
+if you use setup to install this src package, it will be
+unpacked under /usr/src automatically
+  cd /usr/src
+  ./subversion-1.4.0-1.sh all
+
+Or use './subversion-1.4.0-1.sh prep' to get a patched source directory
+
+---
+
+Cygwin port maintained by: Max Bowsher <[EMAIL PROTECTED]>
--- subversion-1.4.0-orig/CYGWIN-PATCHES/gbs.munge  1969-12-31 
16:00:00.0 -0800
+++ subversion-1.4.0/CYGWIN-PATCHES/gbs.munge   2006-09-12 10:58:32.0 
-0700
@@ -0,0 +1,46 @@
+ConfigureArg --enable-shared
+ConfigureArg --disable-static
+ConfigureArg --with-apr=/usr/bin/apr-1-config
+ConfigureArg --with-apr-util=/usr/bin/apu-1-config
+ConfigureArg --with-neon=/usr
+ConfigureArg --disable-neon-version-check
+ConfigureArg --with-swig=/usr/bin/swig
+ConfigureArg --with-apxs=/usr/sbin/apxs2
+
+SubPackage subversion-devel-$VER-$REL.tar.bz2 usr/include 
usr/lib/libsvn_[a-rt-z]* usr/lib/libsvn_subr*
+SubPackage subversion-python-$VER-$REL.tar.bz2 usr/lib/python* 
usr/bin/cygsvn_swig_py* usr/lib/libsvn_swig_py*
+SubPackage subversion-perl-$VER-$REL.tar.bz2 usr/lib/perl5 
usr/bin/cygsvn_swig_perl* usr/lib/libsvn_swig_perl*
+SubPackage subversion-ruby-$VER-$REL.tar.bz2 usr/lib/ruby 
usr/bin/cygsvn_swig_ruby* usr/lib/libsvn_swig_ruby*
+SubPackage subversion-apache2-$VER-$REL.tar.bz2 usr/lib/apache2
+
+AutoreconfCmd ./autogen.sh
+AutoreconfCmd find . -name "autom4te.cache" | xargs rm -rf
+AutoreconfCmd sed -e 's/relink_command=\\"$relink_command\\""/"/' 
ac-helpers/ltmain.sh > gbs.$$.tmp && mv gbs.$$.tmp ac-helpers/ltmain.sh
+
+MakeTarget extraclean-swig-py EXTRA_CFLAGS=
+MakeTarget extraclean-swig-pl EXTRA_CFLAGS=
+MakeTarget extraclean-swig-rb EXTRA_CFLAGS=
+MakeTarget autogen-swig-py EXTRA_CFLAGS=
+MakeTarget autogen-swig-pl EXTRA_CFLAGS=
+MakeTarget autogen-swig-rb EXTRA_CFLAGS=
+MakeTarget EXTRA_CFLAGS=
+MakeTarget swig-py swig_pydir=/usr/lib/python2.4/site-packages/libsvn 
swig_pydir_extra=/usr/lib/python2.4/site-packages/svn EXTRA_CFLAGS=
+MakeTarget swig-pl EXTRA_CFLAGS=
+MakeTarget swig-rb LIBS=-lruby EXTRA_CFLAGS=
+
+MakeInstallTarget install
+MakeInstallTarget install-swig-py 
swig_pydir=/usr/lib/python2.4/site-packages/libsvn 
swig_pydir_extra=/usr/lib/python2.4/site-packages/svn
+MakeInstallTarget install-swig-pl
+MakeInstallTarget install-swig-rb
+
+# Kill perllocal.pod and containing dirs
+InstallExtraCmd rm ${instdir}/usr/lib/perl5/5.8/cygwin/perllocal.pod
+InstallExtraCmd rmdir ${instdir}/usr/lib/perl5/5.8/cygwin
+InstallExtraCmd rmdir ${instdir}/usr/lib/perl5/5.8
+
+UnpackExclude */apr
+UnpackExclude */apr-util
+UnpackExclude */neon
+
+DiffExclude configure
+DiffExclude build-outputs.mk
--- subversion-1.4.0-orig/CYGWI

RE: Similar Bash 3.1.18 CR/LF Problem

[Dave Korn]

On 04 October 2006 18:06, Williams, Gerald S (Jerry) wrote:


> Seriously, I'd have a hard time believing that supporting
>  endings would noticably impact performance if it
> were done as part of upstream BASH. Special-casing Cygwin
> (especially when you start doing things like checking for
> DOS paths, examining the first line, etc.) would impact
> performance, surely. So I agree--don't do that.

  That's a total non-sequitur.  A piece of code will have the same impact,
whether it's included directly in the upstream sources, or whether it's a
cygwin local patch surrounded by #ifdef __CYGWIN__.

cheers,
  DaveK
-- 
Can't think of a witty .sigline today


--
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: bash shell globbing not working anymore

[Dave Korn]

On 04 October 2006 18:08, Andy Telford wrote:

> Nope. The directory was not empty, so * should have been expanded by the
> shell according to the bash "pathname expansion" rules.  I included the
> SHELLOPTS variable in the first email to show that noglob is not set.  
> 
> $ mkdir newdir
> $ cd newdir
> $ touch newfile
> $ ls
> newfile
> $ ls *
> ls: *: No such file or directory
> $ type ls
> ls is hashed (/usr/bin/ls)

  Weird.  Let's have a look at your cygcheck -svr output then (as an
attachment, please).  Hold back on the strace logs just for now, though!


cheers,
  DaveK
-- 
Can't think of a witty .sigline today


--
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: Subversion 1.4

[Williams, Gerald S \(Jerry\)]

David Rothenberger wrote:
> I successfully built it with the attached patch. I haven't
> actually used it yet, since some other tools I use don't
> yet support 1.4, but it passed all tests except the ruby
> tests.

Thanks. I'll give it a try. I meanwhile found an earlier post
that recommended "./configure --disable-shared" for a previous
version. This does allow my build to complete, although I get
many errors from "make check":

[...]
Running all tests in target-test.py...success
Running all tests in getopt_tests.py...FAILURE
Running all tests in basic_tests.py...FAILURE
Running all tests in commit_tests.py...FAILURE
Running all tests in update_tests.py...FAILURE
Running all tests in switch_tests.py...FAILURE
Running all tests in prop_tests.py...FAILURE
Running all tests in schedule_tests.py...FAILURE
Running all tests in log_tests.py...FAILURE
Running all tests in copy_tests.py...FAILURE
Running all tests in diff_tests.py...FAILURE
Running all tests in export_tests.py...FAILURE
Running all tests in externals_tests.py...FAILURE
Running all tests in merge_tests.py...FAILURE
Running all tests in revert_tests.py...FAILURE
Running all tests in stat_tests.py...FAILURE
Running all tests in trans_tests.py...FAILURE
Running all tests in autoprop_tests.py...FAILURE
Running all tests in blame_tests.py...FAILURE
Running all tests in special_tests.py...FAILURE
Running all tests in svnadmin_tests.py...FAILURE
Running all tests in svnlook_tests.py...FAILURE
Running all tests in svnversion_tests.py...FAILURE
Running all tests in utf8_tests.py...success
Running all tests in history_tests.py...FAILURE
Running all tests in lock_tests.py...FAILURE
Running all tests in cat_tests.py...FAILURE
Running all tests in import_tests.py...FAILURE
Running all tests in svnsync_tests.py...FAILURE
Running all tests in authz_tests.py...FAILURE
Running all tests in changes-test.exe...success
[...]

gsw

--
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: Un-attended install ALL

[Vinod Gupta]

On 2006-10-04 11:55, Igor Peshansky wrote:

On Wed, 4 Oct 2006, Vinod Gupta wrote:

  

All this pain, just because some one did not include
"--InstallAll" option to setup.exe??

As the saying goes, .  Of course, you
can always look to see if any of your issues with 'setup.exe' are
addressed by a snapshot .
  

Thanks Lary.
When I ran the latest "setup-2.551.exe --help" I got no output at all.



Check the log file.
Igor
  


And where that log is supposed to be? Surely not /var/log/setup.log 
because cygwin is not yet installed.
Moreover, why should the output of "setup-2.551.exe --help" be sent to 
any log file?


Vinod


--
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: bash shell globbing not working anymore

[Andy Telford]

Eureka!  I checked the cygcheck output and noticed that my cygwin dll was old 
even though "setup" thought I was up to date.  Maybe a previous cygwin update 
failed to complete properly?   I reinstalled the base cygwin package using 
setup and now it is all working fine.

I guess the current bash doesn't jive with  cygwin 1.5.19(0.150/4/2) 2006-01-16 
15:01 i686 Cygwin,

Thanks everyone,

Andrew


- Original Message 
From: Dave Korn <[EMAIL PROTECTED]>
To: cygwin mailing list 
Sent: Wednesday, October 4, 2006 1:13:22 PM
Subject: RE: bash shell globbing not working anymore

On 04 October 2006 18:08, Andy Telford wrote:

> Nope. The directory was not empty, so * should have been expanded by the
> shell according to the bash "pathname expansion" rules.  I included the
> SHELLOPTS variable in the first email to show that noglob is not set.  
> 
> $ mkdir newdir
> $ cd newdir
> $ touch newfile
> $ ls
> newfile
> $ ls *
> ls: *: No such file or directory
> $ type ls
> ls is hashed (/usr/bin/ls)

  Weird.  Let's have a look at your cygcheck -svr output then (as an
attachment, please).  Hold back on the strace logs just for now, though!








--
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: bash shell globbing not working anymore

[Dave Korn]

On 04 October 2006 18:41, Andy Telford wrote:

> Eureka!  I checked the cygcheck output and noticed that my cygwin dll was
> old even though "setup" thought I was up to date.  Maybe a previous cygwin
> update failed to complete properly?   I reinstalled the base cygwin package
> using setup and now it is all working fine.   

  Excellent.  It could be that the previous run had completed but was waiting
for a reboot to replace in-use files, and when you re-ran it the files weren't
in-use any more.

> I guess the current bash doesn't jive with  cygwin 1.5.19(0.150/4/2)
> 2006-01-16 15:01 i686 Cygwin, 

  I just have to wonder if it's possible that bash was somehow seeing "ls
*\r"!

> From: Dave Korn <[EMAIL PROTECTED]>

  BTW, please, try and remember not to quote people's email addresses when you
reply, it increases our spam burden.

cheers,
  DaveK
-- 
Can't think of a witty .sigline today


--
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: 1.5.21 Forked background processes

[Steve]

Steve  sbcglobal.net> writes:


> Hello again,
> 
> This is what I managed to confirm so far by using snapshots:
> 
> Snapshot 2006-03-09  -  Problem does not exist.
> Snapshot 2006-03-18  -  Problem exists
> 
> So it looks like this problem arose between 03/09/06 and 03/18/06. Looking at
> the change logs in between this time shows what looks like process forking
> changes (See change log for 3/13/06) although I haven't tried this snapshot
> yet.
> 
> Thanks,
> ->Steve   
> 
> 

Hello All,

So, I've isolated this problem to snapshot 03-13-06. This is where I first start
seeing this ugly issue. I haven't had a chance to debug it yet but I'm guessing
the change log for this snapshot might tell us something right off thhe bat.
(http://cygwin.com/snapshots/winsup-changelog-20060309-20060313) 

Thanks for your attention,
->Steve
 


--
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/

lyx has problem with network directory names

[David Arnstein]

I just tried to use the Cygwin port of lyx. It cannot cope with my
home directory, which appears as //fs-sj1-15/darnstein in Cygwin. This
is a network directory, obviously.

When lyx starts up, it emits a complaint
QSettings: error creating /fs-sj1-15/darnstein/.qt

When I try to save a lyx document to my home directory, lyx complains
when it presents its file browser dialog box. It says
Could not read directory /fs-sj1-15

It appears that lyx is trying to access the root directory (/). It
does not seem to know how to interpret the Windows syntax "//."

--
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: Un-attended install ALL

[Igor Peshansky]

On Wed, 4 Oct 2006, Vinod Gupta wrote:

> On 2006-10-04 11:55, Igor Peshansky wrote:
> > On Wed, 4 Oct 2006, Vinod Gupta wrote:
> >
> > > > All this pain, just because some one did not include
> > > > "--InstallAll" option to setup.exe??
> > > >
> > > > As the saying goes, .  Of course, you
> > > > can always look to see if any of your issues with 'setup.exe' are
> > > > addressed by a snapshot .
> > > >
> > > Thanks Lary.
> > > When I ran the latest "setup-2.551.exe --help" I got no output at all.
> >
> > Check the log file.
> > Igor
>
> And where that log is supposed to be? Surely not /var/log/setup.log
> because cygwin is not yet installed.

It's setup.log in the directory you ran setup from.

> Moreover, why should the output of "setup-2.551.exe --help" be sent to
> any log file?

Read the cygwin-apps archives -- there's a long discussion of that exact
issue.  In a word, it's because setup cannot reliably write to the
console without other adverse effects.
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_Igor Peshansky, Ph.D. (name changed!)
 |,4-  ) )-,_. ,\ (  `'-'   old name: Igor Pechtchanski
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

--
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/

1.5.21: problem with source command in bash

[Ring, Patrick]

I am having a problem with the "source" command in bash (3.1-9).
When I try to source a file with aliases in it, the aliases get garbled
so that they don't work.  When I type "alias" on the command line, I can
see that it is incorrect.  Other commands also do not work, usually
giving an error like "command not found".
Example:
Put the line
   alias ls='ls -F'
in a file called trysrc.  Inside bash, cd to the directory and type
   source trysrc
   alias
I get the output
   'lias ls='ls -F
If I type 'ls', I get
   ls:  invalid option --

If I type the alias command on the command line, it seems to work fine.
I have also tried this on a second computer and get the same results.
Thanks in advace for your help,
Patrick


cygcheck.out
Description: cygcheck.out
--
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: 1.5.21: problem with source command in bash

[mwoehlke]

Ring, Patrick wrote:

I am having a problem with the "source" command in bash (3.1-9).
When I try to source a file with aliases in it, the aliases get garbled
so that they don't work.  When I type "alias" on the command line, I can
see that it is incorrect.  Other commands also do not work, usually
giving an error like "command not found".
Example:
Put the line
   alias ls='ls -F'
in a file called trysrc.  Inside bash, cd to the directory and type
   source trysrc
   alias
I get the output
   'lias ls='ls -F
If I type 'ls', I get
   ls:  invalid option --

If I type the alias command on the command line, it seems to work fine.
I have also tried this on a second computer and get the same results.
Thanks in advace for your help,


Have you RTFRA'd (for bash-3.1-9) and STFLA'd? It looks like doing these 
would solve your problem.


--
Matthew
This message will self destruct in five millennia.


--
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: Does 'ar' work with native MS Windows libs?

[Coatimundi]

Williams, Gerald S (Jerry) wrote:

You've probably already ruled this out, but if you do see it
again, you might want to verify that you're not mixing path
separators (LIB.EXE will use either). I believe you must use
only backslash-style separators if you want to interoperate
with ar.

gsw


Ironically, I just put a hardcopy of ar.c in the shredder.  As I 
recall... take a look at function normalize().  We see that '/' does 
enjoy special status.  Or, more precisely, the rightmost '/' has special 
status.  This will make sense if you have the code open.  And we also 
see that '\' has special status *if* HAVE_DOS_BASED_FILESYSTEM (or 
something like that) is #defined.  The code is clearly trying to handle 
everything.


For what it's worth, I think my problem was different.  All of the 
members were of the form \.obj where  was either 
Release or Debug; and  was whatever.  For the Release\ form I have 
never seen a problem.  For the Debug\ form, some members were not 
reported by 'ar t' even though 'ar x' got them all.  Oddly enough, 'ar 
tv' identifes all the members -- including the 'T' section -- but just 
gets the name wrong at the top, printing just Debug\ instead of, e.g. 
Debug\foo.obj.


After all this discussion and looking at the code I am reasonaly 
convinced that the problem I saw lay in the structure of my debugging 
libs built with LIB.EXE and was in no way a problem with 'ar.'  So with 
that, I will bow out of this thread which probably no longer belongs on 
gmane.os.cygwin.


Thanks to everyone, including those who took the time to make private 
suggestions.




--
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: Similar Bash 3.1.18 CR/LF Problem

[Christopher Faylor]

On Wed, Oct 04, 2006 at 01:06:19PM -0400, Williams, Gerald S (Jerry) wrote:
>Christopher Faylor wrote:
>> The dilemma here is that I read other mailing lists besides
>> cygwin where people are trying to use Cygwin but are close
>> to giving up because it is so slow.  So, making bash faster
>> for people who are using it correctly is very desirable. 
>
>Which is why we need to get the patch in upstream. If you
>can't make it faster, you can at least make what you're
>comparing against slower. :-)
>
>Seriously, I'd have a hard time believing that supporting 
>endings would noticably impact performance if it were done as part of
>upstream BASH.

You haven't been paying attention, it seems.

We've already been over this ground.  The performance impact for turning
on bash's automatic CRLF handling is profound.  That's why we're here.

cgf

--
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/

cygwin unix commands in windows

[Tom Lee]

Hello,

after further study, I noticed that using "c:/directory" works fine with my 
tests except tar.exe.


all of the following commands works
cp.exe c:/temp/tuner.h c:/test/
mv.exe c:/temp/tt.h c:/test

for tar.exe,
tar test.tar c:/temp/*
works.
however,
 tar cvf c:/test.tar  c:/temp/*
and
 tar xvf c:/test.tar
will fail

is tar.exe the only exception that won't work correctly when using "c:/"?

from my test, I didn't see any other commands has the problem in handling 
"c:/"


I understand people here may like /cygdrive/c more than c:/.  Just want to 
know if it is an accident feature that all other commands can work with c:/ 
except tar?


thanks.

tom

_
The next generation of Search—say hello!  
http://imagine-windowslive.com/minisites/searchlaunch/?locale=en-us&FORM=WLMTAG



--
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/

Cygwin server/cvs passwd problem

[Erik Nijkamp]

{\rtf1\ansi\ansicpg1252\fromhtml1 \deff0{\fonttbl
{\f0\fswiss Arial;}
{\f1\fmodern Courier New;}
{\f2\fnil\fcharset2 Symbol;}
{\f3\fmodern\fcharset0 Courier New;}
{\f4\fswiss\fcharset0 Arial;}}
{\colortbl\red0\green0\blue0;\red0\green0\blue255;}
\uc1\pard\plain\deftab360 \f0\fs24
{\*\htmltag19 http://www.w3.org/TR/REC-html40";>}
{\*\htmltag2 \par }
{\*\htmltag2 \par }
{\*\htmltag34 }
{\*\htmltag1 \par }
{\*\htmltag1 \par }
{\*\htmltag161 }
{\*\htmltag1 \par }
{\*\htmltag241 }
{\*\htmltag241 \par \par }
{\*\htmltag249 }
{\*\htmltag1 \par }
{\*\htmltag1 \par }
{\*\htmltag41 }
{\*\htmltag2 \par }
{\*\htmltag2 \par }
{\*\htmltag50 }\htmlrtf \lang1031 \htmlrtf0
{\*\htmltag0 \par }
{\*\htmltag0 \par }
{\*\htmltag96 }\htmlrtf {\htmlrtf0
{\*\htmltag0 \par }
{\*\htmltag0 \par }
{\*\htmltag64 }\htmlrtf {\htmlrtf0
{\*\htmltag148 }\htmlrtf {\fs20 \f4 \htmlrtf0
{\*\htmltag84 }\htmlrtf {\lang2057 \htmlrtf0 Hello,
{\*\htmltag244 }
{\*\htmltag252 }
{\*\htmltag92 }\htmlrtf }\htmlrtf0
{\*\htmltag156 }\htmlrtf }\htmlrtf0 \htmlrtf\par}\htmlrtf0
\htmlrtf \par
\htmlrtf0
{\*\htmltag72 }
{\*\htmltag0 \par }
{\*\htmltag0 \par }
{\*\htmltag64 }\htmlrtf {\htmlrtf0
{\*\htmltag148 }\htmlrtf {\fs20 \f4 \htmlrtf0
{\*\htmltag84 }\htmlrtf {\lang2057 \htmlrtf0
{\*\htmltag244 }
{\*\htmltag84  }\htmlrtf \'a0\htmlrtf0
{\*\htmltag252 }
{\*\htmltag92 }\htmlrtf }\htmlrtf0
{\*\htmltag156 }\htmlrtf }\htmlrtf0 \htmlrtf\par}\htmlrtf0
\htmlrtf \par
\htmlrtf0
{\*\htmltag72 }
{\*\htmltag0 \par }
{\*\htmltag0 \par }
{\*\htmltag64 }\htmlrtf {\htmlrtf0
{\*\htmltag148 }\htmlrtf {\fs20 \f4 \htmlrtf0
{\*\htmltag84 }\htmlrtf {\lang2057 \htmlrtf0 Currently I
{\*\htmltag84 ’}\htmlrtf \'92\htmlrtf0 m trying to use the newest cygwin
{\*\htmltag4 \par }\htmlrtf  \htmlrtf0 version as ssh server for windows xp sp2,
{\*\htmltag244 }
{\*\htmltag252 }
{\*\htmltag92 }\htmlrtf }\htmlrtf0
{\*\htmltag156 }\htmlrtf }\htmlrtf0 \htmlrtf\par}\htmlrtf0
\htmlrtf \par
\htmlrtf0
{\*\htmltag72 }
{\*\htmltag0 \par }
{\*\htmltag0 \par }
{\*\htmltag64 }\htmlrtf {\htmlrtf0
{\*\htmltag148 }\htmlrtf {\fs20 \f4 \htmlrtf0
{\*\htmltag84 }\htmlrtf {\lang2057 \htmlrtf0 which is working quite smoothly. But actually I need to
{\*\htmltag4 \par }\htmlrtf  \htmlrtf0 create a cvs alias for an existing nt user.
{\*\htmltag244 }
{\*\htmltag252 }
{\*\htmltag92 }\htmlrtf }\htmlrtf0
{\*\htmltag156 }\htmlrtf }\htmlrtf0 \htmlrtf\par}\htmlrtf0
\htmlrtf \par
\htmlrtf0
{\*\htmltag72 }
{\*\htmltag0 \par }
{\*\htmltag0 \par }
{\*\htmltag64 }\htmlrtf {\htmlrtf0
{\*\htmltag148 }\htmlrtf {\fs20 \f4 \htmlrtf0
{\*\htmltag84 }\htmlrtf {\lang2057 \htmlrtf0 Works out of the box in windows/prompt itself, but
{\*\htmltag4 \par }\htmlrtf  \htmlrtf0 whenever I try exactly the same within
{\*\htmltag244 }
{\*\htmltag252 }
{\*\htmltag92 }\htmlrtf }\htmlrtf0
{\*\htmltag156 }\htmlrtf }\htmlrtf0 \htmlrtf\par}\htmlrtf0
\htmlrtf \par
\htmlrtf0
{\*\htmltag72 }
{\*\htmltag0 \par }
{\*\htmltag0 \par }
{\*\htmltag64 }\htmlrtf {\htmlrtf0
{\*\htmltag148 }\htmlrtf {\fs20 \f4 \htmlrtf0
{\*\htmltag84 }\htmlrtf {\lang2057 \htmlrtf0 the cygwin or putty bash it hangs on the second
{\*\htmltag4 \par }\htmlrtf  \htmlrtf0 password verification:
{\*\htmltag244 }
{\*\htmltag252 }
{\*\htmltag92 }\htmlrtf }\htmlrtf0
{\*\htmltag156 }\htmlrtf }\htmlrtf0 \htmlrtf\par}\htmlrtf0
\htmlrtf \par
\htmlrtf0
{\*\htmltag72 }
{\*\htmltag0 \par }
{\*\htmltag0 \par }
{\*\htmltag64 }\htmlrtf {\htmlrtf0
{\*\htmltag148 }\htmlrtf {\fs20 \f4 \htmlrtf0
{\*\htmltag84 }\htmlrtf {\lang2057 \htmlrtf0
{\*\htmltag244 }
{\*\htmltag84  }\htmlrtf \'a0\htmlrtf0
{\*\htmltag252 }
{\*\htmltag92 }\htmlrtf }\htmlrtf0
{\*\htmltag156 }\htmlrtf }\htmlrtf0 \htmlrtf\par}\htmlrtf0
\htmlrtf \par
\htmlrtf0
{\*\htmltag72 }
{\*\htmltag0 \par }
{\*\htmltag0 \par }
{\*\htmltag64 }\htmlrtf {\htmlrtf0
{\*\htmltag148 }

Re: bash shell globbing not working anymore

[Larry Hall (Cygwin)]

On 10/04/2006, Andy Telford wrote:
I guess the current bash doesn't jive with cygwin 1.5.19(0.150/4/2) 
2006-01-16 15:01 i686 Cygwin, 


Yes, I'm quite sure bash doesn't speak jive. ;-)


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

--
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: lyx has problem with network directory names

[Larry Hall (Cygwin)]

David Arnstein wrote:

I just tried to use the Cygwin port of lyx. It cannot cope with my
home directory, which appears as //fs-sj1-15/darnstein in Cygwin. This
is a network directory, obviously.

When lyx starts up, it emits a complaint
QSettings: error creating /fs-sj1-15/darnstein/.qt

When I try to save a lyx document to my home directory, lyx complains
when it presents its file browser dialog box. It says
Could not read directory /fs-sj1-15

It appears that lyx is trying to access the root directory (/). It
does not seem to know how to interpret the Windows syntax "//."



So mounting the share should work-around this issue, 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

--
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: Similar Bash 3.1.18 CR/LF Problem

[Larry Hall (Cygwin)]

Christopher Faylor wrote:

On Wed, Oct 04, 2006 at 01:06:19PM -0400, Williams, Gerald S (Jerry) wrote:

Christopher Faylor wrote:

The dilemma here is that I read other mailing lists besides
cygwin where people are trying to use Cygwin but are close
to giving up because it is so slow.  So, making bash faster
for people who are using it correctly is very desirable. 

Which is why we need to get the patch in upstream. If you
can't make it faster, you can at least make what you're
comparing against slower. :-)

Seriously, I'd have a hard time believing that supporting 
endings would noticably impact performance if it were done as part of
upstream BASH.


You haven't been paying attention, it seems.

We've already been over this ground.  The performance impact for turning
on bash's automatic CRLF handling is profound.  That's why we're here.



But now that this code has been thoroughly chastised and left by itself to
think about its bad behavior, it might have better behavior.  Eric, shall
we turn it back on and see? ;-)


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

--
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: cygwin unix commands in windows

[Larry Hall (Cygwin)]

Tom Lee wrote:

Hello,

after further study, I noticed that using "c:/directory" works fine with 
my tests except tar.exe.


all of the following commands works
cp.exe c:/temp/tuner.h c:/test/
mv.exe c:/temp/tt.h c:/test

for tar.exe,
tar test.tar c:/temp/*
works.
however,
 tar cvf c:/test.tar  c:/temp/*
and
 tar xvf c:/test.tar
will fail

is tar.exe the only exception that won't work correctly when using "c:/"?

from my test, I didn't see any other commands has the problem in 
handling "c:/"


I understand people here may like /cygdrive/c more than c:/.  Just want 
to know if it is an accident feature that all other commands can work 
with c:/ except tar?


Tom, have you ever read the man page for 'tar'?  Now might be a good time.
Pay special attention to the "--force-local" flag.

This is not a Cygwin issue.  Further discussion if it in this thread is
therefore off-topic for this list.  You'll have to find another mailing list
to follow-up with if you want to talk about this more.

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

--
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: Similar Bash 3.1.18 CR/LF Problem

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Williams, Gerald S (Jerry) on 10/4/2006 11:06 AM:
> Christopher Faylor wrote:
>> The dilemma here is that I read other mailing lists besides
>> cygwin where people are trying to use Cygwin but are close
>> to giving up because it is so slow.  So, making bash faster
>> for people who are using it correctly is very desirable. 
> 
> Which is why we need to get the patch in upstream. If you
> can't make it faster, you can at least make what you're
> comparing against slower. :-)

There may be precedent - upstream already had a patch for djgpp that
stripped \r.  But I also heard back from the upstream maintainer that I
probably missed the cutoff for bash 3.2, since he has already built the
release candidate, so I will have to keep it as a cygwin-local patch for
another release cycle.

- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFJF0e84KuGfSFAYARAi7aAJ9DQuo95G3jCqa29KFAfySImZBfEQCg16Xi
meUi+6PMQFaxDjHcCEb4u4Q=
=F5Wm
-END PGP SIGNATURE-

--
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: Similar Bash 3.1.18 CR/LF Problem

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Christopher Faylor on 10/4/2006 5:24 PM:
>>
>> Seriously, I'd have a hard time believing that supporting 
>> endings would noticably impact performance if it were done as part of
>> upstream BASH.
> 
> You haven't been paying attention, it seems.
> 
> We've already been over this ground.  The performance impact for turning
> on bash's automatic CRLF handling is profound.  That's why we're here.

Actually, the performance impact of reading a \r\n file on a binary mount
using my igncr option is much less than the performance impact of the
pristine sources, seeing as how my patch allows reading a buffer at a time
rather than the original reading a character at a time, and I/O time is
more of a bottleneck than character filtering once the data is read in.
On the other hand, igncr has a slight performance penalty on text mounts,
due to the additional branch instruction for every single character read,
only to find that text mounts don't produce \r in the first place.  And on
binary mounts, files with plain \n are slightly penalized by the mere
existence of igncr, again because I added a branch instruction in the code
path of reading every character.

But as long as igncr is present, then I am seriously thinking of turning
it on by default on cygwin.  And yes, if I do this, then I can remove the
special casing of DOS path names (although the speed penalty of calling
cygwin_conv_to_posix_path once per file is generally less than the speed
penalty of checking whether igncr is set once per character).  And we
would be back to the behavior of bash-3.1-6 of gracefully handling \r\n by
default, except that on binary mounts the performance of 3.1-9 is better
than 3.1-6, and that a determined user who _wants_ literal \r can disable
the shopt.

One of the remaining issues in my mind is the following.  I have no
problem making igncr the default for bash, since there are no standards
stating what bash may or may not do.  But I'm not sure whether making
igncr the default in 'bash --posix', aka '/bin/sh', is wise, since POSIX
does not permit this behavior.  My only concern is that by making igncr
cognizant of whether posix behavior is requested, people will start asking
'why does my script work with #!/bin/bash but not #!/bin/sh?'.

- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFJGBg84KuGfSFAYARAvErAJoC9FFPPnk50RzLnJsDGHknEpsPNACfUK4n
Pl1ovb1MWm6fPYbD2nwE3hM=
=fu4P
-END PGP SIGNATURE-

--
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: Cygwin server/cvs passwd problem

[René Berber]

Erik Nijkamp wrote:

> Currently I’m trying to use the newest cygwin version as ssh server
> for windows xp sp2,
> 
> which is working quite smoothly. But actually I need to create a cvs
> alias for an existing nt user.

An alias?

Are you in fact creating a user in the /etc/passwd file? if you want to use it 
as an alias you have to copy the SSID part of the real user to the alias user.

As an option, an much easier, have you considered adding a user in CVS?  You 
just have to add a passwd file into the reporitory's CVSROOT, an entry of the 
form:   

> Works out of the box in windows/prompt itself, but whenever I try
> exactly the same within the cygwin or putty bash it hangs on the second 
> password
> verification:
> 
> [NT]
> C:\Documents and Settings\Administrator>cvs -d :pserver:nijkamp:[EMAIL 
> PROTECTED]
> host:/testrepo passwd -a -r nijkamp afoobar3
> 
> Adding user [EMAIL PROTECTED]
> New Password:
> Verify Password:

I don't understand what you are doing here, what version of CVS understands the 
command "passwd"?

> [Putty/Cygwin]
> 
> [EMAIL PROTECTED] ~
> $ cvs -d :pserver:nijkamp:[EMAIL PROTECTED]:/testrepo passwd -a -r nijkamp 
> foobar2
> 
> Adding user [EMAIL PROTECTED]
> New Password: secret

It looks like it worked, what is the problem?

> This is a must for my current project and I would be glad if somebody
> could help me.

You seem to be using a modified CVS, so why ask here?

My Cederqvist manual for CVS 1.12.12 says "Someday, there may be a cvs passwd 
command", I know that is not the latest version but the latest in Cygwin 
packages is 1.11.21 (latest stable).
-- 
René Berber


--
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/

rsync can run in command line but not in cron

[lin q]

Hi,
 I just installed lastest cygwin on windows xp service pack 1.

 I enabled cron in cygwin, the crontab looks like this,

# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (/tmp/crontab.3548 installed on Wed Oct  4 19:11:00 2006)
# (Cron version -- $Id: crontab.c,v 1.8 2004/12/21 16:14:41 corinna Exp $)
USER=toma
USERNAME=toma
HOME=/cygdrive/c/home/toma
HOMEDRIVE=C:
UID=toma
12 19 * * * /usr/bin/rsync -azvv /cygdrive/u/ /cygdrive/c/bin/swtools > 
/tmp/swtools.cron 2>&1



 But it does not work, I check the log file, it is like this,

building file list ...
rsync: link_stat "/cygdrive/u/." failed: No such file or directory (2)
done

 It looks like it can not work with path like /cygdrive/u, this is a 
network drive.


 The problem is I can run the exact command in command line.

 Do you know why cron make difference on the path?

_
Express yourself - download free Windows Live Messenger themes! 
http://clk.atdmt.com/MSN/go/msnnkwme002001msn/direct/01/?href=http://imagine-msn.com/themes/vibe/default.aspx?locale=en-us&source=hmtagline



--
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: [ANNOUNCEMENT] Updated: bash-3.1-9

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to David Picton on 10/4/2006 10:13 AM:
>> (shopt -s igncr) 2>/dev/null && eval 'shopt -s igncr';#
> 
> Alternatively, you can set the environment variable BASH_ENV to the name
> of a
> file containing startup commands for all bash scripts.  If the above
> command is
> issued in the file, the shopt command will be set before the script is
> read - and
> DOS-format scripts will therefore execute correctly without modification.

Or even experiment with the SHELLOPTS environment variable.  If you set it
in windows, even the first run of bash will obey igncr; or, from within
bash, if you do 'export SHELLOPTS' to convert it from a shell variable to
an environment variable, then further bash invocations will inherit the
setting of this option, without having to edit every script.

- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFJGRR84KuGfSFAYARAhutAKCf9snR/167jRfRYFtyqlbFB4DTmgCdEcqg
i2HyqvlWmZht37VVfCbNPs0=
=h78P
-END PGP SIGNATURE-

--
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: Similar Bash 3.1.18 CR/LF Problem

[Christopher Faylor]

On Wed, Oct 04, 2006 at 07:17:18PM -0600, Eric Blake wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>According to Williams, Gerald S (Jerry) on 10/4/2006 11:06 AM:
>> Christopher Faylor wrote:
>>> The dilemma here is that I read other mailing lists besides
>>> cygwin where people are trying to use Cygwin but are close
>>> to giving up because it is so slow.  So, making bash faster
>>> for people who are using it correctly is very desirable. 
>> 
>> Which is why we need to get the patch in upstream. If you
>> can't make it faster, you can at least make what you're
>> comparing against slower. :-)
>
>There may be precedent - upstream already had a patch for djgpp that
>stripped \r.  But I also heard back from the upstream maintainer that I
>probably missed the cutoff for bash 3.2, since he has already built the
>release candidate, so I will have to keep it as a cygwin-local patch for
>another release cycle.

Am I understanding what this change does correctly?

It does not really fix the "CRLF problem".  Instead it just strips every
\r that it finds regardless of whether the \r is before a \n, right?

If this is right and you can do this level of surgery on bash's buffers
is it harder to detect \r\n because the \n may not be in the current
buffer so you don't know when to strip a \r at the end of the buffer?

--
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: readline-5.2-1 prompt issue on cygwin

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Igor Peshansky on 10/4/2006 9:03 AM:
>> The upstream maintainer claims that this version fixes some prompt display
>> bugs when using non-printing escape sequences with a single-line prompt.
>> I have not verified this, but hope that this is the case.
> 
> FWIW, still doesn't work for me:
> 
> $ export PS1='[\[\e[32m\]\h\[\e[0m\]:\[\e[33m\]\w\[\e[0m\]] \[\]'
> [helios:~] cd /c^L
> [helios:~] cd /c/c
>^^^
> This is what's displayed.  Removing the '\[\]' at the end doesn't help.
>   Igor

I am able to confirm this.  Using the above PS1 (the export is optional,
as it only has to be a shell variable rather than an environment
variable), and the xterm-unicode terminal as compiled for cygwin, along
with bash 3.1.17 and release candidate readline 5.2, I get the following
behavior when I type < ><^L>, where _ is the location of the
cursor:

$ PS1='[\[\e[32m\]\h\[\e[0m\]:\[\e[33m\]\w\[\e[0m\]] \[\]'
[LOUNGE:~] cd /c^L
[LOUNGE:~] cd /c/c_

Then following it by 6 backspaces (although I only typed five characters),
the display is stuck as:

[LOUNGE:~] cd_

Here, I then type < >, and get:
[LOUNGE:/tmp] ] _

I'm really at a loss as to how to go about debugging this, and don't know
whether the bug is in readline or in cygwin's terminal descriptions.  I
haven't yet built bash 3.2 for cygwin; is there any chance that bash-3.2
is using some readline hooks that bash 3.1 was not using, such that this
problem would go away?

This appears to be the same bug that I have been repeatedly reporting:
http://lists.gnu.org/archive/html/bug-bash/2006-05/msg00023.html
http://lists.gnu.org/archive/html/bug-bash/2006-03/msg5.html
http://lists.gnu.org/archive/html/bug-bash/2005-07/msg00115.html

Any hints on what I should try from within a debugger?

- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFJHBi84KuGfSFAYARAveKAKDTj+M/VIBJaY56sEBuaiAtxdPR6ACeJpO/
m145NSw794O2duQErRfqmwk=
=eBIY
-END PGP SIGNATURE-

--
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: 1.5.21: problem with source command in bash

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Ring, Patrick on 10/4/2006 3:07 PM:
> I am having a problem with the "source" command in bash (3.1-9).
> When I try to source a file with aliases in it, the aliases get garbled
> so that they don't work.  When I type "alias" on the command line, I can
> see that it is incorrect.  Other commands also do not work, usually
> giving an error like "command not found".
> Example:
> Put the line
>alias ls='ls -F'
> in a file called trysrc.  Inside bash, cd to the directory and type
>source trysrc

Then type 'd2u trysrc' and try again.  I suspect line endings here; read
the release announcement.

- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
volunteer cygwin bash maintainer
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFJHEa84KuGfSFAYARAtR0AKDXMpdhxNzHmrmzaqbrRebIisdh8wCggwv1
RLY00XaTItzhGDk8QqukK0Q=
=FRl3
-END PGP SIGNATURE-

--
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: cygwin unix commands in windows

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Tom Lee on 10/4/2006 5:45 PM:
> Hello,
> 
> after further study, I noticed that using "c:/directory" works fine with
> my tests except tar.exe.
> 
> 
> I understand people here may like /cygdrive/c more than c:/.  Just want
> to know if it is an accident feature that all other commands can work
> with c:/ except tar?

You asked, so I'll answer.  Yes, it is an accident that other tools
understand c:/.  Cygwin operates on the philosophy that you should use
POSIX paths, aka /cygdrive/c (or if that is too much typing for you, read
'man mount' for how you can shorten it to /c, by remounting cygdrive as
'/').  DOS paths work only when the application is not assigning some
other meaning to the literal colon.  ls does not parse its arguments but
hands them straight to stat(), and so it happens to work.  tar, on the
other hand, parses its arguments, and treats "c:/dir" as meaning
"directory /dir" on "remote machine c", unless you use tar --force-local.
 Another example of a program that parses its arguments is make; you need
only read last months archives for the debate about make 3.80 vs. make
3.81 for proof that using DOS paths in cygwin programs is ASKING for
problems.  And yet another case is bash: bash-3.1-8 always opened DOS
paths in binary mode, even though using POSIX paths would open some files
in text mode.  Either learn to use POSIX paths if you use cygwin, or quit
griping.

- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFJHJ+84KuGfSFAYARAuebAJwPnL9zkIMrnU+tQCSLSiPMGhg3uQCePoOP
MzseCGa1KuXTP5kZKLHfdcY=
=zWJ1
-END PGP SIGNATURE-

--
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: [bash-testers] Re: readline-5.2-1 prompt issue on cygwin

[Chet Ramey]

Eric Blake wrote:
> According to Igor Peshansky on 10/4/2006 9:03 AM:
>>> The upstream maintainer claims that this version fixes some prompt display
>>> bugs when using non-printing escape sequences with a single-line prompt.
>>> I have not verified this, but hope that this is the case.
>> FWIW, still doesn't work for me:
> 
>> $ export PS1='[\[\e[32m\]\h\[\e[0m\]:\[\e[33m\]\w\[\e[0m\]] \[\]'
>> [helios:~] cd /c^L
>> [helios:~] cd /c/c
>>^^^
>> This is what's displayed.  Removing the '\[\]' at the end doesn't help.
>>  Igor
> 
> I am able to confirm this.  Using the above PS1 (the export is optional,
> as it only has to be a shell variable rather than an environment
> variable), and the xterm-unicode terminal as compiled for cygwin, along
> with bash 3.1.17 and release candidate readline 5.2, I get the following
> behavior when I type < ><^L>, where _ is the location of the
> cursor:

I can't reproduce it on Mac OS X using Terminal or xterm, using a UTF-8
locale and the included prompt string.  I will look at it on some other
systems tomorrow.

(I can't tell from the description, but I assume that the ^L is followed
by a screen clear.  It's supposed to.)

> I'm really at a loss as to how to go about debugging this, and don't know
> whether the bug is in readline or in cygwin's terminal descriptions.  I
> haven't yet built bash 3.2 for cygwin; is there any chance that bash-3.2
> is using some readline hooks that bash 3.1 was not using, such that this
> problem would go away?

It's not.  There are no readline hooks to use.

> This appears to be the same bug that I have been repeatedly reporting:
> http://lists.gnu.org/archive/html/bug-bash/2006-05/msg00023.html
> http://lists.gnu.org/archive/html/bug-bash/2006-03/msg5.html
> http://lists.gnu.org/archive/html/bug-bash/2005-07/msg00115.html
> 
> Any hints on what I should try from within a debugger?

Attach to it from another terminal and set breakpoints in
_rl_move_cursor_relative.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
   Live Strong.  No day but today.
Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://cnswww.cns.cwru.edu/~chet/

--
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: Similar Bash 3.1.18 CR/LF Problem

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Christopher Faylor on 10/4/2006 7:58 PM:
> 
> Am I understanding what this change does correctly?
> 
> It does not really fix the "CRLF problem".  Instead it just strips every
> \r that it finds regardless of whether the \r is before a \n, right?

Yes, igncr strips all \r, without looking whether it precedes \n.  I
modeled it after the igncr option of stty; isn't that the way terminals
behave when they have igncr turned on?  In other words, the shopt makes
bash treat files more like terminals.

> 
> If this is right and you can do this level of surgery on bash's buffers
> is it harder to detect \r\n because the \n may not be in the current
> buffer so you don't know when to strip a \r at the end of the buffer?

Correct, but this was also what the existing upstream djgpp code did -
blindly stripping \r without trying to read ahead to see if there is \n.
Is it worth me trying to change the behavior to be more like fopen("rt"),
where the \r is stripped only if it precedes \n?  Remember, text modes
never see \r\n to begin with, \r seldom appears alone, and it is possible
to turn the shopt off if it does the wrong thing.

- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFJHSI84KuGfSFAYARAmExAKC3s38MfY3Yx/tIc8VeiZ2Zstu2YgCfaJlh
Cn//tYOTdxPcKTpLjzoIQHQ=
=Tuvh
-END PGP SIGNATURE-

--
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: lyx has problem with network directory names

[David Arnstein]

On Wed, Oct 04, 2006 at 08:19:32PM -0400, Larry Hall (Cygwin) wrote:
> So mounting the share should work-around this issue, right?

Yes. I also have to redefine the HOME environment variable to P:/ and
do "cd P:/" before starting lyx, in order to get it to work correctly.
In this case, P: is the drive that I mounted the share on.

Oddly enough, lyx still complained
QSettings: error creating P:/.qt

I don't know what the problem was. I created P:/.qt as an empty
directory using mkdir and all is well, apparently.

Anyway, thank you for the suggestion Mr. Hall.

--
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: sshd "ssh_exchange_identification: Connection closed by remote host" until restarted

[David Christensen]

Pritchard, Douglas wrote:
> We tried your solution and did it a few times just to make sure and
> the machines having this problem still have it.  I did find a
> reference that suggested it might be a timing or dependency problem
> with another service.  Sshd already is tied to TCP/IP as a
> dependency.  I don't know what else it could be dependent on.  Just
> some thoughts.

Try updating Cygwin first and then running rebaseall.


If that doesn't work, read and follow the instructions here:

http://cygwin.com/problems.html


HTH,

David

p.s.  Please reply to the list; no need to cc me.


--
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: cygwin unix commands in windows

[Gary R. Van Sickle]

> From: Eric Blake
[snip]
> You asked, so I'll answer.  Yes, it is an accident that other 
> tools understand c:/.

It's no accident that make used to, and now again will, be supporting
Windows paths.  People put considerable time and effort into making it work
originally, and then again just recently in finally solving the problem and
pushing the fix upstream.

[snip]
>  Another example of a program that parses its arguments is 
> make; you need only read last months archives for the debate 
> about make 3.80 vs. make
> 3.81 for proof that using DOS paths in cygwin programs is 
> ASKING for problems.

I think you're misreading the make issue.  Using Windows paths in make was
apparently never "asking for problems" until the last release, at which time
a problem was introduced, a solution was found, pushed upstream, and the
problem is now solved (or will be when the next Cygwin build is released).

-- 
Gary R. Van Sickle
 



--
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: cygwin unix commands in windows

[Christopher Faylor]

On Wed, Oct 04, 2006 at 11:23:49PM -0500, Gary R. Van Sickle wrote:
>> From: Eric Blake
>[snip]
>>You asked, so I'll answer.  Yes, it is an accident that other tools
>>understand c:/.
>
>It's no accident that make used to, and now again will, be supporting
>Windows paths.  People put considerable time and effort into making it
>work originally, and then again just recently in finally solving the
>problem and pushing the fix upstream.

...and, if you're playing along at home, it has been shown that Eli's
change still may not be right.

>[snip]
>>Another example of a program that parses its arguments is make; you
>>need only read last months archives for the debate about make 3.80 vs.
>>make 3.81 for proof that using DOS paths in cygwin programs is ASKING
>>for problems.
>
>I think you're misreading the make issue.  Using Windows paths in make
>was apparently never "asking for problems" until the last release, at
>which time a problem was introduced, a solution was found, pushed
>upstream, and the problem is now solved (or will be when the next
>Cygwin build is released).

Actually, once again, the "make automatically understands MS-DOS paths"
behavior was a bug.  This behavior was supposed to be controlled by a
command-line option or an environment variable (if you don't believe me,
ask Geoff Noer).  That's why I specifically mentioned the option and the
environment variable in my announcement.  Apparently, I broke make
somewhere along the line, people got used to the behavior that I
inadvertently introduced, and they then considered automatic detection
of MS-DOS paths to be a Constitutional right.

cgf

--
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/

Requesting an updated gcc-mingw-g++ package to match gcc-g++-3.4.4-2 (PR24196)

[Prehnite -]

I was running gcc-g++-3.4.4-1, and was running into the same problem of a 
std::string allocating memory in a different DLL described here:

http://www.cygwin.com/ml/cygwin/2005-10/msg00051.html
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24196

So I update to 3.4.4-2, and yes it fixed the problem for the standard tools. 
However, it did not fix the problem for "-mno-cygwin" compile option 
specifying to link with the mingw libraries, and the now old, mingw 
specific, libstdc++.a. So, I need to upgrade my gcc-mingw-* packages to fix 
the problem, however they have not been updated to the latest version in the 
package repositories.


Could someone please upload matching gcc-mingw-* packages that contain the 
fix applied to 3.4.4-2?



Updated binary packages is of course the ideal. In the mean time, I 
attempted to build updated packages myself, however I found that the 
gcc-mingw-g++-20050522-1-src.tar.bz2 package does not meet the source 
package description described here:

http://cygwin.com/setup.html#package_contents
As the supposed source tarball inside it does not contain source files. It 
only contains executables, libraries, and headers. It also contains an 
un-usable configure script, and no build script. This may be ignorance on my 
part as I've never built a cygwin package from source before, but I could 
not get it to do much with the files provided.


I've given up now that I need to download the proper gcc-g++ source package, 
apply the same patch applied to cygwin's 3.4.4-2 version, and attempt to 
compile it for gcc-mingw.

-J

_
Search—Your way, your world, right now!  
http://imagine-windowslive.com/minisites/searchlaunch/?locale=en-us&FORM=WLMTAG



--
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/