[GSoC - x86_64 BSP] Using fPIC to compile RTEMS as a shared library
Joel Sherrill
joel at rtems.org
Mon Jun 4 13:12:44 UTC 2018
On Mon, Jun 4, 2018 at 5:44 AM, Sebastian Huber <
sebastian.huber at embedded-brains.de> wrote:
>
>
> ----- Am 4. Jun 2018 um 12:20 schrieb Amaan Cheval amaan.cheval at gmail.com:
>
> > That's a good idea. That way based on the multilib variant, Newlib would
> be
> > compiled using fPIC, yes?
>
> Yes.
>
This would be desirable for the i386 as well. Having the RTEMS libraries as
dynamic libraries would be more natural under Deos.
Just a statement. Not a requirement on the GSoC project.
>
> >
> > Then I could simply figure out how to solve the crtbegin and crtend
> dilemma
> > (which I believe should be easier), and use those to have a
> dynamic/shared
> > RTEMS kernel + user application.
>
> These files will be compiled with -fPIC as well.
>
>
> >
> > If that sounds right, I'll look into that first. Not familiar with the
> GCC
> > source yet, but it should be doable.
>
> Sorry, I have no idea how the x86_64 configuration of GCC works for RTEMS.
>
> >
> >
> > On Mon, Jun 4, 2018, 3:43 PM Sebastian Huber <
> > sebastian.huber at embedded-brains.de> wrote:
> >
> >> Hello Amaan,
> >>
> >> can't you add a new multilib variant which includes -fPIC to the GCC
> >> configuration for RTEMS?
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20180604/6abcd99d/attachment-0002.html>
More information about the devel
mailing list