control: tag -1 help On Sat, 2016-11-19 at 15:15 +0100, Yves-Alexis Perez wrote: > On Mon, 2016-10-31 at 14:00 +0100, Yves-Alexis Perez wrote: > > On Mon, 2016-10-31 at 10:34 +0000, Radovan Birdic wrote: > > > The problem is in liblightdm-qt-3-0.symbols where these symbols are > > > missing. > > > > > > I have created and attached a patch that adds missing symbols into this > > > file > > > and resolves this issue. > > > With this patch package builds successfully on mips*, i386 and amd64 > > > architectures. > > > > I have to admit I'm not really comfortable *removing* symbols from a file > > just > > for some architectures. It looks weird to me that it would only happen on > > those arches. Maybe something changed in Qt but I'm highly puzzled here. > > > > Well, as assumed, the build fails on i386/amd64 with the updated symbols > file. > I might be able to provide multiple symbols file but it does look weird in > any > case.
So, I've tried to build 1.18.2-2 on arm64 (which suceeded in the past), and it now fails, indicating it's indeed a problem somewhere else. I've tried to build using g++5 and it now works fine. So the symbol changes is due to the upgrade to gcc/g++6. I'm not sure it's really expected, so any help appreciated. I'm adding Matthias to CC: in case he has any idea. Matthias: I'm experiencing a build failure in lightdm due to symbol changes in a C++ library only on non intel arches, following upgrade to gcc6. Does that ring you a bell or something? The changed symbols are only destructors: QDBusError::~QDBusError() QByteArray::~QByteArray() QHash<int, QByteArray>::~QHash() QString::~QString() Regards, -- Yves-Alexis
signature.asc
Description: This is a digitally signed message part