From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Mitani <mitani@ryobi.co.jp>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] About "realtime" build failure
Date: Thu, 11 Nov 2010 13:27:04 +0530 [thread overview]
Message-ID: <1289462224.5622.37.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <000001cb816d$dbdec820$939c5860$@co.jp>
However, yesterdayś git the failure was not there. And hence the reason
for me to replace the October tar.
Regards--
Subrata
On Thu, 2010-11-11 at 15:58 +0900, Mitani wrote:
> Hi,
>
> Build error occured with recent git "ltp-a997c94.tar.gz".
> This failure was caused by "realtime" as follows:
> ------------
> [root@RHEL48-LTP-x86 LTP]# less gitMMDD-makeYYYYMMDD.txt
> [...]
> make[1]: Entering directory `/home/LTP/ltp-a997c94/lib'
> gcc -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall -I../include
> -I../include -
> c -o cloner.o cloner.c
> gcc -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall -I../include
> -I../include -
> c -o dataascii.o dataascii.c
> gcc -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall -I../include
> -I../include -
> c -o databin.o databin.c
> gcc -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall -I../include
> -I../include -
> c -o datapid.o datapid.c
> gcc -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall -I../include
> -I../include -
> c -o file_lock.o file_lock.c
> gcc -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall -I../include
> -I../include -
> c -o forker.o forker.c
> gcc -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall -I../include
> -I../include -
> c -o get_high_address.o get_high_address.c
> gcc -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall -I../include
> -I../include -
> c -o get_path.o get_path.c
> gcc -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall -I../include
> -I../include -
> c -o libtestsuite.o libtestsuite.c
> gcc -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall -I../include
> -I../include -
> c -o open_flags.o open_flags.c
> ...skipping...
> p-a997c94/testcases/realtime/include -I../../../../include
> -I../../../../include
> -L/home/LTP/ltp-a997c94/testcases/realtime/lib -L../../../../lib
> async_handl
> er.c -lrealtime -lpthread -lrt -lm -o async_handler
> In file included from async_handler.c:42:
> /home/LTP/ltp-a997c94/testcases/realtime/include/librttest.h: In function
> `atomi
> c_add':
> /home/LTP/ltp-a997c94/testcases/realtime/include/librttest.h:117: warning:
> impli
> cit declaration of function `__sync_add_and_fetch'
> /home/LTP/ltp-a997c94/testcases/realtime/lib/librealtime.a(librttest.o)(.tex
> t+0x
> 1a7): In function `create_thread':
> /home/LTP/ltp-a997c94/testcases/realtime/lib/../include/librttest.h:117:
> undefin
> ed reference to `__sync_add_and_fetch'
> collect2: ld returned 1 exit status
> make[4]: *** [async_handler] Error 1
> make[4]: Leaving directory
> `/home/LTP/ltp-a997c94/testcases/realtime/func/async_
> handler'
> make[3]: *** [all] Error 2
> make[3]: Leaving directory `/home/LTP/ltp-a997c94/testcases/realtime/func'
> make[2]: *** [all] Error 2
> make[2]: Leaving directory `/home/LTP/ltp-a997c94/testcases/realtime'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/home/LTP/ltp-a997c94/testcases'
> make: *** [testcases-all] Error 2
> ------------
>
> I confirmed that above error is dissolved by following revision:
> ------------
> [root@RHEL48-LTP-x86 ltp-dev-20101111]# diff -u testcases/Makefile.org
> testcases/Makefile
> --- testcases/Makefile.org 2010-11-11 14:20:07.000000000 +0900
> +++ testcases/Makefile 2010-11-11 14:21:25.000000000 +0900
> @@ -37,7 +37,7 @@
> # original list of disabled items...
> # XXX (garrcoop): kdump was in this list.
> # XXX (garrcoop): open_hpi_testsuite was in this list.
> -ifeq ($(UCLINUX),1)
> +ifneq ($(UCLINUX),1)
> FILTER_OUT_DIRS += realtime
> endif
>
> ------------
>
> Is realtime necessary?
> Please revise it if there is not problem.
>
>
> Regards--
>
> -Tomonori Mitani
>
>
>
> ------------------------------------------------------------------------------
> Centralized Desktop Delivery: Dell and VMware Reference Architecture
> Simplifying enterprise desktop deployment and management using
> Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
> client virtualization framework. Read more!
> http://p.sf.net/sfu/dell-eql-dev2dev
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
------------------------------------------------------------------------------
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2010-11-11 7:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 6:58 [LTP] About "realtime" build failure Mitani
2010-11-11 7:57 ` Subrata Modak [this message]
2010-11-11 8:42 ` Garrett Cooper
[not found] <4D0672E6.9000100@ams.org>
2010-12-13 19:42 ` [LTP] About \"realtime\" " Garrett Cooper
[not found] <Act3O838preomyfuTIOsmPN0ITLHHQ==>
2010-10-29 7:35 ` [LTP] About "realtime" " Mitani
2010-11-08 21:51 ` Garrett Cooper
2010-11-09 1:41 ` Mitani
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=1289462224.5622.37.camel@subratamodak.linux.ibm.com \
--to=subrata@linux.vnet.ibm.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=mitani@ryobi.co.jp \
/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