View Issue Details

IDProjectCategoryView StatusLast Update
0006748ardourbugspublic2020-04-19 20:17
Reporterfox Assigned Totimbyr  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
PlatformLinuxOSopenSUSEOS VersionFactory
Product Version4.4 
Summary0006748: Critical code quality build error in openSUSE Open Build Service
DescriptionopenSUSE Open Build Service refuses to allow ardour-4.6 packages to exist with error:
[ 2061s] I: Program is likely to break with new gcc. Try -fno-strict-aliasing.
[ 2061s] W: ardour strict-aliasing-punning ../libs/ardour/midi_ring_buffer.cc:60, 149, 214
[ 2061s]
[ 2061s] I: Program returns random data in a function
[ 2061s] E: ardour no-return-in-nonvoid-function ../gtk2_ardour/plugin_selector.cc:980, 965
[ 2061s]
[ 2061s] I: Program returns random data in a function
[ 2061s] E: ardour no-return-in-nonvoid-function ../gtk2_ardour/plugin_selector.cc:980, 965

It does not allow the lack of returns in function in the programs built in OBS for any distribution that it supports.
Steps To ReproduceMake ardour build on OBS.
Additional InformationVersion is actually 4.6 but there is no such field here now.
TagsNo tags attached.

Activities

x42

2016-01-26 00:05

administrator   ~0017837

The last two errors are false positives.
If needed, we can add a dummy "return" to make the static analysis checker happy.

x42

2016-01-26 14:16

administrator   ~0017839

those false positives should be gone since Ardour 4.6-121-gd1c3563

fox

2016-01-27 13:00

reporter   ~0017844

Thanks, it worked !
Unfortunately, they are "false positives" only from compiler's point of view, OBS treats them as critical errors by design to force its users to complain to upstream. I don't know why is that.

timbyr

2016-02-03 02:19

developer   ~0017872

Marking as resolved based on feedback from reporter.

system

2020-04-19 20:17

developer   ~0023579

Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.

Issue History

Date Modified Username Field Change
2016-01-23 10:42 fox New Issue
2016-01-26 00:05 x42 Note Added: 0017837
2016-01-26 14:16 x42 Note Added: 0017839
2016-01-27 13:00 fox Note Added: 0017844
2016-02-03 02:19 timbyr Note Added: 0017872
2016-02-03 02:19 timbyr Status new => resolved
2016-02-03 02:19 timbyr Resolution open => fixed
2016-02-03 02:19 timbyr Assigned To => timbyr
2020-04-19 20:17 system Note Added: 0023579
2020-04-19 20:17 system Status resolved => closed