All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: LinuxPPC X Server
Date: Tue, 1 Aug 2000 14:03:59 -0700	[thread overview]
Message-ID: <20000801140359.A24586@drow.them.org> (raw)
In-Reply-To: <39852D5F.22135576@relog.ch>; from daenzer@relog.ch on Mon, Jul 31, 2000 at 09:40:15AM +0200


On Mon, Jul 31, 2000 at 09:40:15AM +0200, Michel Dänzer wrote:
> Daniel Jacobowitz wrote:
> >
> > On Sun, Jul 30, 2000 at 08:14:35PM +0200, Michel D?nzer wrote:
> > > Before building, you should have copied xc/config/cf/{xf86site,host}.def
> > >
> > > Then edit the newly created host.def - you probably only want to build the
> > > server and drivers, and choose the drivers you want.
> > >
> > > For DRI, you may have to edit even more files in config/cf/, AFAIK DRI is only
> > > built on i386 by default.
> >
> > DRI won't build on powerpc at present.  The first place it dies is in
> > the makefiles for libOSmesa, where $(SUBDIRS) becomes empty.
>
> Which tree and version?
>
> I was playing around with stock X 4.0.1 on the train about an hour ago, and
> apart from the /dev entries missing (anyone has the majors/minors handy? :),
> everything _seemed_ to at least load fine...
>
> I'll report the definite result after more testing.

Straight 4.0.1.  I turned on BuildXF86DRI in linux.cf in an attempt to
build libOSmesa, and failed.

Dan

/--------------------------------\  /--------------------------------\
|       Daniel Jacobowitz        |__|        SCS Class of 2002       |
|   Debian GNU/Linux Developer    __    Carnegie Mellon University   |
|         dan@debian.org         |  |       dmj+@andrew.cmu.edu      |
\--------------------------------/  \--------------------------------/

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-08-01 21:03 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-30 20:00 LinuxPPC X Server Iain Sandoe
2000-07-30 18:14 ` Michel D nzer
2000-07-30 22:33   ` Steffen Haeuser
2000-07-31  3:12   ` Daniel Jacobowitz
2000-07-31  7:40     ` Michel Dänzer
2000-08-01 21:03       ` Daniel Jacobowitz [this message]
2000-07-31 16:05   ` Michael Schmitz
2000-08-02 10:40     ` Martin Costabel
2000-07-30 22:46 ` Steffen Haeuser
  -- strict thread matches above, loose matches on Subject: below --
2000-08-02 16:07 Jack Howarth
2000-08-03 13:27 ` Kostas Gewrgiou
2000-08-02  0:25 Iain Sandoe
2000-07-31 14:07 Benjamin Herrenschmidt
2000-08-01 19:05 ` Michel Dänzer
     [not found]   ` <20000801191739.26835@mailhost.mipsys.com>
2000-08-01 19:37     ` Michel Dänzer
     [not found]       ` <20000801204113.29901@mailhost.mipsys.com>
2000-08-01 21:31         ` Michel Dänzer
2000-08-02 12:45           ` Geert Uytterhoeven
2000-08-02 23:27             ` Michel Dänzer
2000-07-30 21:24 Iain Sandoe
2000-07-31 12:53 ` Josh Huber
2000-07-31 16:28   ` Michael Schmitz
2000-07-30 20:33 Iain Sandoe
2000-07-31  7:50 ` Michel Dänzer
2000-07-31  9:25   ` Steffen Haeuser
2000-07-31  8:47     ` Michel Dänzer
2000-07-31 10:05       ` Steffen Haeuser
2000-07-31  9:03         ` Michel Dänzer
2000-07-31 10:21           ` Steffen Haeuser
2000-08-01 12:54       ` Kostas Gewrgiou
2000-08-01 16:25         ` Steffen Haeuser
2000-08-01 21:06         ` Daniel Jacobowitz
2000-08-02  9:20           ` Michel Dänzer
2000-08-02 18:17           ` Kostas Gewrgiou
2000-07-30 16:56 Iain Sandoe
2000-07-30 19:29 ` Steffen Haeuser
2000-07-30 21:13 ` Timothy A. Seufert
2000-07-29 13:31 Steffen Haeuser
2000-07-29 22:55 ` Takashi Oe
2000-07-30 11:27   ` Steffen Haeuser
2000-07-30 11:54     ` Takashi Oe
2000-07-30 14:40       ` Steffen Haeuser
2000-07-30 14:41         ` Takashi Oe
2000-07-30 16:13           ` Steffen Haeuser

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=20000801140359.A24586@drow.them.org \
    --to=drow@false.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.