Re: cvs and NTFS streams do not play well together...

2004-01-10 Thread linda w 
It seems that the standard stream notation is "::".  programs like 
Notepad can
read and write to NTFS streams using the :: (double colon notation).  That
would seem to indicate thay are valid pathnames that describe a "file" 
of data.
I.e. -- ":" is valid in a pathname on an NTFS file system to indicate a 
stream.

":" also is a valid chacter on linux.  Sounds like a built-in 
incompatibility.

Note, that if you do a dir of file::stream, it won't showup, but you can 
open it,
so if cygwin implements the "open" call by first calling "dir" it will fail.

-linda



Brian Dessent wrote:

[EMAIL PROTECTED] wrote:

 

Hi, I am using Cygwin 1.5.5 and cvs 1.11.6 on top of Windows NT 5.1.2600
SP1.  When I try to "cvs co" a file with a colon in its name, cvs gets
horribly confused by NTFS streams and commits suicide.  The exact error
message is as follows:  (note:  I was checking out the "src" module on
the "HEAD" branch in the FreeBSD Project's CVS repository when this cropped
up)
   

Filenames under Windows (both FAT and NTFS) cannot contain colons, so
I'm not really sure what you're expecting Cygwin to do here.  It's a
fundamental Windows limitation.
That said, you should try a managed mount for your cvs checkout
directory.  It's still an experimental feature but trying to use a
filename with a colon on a normal mount is guaranteed to fail so I don't
see that you have much to lose.
Brian

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

--
---
Capitalism:   The rewarding of software companies for producing software
 of the least quality the consumer will buy.




--
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: cvs and NTFS streams do not play well together...

2004-01-10 Thread Brian Dessent 
linda w wrote:
> 
> It seems that the standard stream notation is "::".  programs like
> Notepad can
> read and write to NTFS streams using the :: (double colon notation).  That
> would seem to indicate thay are valid pathnames that describe a "file"
> of data.
> I.e. -- ":" is valid in a pathname on an NTFS file system to indicate a
> stream.
> 
> ":" also is a valid chacter on linux.  Sounds like a built-in
> incompatibility.
> 
> Note, that if you do a dir of file::stream, it won't showup, but you can
> open it,
> so if cygwin implements the "open" call by first calling "dir" it will fail.

The "::" idiom is used to denote an alternative stream, but that doesn't
mean it's a valid character for the name of a file.  See also
:

<<
NTFS Naming Conventions

File and directory names can be up to 255 characters long, including any
extensions. Names preserve case, but are not case sensitive. NTFS makes
no distinction of filenames based on case. Names can contain any
characters except for the following:?  "  /  \  <  >  *  |  :
>>

Brian

--
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: Switching between DOS and UNIX mode

2004-01-10 Thread Jason Pearce 
Use the 'mount' command.  In fact, you should be able to simply mount some
particular directories (e.g., the ones the checkout is done into) in text
(DOS) mode for those developers that need this, and leave the Cygwin
installation itself in binary (Unix) mode.  Note: mounts in Cygwin are
(currently) persistent.
Igor
Does the selection of unix / dos at installation time actually make any difference?
Can't everything be redefined later via the mount command? I selected DOS at install 
time, is there an advanteage to installing in unix mode?
I am encountering different behaviour between a few machines with regards to CR LFs. I am trying to work my way through it but it is quite perplexing! I need to do more investigations in order to ask a decent question, but do the mount settings effect the behaviour of any non-cygwin application? I would not expect any effect, is that so?

Thanks,

Jason





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

some advice needed on gui frameworks and cygwin

2004-01-10 Thread Arash Partow 
Hi All,

I was wondering if anyone has had any experience with
getting wxWindows running on the latest release of
cygwin, also anyone with any info about how well
wxWindows runs on cygwin, does it have to be run in
conjunction with x11 or is there a translation done
into the windows gui api?
was it difficult getting wxWindows compiled under cygwin?,
were any extra patches required?
stuff like that...



Any help and/or info would be very much appreciated.



Regards



Arash Partow

__
Be one who knows what they don't know,
Instead of being one who knows not what they don't know,
Thinking they know everything about all things.
http://www.partow.net
_
Send mobile Christmas cards, download a festive ringtone and win a Motorola 
E365. Go to:  http://ninemsn.com.au/mobilecentral/christmas.asp

--
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: Switching between DOS and UNIX mode

2004-01-10 Thread Hannu E K Nevalainen 
> From: Elberger, Richard A.
> Sent: Friday, January 09, 2004 6:02 PM

