Second Groovy Gorilla test rebuild

Christian Ehrhardt christian.ehrhardt at canonical.com
Thu Oct 1 09:37:03 UTC 2020


On Tue, Sep 29, 2020 at 11:07 AM Christian Ehrhardt
<christian.ehrhardt at canonical.com> wrote:
>
> On Mon, Sep 28, 2020 at 9:39 PM Sebastien Bacher <seb128 at ubuntu.com> wrote:
> >
> > Hey Matthias,
> >
> > Le 28/09/2020 à 18:07, Matthias Klose a écrit :
> > > Some build failures on ppc64el and s390x are caused by a buildd issue, and will
> > > be retried soonish. Please ignore these where you see a ftbfs just on those
> > > architectures, but successes on the other architectures.
> >
> > There seems to be some flakyness on arm as well, are those going to be
> > retried or should that be requested by e.g pinging you?
> >
> > Some examples
> >
> > https://launchpadlibrarian.net/499016257/buildlog_ubuntu-groovy-armhf.colord-gtk_0.2.0-0ubuntu1_BUILDING.txt.gz
> > https://launchpadlibrarian.net/499209776/buildlog_ubuntu-groovy-arm64.gpm_1.20.7-6_BUILDING.txt.gz
> > https://launchpadlibrarian.net/499174464/buildlog_ubuntu-groovy-arm64.remmina_1.4.8+dfsg-1ubuntu1_BUILDING.txt.gz
>
> Adding the same armhf dependency issue on these:
> htop: https://launchpadlibrarian.net/499078378/buildlog_ubuntu-groovy-arm64.htop_3.0.2-1_BUILDING.txt.gz
> openvpn: https://launchpadlibrarian.net/499161991/buildlog_ubuntu-groovy-armhf.openvpn_2.4.9-3ubuntu1_BUILDING.txt.gz
> I see that Laney already filed a bug about that with IS.
>
> Furthermore some armhf issues are due to
> https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1890435
> php7.4: https://launchpadlibrarian.net/499168409/buildlog_ubuntu-groovy-armhf.php7.4_7.4.9-1ubuntu1_BUILDING.txt.gz
>
> When doing an initial triage of some errors I found three sets of
> recurring issues:
> 1. rpc includes like "rpc/rpc.h: No such file"
> 2. better null checking like " -Werror=nonnull" or "directive argument is null"
> 3. linker shows "multiple definitions of"

Just as FYI to save you some debugging, common issue #3 is due to gcc now
defaulting to -fno-common Most of the time that is due to missing "extern"
declarations and the fix is to add them.
This even is the first entry on [1] Porting to GCC 10 page.

But there is one more case which is less clear than missing "extern",
Defines that are meant to be linked together like the following also trigger it:
#define __shared __asm__ ( "_shared_bss" ) __aligned
The fix here is to add back -fcommon for such.

[1]: https://gcc.gnu.org/gcc-10/porting_to.html

> #2 likely comes down to fixing code or disabling the warning for now.
> But for #1 and #3 I think there is a general change and every affected
> package likely will need the similar fix.
> So if someone already debugged those it would be great to let the others know.
>
>
> > Cheers,
> > Sebastien Bacher
> >
> >
> >
> > --
> > ubuntu-devel mailing list
> > ubuntu-devel at lists.ubuntu.com
> > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
>
>
>
> --
> Christian Ehrhardt
> Staff Engineer, Ubuntu Server
> Canonical Ltd



-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd



More information about the ubuntu-devel mailing list