public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/24000] couple of testsuite fails with uclibc library
Date: Sat, 09 Feb 2019 22:04:00 -0000	[thread overview]
Message-ID: <bug-24000-10460-bxmIGoCNce@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24000-10460@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=24000

--- Comment #9 from Mark Wielaard <mark at klomp dot org> ---
(In reply to selva from comment #7)
> Created attachment 11582 [details]
> config.log
> 
> Attached the config.log.

>  $ ./configure --target=armv7l-unkown-linux-uclibcgnueabi --host=armv7l-unkown-linux-uclibcgnueabi --build=x86_64-linux-gnu --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --libdir=/usr/lib --libexecdir=/usr/lib --sysconfdir=/etc --datadir=/usr/share --localstatedir=/var --mandir=/usr/share/man --infodir=/usr/share/info --includedir=/usr/include --disable-nls --disable-Werror --enable-largefile --with-biarch --disable-symbol-versioning

That looks like a cross build. It might work, but I never tried myself.
It might be easier to make sure a native build works first.

> =====================================================================
>         elfutils: 0.173 (eu_version: 173)
> =====================================================================

Please try with the latest release: 0.175 

>  RECOMMENDED FEATURES (should all be yes)
>    gzip support                       : yes
>    bzip2 support                      : yes
>    lzma/xz support                    : no
>    libstdc++ demangle support         : yes
>    File textrel check                 : yes
>    Symbol versioning                  : no

Please enable lzma/xz support by installing xz-devel.
Don't disable symbol versioning, without it binary compatibility is broken.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2019-02-09 22:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-17 14:12 [Bug general/24000] New: " ksd.selvakumar at yahoo dot in
2019-01-06 21:06 ` [Bug general/24000] " mark at klomp dot org
2019-01-07  8:30 ` ksd.selvakumar at yahoo dot in
2019-01-13 21:22 ` mark at klomp dot org
2019-01-19  8:31 ` ksd.selvakumar at yahoo dot in
2019-01-23 19:46 ` mark at klomp dot org
2019-02-01  9:31 ` ksd.selvakumar at yahoo dot in
2019-02-01  9:35 ` ksd.selvakumar at yahoo dot in
2019-02-09 21:52 ` mark at klomp dot org
2019-02-09 22:04 ` mark at klomp dot org [this message]
2019-02-18 12:09 ` ksd.selvakumar at yahoo dot in
2019-02-18 12:16 ` ksd.selvakumar at yahoo dot in
2019-02-18 18:51 ` mark at klomp dot org
2019-02-18 18:54 ` mark at klomp dot org
2019-02-19  8:00   ` Ulf Hermann
2019-02-19 10:48     ` Symbol versioning (Was: [Bug general/24000] couple of testsuite fails with uclibc library) Mark Wielaard
2019-02-19 11:30       ` Ulf Hermann
2019-02-19 11:53         ` Mark Wielaard
2019-02-18 21:44 ` [Bug general/24000] couple of testsuite fails with uclibc library mark at klomp dot org
2019-02-19 10:40 ` ksd.selvakumar at yahoo dot in
2019-02-19 15:40 ` [Bug general/24000] couple of ELF compression " mark at klomp dot org
2019-02-20  6:04 ` ksd.selvakumar at yahoo dot in

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=bug-24000-10460-bxmIGoCNce@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=elfutils-devel@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).