From: "Sébastien Dugué" <sebastien.dugue@bull.net>
To: vikas gupta <vikas_gupta51013@yahoo.co.in>
Cc: linux-aio@kvack.org, linux-kernel@vger.kernel.org, bcrl@kvack.org
Subject: Re: AIO Support and related package information??
Date: Wed, 28 Sep 2005 15:35:25 +0200 [thread overview]
Message-ID: <1127914525.2069.46.camel@frecb000686> (raw)
In-Reply-To: <20050928125815.74025.qmail@web8405.mail.in.yahoo.com>
On Wed, 2005-09-28 at 13:58 +0100, vikas gupta wrote:
> hi Sebastien,
>
> Thanks for your Support
> well i am able to build for arm platform by removing
> all the exit statments from configure script but while
> executing on arm board ,i am getting this result log
> for libposix-0.6/check :
>
> aio_cancel: cancel error : 1 (Operation not permitted)
> aio_cancel_fd: cancel returned AIO_NOTCANCELED
> aio_fsync: fsync error 1 (Operation not permitted)
> aio_read_one_sig: aio_read error: Invalid argument
> aio_read_one_thread: aio_read error: Invalid argument
> aio_read_one_thread_id: aio_read error: Invalid
> argument
> aio_suspend: Cannot create testfile: Invalid argument
> aio_suspend_timeout: Cannot create testfile: Invalid
> argument
> aio_write_one_sig: aio_write error: Invalid argument
> aio_write_thread: aio_write error: Invalid argument
> aio_write_one_thread_id: aio_write error: Invalid
> argument
> lio_listio_wait: Cannot open testfile: Invalid
> argument
> lio_listio_nowait: Cannot open testfile: Invalid
> argument
>
> only two test cases ./aio_read_one and ./aio_write_one
> is not giving
> any
> error
>
> Is this justified
> Do you think it is correct ,This is with bare
> kernel2.6.11 and libposix-0.6 package
This is perfectly normal as a vanilla kernel only have
support for aio_read and aio_write without event notification
so only aio_read_one and aio_write_one will pass
> 2)
>
> > ./configure --disable-default-maxevents
> > --disable-aio-signal
> > --disable-lio-signal --disable-lio-wait
> > --disable-cancel-fd
> > --disable-buffered-aio
> >
> > that way, the configure script will not try to
> > autodetect
> > kernel features.
> >
> > The configure options available may be found with
> >
> > configure --help
> >
> > aio_read and aio_write with no event notification
> > should work
> > provided you implemented the ARM syscall wrappers.
>
> I tried this approach but i am getting these errors
>
> Errors :
>
> checking for signal support on AIO completion...
> configure: error:
> cannot
> run test program while cross compiling
> See `config.log' for more details.
> checking for signal support on LIO completion...
> configure: error:
> cannot
> run test program while cross compiling
>
> Can this be Resolved
Strange, if you gave the --disable-aio-signal and
--disable-lio-signal arguments, configure should not even
try to check those features. Send me your resulting
config.log.
Sébastien.
--
------------------------------------------------------
Sébastien Dugué BULL/FREC:B1-247
phone: (+33) 476 29 77 70 Bullcom: 229-7770
mailto:sebastien.dugue@bull.net
Linux POSIX AIO: http://www.bullopensource.org/posix
------------------------------------------------------
next prev parent reply other threads:[~2005-09-28 13:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 3:08 AIO Support and related package information?? vikas gupta
2005-09-22 7:46 ` Sébastien Dugué
2005-09-23 3:10 ` vikas gupta
2005-09-23 7:05 ` Sébastien Dugué
2005-09-26 7:32 ` vikas gupta
2005-09-26 8:59 ` Sébastien Dugué
2005-09-26 9:13 ` vikas gupta
2005-09-26 13:45 ` Sébastien Dugué
2005-09-26 14:06 ` vikas gupta
2005-09-26 14:34 ` Sébastien Dugué
2005-09-27 7:09 ` vikas gupta
2005-09-28 7:25 ` Sébastien Dugué
2005-09-28 12:57 ` vikas gupta
2005-09-28 12:58 ` vikas gupta
2005-09-28 13:35 ` Sébastien Dugué [this message]
2005-09-28 14:04 ` vikas gupta
2005-09-29 9:31 ` Sébastien Dugué
2005-09-30 3:07 ` vikas gupta
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=1127914525.2069.46.camel@frecb000686 \
--to=sebastien.dugue@bull.net \
--cc=bcrl@kvack.org \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vikas_gupta51013@yahoo.co.in \
/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