|
|
$
I am having a really lot of difficulty setting the paths on this one. There is never, never an automatically installed path to a newly installed make. Man files on newly installed apps do not respond to the "man" command. I had to resort to writing full paths with aliases in the ".tcshrc" ~ file. For some reason, Jaguar just does not accept any path I write. I have never had this problem in Linux, BSD, or Darwin. Even with aliases, I had to write, save, rehash, rewrite, etc five times before I could get Nano, Vim, and mc to launch. No paths...., just aliases. The terminal just ignores written paths. Believe me, I have read all I could read on paths in the FreeBSD handbook, Unix for OS X, The Missing Manual, etc..... Nothing works.
$
This is what I have included in my .tcshrc, and it works fine.
$
When I used the ./Configure command this is what it returned:
./configure problems
I'm guessing from error message that that you don't have the Developer tools installed? You'll need them to compile.
$
Looks like we got some interesting problens here. I think I'll take a trip into BASHland via the "chsh" command and see what I can do with ba$h with which I am much more familiar.
$
No..., it doesn't work. The man pages are there in /usr/local/man and /usr/share/man but adding the path has no effect at all. Oh well! If this keeps up I am going back to bash $$$$$$ and dumping the %%%%%%%%% :):):)
$
I went to BASH. I no longer have any problems setting paths. I am beginning to believe that tcsch sucks. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.18 seconds |
|