linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 09:25:24 +0200	[thread overview]
Message-ID: <1127892324.2103.39.camel@frecb000686> (raw)
In-Reply-To: <20050927070933.77908.qmail@web8409.mail.in.yahoo.com>

On Tue, 2005-09-27 at 08:09 +0100, vikas gupta wrote:
> HI Sebastien,
> Thanks for your Reply 
> ...
> 
> As i told you that i am trying to build libposix
> package for arm platform,with bare Kernel AIO Support
> (without applying patches) and libposix-0.6 package.
> 
> When i tried to build the package then while
> configuration it is  showing Following
> 
> Error:
> 
> "Checking for default value for max events...
> configure: error: cannot 
> run
> test program while cross compiling
> See `config.log' for more details."
> 
> I traced the configure script for following Error and
> got following code that is, I think causing this
> Problem:
> 
> Code in configure script:
> 
> if test "${enable_default_maxevents+set}" = set; then
>   enableval="$enable_default_maxevents"
>   ac_aio_default_maxevents=$enableval
> else
>   echo "$as_me:$LINENO: checking for default value for
> max events" >&5
> echo $ECHO_N "checking for default value for max
> events... $ECHO_C" >&6
> if test "$cross_compiling" = yes; then
>   { { echo "$as_me:$LINENO: error: cannot run test
> program while cross
> compiling
> See \`config.log' for more details." >&5
> echo "$as_me: error: cannot run test program while
> cross compiling
> See \`config.log' for more details." >&2;}
>    { (exit 1); exit 1; }; }
> else
>   cat >conftest.$ac_ext <<_ACEOF
> 
> Even on x86 it is going into else part but their as
> cross compiling is false in that case it goes to 
> cat > conftest.$ac_ext <<_ACEOF
> 
> 
> So With this code while cross compiling we always face
> the same  problem...
> 
> So Can you please tell me how to resolve this
> problem...
> 
> Thanks in advance...
> 
> Vikas
> 

  Ok, then try to disable all the feature with:

./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.

  Sebastien.


-- 
------------------------------------------------------

  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
  
------------------------------------------------------


  reply	other threads:[~2005-09-28  7:23 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é [this message]
2005-09-28 12:57                       ` vikas gupta
2005-09-28 12:58                       ` vikas gupta
2005-09-28 13:35                         ` Sébastien Dugué
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=1127892324.2103.39.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;
as well as URLs for NNTP newsgroup(s).