[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: best way to check for compiler _warnings_?
From: |
Miles Bader |
Subject: |
Re: best way to check for compiler _warnings_? |
Date: |
Wed, 03 Nov 2010 09:24:10 +0900 |
Ralf Wildenhues <address@hidden> 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?
Thanks,
-miles
--
Once, adj. Enough.
- best way to check for compiler _warnings_?, Miles Bader, 2010/11/01
- 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 <=
- Re: best way to check for compiler _warnings_?, Ralf Wildenhues, 2010/11/03
- 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