From: Philippe Gerum <rpm@xenomai.org>
To: "Li Yi (Adam)" <liyiadam@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [PATCH]Build xenomai on Blackfin in FDPIC format
Date: Tue, 14 Nov 2006 16:29:51 +0100 [thread overview]
Message-ID: <1163518192.7291.20.camel@domain.hid> (raw)
In-Reply-To: <4546494d0611131932q480046e0vfa092f4eaa15f7b5@domain.hid>
On Tue, 2006-11-14 at 11:32 +0800, Li Yi (Adam) wrote:
> Hi Philippe,
>
> Since bfin-gcc release 2006-R1, bfin-gcc begins to support "FDPIC"
> format besides "BFLT".
> "FDPIC" supports shared library. Bellow patch makes it possible to
> build xenomai-2.2.5 in FDPIC
> format. In docs.blackfin.uclinux.org/doku.php?id=adeos there is step
> by step guide.
>
> Although it is still possible to build xenomai as BFLT in this way:
>
> configure --host=bfin CC=bfin-uclinux-gcc LDFLAGS=-Wl,-elf2flt
> --disable-shared
>
> There will be error:
>
> bfin-uclinux-gcc -Wl,-elf2flt -o cyclictest
> -Wl,@/home/adam/workspace/xenomai/xenomai_src/xenomai-
> 2.2.5/src/skins/posix/posix.wrappers
> cyclictest-cyclictest.o ../../skins/posix/.libs/libpthread_rt.a
> -lpthread -lrt
> /home/adam/workspace/toolchain/1110/bfin-uclinux/bin/../lib/gcc/bfin-uclinux/4.1.1/../../../../bfin-uclinux/lib/libpthread.a( specific.o): In function `_pthread_key_delete':
> (.text+0x24e): undefined reference to `___wrap_pthread_mutex_lock'
> /home/adam/workspace/toolchain/1110/bfin-uclinux/bin/../lib/gcc/bfin-uclinux/4.1.1/../../../../bfin-uclinux/lib/libpthread.a( specific.o): In function `_pthread_key_delete':
>
> And this can be fixed like:
>
> bfin-uclinux-gcc -Wl,-elf2flt -o cyclictest
> -Wl,@/home/adam/workspace/xenomai/xenomai_src/xenomai-2.2.5/src/skins/posix/posix.wrappers cyclictest-cyclictest.o -lpthread -lrt ../../skins/posix/.libs/libpthread_rt.a
>
As Gilles pointed out, we probably need a two steps link process here;
fiddling with the object ordering won't solve the library
inter-dependencies properly.
> But using "FDPIC" format is suggested.
>
We'll move to FDPIC. No need to stick with a limitation on shared
objects, which additionally requires a two step building process for
working around chicken-and-eggs linking issues.
> Thanks,
>
> -Yi
> _______________________________________________
> Xenomai-core mailing list
> Xenomai-core@domain.hid
> https://mail.gna.org/listinfo/xenomai-core
--
Philippe.
prev parent reply other threads:[~2006-11-14 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 3:32 [Xenomai-core] [PATCH]Build xenomai on Blackfin in FDPIC format Li Yi (Adam)
2006-11-14 10:01 ` Gilles Chanteperdrix
2006-11-14 15:29 ` Philippe Gerum [this message]
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=1163518192.7291.20.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=liyiadam@domain.hid \
--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.