Bug#724865: gcc-4.8 also affected
Am 31.10.2013 08:38, schrieb Johannes Schauer:
> Hi,
>
> Quoting Matthias Klose (2013-10-30 20:27:20)
>> Am 30.10.2013 16:55, schrieb Johannes Schauer:
>>> I just wanted to mention that src:gcc-4.8 seems to be affected by the same
>>> problem.
>>
>> I don't see that gcc-4.8 is affected.
>
> the problem with this bug (gcc-4.6) is that gcc-4.6 build-conflicts with
> binutils-gold. binutils-gold is a virtual package provided by binutils. gcc-4.6
> build-depends on binutils and thus the conflict with gcc-4.6.
>
> gcc-4.8 also build-conflicts with binutils-gold and build-depends on binutils.
> Therefore it is logical that it should also not be buildable.
>
> Here is the dose3 output for building gcc-4.8 on Debian Sid:
>
> _build/applications/deb-buildcheck.native --checkonly=gcc-4.8 --explain --failures --deb-native-arch=i386 ~/debian-sid-i386/var/lib/apt/lists/ftp.us.debian.org_debian_dists_sid_main_binary-i386_Packages ~/debian-sid-i386/var/lib/apt/lists/ftp.us.debian.org_debian_dists_sid_main_source_Sources
> native-architecture: i386
> report:
> -
> package: src:gcc-4.8
> version: 4.8.1-3
> architecture: any,all
> essential: false
> source: gcc-4.8 (= 4.8.1-3)
> status: broken
> reasons:
> -
> conflict:
> pkg1:
> package: src:gcc-4.8
> version: 4.8.1-3
> architecture: any,all
> essential: false
> source: gcc-4.8 (= 4.8.1-3)
> unsat-conflict: i386:--virtual-binutils-gold
> pkg2:
> package: i386:binutils
> version: 2.23.90.20131017-1
> architecture: i386
> essential: false
> source: binutils (= 2.23.90.20131017-1)
> depchain2:
> -
> depchain:
> -
> package: src:gcc-4.8
> version: 4.8.1-3
> architecture: any,all
> essential: false
> depends: i386:debhelper (>= 5.0.62)
> -
> package: i386:debhelper
> version: 9.20130921
> architecture: all
> essential: false
> depends: i386:binutils
>
> background-packages: 60748
> foreground-packages: 20218
> broken-packages: 1
>
>
> If this output is wrong then either was the problem fixed a day or so ago (I
> only created the chroot the day before yesterday) or dose3 is wrong (in which
> case I have to fix it).
you didn't check unstable.
Reply to: