From: "Sinisa Denic" <sinisa.denic@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Fwd: Re: Xeno2.5 - 2.5.1 API mismatch?
Date: Thu, 20 May 2010 11:52:16 +0200 [thread overview]
Message-ID: <op.vcz0decz38inye@domain.hid> (raw)
In-Reply-To: <4BF4FB97.5000809@domain.hid>
On Thu, 20 May 2010 11:06:31 +0200, Gilles Chanteperdrix
<gilles.chanteperdrix@xenomai.org> wrote:
> Sinisa Denic wrote:
>>>> /opt/toolchains/arm926t-uclibcgnueabi/usr/bin/arm-linux-gcc
>>>> -I/usr/xenomai-2.5.3-eabi/include -D_GNU_SOURCE -D_REENTRANT -Wall
>>>> -pipe
>>>> -D__XENO__ -lnative -L/usr/xenomai-2.5.3-eabi/lib -lxenomai -lpthread
>>>> -o./iecgoose_ld obj_iecgoose_ld/iec_main.o obj_iecgoose_ld/mms_arb.o
>>>> obj_iecgoose_ld/mmsop_en.o obj_iecgoose_ld/mvlop_en.o
>>>> obj_iecgoose_ld/mvl_acse.o obj_iecgoose_ld/event.o
>>>> obj_iecgoose_ld/logcfgx.o obj_iecgoose_ld/rdwrind.o
>>>> obj_iecgoose_ld/reject.o obj_iecgoose_ld/startup.o
>>>> obj_iecgoose_ld/uca_obj.o /opt/libMMSLITE-eabi//lib/mvlu_ld.a
>>>> /opt/libMMSLITE-eabi//lib/mlogl_ld.a
>>>> /opt/libMMSLITE-eabi//lib/mmsle_ld.a
>>>> /opt/libMMSLITE-eabi//lib/mmsl_ld.a /opt/libMMSLITE-eabi//lib/mem_ld.a
>>>> /opt/libMMSLITE-eabi//lib/slog_ld.a
>>>> /opt/libMMSLITE-eabi//lib/util_ld.a
>>>> /opt/libMMSLITE-eabi//lib/ositp4e_ld.a
>>>> /opt/libMMSLITE-eabi//lib/asn1l_ld.a -lm -lpthread -lrt -lnative
>>>> -static
>>> link order is wrong here: the list of -l should come after the list of
>>> .o, and if you do that, you will not need to repeat the list of -l.
>>>
>>> Your problem is that -lnative is missing in the list of -l you repeat,
>>> but it is better to put the result of xeno-config --xeno-ldflags after
>>> the list of .o (if you are using built-in makefile rules, this means
>>> puttin this in the LOADLIBES variable instead of putting it in
>>> LDFLAGS),
>>> and remove the repetition.
>>>
>> Oh thank you, sorry, this is my fault, this isn't my peace of code, just
>> working around.
>> I saw it and it was suspicious to me, but It was supposed to look more
>> closely,
>> Makefile came with library and it is modified to use Xenomai, because of
>> that it seems such a messy..
>>
>> Now it's compiling but, have you idea why these errors appear from
>> xeno-2.5.1 version,
>> the same code compiling in xeno-2.4.x even xeno-2.5.0 without errors and
>> no need to add <sys/mman.h> .
>>
>> iec_main.c:1037: warning: implicit declaration of function ‘mlockall’
>> iec_main.c:1037: error: ‘MCL_CURRENT’ undeclared (first use in this
>> function)
>> iec_main.c:1037: error: (Each undeclared identifier is reported only
>> once
>> iec_main.c:1037: error: for each function it appears in.)
>> iec_main.c:1037: error: ‘MCL_FUTURE’ undeclared (first use in this
>> function)
>
> Before 2.5.2 there was no libxenomai library, so, the list of -l you
> add: -lpthread -lrt -lnative is sufficient to workaround the fact that
> your link order was wrong. It explains the link error.
>
> Before 2.5.2, what is now implemented in C files was implemented in
> header files, which got included all over the place, and these header
> files included sys/mman.h, but this caused all sort of troubles with
> some versions of uclibc toolchains, this explains the error about the
> missing include.
>
>
Gilles thank you very much,
does it mean that including mman.h is necessary.
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
next prev parent reply other threads:[~2010-05-20 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4BF444C2.9090508@domain.hid>
[not found] ` <4BF45174.7040802@domain.hid>
2010-05-20 7:48 ` [Xenomai-help] Fwd: Re: Xeno2.5 - 2.5.1 API mismatch? Sinisa Denic
2010-05-20 8:13 ` Gilles Chanteperdrix
[not found] ` <op.vczxulyi38inye@domain.hid>
[not found] ` <4BF4FB97.5000809@domain.hid>
2010-05-20 9:52 ` Sinisa Denic [this message]
2010-05-20 9:55 ` Gilles Chanteperdrix
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=op.vcz0decz38inye@domain.hid \
--to=sinisa.denic@domain.hid \
--cc=gilles.chanteperdrix@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.