Re: m68k MANIFEST for xfree86_4.0.1-11

2000-12-15 Thread Aaron Lehmann
On Wed, Dec 13, 2000 at 10:48:13PM -0800, Seth Arnold wrote: > * Branden Robinson <[EMAIL PROTECTED]> [001213 22:43]: > > Let me know if this works out, and I will babysit XFree86 builds for m68k > > myself, using the recently-donated G3. > > Well, I wasn't thinking of emulating one of those old m

Re: m68k MANIFEST for xfree86_4.0.1-11

2000-12-15 Thread Aaron Lehmann
On Wed, Dec 13, 2000 at 10:48:13PM -0800, Seth Arnold wrote: > * Branden Robinson <[EMAIL PROTECTED]> [001213 22:43]: > > Let me know if this works out, and I will babysit XFree86 builds for m68k > > myself, using the recently-donated G3. > > Well, I wasn't thinking of emulating one of those old

Re: m68k MANIFEST for xfree86_4.0.1-11

2000-12-14 Thread Christian T. Steigies
On Thu, Dec 14, 2000 at 03:35:36PM +0100, Michel Dänzer wrote: > > If you mean Egbert, I guess he's at least as busy as Branden. :) Probably. At least Branden bounces the mail to somebody who has the time to write "READ THE FAQ DAMNIT" > Not so sure. I have such a machine here, and a BuildServon

Re: m68k MANIFEST for xfree86_4.0.1-11

2000-12-14 Thread Michel Dänzer
"Christian T. Steigies" wrote: > > On Thu, Dec 14, 2000 at 01:53:52AM +0100, Michel Dänzer wrote: > > > Ben Collins wrote: > > > > > > On Wed, Dec 13, 2000 at 03:46:49PM -0800, Seth Arnold wrote: > > > > > Could a cross-compile environment bring this down? Is there any *need* > > > > to compile

Re: m68k MANIFEST for xfree86_4.0.1-11

2000-12-14 Thread Christian T. Steigies
On Thu, Dec 14, 2000 at 03:35:36PM +0100, Michel Dänzer wrote: > > If you mean Egbert, I guess he's at least as busy as Branden. :) Probably. At least Branden bounces the mail to somebody who has the time to write "READ THE FAQ DAMNIT" > Not so sure. I have such a machine here, and a BuildServo

Re: m68k MANIFEST for xfree86_4.0.1-11

2000-12-14 Thread Michel Dänzer
"Christian T. Steigies" wrote: > > On Thu, Dec 14, 2000 at 01:53:52AM +0100, Michel Dänzer wrote: > > > Ben Collins wrote: > > > > > > On Wed, Dec 13, 2000 at 03:46:49PM -0800, Seth Arnold wrote: > > > > > Could a cross-compile environment bring this down? Is there any *need* > > > > to compile

Re: m68k MANIFEST for xfree86_4.0.1-11

2000-12-14 Thread Christian T. Steigies
Don't drink and derive... anyway, a few comments on this thread. On Thu, Dec 14, 2000 at 01:53:52AM +0100, Michel Dänzer wrote: > Ben Collins wrote: > > > > On Wed, Dec 13, 2000 at 03:46:49PM -0800, Seth Arnold wrote: > > > Could a cross-compile environment bring this down? Is there any *need* >

Re: m68k MANIFEST for xfree86_4.0.1-11

2000-12-14 Thread Christian T. Steigies
Don't drink and derive... anyway, a few comments on this thread. On Thu, Dec 14, 2000 at 01:53:52AM +0100, Michel Dänzer wrote: > Ben Collins wrote: > > > > On Wed, Dec 13, 2000 at 03:46:49PM -0800, Seth Arnold wrote: > > > Could a cross-compile environment bring this down? Is there any *need*

Re: m68k MANIFEST for xfree86_4.0.1-11

2000-12-14 Thread Seth Arnold
* Branden Robinson <[EMAIL PROTECTED]> [001213 22:43]: > Let me know if this works out, and I will babysit XFree86 builds for m68k > myself, using the recently-donated G3. Well, I wasn't thinking of emulating one of those old machines -- I was thinking of setting up gcc to know about the processor

Re: m68k MANIFEST for xfree86_4.0.1-11

2000-12-14 Thread Branden Robinson
On Thu, Dec 14, 2000 at 12:28:54AM +0100, Christian T. Steigies wrote: > Here comes the new MANIFEST for m68k, I hope its not too late. > > Just for reference: Build needed 18:30:59 (so that Branden knows how long I > need _at least_ to get a new MANIFEST). Here it comes where? There was no MIME

