From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.43) id 1DzdiK-0004i2-Ku for garchives@archives.gentoo.org; Mon, 01 Aug 2005 17:04:33 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j71H33KR014626; Mon, 1 Aug 2005 17:03:03 GMT Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.201]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j71H32cq021218 for ; Mon, 1 Aug 2005 17:03:03 GMT Received: by wproxy.gmail.com with SMTP id i23so854665wra for ; Mon, 01 Aug 2005 10:03:13 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=C2XCH5ASJuDTM3O7tbEnVROpDMBlayL7KAmia/89KqK5nYaS3tqLwM0YE7FsL5cExN6hB81gXPCC3S5NXvJ/7JEGS3MuFNPkVdxKBMp+k24WZbvMn0xuYxMJqkxyKT9dBTKrl5T2aCaVI9Y3nPb9iMfVpdlZagYBxID74irnii8= Received: by 10.54.143.10 with SMTP id q10mr3014335wrd; Mon, 01 Aug 2005 10:03:13 -0700 (PDT) Received: by 10.54.7.24 with HTTP; Mon, 1 Aug 2005 10:03:13 -0700 (PDT) Message-ID: Date: Mon, 1 Aug 2005 10:03:13 -0700 From: Karol Krizka To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] Re: Re: x86_64 optimization patches for glibc. In-Reply-To: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: <42E258A7.5080501@telia.com> <42E55ADB.8030201@telia.com> <200508011105.14688.janjitse@gmail.com> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by robin.gentoo.org id j71H32cq021218 X-Archives-Salt: 57fda4c0-4fb6-4556-9f2c-f24152040238 X-Archives-Hash: c7f40d849cb649d73f7cf54c8a2eaa66 On 8/1/05, Duncan <1i5t5.duncan@cox.net> wrote: > Jan Jitse Venselaar posted <200508011105.14688.janjitse@gmail.com>, > excerpted below, on Mon, 01 Aug 2005 11:04:38 +0200: > > > As the reporter of the problem with nano, I'd like to make 1 correction to > > this report: Recompiling nano and its depencies did not fix the crashes. It > > just fixed the eating of the file. > > Thanks for the correction. > I am just compiling my amd64 laptop from stage1 again, but this time I applied the patches right in the beginning. Nano seems to run fine so far (in chroot), so how do you get the crashes? I tried searching as mentioned in the abose post. > > I did not recompile my entire system, but a crash of such a small and basic > > app as nano made me not want to do this outside of a chroot, which I > > currently do not have the means for. > > A rather good point. Of course, some of us like living on the edge , > but it's still something I'd not add as a dev, certainly not unless it was > linked to some sort of local > USE=this-might-kill-your-children-and-eat-their-flesh type of USE flag! > > (OK, s/children/files/, s/their-flesh/your-disk/, but you get the point...) > > Never-the-less, I added the strings patch here, and have the new KDE 3.4.2 > stuff at least, compiled against it... Computing is my hobby; if I > wanted something that would predictably "just work", I'd be doing TiVos or > the like! Much of the fun is the occasional breakage in mysterious ways, > never knowing quite when it'll happen, and the challenge of figuring out > how to get back to a working system, again! > So if you wanted something to just work you would be running Linux on TiVo? I think a intel computer would be better for that... > -- > Duncan - List replies preferred. No HTML msgs. > "Every nonfree program has a lord, a master -- > and if you use the program, he is your master." Richard Stallman in > http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html > > > -- > gentoo-amd64@gentoo.org mailing list > > -- Cheers, Karol Krizka -- gentoo-amd64@gentoo.org mailing list