From owner-freebsd-questions@FreeBSD.ORG Wed Jun 11 17:09:44 2008 Return-Path: Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C3661065675 for ; Wed, 11 Jun 2008 17:09:44 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (unknown [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id CA3828FC1C for ; Wed, 11 Jun 2008 17:09:43 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.1/8.14.1) with ESMTP id m5BH9g12064403; Wed, 11 Jun 2008 19:09:42 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.1/8.14.1/Submit) id m5BH9g7K064402; Wed, 11 Jun 2008 19:09:42 +0200 (CEST) (envelope-from olli) Date: Wed, 11 Jun 2008 19:09:42 +0200 (CEST) Message-Id: <200806111709.m5BH9g7K064402@lurza.secnetix.de> From: Oliver Fromme To: freebsd-questions@FreeBSD.ORG, parish@magichamster.com In-Reply-To: <20080604232434.GA5456@osiris.chen.org.nz> X-Newsgroups: list.freebsd-questions User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.2-STABLE-20070808 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 11 Jun 2008 19:09:42 +0200 (CEST) Cc: Subject: Re: Effects of CPUTYPE X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@FreeBSD.ORG, parish@magichamster.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2008 17:09:44 -0000 Jonathan Chen wrote: > Mark Ovens wrote: > > Trying to identify why I should be having all these problems I've been > > looking for anything that may be specific to my machine. One thing I've > > come up with is the fact that I have CPUTYPE?=athlon-mp in > > /etc/make.conf on both 6.3 and 7.0. > > In my personal opinion, the small gain you get is more than > overwhelmed by the big pain you get from setting CPUTYPE. I'm setting CPUTYPE on all of my machines for many years, without the slightest problems. No pain at all. They're all kinds of different processors, c3-2 (VIA), athlon64, and so on. In some cases the difference is very noticable. Having said that, it's certainly worth trying whether your problems are gone when you compile without that setting. Do you have any other unusual settings, such as non-standard CFLAGS or anything? BTW, I once was bitten by a similar problem, when building software failed in strange ways, it turned out I had a bad variable in my environment that was picked up by some build scripts. Maybe it's worth a try to run your ports builds with a clean environment ("env -"), or try to install binary packages instead of building ports yourself, in order to narrow down where the problem is. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "Python tricks" is a tough one, cuz the language is so clean. E.g., C makes an art of confusing pointers with arrays and strings, which leads to lotsa neat pointer tricks; APL mistakes everything for an array, leading to neat one-liners; and Perl confuses everything period, making each line a joyous adventure . -- Tim Peters