Larry,
I just wanted to speak up quickly to be sure nobody used your example to
"fix" the Mac OS problem and thereby break Solaris instead. No personal
attack/affront was intended.
-Paul
On Wed, Nov 14, 2012 at 7:10 PM, Larry Baker wrote:
> Paul,
>
> 1) I wasn't trying to
Ralph,
> Ick - usually tools support some kind of version option. :-(
In the olden days, -V (big V) was a reasonably standard request for version no.
(little V being verbosity). The GHNU command line parsing added the wordy
options preceded by double dashes. Unfortunately, gcc does not
Paul,
1) I wasn't trying to solve the --version issue, only the parsing of the
response.
2) I assumed from the initial e-mail that the broken parser was in a Perl
script. I'm not a Perl person, so I wrote the example regular expression
parser in sed.
These commands were done on my Mac OS X
Ick - usually tools support some kind of version option. :-(
I'll give Nathan a chance to work on this tonight. If we can't resolve the
problem, I'll revert the m4 check as well.
On Nov 14, 2012, at 5:41 PM, Paul Hargrove wrote:
> On Wed, Nov 14, 2012 at 6:26 PM, Larry
On Wed, Nov 14, 2012 at 6:26 PM, Larry Baker wrote:
> m4 --version | sed -n -E -e
> '1s/^.*[^A-Za-z0-9_-]?([0-9]+[.][0-9]+[.][0-9]+)[^A-Za-z0-9_-]?.*$/\1/p'
>
There are STILL problems with this approach as it is TWICE specific to GNU
software:
1) M4 on OpenBSD (maybe others)
Ah. I see why it worked for me. I was using the MacPorts flex:
vygr:build hjelmn$ type -p flex
/opt/local/bin/flex
vygr:build hjelmn$ flex --version
flex 2.5.35
I will take a look tonight (if you haven't already fixed it) and see if I can
improve find_and_check.
-Nathan
Ralph,
Try sed -n -E -e
'1s/^.*[^A-Za-z0-9_-]?([0-9]+[.][0-9]+[.][0-9]+)[^A-Za-z0-9_-]?.*$/\1/p' (or
its equivalent in Perl).
-n = Don't print out lines that do not match the pattern
-E = Telsl sed to recognize +
pattern = .. (no attempt to rule out nonsense like
0.0.0)
> savaii:~ baker$ m4
Sorry Nathan - I had to revert this out as it broke builds on Mac ML. The
problem is that the find_and_check parser looks for parens to find the version
number, expecting something like this:
$ m4 --version
m4 (GNU M4) 1.4.16
or this:
$ gcc --version
i686-apple-darwin11-llvm-gcc-4.2 (GCC)
A few people have approached me with topics for the Dec meeting. I put the
ones that I could remember on the wiki. Please go fill in whatever topics you
want to discuss:
https://svn.open-mpi.org/trac/ompi/wiki/Dec12Meeting
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal