Apache OpenOffice (AOO) Bugzilla – Issue 116423
[gbuild] ld hash-style both
Last modified: 2017-05-20 10:31:50 UTC
configure prints: checking for --hash-style=both linker support ... not found unxlng.mk has: .IF "$(HAVE_LD_HASH_STYLE)" == "TRUE" LINKFLAGS += -Wl,--hash-style=both .ELSE LINKFLAGS += -Wl,-zdynsort .ENDIF but solenv/gbuild/platform/linux.mk has: -Wl,--hash-style=both \ Please make this conditional as well.
another one for b_michaelsen.... i wonder: since when is this --hash-style=both support in binutils? is it missing only on ancient distros, or did it fail for you (pjanik) on something that isn't so old?
My build machine is Mac OS X Tiger.
accepting (Status -> STARTED) adding issue to cws gnumake3
@pjanik: "solenv/gbuild/platform/linux.mk has" vs. "build machine is Mac OS X Tiger"?!? ;)
ok, ok, I intermixed two issues :-) This issue is on some old SUSE chroot.I think it is 10.0.
Unconditionally falling back on some setting that is rather new (dynsort) and still undocumented in the ld manpage, when configure tells us that ld does not even support --hash-style=both (and that test looks sensible in configure.in) is ... weird. Not using the feature when we have --hash-style=both support is also ... weird (unless it it enabled by default now, but still). @pjanik: Do have any insight on this? Or can mmeeks provide some as he seems to have implemented dynsort for ld?
@mmeeks: do you happen to know whether this fallback from --hash-style=both to -zdynsort makes sense?
-zdynsort was rather useful - but only before --hash-style=both arrived. I believe its deployment is rather tiny now (I hope so anyway), so - I would fall back to nothing. Though, you really want -zcombreloc (though I think we had that already). Hope that helps :-)
Thanks for the hints. Ok, so we will simply fall back to nothing in this case. As for -zcombreloc, my google foo suggests it is enabled by default at least since binutils 2.15.
fixed in gnumake3 (hash-style-both when available, fallback to nothing otherwise). -zcombreloc is always set, although it is on by default on a modern toolchain.
@pjanik: please verify
getting rid of value "enhancement" for field "severity". For enhancement the field "issue type" shall be used.