From: Indu Bhagat <indu.bhagat@oracle.com>
To: binutils@sourceware.org
Subject: Question regarding min reqd dejagnu version
Date: Fri, 30 Sep 2022 17:18:26 -0700 [thread overview]
Message-ID: <79e9f254-791a-7015-b688-d8f0a409753d@oracle.com> (raw)
Hello,
When testing out the SFrame implementation patches (not yet in trunk) on
an i686-linux machine with gcc-4.9.2 and dejagnu-1.5.1, I believe I run
into the following issue:
https://lists.gnu.org/archive/html/dejagnu/2014-10/msg00011.html
It shows as following when you run make check in libsframe folder:
...
gcc -std=gnu99 -DHAVE_CONFIG_H -I.
-I/<SFRAME-TEST>/binutils-gdb/libsframe/testsuite/libsframe.decode
-I../.. -I/<SFRAME-TEST>/binutils-gdb/libsframe/../include -Wall -g
-O2 -MT frecnt_1-frecnt_1.o -MD -MP -MF .deps/frecnt_1-frecnt_1.Tpo
-c -o frecnt_1-frecnt_1.o `test -f 'frecnt_1.c' || echo
'/<SFRAME-TEST>/binutils-gdb/libsframe/testsuite/libsframe.decode/'`frecnt_1.c
mv -f .deps/frecnt_1-frecnt_1.Tpo .deps/frecnt_1-frecnt_1.Po
/bin/bash ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2
-o frecnt_1 frecnt_1-frecnt_1.o ../../libsframe.la
libtool: link: gcc -std=gnu99 -g -O2 -o .libs/frecnt_1
frecnt_1-frecnt_1.o ../../.libs/libsframe.so -Wl,-rpath
-Wl,/<SFRAME-TEST>/install/lib
frecnt_1-frecnt_1.o: In function `main':
/<SFRAME-TEST>/binutils-gdb/libsframe/testsuite/libsframe.decode/frecnt_1.c:80:
undefined reference to `fail'
/<SFRAME-TEST>/binutils-gdb/libsframe/testsuite/libsframe.decode/frecnt_1.c:83:
undefined reference to `pass'
...
libsframe testsuite depends on dejagnu.h (patch link
https://sourceware.org/pipermail/binutils/2022-September/123172.html).
I am wondering what should be the expectation here. Is there a minimum
version of dejagnu that can be expected from the users ?
Thanks
Indu
next reply other threads:[~2022-10-01 0:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 0:18 Indu Bhagat [this message]
2022-10-03 10:23 ` Nick Clifton
2022-10-03 17:55 ` Indu Bhagat
2022-10-04 9:52 ` Nick Clifton
2022-10-04 10:05 ` Jan Beulich
2022-10-04 10:20 ` Nick Clifton
2022-10-04 10:27 ` Jan Beulich
2022-10-04 11:40 ` Nick Clifton
2022-10-05 18:28 ` Indu Bhagat
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=79e9f254-791a-7015-b688-d8f0a409753d@oracle.com \
--to=indu.bhagat@oracle.com \
--cc=binutils@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).