Hi Sarah, Sarah Morgensen <iskar...@mgsn.dev> skribis:
> Gentoo's tracker for this issue [2] also has some more info. I manually > searched Cuirass build logs and found 28 packages failing on x86_64 with > this error: > > arcan-sdl@0.5.5.2-1.b4dd1fb > aris@2.2 > blastem@0.6.2 > chocolate-doom@3.0.1 > crispy-doom@5.8.0 > geeqie@1.5 > glabels@3.4.1 > gmtp@1.3.11 > gpredict@2.2.1 > gtksheet@4.3.5 > jumpnbump@1.61 > lablgtk@2.18.10 > libappindicator@12.10.0 > libopenshot@0.2.5 > libsrtp@2.3.0 > linsmith@0.99.31 > megaglest@3.13.0 > mupen64plus-core@2.5 > ocaml4.07-lablgtk@1.18.10 > ocl-icd@2.2.12 > opencpn@5.0.0 > pcsxr@1.9.95 > pipewire@0.2.7 > transcode@1.1.7 > transmission-remote-gtk@1.4.1 > uget@2.2.1 > uim-gtk@1.8.8 > uim-qt@1.8.8 > > I submitted an issue upstream for transmission-remote-gtk [3], but I > haven't taken a look at the others. Any takers? Great that you built a list of affected packages. I guess there are several options: 1. Build with ‘-fcommon’, effectively restoring pre-GCC-10 behavior; 2. Build with GCC 8.x or so, for example by adding it to ‘native-inputs’; 3. Upgrade packages and hope for the best; 4. Add the missing ‘extern’ keyword in declarations, assuming that really is the problem. I suppose we’ll have to see on a case-by-cases basis which approach is the easiest. Since we have a list, let’s parallelize work and synchronize on IRC and in this issue! Thanks, Ludo’.