From: Mike Frysinger <vapier@gentoo.org>
To: ltp-list@lists.sourceforge.net, Garrett Cooper <yanegomi@gmail.com>
Subject: Re: [LTP] Build Fails on some archs
Date: Tue, 3 Nov 2009 12:30:52 -0400 [thread overview]
Message-ID: <200911031130.53505.vapier@gentoo.org> (raw)
In-Reply-To: <200911021702.09153.vapier@gentoo.org>
[-- Attachment #1.1: Type: Text/Plain, Size: 1600 bytes --]
On Monday 02 November 2009 17:02:08 Mike Frysinger wrote:
> On Monday 02 November 2009 08:33:55 Subrata Modak wrote:
> > gcc -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall
> > -I/root/subrata/ltp/ltp-full-20091031/testcases/kernel/include
> > -I../../../../include -I../../../../include -L../../../../lib
> > ptrace04.c -lltp -o ptrace04
> > ptrace03.c: In function 'main':
> > ptrace03.c:182: warning: format '%d' expects type 'int', but argument 3
> > has type 'long int'
> > ptrace04.c: In function 'compare_registers':
> > ptrace04.c:50: error: storage size of 'pt_regs' isn't known
> > ptrace04.c:50: warning: unused variable 'pt_regs'
> > make[4]: *** [ptrace04] Error 1
>
> the ptrace stuff has always been fairly unfriendly to cross-arch work.
> we'll probably have to add header tests for a bunch of files and unify it
> in a local ptrace.h header.
>
> > gcc -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall
> > -I../../../../include -I../../../../include -L../../../../lib
> > tomoyo_file_test.c -o tomoyo_file_test
> > /tmp/ccvzdsNd.o: In function `main':
> > /root/subrata/ltp/ltp-full-20091031/testcases/kernel/security/tomoyo/newn
> >s. c:43: undefined reference to `clone' collect2: ld returned 1 exit
> > status
>
> these test cases need to be changed to the new common ltp clone code. as
> part of that, we should probably add a macro that changes clone() to a
> compile error so that people stop using it by accident
> #define clone(...) DO_NOT_USE_CLONE
i'll take care of both of these issues if you want to look at the others
-mike
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 399 bytes --]
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
[-- Attachment #3: Type: text/plain, Size: 155 bytes --]
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-11-03 16:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 13:33 [LTP] Build Fails on some archs Subrata Modak
2009-11-02 14:09 ` Cyril Hrubis
2009-11-02 22:02 ` Mike Frysinger
2009-11-03 16:30 ` Mike Frysinger [this message]
2009-11-03 16:34 ` Garrett Cooper
2009-11-03 17:15 ` Garrett Cooper
2009-11-09 17:39 ` Subrata Modak
2009-11-03 13:06 ` Garrett Cooper
2009-11-03 20:10 ` Mike Frysinger
[not found] <mailman.103093.1257283106.5825.ltp-list@lists.sourceforge.net>
2009-11-04 5:41 ` Mark Ver
2009-11-04 5:58 ` Garrett Cooper
2009-11-05 1:43 ` Mark Ver
2009-11-05 8:41 ` Garrett Cooper
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=200911031130.53505.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=ltp-list@lists.sourceforge.net \
--cc=yanegomi@gmail.com \
/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