Return to BSD News archive
Xref: sserve comp.unix.bsd:8514 comp.os.linux:17599 Newsgroups: comp.unix.bsd,comp.os.linux Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.hawaii.edu!ames!saimiri.primate.wisc.edu!usenet.coe.montana.edu!news.u.washington.edu!serval!hlu From: hlu@eecs.wsu.edu (H.J. Lu) Subject: gcc 2.3.2 is broken (Re: [386bsd] gcc-2.3.1 and XFree86-1.1 compile) Message-ID: <1992Dec1.191216.1021@serval.net.wsu.edu> Sender: news@serval.net.wsu.edu (USENET News System) Organization: School of EECS, Washington State University References: <veit.723126991@du9ds3> <JKH.92Nov30231404@whisker.lotus.ie> <veit.723200307@du9ds3> Date: Tue, 1 Dec 92 19:12:16 GMT Lines: 18 In article <veit.723200307@du9ds3>, veit@du9ds3 (Holger Veit) writes: [...] |> Oh, yes, you may be right. I forgot something: You didn't have also compiled |> new libc.a and libm.a with 2.3.1, did you? The old libc.a does not have the |> assert function/macro mapped to the _eprintf builtin. |> |> The problem will occur if you want to have all software coded by 2.3.1/2.3.2 |> on your machine. BTW: 2.3.2 also has this effect. |> |> Holger |> FYI, gcc 2.3.2 is broken. Please wait for gcc 2.3.3. H.J.