Build shared library (.so) for Mini-OS

Build shared library (.so) for Mini-OS

[Yiming Zhang]

Dear all,

I want to realize dynamic library linking/loading for Mini-OS. The first
step is to build a shared libc library (.so) from newlib-1.16.0. To achieve
this, I modified the stubdom/Makefile to:

(i) build all obj files (libc_objs = *.o) with -fPIC option, and 
(ii) tried to do "gcc -shared -o libc.so $(libc_objs)"

However, the 2nd step cannot work because "string/memcpy.o" and
"machine/x86_64/memcpy.o" both have a memcpy() function. Is there any way to
build a shared libc library (.so) from newlib? (and how this problem is
addressed for standard glibc?) Thank you!

Cheers,
Yiming

Re: Build shared library (.so) for Mini-OS

[Ian Campbell]

On Mon, 2013-04-08 at 09:54 +0100, Yiming Zhang wrote:
> Dear all,
> 
> I want to realize dynamic library linking/loading for Mini-OS.

Why? What is your eventual aim?

>  The first
> step is to build a shared libc library (.so) from newlib-1.16.0. To achieve
> this, I modified the stubdom/Makefile to:
> 
> (i) build all obj files (libc_objs = *.o) with -fPIC option, and 
> (ii) tried to do "gcc -shared -o libc.so $(libc_objs)"
> 
> However, the 2nd step cannot work because "string/memcpy.o" and
> "machine/x86_64/memcpy.o" both have a memcpy() function. Is there any way to
> build a shared libc library (.so) from newlib? (and how this problem is
> addressed for standard glibc?) Thank you!

I think you perhaps need to ask the newlib developers questions about
newlib?

I don't know much about newlib but mini-os at least implements a
single/static/monolithic kernel+application binary so I'm not sure how
much use shared libraries will be -- minios has no filesystem support
for one thing so I'm not sure where they would live.

Ian.