Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!samsung!olivea!mintaka!bloom-beacon!eru!hagbard!sunic!mcsun!cernvax!chx400!bernina!wild
From: wild@nessie.cs.id.ethz.ch (Markus Wild)
Newsgroups: comp.unix.amiga
Subject: Re: Problem with gcc
Keywords: gcc unix library amiga
Message-ID: <1991May22.093515.3008@bernina.ethz.ch>
Date: 22 May 91 09:35:15 GMT
References: <1991May19.144743.25904@nntp-server.caltech.edu> <1991May21.045217.19569@csusac.csus.edu>
Sender: news@bernina.ethz.ch (USENET News System)
Organization: Swiss Federal Institute of Technology (ETH), Zurich, CH
Lines: 26
Nntp-Posting-Host: nessie

In article <1991May21.045217.19569@csusac.csus.edu> emmonsl@athena.ecs.csus.edu (L. Scott Emmons) writes:
>In article <1991May19.144743.25904@nntp-server.caltech.edu> tll@nntp-server.caltech.edu (Tal Lewis Lancaster) writes:
>The only way I could get socket stuff to work on my UX was to make sure that
>/usr/ucb was in the path before /usr/ccs.  Also you need to execute gcc
>thusly:
>
>	gcc -o file file.c -lsocket -lucb
>			   ^^^^^^^^ ^^^^^

You are asking for troubles at the moment including -lucb... Besides,
gcc normally doesn't use /usr/ucbinclude (unless you tell it with
-Iucbinclude), and if you link with -lucb you might get unexpected
results due to incompatible headers with the libraries you use. In my
experience, the less I had to use from -lucb, the higher was the chance
to get a working executable in the first run;-)
So I'd strongly plea for having /usr/ccs/bin BEFORE /usr/ucb in your
path.

-Markus



-- 
Markus M. Wild    - mwild@iiic.ethz.ch  |  wild@nessie.cs.id.ethz.ch
--
Still looking for a REAL debugger for Release 4 ...