From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: Re: x86_64 optimization patches for glibc.
Date: Mon, 01 Aug 2005 06:45:01 -0700 [thread overview]
Message-ID: <pan.2005.08.01.13.45.00.753382@cox.net> (raw)
In-Reply-To: 200508011105.14688.janjitse@gmail.com
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 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 <g>,
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! <g>
(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!
--
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
next prev parent reply other threads:[~2005-08-01 13:48 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-23 14:48 [gentoo-amd64] x86_64 optimization patches for glibc Simon Strandman
2005-07-23 16:36 ` Allan Wang
2005-07-23 17:08 ` Simon Strandman
2005-07-23 17:30 ` Allan Wang
2005-07-23 18:11 ` Jared Lindsay
2005-07-23 18:19 ` Allan Wang
2005-07-27 10:09 ` netpython
2005-07-27 16:11 ` [gentoo-amd64] " Duncan
2005-07-23 18:44 ` [gentoo-amd64] " Brian Litzinger
2005-07-25 22:24 ` Luke-Jr
2005-07-25 22:38 ` Olivier Crete
2005-07-26 15:40 ` Luke-Jr
2005-07-26 16:50 ` [gentoo-amd64] " Duncan
2005-07-26 17:02 ` Raffaele BELARDI
2005-07-26 17:49 ` Michael Edwards
2005-07-26 18:42 ` [gentoo-amd64] " Duncan
2005-07-27 0:05 ` [gentoo-amd64] " Sami Samhuri
2005-07-27 2:50 ` Matt Randolph
2005-07-26 2:54 ` [gentoo-amd64] " Brian Litzinger
2005-07-23 16:39 ` Sean Johnson
2005-07-23 22:15 ` Matt Randolph
2005-07-23 22:36 ` Matt Randolph
2005-07-24 1:47 ` Sean Johnson
2005-07-24 3:36 ` Matt Randolph
2005-07-24 5:36 ` Ian McCulloch
2005-07-24 7:42 ` Jared Lindsay
2005-07-24 14:35 ` Simon Strandman
2005-07-24 18:13 ` Jared Lindsay
2005-07-25 20:08 ` Jeremy Huddleston
2005-07-25 21:34 ` Simon Strandman
2005-07-25 22:00 ` Jared Lindsay
2005-07-31 14:24 ` [gentoo-amd64] " Duncan
2005-07-31 14:56 ` Brian Hall
2005-07-31 16:23 ` [gentoo-amd64] " Duncan
2005-07-31 17:42 ` Ben Skeggs
2005-07-31 18:46 ` Jared Lindsay
2005-07-31 18:52 ` Nuitari
2005-08-01 13:51 ` [gentoo-amd64] " Duncan
2005-07-31 19:21 ` [gentoo-amd64] " Simon Strandman
2005-08-01 9:04 ` Jan Jitse Venselaar
2005-08-01 13:45 ` Duncan [this message]
2005-08-01 17:03 ` [gentoo-amd64] " Karol Krizka
2005-08-02 10:21 ` [gentoo-amd64] " Duncan
2005-08-02 19:41 ` Matt Randolph
2005-08-02 23:27 ` [gentoo-amd64] hijacked! :) television (was: x86_64 optimization patches for glibc.) Sami Samhuri
2005-08-04 2:28 ` Luke-Jr
2005-08-05 0:28 ` Sami Samhuri
2005-08-05 7:43 ` Arm Suwarnaratana
2005-08-09 10:29 ` [gentoo-amd64] Re: x86_64 optimization patches for glibc Simon Strandman
2005-07-26 17:40 ` [gentoo-amd64] " ardour
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pan.2005.08.01.13.45.00.753382@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox