Overview
Candidate to break the build of virtualbox - testing
Confirmed - by removing acpica from the Staging, virtualbox succeeded again. Can you please take care of that? (either by fixing or linking up with the virtualbox maintainer)
Unignored: returned to active backlog.
CC @lwfinger
Larry, seems our current virtualbox package does not like acpica 20200110
Can you please check if there is any way to make this work?
I will see what I can do. I'm not really pleased that every time that package gets updated, virtualbox breaks!
Understandable...
In anzycase: please only submit once the currently pending submission has been accepted. This is in a currently green Staging, waiting for a check-in slot (so, no rush with a fix)
I expect the current submission to be checked in by Thursday evening
I saw VB 6.1.2 in the 20200201 snapshot, and then tried a new build using openSUSE:Factory:Staging:M as an alternative project. Unfortunately, that project still uses the old acpica. Which project has the new one?
Now, I am thoroughly confused. Building against that alternative project does not fail. Is it possible that there was an OBS glitch?
This is because openSUSE:Factory:Staging:M uses gcc10 which enables -fno-common compile option by default. I will supersede this submitrequest having this fixed. Not sure whether this helps for VirtualBox. If, then it may have been built with latest staging projects and acpica failed totally to build and is a virtualbox requirement, right?
https://build.opensuse.org/request/show/770466
Yes, acpica is a VirtualBox requirement as the VB build includes compilation of the BIOS for virtual machines.
The -fno-common option likely explains the difference between the failure with Staging:M and the correct build with acpica version 20200110 using hardware as an alternativeproject. The resulting VB packages work correctly for Windows XP, 7, and 10, FreeDOS, and TW and Leap 15.2 virtual machines.
Thanks for looking into this issue. We might avoid some problems if I were notified the next time that acpica is updated so that I can test against your project before it gets pushed upstream. VB consumes at least 1 hour of OBS time per build, and the failures seem to happen near the end of the build, as Murphy's Law would predict. :) If we coordinate, we might push some of this development time onto my local machines.
I have added user lwfinger to the acpica devel project as "Reader". Whatever that means, I hope you get notifications on requests, etc.
You may want to use: osc requestmaintainership and friends to remove this one and request reviewer if you do not get notifications.
Thanks for the heads up!
Request History
trenn created request
- Add -fcommon as there are a lot re-definitions which lead to errors
and compile failures with gcc10 which enables -fno-common by default
bsc#1160383 - acpica fails with -fno-common
- Update to version 20200110
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto accepted review
Check script succeeded
licensedigger accepted review
ok
dimstar_suse set openSUSE:Factory:Staging:M as a staging project
Being evaluated by staging project "openSUSE:Factory:Staging:M"
dimstar_suse accepted review
Picked "openSUSE:Factory:Staging:M"
dimstar_suse added factory-staging as a reviewer
Being evaluated by group "factory-staging"
dimstar_suse accepted review
Unstaged from project "openSUSE:Factory:Staging:M"
staging-bot set openSUSE:Factory:Staging:F as a staging project
Being evaluated by staging project "openSUSE:Factory:Staging:F"
staging-bot accepted review
Picked "openSUSE:Factory:Staging:F"
dimstar accepted review
okurz-factory accepted review
Staging Project openSUSE:Factory:Staging:F got accepted.
okurz-factory approved review
Staging Project openSUSE:Factory:Staging:F got accepted.
okurz-factory accepted request
Staging Project openSUSE:Factory:Staging:F got accepted.