From: Wally Kramer <wally@steptech.com>
To: 'Randall R Schulz' <rrschulz@cris.com>, sourcenav@sources.redhat.com
Subject: RE: Question about the snavigator compliation under win98
Date: Mon, 18 Mar 2002 11:12:00 -0000 [thread overview]
Message-ID: <26F9F6EAB586D411850700B0D049E6E410BE03@shasta.pdx.steptech.com> (raw)
As far as we can tell, using "dos mode" instead of "unix mode" only affects
the Cygwin as to (respectively) translate CF/LF into LF when accessed by the
Cygwin utilities--or not. That is, dos mode makes the cygwin implied file
system mounts "textmode" instead of "binarymode".
Doing this should not threaten one's purity, wholesomeness or faith. But it
does allow source navigator's "configure" to detect the presence of MSVC++,
various header files, library functions, etc.
Theoretically, one could set default options for grep, flex, etc. to
accomplish the same thing, but this is significantly harder than just
setting the filesystem to textmode. Why *wouldn't* you want to do that?
-----Original Message-----
From: Randall R Schulz [mailto:rrschulz@cris.com]
Sent: Monday, 18 March 2002 09:09
To: Bruce Edson; Wu Fan; sourcenav@sources.redhat.com
Subject: RE: Question about the snavigator compliation under win98
Bruce, Wu,
Many Cygwin users are going to be unwilling to use "DOS-mode" mounts (I
know I am).
Perhaps these grep options would help (from the output of "grep --help"):
-U, --binary do not strip CR characters at EOL (MSDOS)
-u, --unix-byte-offsets report offsets as if CRs were not there (MSDOS)
Randall Schulz
Mountain View, CA USA
At 08:20 2002-03-18, Bruce Edson wrote:
>Having just run across a similar problem, what we found was that the
>install of Cygwin needs to have the default text file type set as
>'DOS'. If you left it set to 'UNIX', the grep utility works incorrectly
>when interpreting eol characters in DOS.
>
>Bruce
>
>-----Original Message-----
>From: Wu Fan [mailto:wufan@beijing.sema.slb.com]
>Sent: Monday, March 18, 2002 1:46 AM
>To: sourcenav@sources.redhat.com
>Subject: Question about the snavigator compliation under win98
>
>
>Dear supporter:
>
>I am trying to compile the source navigator under win98 platform, according
>to the readme file, would you mail me the
> rational build instructions.
>
>Actually, I have tried many times under win98, it is always cann't found my
>VC6, I have this kind of environment:
>
>c:\cygwin
>c:\progra~1\micros~3\vc98
>c:\snvaigator
>
>PATH=$PATH:/cygdrive/c/progra~1\micros~3\vc98
>
>During it execute the .../snavigator/source/db/configure
>It will report :
>"Checking for the Microsoft VC++ ..." no
>
>Any comments is highly appreciated!!
>
>
>Regards
>
>Wu Fan
next reply other threads:[~2002-03-18 19:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-18 11:12 Wally Kramer [this message]
[not found] <26F9F6EAB586D411850700B0D049E6E410BE03@shasta.pdx.steptech .com>
2002-03-18 11:50 ` Randall R Schulz
[not found] <26F9F6EAB586D411850700B0D049E6E4014D2EDC@shasta.pdx.stepte ch.com>
2002-03-18 11:02 ` Randall R Schulz
-- strict thread matches above, loose matches on Subject: below --
2002-03-18 8:51 Bruce Edson
2002-03-18 8:21 dave.banham
2002-03-18 4:15 Wu Fan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=26F9F6EAB586D411850700B0D049E6E410BE03@shasta.pdx.steptech.com \
--to=wally@steptech.com \
--cc=rrschulz@cris.com \
--cc=sourcenav@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).