On Sun, Aug 25, 2019 at 03:49:47PM -0400, Jean-Marc Pigeon via blfs-dev wrote:
> Hello guys (and girls).
> 
> I need your wisdom... Let's share a pint of brain juice.
> Here's the drill.
> 
> context:
> - LFS-9.0rc (linux 5.2.8, glibc-2.30, gcc-9.2.0)
> - I am able to build libreoffice-6.3.0.4 with all
>   bells and whistles
> (lets assume I didn't really goofed with the book directives).
> 
> I am using zypper + rpm as my own packages management toolkit
> and rpm say:
> 
> Error: Failed dependencies:
>       rtld(GNU_HASH) is needed by libreoffice-6.3.0.4-1.53.249.ok_9.0.x86_64
> 
[...]
> 
> My "friend" Google:
> According my understanding of Google, this kind of problem
> is caused by the libc library not in pace (lib version)
> with package. This seems very unlikely, in our context
> libreoffice is compiled with the running glibc.
> 

The first match which google gave me (stackoverflow.com from 2011)
suggests this can also happen when glibc is built with binutils
less than 2.17.  That is also very unlikely.

In general, the first matches were related to yum (and I think
zypper is related to that).  There was a suggestion (for Arm) that POSIX
threads were not enabled in Arm glibc before the glibc-2.3.4
series.  All very old, but I wonder if the fault might be in your
builds of zypper or rpm.

Google also suggested related searches including openoffice.org.
From 2008,
https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=472093
where the problem seemed to be in rpm (or, perhaps, the specfile).

> 
> Questions:
> 1) Could someone give us some enlightenment  about
>    what is rtld (GNU_HASH) exactly?

I have no idea, but all the top google matches seem to involve rpms
(i.e. people asking 'which rpm do I need to provide it).

> 2) I noticed libreoffice come with its own set of luggage
>    (some as esoteric as
>    ba2930200c9f019c2d93a8c88c651a0f-flow-engine-0.9.4.zip)
>    but I'll be very surprised libreoffice loading/using its own
>    precompiled glibc, agreed?

Yes, if you exclude the fonts (which I do in my own builds since I
consider I have adequate coverage, and installing fonts which are
only usable by LO is annoying) there are still many of them.  The
total set is in 'download.lst'.

In BLFS our policy for these seems to be : if it is a released
version, use a system version if we have it in the book, but do not
add extra deps to the book unless they fix a build problem (or are
more-generally usable.

Some of these packages _might_ be releases, e.g. your flow-engine
example might just be a hash for a particular git tag, or it might
have been locally modified, or never released.

Anyway, since you are using zypper I assume you are familiar with
OpenSuSe srpms.  I think they, like fedora, do not let libreoffice
download packages and instead make each one into a separate
dependency.  The links to OpenSuse and Fedora in 'Going Beyond BLFS'
at the start of the book should work (unfortunately srpm only for
both of them, not git trees).

>    However, I have the very strong feeling the problem
>    is caused by the "zillion" of external/outdated
>    components downloaded by the build process.
> 2) Could the problem be within the glibc library I/We
>    have build  (a glibc building sequence weakness?)

Since it only ever seemed to have been reported in the context of
rpm, and mostly in the distant past, I doubt it .

> 3) I am very curious to find+understand from where the
>    RTLD story is coming from. I was not good enough
>    to extract something useful by doing a binary objdump
>    to track down the origin.
>    Could someone propose a search path?
> 

For that, I've made no progress.

> 
> Thanks for your kind help and your wisdom.
> 

Good luck in investigating this.  I hope you find out where the
problem is.

ĸen
-- 
Adopted by dwarfs, brought up by dwarfs.  To dwarfs I'm a dwarf, sir.
I can do the rite of k'zakra, I know the secrets of h'ragna, I can
ha'lk my g'rakha correctly ... I am a dwarf
           Captain Carrot Ironfoundersson (in The Fifth Elephant)
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to