On 03/08/17 18:40 +0200, Valentin Vidic wrote: > On Tue, Aug 01, 2017 at 11:07:24PM +0200, Jan Pokorný wrote: >> https://bugzilla.redhat.com/1477354 > > Thanks for the info. We are seeing similar problems with the > pacemaker build on Debian now: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869986
Yep, the same issue, because of compiling pacemaker with the same
fancy linker that decided to hide those symbols without notices,
I guess.
Can you somehow scrape the number of project in Debian that
suffer from __{start,stop}_<section> symbols missing? That might
help to convince binutils maintainers there's something wrong.
> Guess we'll need to fix pacemaker libs to get this fixed?
Iterim non-production-ready solution (e.g. equivalent of Fedora
Rawhide):
- use patch(es) from
https://github.com/jnpkrn/libqb/commits/workaround-ld-2.29
above "Doc tweaking (#261)"
- short path: generate and grab "qblog.t", build pacemaker
(and possibly other dependants) with LDFLAGS=<path to qblog.t>,
- longer proper path:
. build updated libqb with that
. rebuild pacemaker on top of that rebuilt libqb
(hopefully it uses pkconfig and hopefuly the patched
libqb.pc will be OK, untested)
Proper solution:
- give me few days to investigate better ways to deal with this
fancy linker, it will likely differ from the iterim one above
(so far, I had quite miserable knowledge of linker script and
other internals, getting better but not without headaches);
we should also ensure there's a safety net because realizing
there are logs missing when they are expected the most
... priceless
Thanks
--
Jan (Poki)
pgpk7ElxDixVU.pgp
Description: PGP signature
_______________________________________________ Developers mailing list [email protected] http://lists.clusterlabs.org/mailman/listinfo/developers
