From: Scott Schwartz <schwartz@bio.cse.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Few silly ones..
Date: Mon, 23 Dec 2002 23:16:00 -0500 [thread overview]
Message-ID: <20021224041600.14310.qmail@g.bio.cse.psu.edu> (raw)
In-Reply-To: Message from Ish Rattan <ishwar@pali.cps.cmich.edu> of "Mon, 23 Dec 2002 22:49:07 EST." <Pine.LNX.4.50.0212232245410.23027-100000@pali.cps.cmich.edu>
> /386/bin/gnu/gcc
> but is not found when gcc is invoked
rc has nicer path searching rules than sh: it searches for relative paths,
so you can use directories as prefixes to package binaries in groups.
Thus, you can say "gnu/gcc" to run the program. Or you can add /bin/gnu
to your $path. :)
next prev parent reply other threads:[~2002-12-24 4:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ishwar@pali.cps.cmich.edu>
2002-12-24 3:49 ` Ish Rattan
2002-12-24 4:16 ` Scott Schwartz [this message]
2002-12-24 4:16 ` Russ Cox
2002-12-24 4:24 a
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=20021224041600.14310.qmail@g.bio.cse.psu.edu \
--to=schwartz@bio.cse.psu.edu \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).