Bug#908459: theseus FTBFS with gcc 8
On Fri, Sep 14, 2018 at 10:50:36AM +0200, Fabian Klötzl wrote: > > On 11.09.2018 15:58, Adrian Bunk wrote: > > Control: reopen -1 > > > > Some builds were still running into #897876 due to the buildd chroots > > only regenerated twice per week (which is not something you should be > > worried about), but the armhf/i386 and ppc64el FTBFS look more like > > actual problems that need fixing in theseus. > > Unfortunately, fixing this will take a while longer. I first have to figure > out how to build an arm vm because I don't want to debug remotely via the > autobuilds. ☺ i386 looks like the same problem as arm, debootstrap --arch=i386 sid i386-sid would be one way to create a root filesystem for that you can then chroot into. > Best, > Fabian cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#908459: theseus FTBFS with gcc 8
On 11.09.2018 15:58, Adrian Bunk wrote: Control: reopen -1 Some builds were still running into #897876 due to the buildd chroots only regenerated twice per week (which is not something you should be worried about), but the armhf/i386 and ppc64el FTBFS look more like actual problems that need fixing in theseus. Unfortunately, fixing this will take a while longer. I first have to figure out how to build an arm vm because I don't want to debug remotely via the autobuilds. ☺ Best, Fabian
Processed: Re: Bug#908459: theseus FTBFS with gcc 8
Processing control commands:
> reopen -1
Bug #908459 {Done: Fabian Kloetzl } [src:theseus]
theseus FTBFS with gcc 8
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions theseus/3.3.0-7.
--
908459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#908459: theseus FTBFS with gcc 8
Control: reopen -1 On Mon, Sep 10, 2018 at 03:18:13PM +0200, Fabian Klötzl wrote: >... > On 10.09.18 13:59, Andreas Tille wrote: > > /usr/bin/gcc -O3 -ffast-math -fstrict-aliasing -funroll-loops > > -fomit-frame-pointer -Wall -Werror -pedantic -std=c99 -Wno-unused-result > > -Wformat-truncation=0 -pthread -c logistic_dist.c > > logistic_dist.c: In function 'evallogisticML': > > logistic_dist.c:172:1: error: 'reciptmp.16' is used uninitialized in this > > function [-Werror=uninitialized] > > evallogisticML(const double *x, const int n, > > ^~ > > cc1: all warnings being treated as errors > > > > That is a compiler bug [1, 2]. Temporarily deactivating -ffast-math or > -Werror should help to move on, nonetheless. Some builds were still running into #897876 due to the buildd chroots only regenerated twice per week (which is not something you should be worried about), but the armhf/i386 and ppc64el FTBFS look more like actual problems that need fixing in theseus. > Best, > Fabian >... cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#908459: theseus FTBFS with gcc 8
Hi Andreas, On 10.09.18 13:59, Andreas Tille wrote: > /usr/bin/gcc -O3 -ffast-math -fstrict-aliasing -funroll-loops > -fomit-frame-pointer -Wall -Werror -pedantic -std=c99 -Wno-unused-result > -Wformat-truncation=0 -pthread -c logistic_dist.c > logistic_dist.c: In function 'evallogisticML': > logistic_dist.c:172:1: error: 'reciptmp.16' is used uninitialized in this > function [-Werror=uninitialized] > evallogisticML(const double *x, const int n, > ^~ > cc1: all warnings being treated as errors > That is a compiler bug [1, 2]. Temporarily deactivating -ffast-math or -Werror should help to move on, nonetheless. Best, Fabian 1: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86835 2: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897876
Bug#908459: theseus FTBFS with gcc 8
On Mon, Sep 10, 2018 at 12:47:34PM +0200, Fabian Klötzl wrote: > Thanks for reporting. There were plenty of string related errors. Fixed in > git repo. Hmmm, the string related errors are gone - thanks /usr/bin/gcc -O3 -ffast-math -fstrict-aliasing -funroll-loops -fomit-frame-pointer -Wall -Werror -pedantic -std=c99 -Wno-unused-result -Wformat-truncation=0 -pthread -c logistic_dist.c logistic_dist.c: In function 'evallogisticML': logistic_dist.c:172:1: error: 'reciptmp.16' is used uninitialized in this function [-Werror=uninitialized] evallogisticML(const double *x, const int n, ^~ cc1: all warnings being treated as errors Do you have any idea how to fix this? Kind regards Andreas. -- http://fam-tille.de
Bug#908459: Bug#908459: theseus FTBFS with gcc 8
Cool. Das macht dann auf jeden Fall einen $drink wie in der anderen Mail versprochen. Dein einer commit zu pbbam ist auch einen Wert - da schreibe ich noch mal was dazu ... Erinner mich aber bitte, wenn wir uns sehen. ;-) Bis dann Andreas. On Mon, Sep 10, 2018 at 12:47:34PM +0200, Fabian Klötzl wrote: > Thanks for reporting. There were plenty of string related errors. Fixed in > git repo. > > ___ > Debian-med-packaging mailing list > debian-med-packag...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging -- http://fam-tille.de
Bug#908459: [Debian-med-packaging] Bug#908459: theseus FTBFS with gcc 8
Thanks for reporting. There were plenty of string related errors. Fixed in git repo.
Bug#908459: theseus FTBFS with gcc 8
Source: theseus Version: 3.3.0-6 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/theseus.html ... /usr/bin/gcc -O3 -ffast-math -fstrict-aliasing -funroll-loops -fomit-frame-pointer -Wall -Werror -pedantic -std=c99 -Wno-unused-result -pthread -c DLTutils.c DLTutils.c: In function 'mystrncpy': DLTutils.c:159:5: error: 'strncpy' specified bound depends on the length of the source argument [-Werror=stringop-overflow=] strncpy(s1, s2, len); ^~~~ DLTutils.c:156:26: note: length computed here size_t len = strlen(s2); /* minimum allocated length of s2 */ ^~ DLTutils.c: In function 'mystrcpy': DLTutils.c:173:5: error: 'strncpy' output truncated before terminating nul copying as many bytes from a string as its length [-Werror=stringop-truncation] strncpy(s1, s2, len); ^~~~ DLTutils.c:171:27: note: length computed here size_t len = strlen(s2); ^~ In function 'mystrcpy', inlined from 'mystrcat' at DLTutils.c:187:5: DLTutils.c:173:5: error: 'strncpy' specified bound depends on the length of the source argument [-Werror=stringop-overflow=] strncpy(s1, s2, len); ^~~~ DLTutils.c: In function 'mystrcat': DLTutils.c:171:27: note: length computed here size_t len = strlen(s2); ^~ In function 'mystrcpy', inlined from 'GetUniqFileNameNum' at DLTutils.c:323:5: DLTutils.c:173:5: error: 'strncpy' output truncated before terminating nul copying as many bytes from a string as its length [-Werror=stringop-truncation] strncpy(s1, s2, len); ^~~~ DLTutils.c: In function 'GetUniqFileNameNum': DLTutils.c:171:27: note: length computed here size_t len = strlen(s2); ^~ In function 'mystrcpy', inlined from 'GetUniqFileNameNum' at DLTutils.c:323:5, inlined from 'myfopen' at DLTutils.c:342:5: DLTutils.c:173:5: error: 'strncpy' output truncated before terminating nul copying as many bytes from a string as its length [-Werror=stringop-truncation] strncpy(s1, s2, len); ^~~~ DLTutils.c: In function 'myfopen': DLTutils.c:171:27: note: length computed here size_t len = strlen(s2); ^~ In function 'mystrncpy', inlined from 'getroot' at DLTutils.c:560:5: DLTutils.c:159:5: error: 'strncpy' specified bound depends on the length of the source argument [-Werror=stringop-overflow=] strncpy(s1, s2, len); ^~~~ DLTutils.c: In function 'getroot': DLTutils.c:556:30: note: length computed here int length = strlen(filename); ^~~~ cc1: all warnings being treated as errors make[3]: *** [Makefile:10: DLTutils.o] Error 1
