public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: "Carlos O'Donell" <carlos@redhat.com>
To: Vishal Agrawal <vishal4556@gmail.com>
Cc: libc-ports@sourceware.org
Subject: Re: Has anyone progressed/tried to port glibc to non posix system (windows)
Date: Fri, 05 Apr 2013 14:44:00 -0000	[thread overview]
Message-ID: <515EE355.9070801@redhat.com> (raw)
In-Reply-To: <CAF6ttfGCzAgJVRYTL7nwacSm6fLfXhsSvuVm3G=aO3Y7dXdQTA@mail.gmail.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.

  reply	other threads:[~2013-04-05 14:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAF6ttfHcG5s6OUAiuDfXWg3kQr_9Yxo+BHbhOZa8E2SeEnY-uA@mail.gmail.com>
     [not found] ` <CAF6ttfGk0AxJQypSTB+5bNsDyzWXBG96hbOijFSbkVaSWiwESg@mail.gmail.com>
2013-04-05 13:30   ` Vishal Agrawal
2013-04-05 14:44     ` Carlos O'Donell [this message]
2013-04-05 20:08       ` Mike Frysinger
2013-04-05 22:32         ` Carlos O'Donell
2013-04-05 23:01           ` Mike Frysinger

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=515EE355.9070801@redhat.com \
    --to=carlos@redhat.com \
    --cc=libc-ports@sourceware.org \
    --cc=vishal4556@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).