Add riscv64 to cross-targets

Hello Dimitri, or anyone else affected,

Accepted build-essential into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/build-essential/12.8ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

All autopkgtests for the newly accepted build-essential (12.8ubuntu1.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

cyrus-imapd/3.0.13-5 (armhf)
libhx/3.24-1 (i386)
gmp-ecm/7.0.4+ds-5 (i386)
flatpak/1.6.5-0ubuntu0.1 (arm64)
mbedtls/2.16.4-1ubuntu2 (i386)
spooles/2.2-14 (i386)
mpfi/1.5.3+ds-3 (i386)
apache2/2.4.41-4ubuntu3.1 (armhf)
iniparser/4.1-4 (i386)
boost1.71/1.71.0-6ubuntu6 (amd64)
freediameter/1.2.1-7 (i386)
testu01/1.2.3+ds1-1 (i386)
mir/unknown (arm64)
libosmo-sccp/0.10.0-4 (i386)
metis/5.1.0.dfsg-5 (i386)
fflas-ffpack/2.4.3-1 (s390x)
symmetrica/2.0+ds-6 (i386)
scipy/1.3.3-3build1 (ppc64el)
fclib/3.0.0+dfsg-2build1 (ppc64el)
systemd/245.4-4ubuntu3.2 (amd64, s390x, ppc64el)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/focal/update_excuses.html#build-essential

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

build-essential is a metapackage that doesn't change which compilers are used, thus autopkgtest regressions identified, could not have been caused by build-essential rebuild itself.

retried all of those tests.

linux is in updates that have matching libc headers across all architectures as needed for cross building linux 5.4.0-47.51

Created cross-build chroot using sbuild, and crossbuilt hello successfully producing hello_2.10-2ubuntu2_riscv64.deb

crossbuild-essential-riscv64 12.8ubuntu1.1 is installable too on amd64.

Hello, build-essential is correct and installs toolchain packages correctly.

Autopkgtest regressions cannot have been caused by this package update.

Please release this update.

This bug was fixed in the package build-essential - 12.8ubuntu1.1

---------------
build-essential (12.8ubuntu1.1) focal; urgency=medium

  * Add riscv64 post to cross-targets. LP: #1891460

 -- Dimitri John Ledkov <email address hidden> Thu, 13 Aug 2020 10:29:57 +0100

The verification of the Stable Release Update for build-essential has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.