> I am looking to have "switchability" between UNIX mode and DOS mode in
> cygwin (the choice during the installation).  We install all of our
> cygwin installations in UNIX mode.

 A good choice ;-) - my personal opinion.

> A subset of our developers use Windows-based editors. We use the cygwin
> cvs to checkout files from a remote repository.
>
> For some reason, this hiccups the windows editors -- probably CR/LFs.

 Moving the files to a text based mount might just as well move the "hiccup"
from the editor to some other place; e.g. make or gcc.
 IMO this is a "tricky corner" to be in. It happens just because of the
mixed environment of cygwin and windows as a combination - and having EOL
conventions differ.

> Is there a way to "switch" to DOS mode either through setting a variable
> in local shell, .profile, or some config file in /etc?

 I wouldn't expect so. Only possible way might be text mounts, but that has
limitations too...

 May I suggest that persons, preferring an Windows-based editor, take
actions to launch such an editor from a bash script like this (note
UNTESTED!):

-- wed -- (i.e. Windows EDitor)
#!/bin/bash
#Quick and Simple version: assuming ONE filename as argument
# and no problems WRT multiple people attempting to edit same file.

EDITOR="notepad"
file="$1"

if [ -z "`which $EDITOR`" ] ;then
  echo "$EDITOR is not in \$PATH"
else
  cmd="`cygpath -w $EDITOR` `cygpath -w $file`"
  u2d "$file"
  cmd /c $cmd
  d2u "$file"
fi
-- eof --

Assumed benefit: Keep all files in UNIX EOL mode at all times, except when
they're actually edited by use of u2d/d2u.

Culprit: Editor saves files in CRLF mode, making stuff misbehave _while the
editor is still running_ . This is asynchronous, remember.

Fix(?): run the "d2u" utility as soon as the file is to be used, e.g. in a
makefile.
...or an example at a more complex level: create/maintain a list of files
"currently being edited" in the script above. Then have the makefile use
that list as argument to "d2u" just before use.

My experience, from some twenty years being in a similar sitiation, is that:
It will always require 'self discipline' from the people using Win-editors
for cygwin files. Independent of the measures you take to avoid it and/or
protect from it.
A saying in Swedish "Hur du an vander dig sa har du andan dar bak"
(something like "No matter how you turn, your bottom is still behind you" in
translation)


/Hannu E K Nevalainen, B.Sc. EE - 59+16.37'N, 17+12.60'E

** on a mailing list; please keep replies on that particular list **

-- printf("LocalTime: UTC+%02d\n",(DST)? 2:1); --
--END OF MESSAGE--


--
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: Switching between DOS and UNIX mode

2004-01-10 Thread Igor Pechtchanski 
On Sat, 10 Jan 2004, Jason Pearce wrote:

> >Use the 'mount' command.  In fact, you should be able to simply mount some
> >particular directories (e.g., the ones the checkout is done into) in text
> >(DOS) mode for those developers that need this, and leave the Cygwin
> >installation itself in binary (Unix) mode.  Note: mounts in Cygwin are
> >(currently) persistent.
> >   Igor
>
> Does the selection of unix / dos at installation time actually make any
> difference?

Not currently, AFAIK (in a sense that if you plan to set all mounts to
binary eventually, you may do so either at install time, or later via the
'mount' command).  It may make a difference for postinstall scripts and
the like, though.

> Can't everything be redefined later via the mount command?

Yes, it can.  I've posted the exact incantation to the list a few times --
searching the archives for "remount binary" should unearth at least one.

> I selected DOS at install time, is there an advanteage to installing in
> unix mode?

It makes your files look like Unix files, which helps if you need to
transfer them back and forth between Cygwin and a Unix machine, or use
utilities that expect only binary mounts (e.g., X is notorious for missing
the O_BINARY attribute when opening files, so /tmp and the fonts directory
have to be binary-mounted under Cygwin if you want to use it).  Most
Cygwin packages are tested in mixed mount mode environments, however, and
most maintainers will accept reports of wrong behavior on text mounts as
bug reports (and try to fix them).

> I am encountering different behaviour between a few machines with
> regards to CR LFs. I am trying to work my way through it but it is quite
> perplexing! I need to do more investigations in order to ask a decent
> question, but do the mount settings effect the behaviour of any
> non-cygwin application? I would not expect any effect, is that so?

Non-Cygwin applications don't see Cygwin mounts, so these settings by
themselves should not affect non-Cygwin applications.  However, if you're
using a *mix* of Cygwin and non-Cygwin apps, the Cygwin apps in the mix
*will* be affected (i.e., they may write the files differently), and that,
in turn, may affect the non-Cygwin ones.

