From: Stanislav Pankevich <s.pankevich@gmail.com>
To: newlib@sourceware.org
Subject: [libm] How to run tests in newlib-cygwin/newlib/libm/test/* ?
Date: Fri, 18 Aug 2017 14:11:00 -0000 [thread overview]
Message-ID: <CAFXpGYaTmy+kH0uYGyQqT6oedLbmCHvMmCLqSy2q8-xQ_fVgiQ@mail.gmail.com> (raw)
Hello again,
I decided to try Docker image with Ubuntu to see if it will change
anything. I was able to compile libm.a, libc.a, etc using
../newlib-cygwin/configure --target=x86_64 && make
However I still don't see any automated way to run the tests from
libm/test/* group.
- - - -
If I start trying to run them manually by doing dirty things like:
make -f Makefile.in
CFLAGS="-I../../../../newlib-cygwin/newlib/libc/include" I get
test_is.c:2021:15: error: '_tolower' undeclared (first use in this function)
test_to_set(_tolower, "_tolower function", &setlower, 'A','Z');
^
test_is.c:2021:15: note: each undeclared identifier is reported only
once for each function it appears in
test_is.c:2022:15: error: '_toupper' undeclared (first use in this function)
test_to_set(_toupper, "_toupper function", &setupper, 'a','z');
^
<builtin>: recipe for target 'test_is.o' failed
I would appreciate an advice on how these tests should be run.
Thanks,
Stanislav
On Tue, Aug 15, 2017 at 5:55 PM, Stanislav Pankevich
<s.pankevich@gmail.com> wrote:
> Hello,
>
> We are developers of mutation testing system based on top of LLVM:
> Mull [1]. For our research we would like to analyze libm with our
> tool.
>
> I was able to compile libm and get the libm.a on Mac OS however I
> don't see any targets in newlib-cygwin/newlib/libm/**'s Makefiles
> which would produce a binary executable from test.c file which I
> believe is the test driver for these tests.
>
> I didn't find any information in README file how to setup and run the
> tests for libm. README describes how to run dejagnu-based tests but I
> didn't find such tests for libm so I suppose the tests for libm are
> run via a separate method.
>
> I could create my own Makefile to assemble all the pieces and run
> test.c myself but I hope there is a better way of running tests.
>
> Any hints are appreciated.
>
> Thanks,
>
> Stanislav
>
> [1] https://github.com/mull-project/mull
reply other threads:[~2017-08-18 7:41 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=CAFXpGYaTmy+kH0uYGyQqT6oedLbmCHvMmCLqSy2q8-xQ_fVgiQ@mail.gmail.com \
--to=s.pankevich@gmail.com \
--cc=newlib@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).