Re: Unparsable gcc version string? [WAS: lily 1.4.15]

To: <debian-devel@lists.debian.org>
Subject: Re: Unparsable gcc version string? [WAS: lily 1.4.15]
From: Matthew Woodcraft <mattheww@chiark.greenend.org.uk>
Date: Tue, 02 Jul 2002 14:11:07 +0100
Message-id: <[🔎] E17PNQx-00039r-00@chiark.greenend.org.uk>
In-reply-to: <[🔎] 87u1ni9zaa.fsf@peder.flower>
References: <15648.24300.89063.346207@meddo.cs.uu.nl> <15648.55397.503777.749196@wombat.chubb.wattle.id.au> <87d6u6bko4.fsf@peder.flower> <15649.27301.279592.346666@wombat.chubb.wattle.id.au> <877kkebh5k.fsf@peder.flower> <15649.31569.685205.152763@wombat.chubb.wattle.id.au> <[🔎] 871yambf1n.fsf_-_@peder.flower> <[🔎] 20020702104958.GB8531@cibalia.gkvk.hr> <[🔎] 20020702104958.GB8531@cibalia.gkvk.hr>

In article <[🔎] 87u1ni9zaa.fsf@peder.flower> Jan Nieuwenhuizen wrote:
>Yes, that's what I mean.  We just need:
>
>   gcc --version
>   3.1.1

Try

  gcc -dumpversion

-M-


-- 
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to:

Follow-Ups:
- Re: Unparsable gcc version string? [WAS: lily 1.4.15]
  - From: Jan Nieuwenhuizen <janneke@gnu.org>

References:
- Unparsable gcc version string? [WAS: lily 1.4.15]
  - From: Jan Nieuwenhuizen <janneke@gnu.org>
- Re: Unparsable gcc version string? [WAS: lily 1.4.15]
  - From: Josip Rodin <joy@gkvk.hr>
- Re: Unparsable gcc version string? [WAS: lily 1.4.15]
  - From: Jan Nieuwenhuizen <janneke@gnu.org>

Prev by Date: Re: Version control systems for debian devlopment
Next by Date: Re: Unparsable gcc version string? [WAS: lily 1.4.15]
Previous by thread: Re: Unparsable gcc version string? [WAS: lily 1.4.15]
Next by thread: Re: Unparsable gcc version string? [WAS: lily 1.4.15]
Index(es):
- Date
- Thread