[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: best way to check for compiler _warnings_?
From: |
Ralf Wildenhues |
Subject: |
Re: best way to check for compiler _warnings_? |
Date: |
Wed, 3 Nov 2010 06:35:32 +0100 |
User-agent: |
Mutt/1.5.20 (2010-08-04) |
* Miles Bader wrote on Wed, Nov 03, 2010 at 01:24:10AM CET:
> Ralf Wildenhues writes:
> >> if grep -e "$ONE_OPT" conftest.err >/dev/null; then
> >
> > -e is not portable to Solaris grep. Does MSVC print options at the
> > beginning of the line? If not, then you could
> > if grep ".$ONE_OPT" ...
>
> Hmm, ".*$ONE_OPT" should work everywhere, right?
Of course; thanks,
Ralf
- Re: best way to check for compiler _warnings_?, (continued)
- Re: best way to check for compiler _warnings_?, Ralf Wildenhues, 2010/11/01
- Re: best way to check for compiler _warnings_?, Miles Bader, 2010/11/01
- Re: best way to check for compiler _warnings_?, Miles Bader, 2010/11/01
- Re: best way to check for compiler _warnings_?, Ralf Wildenhues, 2010/11/02
- Re: best way to check for compiler _warnings_?, Peter Rosin, 2010/11/02
- Re: best way to check for compiler _warnings_?, Miles Bader, 2010/11/02
- Re: best way to check for compiler _warnings_?, Peter Rosin, 2010/11/02
- Re: best way to check for compiler _warnings_?, Miles Bader, 2010/11/02
- Re: best way to check for compiler _warnings_?, Ralf Wildenhues, 2010/11/02
- Re: best way to check for compiler _warnings_?, Miles Bader, 2010/11/02
- Re: best way to check for compiler _warnings_?,
Ralf Wildenhues <=
- Re: best way to check for compiler _warnings_?, Peter Rosin, 2010/11/03
Re: best way to check for compiler _warnings_?, Joseph S. Myers, 2010/11/02