From: Josh Boyer <jwboyer-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: Jon Loeliger <jdl-CYoMK+44s/E@public.gmane.org>
Cc: devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org
Subject: Re: [PATCH] libfdt: Use libfdt shared library for testcases
Date: Fri, 2 Jan 2009 12:07:19 -0500 [thread overview]
Message-ID: <20090102170719.GB10193@zod.rchland.ibm.com> (raw)
In-Reply-To: <E1LIm90-00048J-HK-CYoMK+44s/E@public.gmane.org>
On Fri, Jan 02, 2009 at 09:41:02AM -0600, Jon Loeliger wrote:
>> Link the testcases against the libfdt.so that is built and use
>> it for the testsuite verification.
>>
>> Signed-off-by: Josh Boyer <jwboyer-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
>
>Not applied. Something is wrong here, not quite sure what.
>
>First, after I apply this patch, when I do:
>
> $ make clean
> $ make check
>
>I get this:
>
> DEP flattree.c
> DEP dtc.c
> DEP data.c
> DEP checks.c
> CHK version_gen.h
> UPD version_gen.h
> CC tests/get_mem_rsv.o
> cc: -lfdt: linker input file unused because linking not done
> CC libfdt/fdt.o
> CC libfdt/fdt_ro.o
> CC libfdt/fdt_wip.o
> CC libfdt/fdt_sw.o
> CC libfdt/fdt_rw.o
> CC libfdt/fdt_strerror.o
> LD libfdt/libfdt.so
> /usr/bin/ld: cannot find -lfdt
> collect2: ld returned 1 exit status
> make: *** [libfdt/libfdt.so] Error 1
Argh. Yeah, that's annoying. I hate makefile dependency crap.
>Doing just:
>
> $ make
> $ make check
>
>seems to clear it up and it finishes building.
>So that is promising.
Sort of :)
>However, the "make check" yields funny results:
>
> $ make check
>
> ********** TEST SUMMARY
> * Total testcases:1197
> * PASS:88
> * FAIL:0
> * Bad configuration:0
> * Strange test result:1109
> **********
>
>Not sure there at all..
Was that the first version of 'make clean; make check', or
the second version of 'make; make check'?
I ran the tests with 'make; make check' and they all passed
so I'll assume the first. I think you get odd results
because the testcases aren't actually runnable. The
cases where it passes are probably expecting error and/or
don't use libfdt (there are a few like that).
Anyway, I have a few things I need to do today and this
weekend so I'll try to fix up this patch as soon as I can.
josh
prev parent reply other threads:[~2009-01-02 17:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 13:21 [PATCH] libfdt: Use libfdt shared library for testcases Josh Boyer
[not found] ` <20090102132113.GC8954-jnIq6iUNB1CO8iYQgJmm/0EOCMrvLtNR@public.gmane.org>
2009-01-02 15:41 ` Jon Loeliger
[not found] ` <E1LIm90-00048J-HK-CYoMK+44s/E@public.gmane.org>
2009-01-02 17:07 ` Josh Boyer [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=20090102170719.GB10193@zod.rchland.ibm.com \
--to=jwboyer-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
--cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
--cc=jdl-CYoMK+44s/E@public.gmane.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