On 08/03/18 19:20, Wookey wrote: > On 2018-03-08 18:48 +0100, po...@debian.org wrote: >> Source: dewalls >> Severity: serious >> Tags: sid buster >> User: debian-...@lists.debian.org >> Usertags: gcc-6-rm >> >> Hi, >> >> dewalls build-depends on GCC 6. We now have GCC 7 (default) and GCC 8 >> in the archive, so please make your package build with a newer >> compiler (preferably the default one) again, since we'd like to >> remove GCC 6 from testing before the buster release. > > Hmm. The control files says: > Build-Depends: debhelper (>= 9), dh-exec, qbs (>=1.7), qtbase5-dev, > libstdc++-6- > dev, catch > > so I guess that libstdc++-6-dev is only provided by gcc6? I hadn't > realised that. Dewalls doesn't care about the gcc versions. > > There are now a million libstdc++* packages in debian with all the > cross ones. What is the correct generic dependency on 'current > libstdc++' so I avoid causing this problem again in future. > > It looks like we have libstdc++6 and libstdc++-dev virtual > packages. Is it OK to build-depend on just a virtual package? Perusing > Policy has not made me much wiser. > > Is there a doc about this somewhere?
Why do you even build-depend on libstdc++ ? That's installed through g++. g++-6 installs libstdc++-6-dev, while g++-7 installs libstdc++-7-dev. g++ is build-essential, so you can just let g++ do the work here and drop the dependency entirely AFAICS. Just like you don't build-depend on libc-dev normally. Or is there a special reason for your build-dependency? Cheers, Emilio
