On Tue, 18 Feb 2020 at 19:40, Kevin Fenzi wrote:
>
> So, I'd say try and duplicate it in a i686 mock chroot on a x86_64
> machine and see if you can gather enough info for a c++ or qt5 bug.
>
> Hope that helps.
Thanks Kevin,
Strangely, as I was attempting to try out what you suggested I got a
"build complete" notification email. I took a glance at the logs to
find a possible clue of what happened and I found the following in
build.log:
---
[100%] Built target muse
<---- 20 hour break (this line is not in the log) ---->
In file included from /usr/include/string.h:495,
from /usr/include/qt5/QtCore/qarraydata.h:44,
from /usr/include/qt5/QtCore/qbytearray.h:46,
from /usr/include/qt5/QtCore/qstring.h:49,
from /usr/include/qt5/QtCore/qdir.h:43,
from /usr/include/qt5/QtCore/QDir:1,
from
/builddir/build/BUILD/muse-3.0.2/synti/deicsonze/deicsonzegui.cpp:30:
In function 'char* strncpy(char*, const char*, size_t)',
inlined from 'void DeicsOnzeGui::setInitSetPath(const QString&)'
at /builddir/build/BUILD/muse-3.0.2/synti/deicsonze/deicsonzegui.cpp:2522:10:
/usr/include/bits/string_fortified.h:106:34: warning: 'char*
__builtin_strncpy(char*, const char*, unsigned int)' specified bound
256 equals destination size [-Wstringop-truncation]
106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
| ~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
---
Seems to me like a valid warning, however it doesn't explain the delay.
Another interesting observation that I forgot to add to the original
post was, the scratch build in koji went through fine before I tried
the actual build.
Maybe your magic touch helped? :)
Thanks,
Orcan
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
