Path: utzoo!utgpu!attcan!uunet!dino!ux1.cso.uiuc.edu!bach.csg.uiuc.edu!kubiak
From: kubiak@bach.csg.uiuc.edu (Ken Kubiak)
Newsgroups: unix-pc.general
Subject: g++/gcc on unixpc
Summary: gcc asks for -lg++ -lc
Message-ID: <1989Oct16.143219.29485@ux1.cso.uiuc.edu>
Date: 16 Oct 89 14:32:19 GMT
Sender: news@ux1.cso.uiuc.edu (News)
Reply-To: kubiak@bach.csg.uiuc.edu.UUCP (Ken Kubiak)
Distribution: unix-pc.general, gnu.gcc.bug
Organization: Univ of Illinois at Urbana-Champaign
Lines: 36

I've been trying to build g++ (near-1.36 version from labrea) on the unixpc.
I began by using the 1.36 gcc compiler avaliable from cheops.  Since g++
requires the gcc .o files anyway, Istarted rebuilding gcc 1.36 myself using
gcc 1.35 (which I built earlier using the gcc 1.30 compiler from umn ?).
Anyway, the problem I have with gcc 1.36 on the unixpc applies to both the 
binaries from cheops and the first-level binary I built.

When gcc is called as a loader (i.e., with a bunch of .o's), I get an error:

*** ld: command line *** -l can't find /libc.a
*** ld: command line *** -l can't find /libg++.a

Two questions:  (1) why is it looking for these?  Doesn't it just need gnulib?
                (2) why can't it find libc.a anyway?  

By the way, I edited the linker spec in gcc.c so as not to put -lc and -lg++
on the line, but then I have a bunch of undefineds, like "exit" and "fprintf"
w/o leading underscores.

I suppose I can use ld directly, but I'm curious about this problem.
Perhaps the kind person who built the 1.36 binary on cheops can give be a hint
on how he/she got past stage1.

Of course, if anybody has already built g++ for the unix-pc (aka 3b1, 7300),
that would save me a lot of headache.  If so, perhaps we could have the
binaries posted to cheops.


Thanks in advance,
Ken Kubiak
kubiak@csg.uiuc.edu

Ken Kubiak
Computer Systems Group
University of Illinois at Urbana-Champaign
kubiak@csg.uiuc.edu