From owner-freebsd-stable Wed Mar 7 1:11:33 2001 Delivered-To: freebsd-stable@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 ED0CC37B719 for ; Wed, 7 Mar 2001 01:11:29 -0800 (PST) (envelope-from ohartman@klima.physik.uni-mainz.de) Received: from klima.Physik.Uni-Mainz.DE (klima.Physik.Uni-Mainz.DE [134.93.180.162]) by klima.physik.uni-mainz.de (8.11.3/8.11.3) with ESMTP id f279Epb92516; Wed, 7 Mar 2001 10:14:52 +0100 (CET) (envelope-from ohartman@klima.physik.uni-mainz.de) Date: Wed, 7 Mar 2001 10:14:51 +0100 (CET) From: "Hartmann, O." To: Kris Kennaway Cc: Subject: Re: ARCH flag in new make.conf In-Reply-To: <20010307010024.A98154@mollari.cthul.hu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 7 Mar 2001, Kris Kennaway wrote: Dear Kris. I asure you: the only flag was -march=i686 and -O on both kernel and system code flags. The phenomenon was that a local ypbind couldn't contact the local or any remote ypserver and it disappeared exactly then when removing the i686 option (and not changing anything else!). Well, I tried nearly everything for about one week and only removing this flag helped. I will do this again, maybe it was a phenomenon on "moving" code from 4.2 to 4.3? I do not know ... I would only mention this here because it pushed me in trouble nobody could help me for the past days. Thank you for responding. :>On Wed, Mar 07, 2001 at 09:30:33AM +0100, Hartmann, O. wrote: :>> Dear Sirs. :>> :>> I'm really confused and surprised by the fact, that with the upcoming new :>> FreeBSD 4.3 in its make.conf we can choose architectural parameters for the :>> CPU architecture. And I will tell you why. :>> :>> Due the last two weeks, that was in fact in the time of FreebSD 4.2, but :>> I think it doesn't matter, I compiled on three SMP system ( one 2x PII 350MHz, :>> one 2x PIII 600MHz KATMAI, one 2x PIII 866MHz Coppermine) the whole stuff :>> with the compiler option -march=i686 on both the kernel compilation option :>> field and the system code optimization field. The result was a completely :>> malfunctional NIS/YP system! I thank Mr. Jan Conrad from University of Bonn :>> who spent more than three hours with me on telephon to checkout what's going :>> wrong on FreeBSD because he used a functional NIS/YP installation - and at mine :>> the cheapest, simplest configuration would work. I do not know exactly which :>> compiler switches the new flag targets, either this for the source code or that :>> for the kernel and I do not know which compiler option, either for kernel or the system, :>> killed the NIS/YP functionality. Fact is - after removing on both optimization :>> fields NIS/YP works well! :> :>I've been running NIS on FreeBSD with world and kernel compiled with :>-march=pentiumpro for about 9 months with no ill effects. In fact :>I've never heard of reports of bad code generation using the -march :>settings -- it appears to be very stable. Are you sure you didn't :>have a nonstandard optimization setting (-O2, etc) as well? :> :>Kris :> -- 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-stable" in the body of the message