From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Some new xorg ebuilds
Date: Wed, 04 May 2005 03:54:49 -0700 [thread overview]
Message-ID: <pan.2005.05.04.10.54.48.458202@cox.net> (raw)
In-Reply-To: 4265C541.9020104@gentoo.org
Donnie Berkholz posted <4265C541.9020104@gentoo.org>, excerpted below, on
Tue, 19 Apr 2005 19:58:09 -0700:
> Daniel Goller wrote:
>> do you want both on one bug or seperate bugs, from your email, you do
>> want success and problems on bugs.g.o, correct? do you want hardware
>> info/binary drivers used added?
>
> Basically emerge info and xorg.conf, from which I can suck out your
> architecture, xorg USE flags, toolchain and driver.
>
> Successes are only really interesting for 6.8.99.*. THe other, I expect
> to work fairly well.
OK, I'm currently running the 6.8.99.3 snapshot, on ~amd64 w/ the radeon
xorg native drivers and gcc-3.4.3. No issues with it save for the
previously posted font problems, now corrected I gather.
However, my question is do you want gcc-4.0.0 bugs yet, or not? I tried
remerging w/ gcc4 without success, and now that I see the .99.5
snapshot out, before I go trying to upgrade to it, I'm wondering if it's
worth my while to try it under my gcc4 gcc-profile, bugging
success/failure, or if you aren't ready for that yet and I should just
report on gcc-3.4.3 merges (gcc-3.3 is deprecated on amd64).
--
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-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-05-04 10:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-19 8:00 [gentoo-dev] Some new xorg ebuilds Donnie Berkholz
2005-04-19 9:15 ` Sebastian Bergmann
2005-04-19 12:11 ` Henrik Brix Andersen
2005-04-20 10:39 ` [gentoo-dev] " Duncan
2005-04-20 18:25 ` Donnie Berkholz
2005-04-21 9:42 ` [gentoo-dev] " Duncan
2005-04-19 19:46 ` [gentoo-dev] " Paul de Vrieze
2005-04-19 19:56 ` Stefan Schweizer
2005-04-19 21:11 ` Donnie Berkholz
2005-04-21 13:19 ` Paul de Vrieze
2005-04-21 18:03 ` Donnie Berkholz
2005-04-20 1:27 ` Daniel Goller
2005-04-20 2:58 ` Donnie Berkholz
2005-05-04 10:54 ` Duncan [this message]
2005-05-04 19:03 ` [gentoo-dev] " Donnie Berkholz
2005-05-05 10:11 ` [gentoo-dev] " Duncan
2005-05-05 15:20 ` Donnie Berkholz
2005-05-06 2:27 ` [gentoo-dev] " Duncan
2005-04-20 5:49 ` [gentoo-dev] " Donnie Berkholz
2005-04-20 5:52 ` Donnie Berkholz
2005-04-20 9:10 ` Marcus D. Hanwell
2005-05-22 21:14 ` Beber [Gentoo]
2005-05-23 5:08 ` Donnie Berkholz
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.05.04.10.54.48.458202@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-dev@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