This is the mail archive of the
mailing list for the Cygwin project.
Re: cygwin 1.1.2: undefined reference to `setlinebuf'
- To: Earnie Boyd <earnie_boyd at yahoo dot com>
- Subject: Re: cygwin 1.1.2: undefined reference to `setlinebuf'
- From: Adam Schlegel <aceschle at thinkage dot ca>
- Date: Fri, 9 Jun 2000 10:25:17 -0400 (EDT)
- cc: tsfu at graduate dot hku dot hk, cygwin at sourceware dot cygnus dot com, jason_fu at hkmc dot com dot hk
On Fri, 9 Jun 2000, Earnie Boyd wrote:
> *IMPERITIVE* /usr/bin must be *first* in the list for PATH.
This may be a stupid question, but why does /usr/bin have to be *first*?
Is it not sufficient to have it somewhere near the front of your path, so
that there is the possibility that certain programs can override the
default ones. For example, I like to maintain a ~/bin directory at the
start of my path so that I can easily stress-test programs that I am
building, without adding them to /usr/bin or /usr/local/bin. Does this
break something that I haven't noticed yet? Or is it just a bad habit that
I should break as soon as possible?
Want to unsubscribe from this list?
Send a message to email@example.com