[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Unparsable gcc version string? [WAS: lily 1.4.15]
From: |
Jan Nieuwenhuizen |
Subject: |
Re: Unparsable gcc version string? [WAS: lily 1.4.15] |
Date: |
Tue, 02 Jul 2002 14:03:31 +0200 |
User-agent: |
Gnus/5.090006 (Oort Gnus v0.06) Emacs/21.2 (i386-debian-linux-gnu) |
Josip Rodin <address@hidden> writes:
>> Yes, that's what I mean. We just need:
>>
>> gcc --version
>> 3.1.1
>
> Well, if gcc upstream switched to printing both "gcc " and the version
> afterwards, you can just use $2.
That would not work with (see my 1st email):
$ bison --version
bison (GNU Bison) 1.35
$ flex --version
flex version 2.5.4
Great fun, if everyone would think they've grown so big and important,
it would warrant a diversion from a resonable standardised version
string.
Currently, we just use $NF, which has worked for all tools up till now,
but I can imagine inserting something like:
| sed 's/[^0-9]*$//'
However, with the current:
gcc (GCC) 3.1.1 20020606 (Debian prerelease)
this would yield '20020606'. I don't like the idea having to go the
way of
expr "$ver" : '.*[^-.0-9]\([0-9][0-9]*\.[^ ]*\)'
Jan.
--
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
- lily 1.4.15, Peter Chubb, 2002/07/01
- Re: lily 1.4.15, Jan Nieuwenhuizen, 2002/07/02
- Re: lily 1.4.15, Peter Chubb, 2002/07/02
- Re: lily 1.4.15, Jan Nieuwenhuizen, 2002/07/02
- Message not available
- Unparsable gcc version string? [WAS: lily 1.4.15], Jan Nieuwenhuizen, 2002/07/02
- Re: Unparsable gcc version string? [WAS: lily 1.4.15], Josip Rodin, 2002/07/02
- Re: Unparsable gcc version string? [WAS: lily 1.4.15], Jan Nieuwenhuizen, 2002/07/02
- Re: Unparsable gcc version string? [WAS: lily 1.4.15], Josip Rodin, 2002/07/02
- Re: Unparsable gcc version string? [WAS: lily 1.4.15],
Jan Nieuwenhuizen <=
- Re: Unparsable gcc version string? [WAS: lily 1.4.15], Wichert Akkerman, 2002/07/02
- Re: Unparsable gcc version string? [WAS: lily 1.4.15], Jan Nieuwenhuizen, 2002/07/02
- Re: Unparsable gcc version string? [WAS: lily 1.4.15], Han-Wen Nienhuys, 2002/07/02
- Re: Unparsable gcc version string? [WAS: lily 1.4.15], Wichert Akkerman, 2002/07/02
- Re: Unparsable gcc version string? [WAS: lily 1.4.15], Han-Wen Nienhuys, 2002/07/02
- Re: Unparsable gcc version string? [WAS: lily 1.4.15], Jochen Voss, 2002/07/02
Re: lily 1.4.15, Jan Nieuwenhuizen, 2002/07/02