This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: .../lib/gcc/<triplet>/7.1.1/ vs. .../lib/gcc/<triplet>/7/
- From: Richard Biener <rguenther at suse dot de>
- To: Jakub Jelinek <jakub at redhat dot com>,Szabolcs Nagy <szabolcs dot nagy at arm dot com>
- Cc: gcc at gcc dot gnu dot org,nd at arm dot com
- Date: Fri, 06 Jan 2017 18:51:13 +0100
- Subject: Re: .../lib/gcc/<triplet>/7.1.1/ vs. .../lib/gcc/<triplet>/7/
- Authentication-results: sourceware.org; auth=none
- References: <20170106124826.GJ21933@tucnak> <586F968B.2010301@arm.com> <20170106131151.GM21933@tucnak>
On January 6, 2017 2:11:51 PM GMT+01:00, Jakub Jelinek <jakub@redhat.com> wrote:
>On Fri, Jan 06, 2017 at 01:07:23PM +0000, Szabolcs Nagy wrote:
>> On 06/01/17 12:48, Jakub Jelinek wrote:
>> > SUSE and some other distros use a hack that omits the minor and
>patchlevel
>> > versions from the directory layout, just uses the major number, it
>is very
>>
>> what is the benefit?
>
>Various packages use the paths to gcc libraries/includes etc. in
>various
>places (e.g. libtool, *.la files, etc.). So any time you upgrade gcc
>(say from 6.1.0 to 6.2.0 or 6.2.0 to 6.2.1), everything that has those
>paths
>needs to be rebuilt. By having only the major number in the paths
>(which is
>pretty much all that matters), you only have to rebuild when the major
>version of gcc changes (at which time one usually want to mass rebuild
>everything anyway).
RPMs from ISVs having this issue made us change is for SUSE. Note another workaround is to provide symlinks from old provided versions to the actual one.
It's really all a packaging issue so not sure if upstream should change anything by default. Providing a way to do it would be nice of course.
Richard.
>
> Jakub