From: Michel Dänzer <daenzerm@student.ethz.ch>
To: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: How to get up-to-speed on the 3D / DRI in Rage 128
Date: Tue, 08 Aug 2000 23:26:25 +0200 [thread overview]
Message-ID: <39907B00.45AE35FF@student.ethz.ch> (raw)
In-Reply-To: 39903341.6195EF62@relog.ch
Michel Dänzer wrote:
> > Where or how do I go about getting the DRI CVS trunk? Is this a project
> > on sourceforge? Is there anonymous cvs access?
>
> The great news is that I've just been added to the DRI project at
> sourceforge (http://dri.sourceforge.net). I'll start a PPC branch which you
> should be able to just checkout and build and it should work (and which will
> eventually be integrated into the trunk of course :).
Unfortunately, it takes some time for my write access to the repository to
take effect (until some cron job at sourceforge adds me to group dri ;) .
I've put a diff of the modifications I made up here for the impatient:
http://n.ethz.ch/student/daenzerm/download/XFree86/dri.diff.bz2
Checking out the DRI CVS trunk and applying this patch should enable you to do
'make World; make install' and use DRI. YMMV :)
Michel
--
Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-08 21:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-08 15:48 How to get up-to-speed on the 3D / DRI in Rage 128 Kevin B. Hendricks
2000-08-08 15:59 ` Michel Dänzer
2000-08-08 16:10 ` Kevin B. Hendricks
2000-08-08 16:20 ` Michel Dänzer
2000-08-08 21:26 ` Michel Dänzer [this message]
2000-08-09 1:10 ` Giuliano Pochini
2000-08-08 19:22 ` Michel Dänzer
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=39907B00.45AE35FF@student.ethz.ch \
--to=daenzerm@student.ethz.ch \
--cc=khendricks@ivey.uwo.ca \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).