Date: Thu, 11 Dec 2008 01:54:32 +1100 From: Horst =?ISO-8859-1?Q?G=FCnther?= Burkhardt III <horst@sxemacs.org> To: FreeBSD PowerPC ML <freebsd-ppc@freebsd.org> Subject: Re: Two issues. One minor, one major. Message-ID: <1228920872.1832.67.camel@horst-tla> In-Reply-To: <20081210141039.GA52605@narn.knownspace> References: <1228910881.1832.63.camel@horst-tla> <20081210141039.GA52605@narn.knownspace>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-etn9vDXkGz2z89LaOu8Z Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Wed, 2008-12-10 at 09:10 -0500, Justin Hibbits wrote: > On Wed, Dec 10, 2008 at 11:08:01PM +1100, Horst G=C3=BCnther Burkhardt II= I wrote: > > .... This is exceedingly disturbing. EXCEEDINGLY disturbing. I kinda > > need Python 2.5 :( >=20 > Have you been compiling everything with altivec support? That would caus= e > illegal instructions for a lot of things, since it's not yet enabled. >=20 > - Justin No no no, I removed the altivec flags to the compiler, make.conf now says : CFLAGS=3D-Os -pipe -mcpu=3D7400 -mtune=3D7400 CCFLAGS=3D-Os -pipe -mcpu=3D7400 -mtune=3D7400 CXXFLAGS=3D-Os -pipe -mcpu=3D7400 -mtune=3D7400 I think those are perfectly reasonable CFLAGS ;) I'm hoping -mcpu=3D7400 does not imply -maltivec here or I'm really screwed :( Irssi compiled with these flags is working perfectly, as is glib, as is perl, etc. Any other ideas?=20 Thanks, --Horst. --=-etn9vDXkGz2z89LaOu8Z Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEABECAAYFAkk/2CgACgkQRtTtv0BbTe5fwACeMV69tIjCjxpx7BARemsn0AA2 2xsAn00qiDyhfaVpO50NHMzJ6HQnF0yn =4Kti -----END PGP SIGNATURE----- --=-etn9vDXkGz2z89LaOu8Z--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1228920872.1832.67.camel>