From: Nurdin Premji <npremji@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: frysk@sourceware.org, npremji@sourceware.org
Subject: Re: frysk-imports/elfutils src/ranlib.c src/Change ...
Date: Fri, 16 Feb 2007 17:16:00 -0000 [thread overview]
Message-ID: <45D5E4E2.8090608@redhat.com> (raw)
In-Reply-To: <1171627495.3385.4.camel@dijkstra.wildebeest.org>
Mark Wielaard wrote:
>> find-prologues funcretval allregs rdwrmmap
>> -# dwfl-bug-addr-overflow
>> + dwfl-bug-addr-overflow arls
>>
>>
> The newly enabled dwfl-bug-addr-overflow test doesn't compile for me with make check:
>
> make[5]: Entering directory `/home/mark/src/frysk-clean/frysk-clean-obj/frysk-imports/elfutils/tests'
> gcc -g -O2 ../../../../frysk/frysk-imports/elfutils/tests/dwfl-bug-addr-overflow.c -o dwfl-bug-addr-overflow
> ../../../../frysk/frysk-imports/elfutils/tests/dwfl-bug-addr-overflow.c:26:20: error: config.h: No such file or directory
> ../../../../frysk/frysk-imports/elfutils/tests/dwfl-bug-addr-overflow.c:33:10: error: #include expects "FILENAME" or <FILENAME>
>
>
Aha, missing an ending \ on the previous line. that got fixed. Wonder
why that didn't cause a bigger explosion with some random files hanging
around in a Makefile. Oh well.
> Also the run-elflint-test FAILs:
>
> section [22] '.dynamic': mandatory tag HASH not present
> section [22] '.dynamic': contains SYMTAB entry but not HASH
> FAIL: run-elflint-test.sh
>
> Could you take a look?
>
I took a look at this, I'm not sure how to fix it so I just commented
out the two tests that were added in version 0.126.
So make check should now pass again, at least on imports.
prev parent reply other threads:[~2007-02-16 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070215205220.11016.qmail@sourceware.org>
2007-02-16 12:05 ` Mark Wielaard
2007-02-16 17:16 ` Nurdin Premji [this message]
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=45D5E4E2.8090608@redhat.com \
--to=npremji@redhat.com \
--cc=frysk@sourceware.org \
--cc=mark@klomp.org \
--cc=npremji@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).