Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#49025 - [gcc] please stop modifying the gcc version string

Attached to Project: Arch Linux
Opened by Jonathan Wakely (jwakely) - Wednesday, 20 April 2016, 14:56 GMT
Last edited by Allan McRae (Allan) - Thursday, 05 May 2016, 03:53 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Allan McRae (Allan)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

The gcc packages in Arch are built with a modified version string, which causes them to report an incorrect version. The new upstream GCC numbering scheme was intentionally designed so that we can distinguish bug reports for official releases such as 5.3.0 from pre-release snapshots such as 5.3.1 20160209. The Arch packages break this, causing users to report bugs upstream for "GCC 5.3.0" which are not actually present in GCC 5.3.0 e.g.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70735

This wastes upstream devs' time because it makes it harder to identify the version being used by Arch users and causes confusion for identifying regressions.

The culprit is this line in your build script:
https://projects.archlinux.org/svntogit/packages.git/tree/gcc/trunk/PKGBUILD#n48

That might have made sense prior to GCC 5 (although I still found it annoying that your users would say they had a bug in 4.9.3 when it was really a bug in a pre-release 4.9.4 YYYYMMDD snapshot) but the new numbering scheme introduced with GCC 5 makes this unnecessary and only causes confusion.

Steps to reproduce:

gcc -v
This task depends upon

Closed by  Allan McRae (Allan)
Thursday, 05 May 2016, 03:53 GMT
Reason for closing:  Fixed
Additional comments about closing:  gcc-6.1.1
Comment by Allan McRae (Allan) - Wednesday, 20 April 2016, 21:07 GMT
Ah - I missed that was still there. Will remove when I build gcc-6.

Loading...