#14665 closed bug (fixed)

HaikuPorts bots using gcc8

Reported by: miqlas Owned by: haiku-web
Priority: normal Milestone: Unscheduled
Component: Sys-Admin Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

Checking a log here: https://build.haiku-os.org/buildmaster/master/x86_gcc2/logviewer.html?buildruns/2241/builds/31203.log i noticed the bot uses gcc8 package to build the port.

AFAIK the current official gcc version is gcc7.3.0, so i assume the bots should use the same version.

Change History (4)

comment:1 Changed 10 months ago by miqlas

It seems only the gcc2h bots are affected.

comment:2 Changed 10 months ago by korli

Component: Build SystemSys-Admin
Owner: changed from bonefish to haiku-web

comment:3 Changed 10 months ago by mmlr

This issue should be raised on the HaikuPorts side, not here.

The compiler that is used is in no way special as far as HaikuPorter is concerned. It is resolved as a dependency the same way any library or other program is and all of the providers that are available in the repository are considered. So if the gcc8 package provides overlapping commands (which it does, here it's cmd:gcc$secondaryArchSuffix compat >= 7) then matching the gcc8 packages for the cmd:gcc$secondaryArchSuffix dependency is perfectly valid.

There is no notion of "official gcc version". There is only the set of build packages that are used to initially build the images. These also serve as the set of initial packages when the buildmaster system is originally bootstrapped. From there on out, new packages are built and made available and will shadow the original ones. Restricting HaikuPorts to the set of build packages would obviously not be desirable, as it would preclude any updated packages and packages outside of the build packages set.

I guess the gcc8 package was not actually supposed to be present in the repository at all, as the recipe for gcc8-8.1.0 seems to disable all the primary architectures. It does not disable the x86 secondary architecture however, which caused it to be built and added to the repository on x86_gcc2. The gcc8-8.0.0 recipe did also disable the x86 secondary architecture, which is the reason why that one did not get built at all.

So if gcc8 is not supposed to be available in the x86_gcc2 repository, just disable the x86 secondary architecture and the corresponding packages will be purged.

comment:4 Changed 10 months ago by waddlesplash

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.