public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Syd Polk <spolk@baritoneconsulting.com>
To: Bernard Dautrevaux <Dautrevaux@microprocess.com>
Cc: "'Jordan'" <jordan.howarth@cmis.csiro.au>, sourcenav@sources.redhat.com
Subject: Re: At hair pulling stage
Date: Tue, 16 Oct 2001 20:20:00 -0000	[thread overview]
Message-ID: <8092E564-D930-11D5-B62D-0050E4C09301@baritoneconsulting.com> (raw)
In-Reply-To: <17B78BDF120BD411B70100500422FC6309E3A3@IIS000>


On Wednesday, November 14, 2001, at 06:11 , Bernard Dautrevaux wrote:

>> -----Original Message-----
>> From: Jordan [mailto:jordan.howarth@cmis.csiro.au]
>> Sent: Wednesday, November 14, 2001 2:35 AM
>> To: sourcenav@sources.redhat.com
>> Subject: At hair pulling stage
>>
>>
>>
>> + SN 5.0 Windows binaries running on Win2000
>> + CYGWIN internet download last night
>>
>>
>> SNav cannot find "rm", "g++" or any other cygwin based program. It can
>> only find "make". I am assuming that SNav has its own version of make
>> and so doesn't need to go looking for it.
>
> I don't know if SN was compiled for CYGWIN, or as a native WIN32 program
> (tip: look at the DLLs needed by SN; if you don't find cygwin1.dll then 
> SN
> is a pure WIN32 program).
>
> If SN is a pure WIN32 program then he will not be able to find 
> /usr/bin/rm,
> as this file, when viewed from Windows, is "C:\cygwin\usr\bin\rm", 
> assuming
> you installed cygwin in "C:\cygwin" as the installer propose it.

SN is a pure Win 32 program.

>
> You must then put "C:\cygwin\usr\bin" in your Windows path, so that SN 
> will
> be able to find the cygwin tools.
>

This is the correct diagnosis. The path must have Windows pathnames in 
it for SN to work.

> HTH
>
> 	Bernard
>
> PS: Note that with old versions of Cygwin (back to the B20 era), this 
> was
> not a problem as cygwin installed in the C: root directory by default; 
> you
> also can install newer cygwins there, although you get bored by the
> installer that will insist that this is "not recommended", while I never
> understand what the problem may be (and I'm using it installed there 
> without
> any problem for quite a long time).
>
>>
>> /usr/bin is in both my cygwin and windows path, ie. "which rm" yields
>> "/usr/bin/rm".
>>
>> What gives? I thought that SNav would drive of at least one of these
>> paths.  Please help me identify the fix for this error as premature
>> balding is supposed to be a gift from nature not RH.
>>
>> Regards,
>>
>> J.
>>
>>
>> P.S. Please Cc: me directly in the reply as I have not subscribed to
>> the list, yet!
>>
>>
>> --
>> Jordan Howarth				
> mailto:jordan.howarth@cmis.csiro.au
> CSIRO					p: (07) 3375 9632, (07) 3826 7314
> Mathematical and Information Sciences	f: (07) 3826 7304
>
>          -=| For every truth there are a thousand lies |=-
>
>
> --------------------------------------------
> Bernard Dautrevaux
> Microprocess Ingenierie
> 97 bis, rue de Colombes
> 92400 COURBEVOIE
> FRANCE
> Tel:	+33 (0) 1 47 68 80 80
> Fax:	+33 (0) 1 47 88 97 85
> e-mail:	dautrevaux@microprocess.com
> 		b.dautrevaux@usa.net
> --------------------------------------------
>
>
Syd Polk
QA and Integration Manager, Mac OSX Development Tools
+1 408 974-0577

  reply	other threads:[~2001-11-14 18:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-16 19:42 Bernard Dautrevaux
2001-10-16 20:20 ` Syd Polk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-04  1:28 Jordan
2001-10-04  9:47 ` Khamis Abuelkomboz

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=8092E564-D930-11D5-B62D-0050E4C09301@baritoneconsulting.com \
    --to=spolk@baritoneconsulting.com \
    --cc=Dautrevaux@microprocess.com \
    --cc=jordan.howarth@cmis.csiro.au \
    --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).