[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5143748E.3090603@eservices.virginia.edu>
Date: Fri, 15 Mar 2013 15:20:46 -0400
From: Zvi Gilboa <zg7s@...rvices.virginia.edu>
To: <musl@...ts.openwall.com>
Subject: Re: question: hard-coded file descriptors in stdin/stdout/stderr
>> If on the other hand your work provides a pseudo-syscall-interface
musl could ride on top of, it might be possible to use most of musl
almost-unmodified on top of windows.
That's perfectly understood! I'm indeed writing psxcalls with musl in
mind, with the goal that the library would provide musl with all it
needs to treat it just like any other linux system. This means that the
only "specialties" would exist where they are present for other
platforms as well, namely as sub-folders under /src/thread or
/src/internal. As for /src/math, I have already created some basic sed
scripts that convert the Linux .S files to MinGW ones.
There are probably some fine details of which I am not yet aware,
however I'm overall optimistic about musl's eventual ability to
integrate win32 and win64 transparently, just like it would with any
other Linux platform.
Zvi
On 03/15/2013 03:03 PM, Rich Felker wrote:
> On Fri, Mar 15, 2013 at 02:55:44PM -0400, Zvi Gilboa wrote:
>> Thank you for the encouragement, Rich! It is great to know that the
>> project will be warmly welcome by the musl community. As for the
> No problem. To clarify a bit, musl itself will most likely remain
> Linux-only (or rather Linux-syscall-API-only) in the main repository,
> because I don't like the complexity cost (which you can see in its
> extreme form in glibc :) of abstracting for that kind of underlying
> system diversity. The approach I would recommend to you if you want to
> use musl for this is to fork files which need to be seriously
> different on Windows, and keep a separate list of files that can be
> synchonized automatically or with minimal manual intervention.
>
> If there end up being things that are gratuitously difficult to reuse
> in their current form, that could be changed in musl without making it
> more complex or having other undesirable side effects, I think we
> could probably make changes that make your work easier.
>
> If on the other hand your work provides a pseudo-syscall-interface
> musl could ride on top of, it might be possible to use most of musl
> almost-unmodified on top of windows.
>
> Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
