Re: MiG, -isystem and something...

2005-04-11 Thread Alfred M. Szmidt
Now that I have chilled for a while, how about making a smallish change to MiG, add a new option, call it -file. And to call mig with a file name, you need to specify that option. Then, we pass _everything_ what we do not wish to handle to CPP, instead of making special cases for stuff. How abou

Re: MiG, -isystem and something...

2005-04-11 Thread Roland McGrath
The Hurd doesn't use the front-end script because of the nightmares of getting the options right. ___ Bug-hurd mailing list Bug-hurd@gnu.org http://lists.gnu.org/mailman/listinfo/bug-hurd

Re: MiG, -isystem and something...

2005-04-11 Thread Alfred M. Szmidt
Note to self, usage line should be updated from: Usage: $progname [OPTION]... [FILE]... to Usage: $progname [OPTION]... ___ Bug-hurd mailing list Bug-hurd@gnu.org http://lists.gnu.org/mailman/listinfo/bug-hurd

Re: MiG, -isystem and something...

2005-04-11 Thread Alfred M. Szmidt
'mig -imacros IMACROFILE -DFOO MIGFILE' needs to be transformed to '$cpp -imacros IMACROFILE -DFOO MIGFILE' and not to '$cpp -imacros -DFOO IMACROFILE MIGFILE' (as it would look like without '-imacros IMACROFILE' getting catched). The same applies to '-isystem ...'. Hmph, the GCC peop

Re: MiG, -isystem and something...

2005-04-11 Thread Thomas Schwinge
On Mon, Apr 11, 2005 at 08:59:19PM +0200, Alfred M. Szmidt wrote: > How about making MiG ignore any unregogniced options instead? That's not the problem. mig (the shell script) basically works that way: #v+ [...] until [ $# -eq 0 ] do case "$1" in [...] -imacros ) cppflags="$cppflags $

MiG, -isystem and something...

2005-04-11 Thread Alfred M. Szmidt
[sorry for breaking threading, but I don't have access to my usual mail account here] How about making MiG ignore any unregogniced options instead? I think it should already do that, if it doesn't, then I'd consider it a bug. ___ Bug-hurd mailing list