> Thanks,
> Jason

HTH,
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
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: CVS on Windows OS, under Cygwin: incompatibility with textmode

2004-01-10 Thread Larry Hall 
At 09:43 PM 1/9/2004, Agosta, John M you wrote:

>(w/ cross posting to gnu.cvs.help)
> 
> 
>I set up the CVS (1.11.6-3) port to Windows that comes in Cygwin.
>Everything worked fine, except checking out files with CVS was adding
>extra lines to files -- under some circumstances---checked-out files had
>the Windows \r\n line termination changed to \r\r\n. 
> 
>It appears to be an interaction between Cygwin and CVS. Using a Cygwin
>port of a Unix shell appears to be necessary to running a command-line
>CVS client from Windows---using the windows cmd prompt to run CVS gave
>me errors.  The configuration is simple.  The archive is a remote file
>system mounted on the client windows machine.  All commands are run on
>the client with CVSROOT pointing to the archive directory on the remote.
>
> 
>Here were the clues: The problem only appeared on one of two apparently
>identical client machines. The archive files themselves were not
>corrupted. All profile, install scripts, environment variables were
>identical on both machines, but the mount command showed that the
>mis-functioning machine mounted its directories in textmode, and the
>functioning machine in binmode. Since there is no equivalent fstab file
>in Cygwin, this configuration is read from in the Windows registry at
>boot time. (See http://cygwin.com/cygwin-up-net/using.html#MOUNT-TABLE.)
>The registry configuration is the first step in the Cygwin
>setup.exe---It can be modified by re-running setup  and choosing default
>text file type == UNIX (without re-installing any files). 
> 
>Users who choose this setting will have to accept not being able to open
>files saved by Cygwin commands (e.g. cat) in Windows notepad.
>Fortunately most Windows applications (MS Word, VS6) have no problem
>interpreting line breaks in unix style text files. 
> 
>I suppose that CVS is conservative when it archives files, and does not
>"unixify" them, but interacts with Cygwin to modify them on checkout.
>Is is possible to configure cvs to treat import and checkout
>consistently when Cygwin mounts directories in textmode?


IIRC, no.  There's history on this in the Cygwin email archives, if you're 
interested.  It's a PTC  situation for the 
CVS code.


--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
838 Washington Street   (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: Ncurses prob

2004-01-10 Thread Larry Hall 
At 11:19 PM 1/9/2004, Paul-Kenji Cahier you wrote:
>hello again,
>
>
>new question now, since every lib compiled well i went to the main
>program and it cant find the new lib i just compiled, so i was
>wondering what is it looking for when one does -lnameofthelib
>cuz on my linux box everything goes fine, and i've checked the include
>which are exactly the same
>
>
><05:11:07> [EMAIL PROTECTED]:/home/calendar/src$ make
>gcc -g -Wall -ansi -pedantic -Wwrite-strings -Wshadow -Waggregate-return -I. 
>-I/home/calendar/include -I/usr/local/include/ncurses -I/usr/local/include 
>-L/usr/local/lib parser.o main.o cal.o   -L/home/calendar/lib -lncurses -loncurses 
>-loxhtml -lotxt -lcal -ldate -o ../main
>/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../../i686-pc-cygwin/bin/ld: cannot find 
>-loncurses
>collect2: ld returned 1 exit status
>make: *** [all] Error 1
>
>
><05:14:57> [EMAIL PROTECTED]:/home/calendar/lib$ ll
>total 210
>drwxrwxrwx+   9 DeathWol None0 Jan 10 05:08 .
>drwxrwxrwx+   8 DeathWol None0 Jan 10 05:14 ..
>drwxrwxrwx+   2 DeathWol None0 Jan 10 04:12 CVS
>-rw-rw-rw-1 DeathWol None  221 Nov 26 11:39 Makefile
>drwxrwxrwx+   3 DeathWol None0 Jan 10 04:48 libcal
>-rwxrwxrwx1 DeathWol None41038 Jan 10 05:04 libcal.so
>drwxrwxrwx+   3 DeathWol None0 Jan 10 04:48 libdate
>-rwxrwxrwx1 DeathWol None29857 Jan 10 05:04 libdate.so
>drwxrwxrwx+   3 DeathWol None0 Jan 10 04:48 libdebug
>-rwxrwxrwx1 DeathWol None26422 Jan 10 05:04 libdebug.so
>drwxrwxrwx+   3 DeathWol None0 Jan 10 05:01 liboncurses
>-rwxrwxrwx1 DeathWol None49859 Jan 10 05:04 liboncurses.so
>drwxrwxrwx+   3 DeathWol None0 Jan 10 05:03 libotxt
>-rwxrwxrwx1 DeathWol None31712 Jan 10 05:04 libotxt.so
>drwxrwxrwx+   3 DeathWol None0 Jan 10 05:00 liboxhtml
>-rwxrwxrwx1 DeathWol None32088 Jan 10 05:04 liboxhtml.so
>


OK, so you don't have liboncurses.a.  That's the problem.  


><05:15:45> [EMAIL PROTECTED]:/home/calendar/include$ ll
>total 23
>drwxrwxrwx+   3 DeathWol None0 Jan 10 04:48 .
>drwxrwxrwx+   8 DeathWol None0 Jan 10 05:14 ..
>drwxrwxrwx+   2 DeathWol None0 Jan 10 04:12 CVS
>-rw-rw-rw-1 DeathWol None 3570 Jan 10 05:14 cal.h
>-rw-rw-rw-1 DeathWol None 2744 Jan 10 05:04 libcal.h
>-rw-rw-rw-1 DeathWol None 1909 Jan 10 05:04 libdate.h
>-rw-rw-rw-1 DeathWol None 1946 Jan 10 05:04 libdebug.h
>-rw-rw-rw-1 DeathWol None  608 Jan 10 05:04 liboncurses.h
>-rw-rw-rw-1 DeathWol None  114 Jan 10 05:04 libotxt.h
>-rw-rw-rw-1 DeathWol None  102 Jan 10 05:04 liboxhtml.h
>-rw-rw-rw-1 DeathWol None 2567 Jan 10 05:14 parser.h
>-rw-rw-rw-1 DeathWol None 5998 Jan 10 05:14 queue.h
>
>
>
>
>
>Most libs were compiled this way:
>
>gcc -g -Wall -ansi -pedantic -Wwrite-strings -Wshadow -Waggregate-return -I. 
>-I/home/calendar/include -I. -I/usr/include -I/usr/include/ncurses 
>-I/usr/local/include -c output.c -o ../liboxhtml.so
>gcc -g -shared -o ../liboxhtml.so.dll -Wl,--export-all-symbols 
>-Wl,--enable-auto-import -Wl,--whole-archive ../liboxhtml.so -Wl,--no-whole-archive 
>-L/home/calendar/lib -L/usr/lib -lintl -lncurses
>cp liboxhtml.h /home/calendar/include
>cp ../liboxhtml.so.dll ../liboxhtml.so (i added this line later to
>check it wasnt a prob with filenames but it wasnt)


Why are you naming the files *.so?  These aren't shared libraries in the 
traditional UNIX sense.




--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
838 Washington Street   (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: Updated: man-1.5k-2

2004-01-10 Thread Peter J. Stieber 
Steve Kelem wrote:
>>I installed this version, and I still get the ESC characters.
>> Do you have any idea why I'm getting them?

Larry Hall wrote:
> Does '/usr/share/misc/man.conf' contain this line?
>
> PAGER   /usr/bin/less -isrR

I updated to man-1.5k-2 too and my '/usr/share/misc/man.conf' contains

PAGER   /bin/less -is

I don't get ESC chars because I setup the fix posted on this mailing list
prior to the fix being provided in the man package. I think it was add the
following to .bashrc.

export LESS=R
export MANPAGER=less

HTH,
Pete


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

dig on cygwin

2004-01-10 Thread Steve 
Hi;

I noticed that dig was not in my cygwin at work ( win2k box ).

I didn't see it on the page brought up on the "software" link on the 
cygwin web site.

Googling around I saw a windows port that looked a bit different.  I 
also found some *old* usenet posts about having to compile it yourself.

I just learned about this tool.

Before I use the other options above I thought I would ask if dig is in 
cygwin but rolled into another package under another name.

Thanks for any tips

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/

Re: dig on cygwin

2004-01-10 Thread Brian Dessent 
Steve wrote:

> I noticed that dig was not in my cygwin at work ( win2k box ).
> 
> I didn't see it on the page brought up on the "software" link on the
> cygwin web site.
> 
> Googling around I saw a windows port that looked a bit different.  I
> also found some *old* usenet posts about having to compile it yourself.
> 
> I just learned about this tool.
> 
> Before I use the other options above I thought I would ask if dig is in
> cygwin but rolled into another package under another name.

I don't belive dig is included in any Cygwin package.  But ISC BIND
supports windows and one of the downloads you can get is the set of
command-line tools, which includes dig.  So just install that somewhere
in the path and you're good to go.  At least that's what I do.

Brian

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