All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yogi A. Patel" <yapatel@gatech.edu>
To: xenomai@xenomai.org
Subject: [Xenomai] mlockall and dlopenskins?
Date: Sun, 07 Sep 2014 12:21:05 -0400	[thread overview]
Message-ID: <540C85F1.4070809@gatech.edu> (raw)

Hi -

I used to provide --enable-posix-auto-mlockall --enable-dlopen-skins as 
options to the configure script when compiling user space support. 
However in 2.6.3 I get a warning saying those are unrecognized options.

Now. I was looking online at the documentation and found the following:

/Xenomai libraries only invoked mlockall if a special option was passed 
to the configure script when compiling Xenomai user-space support. So, 
applications which did not want to depend on this configuration had to 
call mlockall by themselves, before using any Xenomai service, by using://
//
//mlockall(MCL_CURRENT | MCL_FUTURE);/

This is slightly vague and hard to understand. The warnings make it 
obvious that the enable-posix-auto-mlockall call does nothing when used 
during compile. Does this mean that in 2.6.3 and above mlockall is 
included in user space libraries by default (requring no changes to our 
software besides removing that flag from the compile)?

And what about enable-dlopen-skins? I can't find any documentation 
online on that changing in 2.6.3.

Thanks!

-- 
Yogi

             reply	other threads:[~2014-09-07 16:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-07 16:21 Yogi A. Patel [this message]
2014-09-07 16:37 ` [Xenomai] mlockall and dlopenskins? Gilles Chanteperdrix
2014-09-07 16:39   ` Yogi A. Patel
2014-09-07 16:41     ` Gilles Chanteperdrix
2014-09-07 16:44       ` Yogi A. Patel
2014-09-07 16:46         ` Gilles Chanteperdrix
2014-09-07 16:46     ` Gilles Chanteperdrix
2014-09-07 16:47       ` Yogi A. Patel

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=540C85F1.4070809@gatech.edu \
    --to=yapatel@gatech.edu \
    --cc=xenomai@xenomai.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.