Path: utzoo!attcan!uunet!lll-winken!arisia!sgi!scotth@harlie.SGI.COM From: scotth@harlie.SGI.COM (Scott Henry) Newsgroups: comp.sys.amiga Subject: Re: Manx C from harddisk? Message-ID: <23905@sgi.SGI.COM> Date: 22 Dec 88 01:50:04 GMT References: <1219@tank.uchicago.edu> Sender: daemon@sgi.SGI.COM Distribution: na Organization: Silicon Graphics, Inc., Mountain View, CA Lines: 39 From article <1219@tank.uchicago.edu>, by arxt@sphinx.uchicago.edu (patrick palmer): > > I have been installing Manx c compiler on my harddisk, and I cannot seem to > get it right. (I was so furious last night that I waited until morning to > [deleted stuff] > I would greatly appreciate any hints about a correct - and efficient while > we are at it - setup for using Manx C from a hard disk under 1.3. > > Pat Palmer email: ppalmer@oddjob.uchicago.edu It's actually very simple. Manx doesn't care about what is ASSIGN'ed where, it only cares about where the environment points, and that the binaries are in your path. Let's say you have set up things as: DH0:manx/bin DH0:manx/lib DH0:manx/include ... etc. (those are the important ones), where the directory contents should be self-explanatory(??), and they can contain EVERYTHING from similarly named directories on all of the Manx distribution disks (SYS1:, SYS2:, ...). The following set of commands will set things up: path DH0:manx/bin add dh0:manx/bin/set INCLUDE=DH0:manx/include/ DH0:manx/bin/set LIBS=DH0:manx/bin/lib ... Other SET's as appropriate to your system. (I hope I got the names and syntax correct, I'm doing it from memory). Mine has been set up this way for months, and working fine the whole time. If you are still having problems, e-mail me and maybe we can figure it out. Scott Henry #include -- Scott Henry {or, also on the Internet:} #include