This is the mail archive of the
libc-ports@sources.redhat.com
mailing list for the libc-ports project.
Re: Has anyone progressed/tried to port glibc to non posix system (windows)
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Vishal Agrawal <vishal4556 at gmail dot com>
- Cc: libc-ports at sourceware dot org
- Date: Fri, 05 Apr 2013 10:44:37 -0400
- Subject: Re: Has anyone progressed/tried to port glibc to non posix system (windows)
- References: <CAF6ttfHcG5s6OUAiuDfXWg3kQr_9Yxo+BHbhOZa8E2SeEnY-uA at mail dot gmail dot com> <CAF6ttfGk0AxJQypSTB+5bNsDyzWXBG96hbOijFSbkVaSWiwESg at mail dot gmail dot com> <CAF6ttfGCzAgJVRYTL7nwacSm6fLfXhsSvuVm3G=aO3Y7dXdQTA at mail dot gmail dot com>
On 04/05/2013 09:30 AM, Vishal Agrawal wrote:
> I am working to port a part of glibc to windows. Can anyone help me
> with their progress or write about how hard it is. With no changes it
> is listing:
>
> *** The GNU C library is currently not available for this platform.
> *** So far nobody cared to port it and if there is no volunteer it
> *** might never happen. So, if you have interest to see glibc on
> *** this platform visit
> *** http://www.gnu.org/software/libc/porting.html
> *** and join the group of porters
Nobody that I know of in the community is working on a Windows
port of glibc.
Even a minimal port would be difficult because glibc supports
only ELF and for a Windows port you'd have to extend everything
to support an alternate binary format e.g. PE, with all of the
differences that that entails. You might try to use a PE stub
to run the dynamic loader which can then load ELF files.
A full port to Windows would require expert level knowledge
to complete and would be considerable work, probably on the
order of a year of full-time work by said expert.
You would likely end up duplicating much of what is already
in cygwin to provide all of the functionality required by POSIX.
Why not consider using cygwin?
Cheers,
Carlos.