[Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04
Rik Mills
rik.mills88 at gmail.com
Tue Feb 14 10:05:20 UTC 2017
On 10/02/17 09:48, Andre Heinecke wrote:
> Ah but now armhf and arm64 fail because of the same problem. The
> connects in the Qt Testsuite fail.
>
> As I already mentioned I think its some incompatibility between the Qt
> buildflags and the QGpgME buildflags:
>
> https://bugreports.qt.io/browse/QTBUG-36129 but I'm not sure what the
> suggestion from this should be. Adding pie to the compile flags? Or
> removing the -Bsymbolic-functions (Debian does not use that flag). I
> don't have much knowledge on these kinds of problems.
thiago = Thiago Macieira (from your buglink)
#kde-devel on irc.freenode.net
[20:59] <thiago> acheronuk: any chance you can get me the build logs in
the actual server?
[20:59] <thiago> if the -Bsymbolic-functions argument is there, that's
the reason
[20:59] <thiago> that option is ABI-incompatible outside
strictly-controlled environments
[21:00] <thiago> it should be opt-in, not opt-out
[21:03] <acheronuk> all I have
https://launchpadlibrarian.net/305535133/buildlog_ubuntu-zesty-arm64.gpgme1.0_1.8.0+git20170207-0build1_BUILDING.txt.gz
[21:23] <thiago> acheronuk: thanks
[21:24] <thiago> acheronuk: /bin/bash ../../../libtool --tag=CXX
--mode=link g++ [...] -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now
-o libqgpgme.la [...]
[21:24] <thiago> culprit found
[21:25] <svuorela> thiago: that log file seems to be full of
-Bsymbolic-functions
[21:25] <thiago> it is
[21:26] <thiago> the one that matters is the one I pasted: libqgpgme.so
was linked with it
[21:27] <svuorela> the debian build log does not look like it contains that
[21:28] <thiago> as I said, outside of x86-64, you have to make it opt-in
[21:28] <acheronuk> thiago: thx. now I have to work out how to get rid
of that without nuking the rest of the build
[21:29] <svuorela> acheronuk: talk to your toolchain maintainers
[21:29] <svuorela> I guess that's where it is injected
[21:32] <thiago> acheronuk: nuke the rest of the build and rebuild the world
[21:33] <thiago> I'm not kidding
[21:33] <thiago> rebuild the world
[21:33] <thiago> if your toolchain people don't like the change, they
can join the club. I've been trying to get GCC+binutils folks to do
something about unnecessary ELF interposition for some time
How to achieve a working solution is something I still don't know
though.
For my purposes, I care very little if arm* builds break/fail, but is
obviously an issue for others, and regards getting this out of
'-proposed' wilderness.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gpgme1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1647204
Title:
1.8.0-2 FTBFS in zesty 17.04
Status in gpgme1.0 package in Ubuntu:
Confirmed
Bug description:
1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all
architectures from source with the error:
checking whether a simple qt program can be built... no
configure: error:
***
*** Qt5 (Qt5Core) is required for Qt binding.
***
The packages builds without this issue in debian unstable.
A little experimentation shows that is a ubuntu sbuild/pbuilder and
ppa, setting -pie in the hardening options allows the build to proceed
with the Qt bindings building properly.
Not being overly familiar with the hardening, I am unsure if dropping
that feature set is relatively harmless, or massively undesirable and
potentially harmful.
However, in a ppa build, but NOT in my local sbuild/pbuilder chroot,
the resulting build then hangs on the (python?) tests on starting or
stopping gpg-agent, and the build is eventually killed due to
inactivity after 150 mins as follows
GNUPGHOME=/<<PKGBUILDDIR>>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" /usr/bin/python3 ./run-tests.py \
--interpreters="/usr/bin/python /usr/bin/python3" --srcdir=. \
initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py
starting gpg-agent
Session terminated, terminating shell...make[1]: *** wait: No child processes. Stop.
make[1]: *** Waiting for unfinished jobs....
make[1]: *** wait: No child processes. Stop.
make[3]: *** wait: No child processes. Stop.
make[3]: *** Waiting for unfinished jobs....
make[3]: *** wait: No child processes. Stop.
...terminated.
make: *** wait: No child processes. Stop.
make: *** Waiting for unfinished jobs....
make: *** wait: No child processes. Stop.
Makefile:457: recipe for target 'check-recursive' failed
make[2]: *** [check-recursive] Terminated
Makefile:602: recipe for target 'xcheck' failed
make[4]: *** [xcheck] Terminated
Build killed with signal TERM after 150 minutes of inactivity
I would note that this is the first gpgme version from gpg directly,
with the Qt bindings built. These will be essential for future KDE
applications and frameworks, as the gpgmepp previously built in KDE's
own packages is being dropped.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+subscriptions
More information about the foundations-bugs
mailing list