From: "ksd.selvakumar at yahoo dot in" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/24240] New: couple of elftuiltls testsuite fails with uclibc library
Date: Wed, 20 Feb 2019 06:02:00 -0000 [thread overview]
Message-ID: <bug-24240-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=24240
Bug ID: 24240
Summary: couple of elftuiltls testsuite fails with uclibc
library
Product: elfutils
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: general
Assignee: unassigned at sourceware dot org
Reporter: ksd.selvakumar at yahoo dot in
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
Created attachment 11621
--> https://sourceware.org/bugzilla/attachment.cgi?id=11621&action=edit
Complete testsuite log
When elfutils is compiled against uclibc i got the below memory exhaust with
eu-elflint
eu-elflint src/nm.o
invalid machine flags: 0x5000000
eu-elflint: memory exhausted
Attached the whole testsuite log.
Reference
https://sourceware.org/bugzilla/show_bug.cgi?id=24000
--
You are receiving this mail because:
You are on the CC list for the bug.
reply other threads:[~2019-02-20 6:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-24240-10460@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).