From owner-freebsd-current@FreeBSD.ORG Fri Sep 9 09:55:26 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B75BC1065670; Fri, 9 Sep 2011 09:55:26 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 36B8B8FC15; Fri, 9 Sep 2011 09:55:25 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p899tL5p070891 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 9 Sep 2011 12:55:21 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p899tLdN049257; Fri, 9 Sep 2011 12:55:21 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p899tLUN049256; Fri, 9 Sep 2011 12:55:21 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 9 Sep 2011 12:55:21 +0300 From: Kostik Belousov To: Oliver Lehmann Message-ID: <20110909095521.GX17489@deviant.kiev.zoral.com.ua> References: <20110909113046.Horde.MHKEMKQd9PdOadzGA0vRXXA@avocado.salatschuessel.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dGpy7zMmU3HloscK" Content-Disposition: inline In-Reply-To: <20110909113046.Horde.MHKEMKQd9PdOadzGA0vRXXA@avocado.salatschuessel.net> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: Chris Rees , freebsd-current@freebsd.org, Mike Tancsa Subject: Re: cvsup broken on amd64? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Sep 2011 09:55:26 -0000 --dGpy7zMmU3HloscK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 09, 2011 at 11:30:46AM +0200, Oliver Lehmann wrote: >=20 > Chris Rees wrote: >=20 > >On 9 September 2011 06:33, Oliver Lehmann wrote: > >>I got used to it in the past 12 years? But this is not realy the questi= on. > >>If it is "BROKEN" it should be marked as BROKEN or there should be a > >>statement that it will not work with FreeBSD 9 on at least amd64 or we > >>will have other users complaining about the same at least when > >>9.0 RELEASE is out - right? > > > >The cvsup port is normally used now only for cvsupd, for which there > >is no csupd analog. As far as I know, and perhaps mux (CC'd) could > >confirm every feature present in cvsup is present in csup-- and it's a > >fair amount faster too. >=20 > Ok, but this again is not the point of my email ;) > This is not about "just me". I know how to help me in that case. I want > to prevent users facing the same problem and writing mails like my initial > mail. > I'm quiet sure that there are numerous users out there still using cvsup > as client so they will start like me with cvsup on ther new instaled syst= em. > It would be better if they just would not be able to install cvsup if it > will not run and we don't want it to run. > I was also curious if it is only me where it fails on amd64 or if it is > because it was compiled on an Atom 330 with some amd64 flags determined by > the system which does not fit the Atom 330 (gcc 4.2 is older than the CPU > design). > With other words: If the support for cvsup on amd64 is dropped, it has > to be marked as BROKEN/IGNORE/whatever. Otherwise it need to get fixed for > 9.0? For start, you should provide the information what exactly is the instruction that caused the fault. Show the disassembly from gdb for the function that caused the fault. --dGpy7zMmU3HloscK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk5p4ogACgkQC3+MBN1Mb4g4BgCfVOxElwAeHLlCDjKiuF6rgRtt ZEoAn0xNaGxDtOESb1/Xsd7UkBSr6SwD =Qckp -----END PGP SIGNATURE----- --dGpy7zMmU3HloscK--