Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!rutgers!usc!julius.cs.uiuc.edu!ux1.cso.uiuc.edu!ux1.cso.uiuc.edu!olson From: olson@sax.cs.uiuc.edu (Bob Olson) Newsgroups: comp.sys.next Subject: Re: Installing f2c on the NeXT Message-ID: Date: 2 Jan 91 18:00:44 GMT References: <1991Jan2.095723.16706@wuphys.wustl.edu> Sender: news@ux1.cso.uiuc.edu (News) Organization: University of Illinois, Urbana-Champaign Lines: 34 In-Reply-To: rdd@wuphys.wustl.edu's message of Wed, 2 Jan 91 09:57:23 GMT In article <1991Jan2.095723.16706@wuphys.wustl.edu> rdd@wuphys.wustl.edu (Rakhal D. Dave) writes: 1. How to get the computer to recognize an addition to /bin without rebooting. Do a "rehash". 2. Why doesn't root recognize a.out. Because as supplied, the PATH variable for root does not include the current directory ".". Try ./a.out. 3. What corresponds to /usr/lib/libc.a on the NeXT. Why do my programs compiled as above work without linking libc.a as requested by the remark lines in the translated C program prog.c . /lib/libsys_s.a, /usr/lib/libNeXT.a for the appkit stuff. You don't need to explicitly include libsys because the compiler does that for you. 4. Apparently the only pieces that are useful are f2csrc/f2c, f2csrc/f2c.h, LibF77/libF77.a and LibI77/libI77.a . After these are manufactured by "make" and installed in different directories as described above, it seems that the remaining stuff, that is the contents of directory /f2c may be thrown away. Yes, I would imagine that is fine. 5. Any information on the warning messages displayed while "make"ing f2c. Here is the portion of messages displayed while "make"ing f2c which are worrisome. You shouldn't have to worry, these are just warning messages from the compiler.