Re: m68k MANIFEST for xfree86_4.0.1-11

2000-12-14 Thread Branden Robinson
On Wed, Dec 13, 2000 at 07:25:23PM -0500, Ben Collins wrote: > On Wed, Dec 13, 2000 at 03:46:49PM -0800, Seth Arnold wrote: > > * Christian T. Steigies <[EMAIL PROTECTED]> [001213 15:37]: > > > Just for reference: Build needed 18:30:59 (so that Branden knows how long > > > I > > > need _at least_

Re: m68k MANIFEST for xfree86_4.0.1-11

2000-12-13 Thread Seth Arnold
* Branden Robinson <[EMAIL PROTECTED]> [001213 22:43]: > Let me know if this works out, and I will babysit XFree86 builds for m68k > myself, using the recently-donated G3. Well, I wasn't thinking of emulating one of those old machines -- I was thinking of setting up gcc to know about the processo

Re: m68k MANIFEST for xfree86_4.0.1-11

2000-12-13 Thread Branden Robinson
On Thu, Dec 14, 2000 at 12:28:54AM +0100, Christian T. Steigies wrote: > Here comes the new MANIFEST for m68k, I hope its not too late. > > Just for reference: Build needed 18:30:59 (so that Branden knows how long I > need _at least_ to get a new MANIFEST). Here it comes where? There was no MIM

Re: m68k MANIFEST for xfree86_4.0.1-11

2000-12-13 Thread Branden Robinson
On Wed, Dec 13, 2000 at 07:25:23PM -0500, Ben Collins wrote: > On Wed, Dec 13, 2000 at 03:46:49PM -0800, Seth Arnold wrote: > > * Christian T. Steigies <[EMAIL PROTECTED]> [001213 15:37]: > > > Just for reference: Build needed 18:30:59 (so that Branden knows how long I > > > need _at least_ to get

Re: m68k MANIFEST for xfree86_4.0.1-11

2000-12-13 Thread Michel Dänzer
Ben Collins wrote: > > On Wed, Dec 13, 2000 at 03:46:49PM -0800, Seth Arnold wrote: > > * Christian T. Steigies <[EMAIL PROTECTED]> [001213 15:37]: > > > Just for reference: Build needed 18:30:59 (so that Branden knows how > > > long I need _at least_ to get a new MANIFEST). > > > > Could a cross-

Re: m68k MANIFEST for xfree86_4.0.1-11

2000-12-13 Thread Ben Collins
On Wed, Dec 13, 2000 at 03:46:49PM -0800, Seth Arnold wrote: > * Christian T. Steigies <[EMAIL PROTECTED]> [001213 15:37]: > > Just for reference: Build needed 18:30:59 (so that Branden knows how long I > > need _at least_ to get a new MANIFEST). > > Could a cross-compile environment bring this do

Re: m68k MANIFEST for xfree86_4.0.1-11

2000-12-13 Thread Seth Arnold
* Christian T. Steigies <[EMAIL PROTECTED]> [001213 15:37]: > Just for reference: Build needed 18:30:59 (so that Branden knows how long I > need _at least_ to get a new MANIFEST). Could a cross-compile environment bring this down? Is there any *need* to compile these things on an m68k? I imagine t

Re: m68k MANIFEST for xfree86_4.0.1-11

2000-12-13 Thread Michel Dänzer
Ben Collins wrote: > > On Wed, Dec 13, 2000 at 03:46:49PM -0800, Seth Arnold wrote: > > * Christian T. Steigies <[EMAIL PROTECTED]> [001213 15:37]: > > > Just for reference: Build needed 18:30:59 (so that Branden knows how > > > long I need _at least_ to get a new MANIFEST). > > > > Could a cross

Re: m68k MANIFEST for xfree86_4.0.1-11

2000-12-13 Thread Ben Collins
On Wed, Dec 13, 2000 at 03:46:49PM -0800, Seth Arnold wrote: > * Christian T. Steigies <[EMAIL PROTECTED]> [001213 15:37]: > > Just for reference: Build needed 18:30:59 (so that Branden knows how long I > > need _at least_ to get a new MANIFEST). > > Could a cross-compile environment bring this d

Re: m68k MANIFEST for xfree86_4.0.1-11

2000-12-13 Thread Seth Arnold
* Christian T. Steigies <[EMAIL PROTECTED]> [001213 15:37]: > Just for reference: Build needed 18:30:59 (so that Branden knows how long I > need _at least_ to get a new MANIFEST). Could a cross-compile environment bring this down? Is there any *need* to compile these things on an m68k? I imagine