From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Jeff Hammond <jhammond@alcf.anl.gov>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] present but cannot be compiled
Date: Wed, 11 Jul 2012 11:28:51 +0800 [thread overview]
Message-ID: <4FFCF2F3.6000504@cn.fujitsu.com> (raw)
In-Reply-To: <CAGKz=u+6VcdDMGyMq02ZkL3J-75TkSvyjQ78Jz2_UEHp_jgMjg@mail.gmail.com>
On 07/05/2012 06:14 AM, Jeff Hammond wrote:
> I'm trying to use LTP on Blue Gene/Q after being told that Open POSIX
> Test was dead. This is not a Linux kernel but is supposed to be
> Linux-like and POSIX-compliant. I am using GCC 4.4.6 and GNU
> binutils.
>
> What kind of information do you want to deal with these issues?
If you just want to test open-posix, please just do
$ cd testcases/open_posix_testsuite/
$ make all
It's no need to compile the ltp part since it's not a Linux-like system,
and some headers may be not consistent with Linux.
Thanks,
Wanlong Gao
>
> configure: WARNING: linux/genetlink.h: present but cannot be compiled
> configure: WARNING: linux/genetlink.h: check for missing
> prerequisite headers?
> configure: WARNING: linux/genetlink.h: see the Autoconf documentation
> configure: WARNING: linux/genetlink.h: section "Present But Cannot
> Be Compiled"
> configure: WARNING: linux/genetlink.h: proceeding with the preprocessor's result
> configure: WARNING: linux/genetlink.h: in the future, the compiler
> will take precedence
> configure: WARNING: ## --------------------------------------------- ##
> configure: WARNING: ## Report this to ltp-list@lists.sourceforge.net ##
> configure: WARNING: ## --------------------------------------------- ##
> ..
> configure: WARNING: linux/netlink.h: present but cannot be compiled
> configure: WARNING: linux/netlink.h: check for missing prerequisite headers?
> configure: WARNING: linux/netlink.h: see the Autoconf documentation
> configure: WARNING: linux/netlink.h: section "Present But Cannot
> Be Compiled"
> configure: WARNING: linux/netlink.h: proceeding with the preprocessor's result
> configure: WARNING: linux/netlink.h: in the future, the compiler will
> take precedence
> configure: WARNING: ## --------------------------------------------- ##
> configure: WARNING: ## Report this to ltp-list@lists.sourceforge.net ##
> configure: WARNING: ## --------------------------------------------- ##
>
> Thanks,
>
> Jeff
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2012-07-11 3:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 22:14 [LTP] present but cannot be compiled Jeff Hammond
2012-07-11 3:28 ` Wanlong Gao [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=4FFCF2F3.6000504@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--cc=jhammond@alcf.anl.gov \
--cc=ltp-list@lists.sourceforge.net \
/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