Date: Tue, 20 Mar 2001 10:22:34 -0500 (EST) From: Andrew Gallatin <gallatin@cs.duke.edu> To: naddy@mips.inka.de (Christian Weisgerber) Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: How serious are we about ccc? Message-ID: <15031.30138.214213.123377@grasshopper.cs.duke.edu> In-Reply-To: <99656d$hgs$1@kemoauc.mips.inka.de> References: <99656d$hgs$1@kemoauc.mips.inka.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Christian Weisgerber writes: > Do we consider ccc (ports/lang/compaq-cc) just a curiosity and > squarely put the blame on ccc if something doesn't build with it, > or do we want ccc do have a modicum of usefulness? No. Yes(*) Yes. (*) But it might be fixable, via comp.config. > Lest this be misunderstood, I'm merely asking an honest question. > I recently built the mawk port with ccc, which works. Today I've > tried Ogg Vorbis. Libtool doesn't handle building shared libraries > with ccc (which I would assume to be a configuration issue) and > the compiler dies on some of our system header files, which I > haven't examined yet. Is there any worth in investigating these > problems? Yes, very much so. The gnu compiler is terrible on the alpha platform. Not only does it produce slow code, it produces broken code and/or crashes at even modest optimization levels. Wrt dying on the system header files, I assume you are aware of how to setup the comp.config so that it searches ccc specific versions of our header files prior to looking in /usr/include? Check out /usr/lib/compaq/ccc-($version)/alpha-linux/bin/comp.config Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15031.30138.214213.123377>