xf86cfg segfault, missing directories (?)

2001-07-19 Thread Alan Garrison
Hi... (disclaimer: I'm still a bit of a newbie in this area, so please be gentle :) What I did today: 1. Installed Potato on workstation (clean partitions, just essential packages). 2. Set up sources.list to point to "unstable" branch, did "apt-get dist-upgrade", handled a few problems, bl

xf86cfg segfault, missing directories (?)

2001-07-19 Thread Alan Garrison
Hi... (disclaimer: I'm still a bit of a newbie in this area, so please be gentle :) What I did today: 1. Installed Potato on workstation (clean partitions, just essential packages). 2. Set up sources.list to point to "unstable" branch, did "apt-get dist-upgrade", handled a few problems, b

Re: XFree86 4.1.0-0pre1v5 now available; 4.1.0-1 imminent

2001-07-19 Thread Adam C Powell IV
Philip Blundell wrote: Nope, failed again, different error (MANIFEST check failed). I'm afraid I've run out of time to debug, but if someone sends a patch I'd be glad to start another build. MANIFEST checks don't usually need much debugging. You just need to look over the diff to make su

Re: XFree86 4.1.0-0pre1v5 now available; 4.1.0-1 imminent

2001-07-19 Thread Adam C Powell IV
Philip Blundell wrote: >>Nope, failed again, different error (MANIFEST check failed). I'm afraid >>I've run out of time to debug, but if someone sends a patch I'd be glad >>to start another build. >> > >MANIFEST checks don't usually need much debugging. You just need to look over >the diff t

Re: XFree86 4.1.0-0pre1v5 now available; 4.1.0-1 imminent

2001-07-19 Thread Philip Blundell
>Nope, failed again, different error (MANIFEST check failed). I'm afraid >I've run out of time to debug, but if someone sends a patch I'd be glad >to start another build. MANIFEST checks don't usually need much debugging. You just need to look over the diff to make sure that it all seems reas

Re: XFree86 4.1.0-0pre1v5 now available; 4.1.0-1 imminent

2001-07-19 Thread Adam C Powell IV
Adam C Powell IV wrote: It's building now with the patch put in as debian/patches/999_z_arm_pci.diff (you'll probably give it a different number, or merge it with another patch?), log-in-progress at http://lyre.mit.edu/~powell/debs/xfree86_4.1.0-0pre1v5b.log . Nope, failed again, different

Re: XFree86 4.1.0-0pre1v5 now available; 4.1.0-1 imminent

2001-07-19 Thread Philip Blundell
>Nope, failed again, different error (MANIFEST check failed). I'm afraid >I've run out of time to debug, but if someone sends a patch I'd be glad >to start another build. MANIFEST checks don't usually need much debugging. You just need to look over the diff to make sure that it all seems rea

Re: XFree86 4.1.0-0pre1v5 now available; 4.1.0-1 imminent

2001-07-19 Thread Adam C Powell IV
Adam C Powell IV wrote: > It's building now with the patch put in as > debian/patches/999_z_arm_pci.diff (you'll probably give it a different > number, or merge it with another patch?), log-in-progress at > http://lyre.mit.edu/~powell/debs/xfree86_4.1.0-0pre1v5b.log . Nope, failed again, dif

Re: help needed to get XFree86 4.1.0 working on MIPS

2001-07-19 Thread Guido Guenther
On Thu, Jul 19, 2001 at 01:54:55AM -0400, Stephen Frost wrote: > The second problem is more difficult. xf86WriteMmio32Be is > undefined in MIPS and is implemented under other archs in > assembly which I'm not sure what to do with. xf86WriteMmio32Be > is used in atimach64.c

Re: help needed to get XFree86 4.1.0 working on MIPS

2001-07-19 Thread Guido Guenther
On Thu, Jul 19, 2001 at 03:38:44AM -0400, Christopher C. Chimelis wrote: > > On Thu, 19 Jul 2001, Stephen Frost wrote: > > > > Ryan Murray reported to me that a 4.1 compile on mips fails. > > > > This is an update to this issue. > > > > After adding another parameter to RANGE ('0' for p

Re: Offlist Wishlist: DRI Kernel Modules

2001-07-19 Thread Warren Turkal
Branden, do you think you could package up the DRI sources in a way that could be easily compiled and installed with make-kpkg. ALSA does somthing like that. It would be helpful and neat. :) --Warren On Wednesday 18 July 2001 05:56, Mike A. Harris wrote: > On Wed, 18 Jul 2001, Warren Turkal wr

Re: help needed to get XFree86 4.1.0 working on MIPS

2001-07-19 Thread Guido Guenther
On Thu, Jul 19, 2001 at 01:54:55AM -0400, Stephen Frost wrote: > The second problem is more difficult. xf86WriteMmio32Be is > undefined in MIPS and is implemented under other archs in > assembly which I'm not sure what to do with. xf86WriteMmio32Be > is used in atimach64.

Re: help needed to get XFree86 4.1.0 working on MIPS

2001-07-19 Thread Guido Guenther
On Thu, Jul 19, 2001 at 03:38:44AM -0400, Christopher C. Chimelis wrote: > > On Thu, 19 Jul 2001, Stephen Frost wrote: > > > > Ryan Murray reported to me that a 4.1 compile on mips fails. > > > > This is an update to this issue. > > > > After adding another parameter to RANGE ('0' for

Re: help needed to get XFree86 4.1.0 working on MIPS

2001-07-19 Thread Christopher C. Chimelis
On Thu, 19 Jul 2001, Stephen Frost wrote: > > Ryan Murray reported to me that a 4.1 compile on mips fails. > > This is an update to this issue. > > After adding another parameter to RANGE ('0' for pci domain) and > attempting to compile I ran into a few other problems. First

Re: Offlist Wishlist: DRI Kernel Modules

2001-07-19 Thread Warren Turkal
Branden, do you think you could package up the DRI sources in a way that could be easily compiled and installed with make-kpkg. ALSA does somthing like that. It would be helpful and neat. :) --Warren On Wednesday 18 July 2001 05:56, Mike A. Harris wrote: > On Wed, 18 Jul 2001, Warren Turkal w

Re: help needed to get XFree86 4.1.0 working on MIPS

2001-07-19 Thread Stephen Frost
* Branden Robinson ([EMAIL PROTECTED]) wrote: > [I do not subscribe to debian-mips; please include debian-x when replying.] > > Ryan Murray reported to me that a 4.1 compile on mips fails. This is an update to this issue. After adding another parameter to RANGE ('0' for pci domai

Re: help needed to get XFree86 4.1.0 working on MIPS

2001-07-19 Thread Christopher C. Chimelis
On Thu, 19 Jul 2001, Stephen Frost wrote: > > Ryan Murray reported to me that a 4.1 compile on mips fails. > > This is an update to this issue. > > After adding another parameter to RANGE ('0' for pci domain) and > attempting to compile I ran into a few other problems. First