From owner-freebsd-ports Wed May 23 12:42:47 2001 Delivered-To: freebsd-ports@freebsd.org Received: from klima.physik.uni-mainz.de (klima.Physik.Uni-Mainz.DE [134.93.180.162]) by hub.freebsd.org (Postfix) with ESMTP id 38FBA37B423 for ; Wed, 23 May 2001 12:42:28 -0700 (PDT) (envelope-from ohartman@klima.physik.uni-mainz.de) Received: from klima.Physik.Uni-Mainz.DE (Sturm@klima.Physik.Uni-Mainz.DE [134.93.180.162]) by klima.physik.uni-mainz.de (8.11.3/8.11.3) with ESMTP id f4NJgRT24165 for ; Wed, 23 May 2001 21:42:27 +0200 (CEST) (envelope-from ohartman@klima.physik.uni-mainz.de) Date: Wed, 23 May 2001 21:42:27 +0200 (CEST) From: "Hartmann, O." To: Subject: Ports building problem on AMD based systems! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Dear Sirs. This seems to be a curiosity: We run several serving systems around here, all FBSD 4.3 boxes as cvsupdated 4 days ago. I realized that on all AMD based systems (TBird machines, in /etc/make.conf is CPUTYPE=k7 set) I have problems to compile ports! They compile without problem on all other SMP machines based on Intel PIII or PII chips! xv, mtools and several other reports while patching: which file to patch? This message does not appear on Intel machines with nearly the same configuration. I delete the whole ports tree and cvsupdated it again but the phenomenon is still the same. Does anyone realized this, too? -- MfG O. Hartmann ohartman@klima.physik.uni-mainz.de ---------------------------------------------------------------- IT-Administration des Institut fuer Physik der Atmosphaere (IPA) ---------------------------------------------------------------- Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinensaal) Tel: +496131/3924144 FAX: +496131/3923532 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message