From: Giulio Moro <g.moro@qmul.ac.uk>
To: Philippe Gerum <rpm@xenomai.org>,
"xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] xeno-config --no-mode-check still has -lmodechk
Date: Thu, 5 Apr 2018 11:15:19 +0000 [thread overview]
Message-ID: <DB6PR0701MB245618054AEE22508685BDE4B5BB0@DB6PR0701MB2456.eurprd07.prod.outlook.com> (raw)
In-Reply-To: <7528e4df-ac06-8893-bf77-7cbf9e91eeef@xenomai.org>
so would it not be up to the external libs to specify in their docs that they should be linked with -lmodechk?
________________________________________
From: Philippe Gerum <rpm@xenomai.org>
Sent: 05 April 2018 07:43
To: Giulio Moro; xenomai@xenomai.org
Subject: Re: [Xenomai] xeno-config --no-mode-check still has -lmodechk
On 04/04/2018 09:58 PM, Giulio Moro wrote:
> /usr/xenomai/bin/xeno-config --skin cobalt --ldflags --no-mode-check
>
> returns
> -Wl,--no-as-needed /usr/xenomai/lib/xenomai/bootstrap.o -Wl,--wrap=main -Wl,--dynamic-list=/usr/xenomai/lib/dynlist.ld -L/usr/xenomai/lib -lcobalt -lmodechk -lpthread -lrt
>
> which removes the modechk wrappers, but leaves -lmodechk in. Is this expected?
>
> As I understand it, libmodechk provides implementations for __wrap_malloc, __wrap_free and __real_malloc, __real_free() are these needed even when the wrappers are disabled, or should -lmodechk not be included?
>
>
The main exec may still depend on external libs built with mode checking
wrappers.
--
Philippe.
next prev parent reply other threads:[~2018-04-05 11:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 19:58 [Xenomai] xeno-config --no-mode-check still has -lmodechk Giulio Moro
2018-04-05 6:43 ` Philippe Gerum
2018-04-05 11:15 ` Giulio Moro [this message]
2018-04-05 13:09 ` Philippe Gerum
2018-04-25 16:40 Lange Norbert
2018-04-25 16:45 Lange Norbert
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=DB6PR0701MB245618054AEE22508685BDE4B5BB0@DB6PR0701MB2456.eurprd07.prod.outlook.com \
--to=g.moro@qmul.ac.uk \
--cc=rpm@xenomai.org \
--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.