From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: GNU C Library <libc-alpha@sourceware.org>,
Florian Weimer <fweimer@redhat.com>
Subject: Re: Newer hwcap failures
Date: Thu, 28 Jan 2021 15:52:00 -0300 [thread overview]
Message-ID: <e5801055-289e-249b-6b3d-c9dae66ce4d4@linaro.org> (raw)
In-Reply-To: <c67c8914-c8e0-9dc5-d59c-b697c4ded8df@linaro.org>
On 28/01/2021 15:47, Adhemerval Zanella wrote:
> Hi Florian,
>
> I am seeing two tests failures on system with support 32-bit and 64-bit
> ABIs (powerpc, sparc, x86). All of them are 64-bit kernel and userland
> running 32-bit ABIs.
>
> FAIL: elf/tst-glibc-hwcaps-prepend-cache
> FAIL: elf/tst-ldconfig-ld_so_conf-update
>
> $ cat elf/tst-ldconfig-ld_so_conf-update.out
> error: tst-ldconfig-ld_so_conf-update.c:112: not true: dlopen (DSO, RTLD_NOW | RTLD_GLOBAL) != NULL
> error: 1 test failures
> running post-clean rsync
>
> $ cat elf/tst-glibc-hwcaps-prepend-cache.out
> error: xdlfcn.c:29: error: dlopen: libmarkermod1.so: cannot open shared object file: No such file or directory
>
> error: 1 test failures
> running post-clean rsync
>
>
> Debugging the tst-ldconfig-ld_so_conf-update it seems that for some
> reason ldconfig is not updating the search path. Modifying the testcase
> to print the dlerror:
>
> dlopen (libldconfig-ld-mod.so): libldconfig-ld-mod.so: cannot open shared object file: No such file or directory
>
> I am trying to run strace on the container environment, but it seems
> that it gets confused (it triggers a failure in the rename call).
>
> Any idea?
Also as a side note, I think it would be useful to add a note
about this new glibc-hwcap feature on NEWS.
next prev parent reply other threads:[~2021-01-28 18:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 18:47 Adhemerval Zanella
2021-01-28 18:52 ` Adhemerval Zanella [this message]
2021-01-28 19:53 ` Florian Weimer
2021-01-28 20:01 ` Adhemerval Zanella
2021-01-28 20:21 ` Adhemerval Zanella
2021-01-28 20:30 ` Adhemerval Zanella
2021-01-28 21:23 ` Adhemerval Zanella
2021-01-28 22:03 ` DJ Delorie
2021-01-29 5:56 ` Florian Weimer
2021-01-29 6:07 ` DJ Delorie
2021-01-29 6:09 ` DJ Delorie
2021-01-29 9:20 ` Florian Weimer
2021-01-29 10:43 ` Szabolcs Nagy
2021-01-29 10:48 ` Florian Weimer
2021-01-29 10:51 ` Szabolcs Nagy
2021-01-29 11:53 ` Adhemerval Zanella
2021-01-29 12:46 ` H.J. Lu
2021-01-29 12:31 ` Florian Weimer
2021-01-29 13:06 ` Adhemerval Zanella
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e5801055-289e-249b-6b3d-c9dae66ce4d4@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).