[patch #2507] Patch to update autoconf files

2005-07-12 Thread Marcus Brinkmann
Update of patch #2507 (project hurd): Status:None => Done Open/Closed:Open => Closed ___ Follow-up Comment #9: Applied an only very

Re: [patch #2507] Patch to update autoconf files

2005-06-06 Thread Alfred M. Szmidt
Commited. 2005-05-27 Thomas Schwinge <[EMAIL PROTECTED]> * mig.in (prj_quote_sh): New shell funcion; copied from Paul Jarc's prjlibs. Use that function to properly quote strings in $cppflags that contain whitespace. ___ Bug-

Re: [patch #2507] Patch to update autoconf files

2005-06-02 Thread Roland McGrath
Looks ok to me. ___ Bug-hurd mailing list Bug-hurd@gnu.org http://lists.gnu.org/mailman/listinfo/bug-hurd

Re: [patch #2507] Patch to update autoconf files

2005-06-02 Thread Guillem Jover
Hi, On Thu, Jun 02, 2005 at 03:08:36PM -0400, Alfred M. Szmidt wrote: > Ok to apply? Fixes so that stuff like -DFOO=\"bar\ baz\" is passed > correctly. I assume that Thomas has checked that the patch works. > > 2005-05-27 Thomas Schwinge <[EMAIL PROTECTED]> > > * mig.in (prj_quote_sh):

Re: [patch #2507] Patch to update autoconf files

2005-06-02 Thread Alfred M. Szmidt
Ok to apply? Fixes so that stuff like -DFOO=\"bar\ baz\" is passed correctly. I assume that Thomas has checked that the patch works. 2005-05-27 Thomas Schwinge <[EMAIL PROTECTED]> * mig.in (prj_quote_sh): New shell funcion; copied from Paul Jarc's prjlibs. Use that function to

[patch #2507] Patch to update autoconf files

2005-05-29 Thread Thomas Schwinge
Follow-up Comment #8, patch #2507 (project hurd): This is an example of the error message, Alfred is speaking about: #v+ mig -nostdinc -DMACH -DCMU -DMACH_KERNEL -DKERNEL -DPACKAGE_NAME=\"GNU\ Mach\" -DPACKAGE_TARNAME=\"gnumach\" -DPACKAGE_VERSION=\"1.3\" -DPACKAGE_STRING=\"GNU\ Mach\ 1.3\" -DPAC

[patch #2507] Patch to update autoconf files

2005-05-19 Thread Alfred M. Szmidt
Follow-up Comment #7, patch #2507 (project hurd): To be able to define PACKAGE_NAME as "GNU Mach", we need to fix MiG to parse arguments that contain whitespaces. From [mig]/mig.in: # If an argument to this shell script contains whitespace, # then we will screw up. migcom will see it as multip

[patch #2507] Patch to update autoconf files

2004-10-26 Thread Guillem Jover
This mail is an automated notification from the patch tracker of the project: The GNU Hurd. /**/ [patch #2507] Latest Modifications: Changes by: Guillem Jover <[EMAIL PROTECTED]> 'Date: Wed

Re: [patch #2507] Patch to update autoconf files

2004-09-21 Thread Alfred M. Szmidt
Oh oh oh, I have an idea! Can we change so that uname -m reports something logical? Instead of "i386-AT386" it could like report "i386", "i686" etc. There is some ifdefed code for this, but I guess nobody ever tested it. Even disabling just the whole machine_slot[0].cpu_subtype would make it so

[patch #2507] Patch to update autoconf files

2004-09-20 Thread Guillem Jover
This mail is an automated notification from the patch tracker of the project: The GNU Hurd. /**/ [patch #2507] Latest Modifications: Changes by: Guillem Jover <[EMAIL PROTECTED]> 'Date: Mon

Re: [patch #2507] Patch to update autoconf files

2004-09-15 Thread Alfred M. Szmidt
This is an update of Neal's patch and fixes all issues left. The two disabled drivers are now enabled. Thanks. The only thing I've not changed is "GNUmach" to @PACKAGE_NAME@ in version.c.in, beacuse it's used for example in "uname -v" and I'm not sure if it will break programs pars

[patch #2507] Patch to update autoconf files

2004-09-15 Thread Guillem Jover
This mail is an automated notification from the patch tracker of the project: The GNU Hurd. /**/ [patch #2507] Latest Modifications: Changes by: Guillem Jover <[EMAIL PROTECTED]> 'Date: Wed

Re: [patch #2507] Patch to update autoconf files

2004-09-07 Thread Alfred M. Szmidt
Okie, since you are incapable of actually keeping a two-sided technical discussion; lets change into my flame proof clothes and drop to your level of skills when it comes to discussions. >> "Comment out the u1434f and viarhine drivers which break >> autoconf." >> >

Re: [patch #2507] Patch to update autoconf files

2004-09-07 Thread Neal H. Walfield
At Tue, 07 Sep 2004 15:37:54 +0200, Alfred M. Szmidt <[EMAIL PROTECTED]> wrote: > >> "Comment out the u1434f and viarhine drivers which break >> autoconf." >> >> Is there any good reason why not just fix those two drivers to be >> sane and work with autoconf? > >N

Re: [patch #2507] Patch to update autoconf files

2004-09-07 Thread Alfred M. Szmidt
> "Comment out the u1434f and viarhine drivers which break > autoconf." > > Is there any good reason why not just fix those two drivers to be > sane and work with autoconf? No, feel free. Then why do you bother sending in a broken patch? Disabling drivers for the sake o

Re: [patch #2507] Patch to update autoconf files

2004-09-07 Thread Neal H. Walfield
At Tue, 07 Sep 2004 13:16:10 +0200, Alfred M. Szmidt <[EMAIL PROTECTED]> wrote: > > "Comment out the u1434f and viarhine drivers which break autoconf." > > Is there any good reason why not just fix those two drivers to be > sane and work with autoconf? No, feel free. __

Re: [patch #2507] Patch to update autoconf files

2004-09-07 Thread Alfred M. Szmidt
"Comment out the u1434f and viarhine drivers which break autoconf." Is there any good reason why not just fix those two drivers to be sane and work with autoconf? ___ Bug-hurd mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug

[patch #2507] Patch to update autoconf files

2004-09-07 Thread Neal H. Walfield
This mail is an automated notification from the patch tracker of the project: The GNU Hurd. /**/ [patch #2507] Latest Modifications: Changes by: Neal H. Walfield <[EMAIL PROTECTED]> 'Date: T

[patch #2507] Patch to update autoconf files

2004-04-08 Thread Daniel Wagner
This mail is an automated notification from the patch tracker of the project: The GNU Hurd. /**/ [patch #2507] Latest Modifications: Changes by: Daniel Wagner <[EMAIL PROTECTED]> 'Date: Thu