On 07/23/2018 11:57 AM, Mattia Rizzolo wrote: > On Mon, Jul 23, 2018 at 09:10:02AM +0200, Olivier Sallou wrote: >> with a quick look, it seems that several packages are impacted by >> new/removed symbols with gcc8 > Please provide some examples. I refer for example to this bug [0]. I do not maintain the package, but as many debianmed packages seems to be broken by gcc-8 , I wanted to see what is the reason. [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897780 > >> I think that in this case, symbol files must be regenerared for those >> packages, however I do not really know: >> >> 1) how to manage symbol files > Generally speaking, I wish people would learn to handle those before > starting to maintain such packages. Hopefully here is the case as well. > >> 2) how to manage the gcc7/gcc8 symbol files if those are different for >> each gcc.... > What kind of symbols are you talking about? gcc-8 shouldn't have broken > anything, so at most they should be compiler-specific leaks of some > implementations of c++ templates or stuff like that. > -- Olivier Sallou Univ Rennes, Inria, CNRS, IRISA Irisa, Campus de Beaulieu F-35042 RENNES - FRANCE Tel: 02.99.84.71.95 gpg key id: 4096R/326D8438 (keyring.debian.org) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
Attachment:
signature.asc
Description: OpenPGP digital signature