This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Problem with command line string parsing


Hi,

I filed a bug report
(http://gcc.gnu.org/ml/gcc-bugs/2003-02/msg00493.html) over the use of
the -MT flag with multiple targets.

I have now noticed this happens with the -D flag.  

e.g. with the latest snapshot release

$gcc-snap -DDEFINE="part1 part2"
gcc: part2: No such file or directory
gcc: no input files

gcc is seeing the part(s) after the space as files to be compiled.  I
noticed this as something I was compling defined a version string
-DVERSION="\"LALA v1.0\"" and I got errors about trying to compile
multiple files with -c.

Can anyone suggest where this might be happening in the command line
parsing code?  What does -MT and -D have in common, as it appears to
be the same problem for both?  I thought it might be munge() but it
looks OK to me.

any help appreciated

-i
ianw at gelato dot unsw dot edu dot au
http://www.gelato.unsw.edu.au


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]