From owner-freebsd-questions@FreeBSD.ORG Wed Mar 10 15:02:56 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E923E16A4CE for ; Wed, 10 Mar 2004 15:02:56 -0800 (PST) Received: from hosea.tallye.com (joel.tallye.com [216.99.199.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D50543D31 for ; Wed, 10 Mar 2004 15:02:52 -0800 (PST) (envelope-from lorenl@alzatex.com) Received: from hosea.tallye.com (hosea.tallye.com [127.0.0.1]) by hosea.tallye.com (8.12.8/8.12.10) with ESMTP id i2AN2lWj011512 for ; Wed, 10 Mar 2004 15:02:47 -0800 Received: (from sttng359@localhost) by hosea.tallye.com (8.12.8/8.12.10/Submit) id i2AN2lcq011510 for freebsd-questions@freebsd.org; Wed, 10 Mar 2004 15:02:47 -0800 X-Authentication-Warning: hosea.tallye.com: sttng359 set sender to lorenl@alzatex.com using -f Date: Wed, 10 Mar 2004 15:02:47 -0800 From: "Loren M. Lang" To: FreeBSD Mailing list Message-ID: <20040310230247.GA10942@alzatex.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zYM0uCDKw75PZbzx" Content-Disposition: inline User-Agent: Mutt/1.4.1i X-GPG-Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc X-GPG-Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C Subject: GCC 3.3 seg faulting X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Mar 2004 23:02:57 -0000 --zYM0uCDKw75PZbzx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I've recently installed FreeBSD 5.2.1 on an old system, mainly since I need bluetooth support. After trying to install a couple of ports, I've found that the default gcc compiler version 3.3.3-20031106 keeps segment faulting at different times. If I keep restarting the port install, it will eventually complete, but slowly. I can't seem to find and reports about this, but I'd like to try and fix it by installing a newer gcc from the ports collection. Since gcc is also part of the core system, that means I'll end up with too version of gcc, will this be a problem and is there an easy way to make sure that the right version of gcc is executed? --=20 I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C =20 --zYM0uCDKw75PZbzx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAT56X+vN6RuSjKAwRAsDFAJ9ljdVh8kM0f7JdyBhiaw1pu2jevwCfZ/4k OhCu7CQgWGrz2PtULOEIUXs= =Pt54 -----END PGP SIGNATURE----- --zYM0uCDKw75PZbzx--