Re: Shared Libraries for Newlib

Thanks! Knowing it was removed makes me feel better for not finding it. :)

I did find someone who had a Makefile for libc and another for libm which
just directly produced the shared library. That might work for some limited
use case.

I need to double check my configure command but I didn't get .so files from
GCC either. I thought enable shared would turn something on.

--joel



On Fri, Sep 6, 2024, 3:52 PM Jeff Johnston <[email protected]> wrote:

> Hi Joel,
>
> The shared library support for newlib was for host newlib builds
> (primarily x86-linux but perhaps cygwin support as well?).  Anyway, that
> support has been stripped out since linux was dropped and the build system
> rewritten.  It involved a number of things including libtool support via
> the top-level libtool.m4.  There were special checks for USE_LIBTOOL in
> various Makefile.am files and we had a separate oext variable for the
> object extension (.lo instead of .o) and library (.la vs .a).
>
> case "${host}" in
>   i[34567]86-pc-linux-*)
>     use_libtool=yes
>     have_sys_mach_dir=yes
>     stdio64_dir=stdio64
>     oext=lo
>     lpfx=
>     aext=la ;;
>   *) ;; #shared library not supported for ${host}
> esac
>
> If you want to look at what was there, take a look at newlib 3.1.0.
>
> -- Jeff J.
>
> On Thu, Sep 5, 2024 at 7:51 PM Joel Sherrill <[email protected]> wrote:
>
>> Hi
>>
>> I am looking at porting RTEMS to a virtualized environment where the
>> hypervisor can manage shared libraries for the clients. I would like to
>> build gcc+newlib to produce both static and dynamic libraries. I tried
>> adding --enable-shared to configure but didn't get any .so files.
>>
>> Is there some magic I am missing to configure an *-rtems* target to also
>> produce .so libraries?
>>
>> Thanks.
>>
>> --joel
>>
>