On 4/14/13 7:08 PM, David Lichteblau wrote:
> Quoting Mark Evenson (evenson@...):
>> I'd love to consolidate patches for running SBCL with POSIX threads on
>> x64 hardware for the open Solaris platforms.
> - Which of the .diff files are strictly needed? All of them? Is this
> one logical changeset, or should it be split up into distinct
My patches are organized as a hg repo whose index is in the file
'series'. Something like the first five or six patches are
improvements, but certainly need to be refactored before inclusion in
the sbcl master.
> - Why "incomplete"?
Problems with compiling UNIX-SELECT syscalls, something fundamentally
missing in the POSIX layer. I haven't had enough time to sort
everything out after some years at this point.
> - Let's please not comment out code that's out of date, just remove
> it entirely.
I'll endeavor to adjust the draft patchset in this direction.
> - It's a bit unfortunate that we hardcode absolute paths to system
> binaries in Config.* files at all, so this is not a problem you've
> caused. :-) I have to ask anyway though:
> These patches change some of those paths. If we do that, let's at
> least make certain that the situation truly improves. So how
> canonical are these new locations really?
That's exactly what I'd like to "crowdsource" here, as I don't have
access to all the Solaris mutations: just mine.
> Specifically, if Solaris Express has different paths than
> OpenIndiana, I'd personally prefer the Solaris Express paths...
My paths tends toward the gnu toolchain, as it allows me to take stabs
at upgrading the compiler. I dunno how many Solaris shops really don't
use the SUNW/ORCL provided compile toolchain.
I think Solaris Express was effectively subsumed in OpenIndiana. Or are
you talking about the current ORCL Solaris 11 "product"? I've long
since given up trying to keep track of the mutation. I'd expect it to
work with the ORCL supplied stuff, as it seems to be in their interest
in having *any* customers to what is rapidly becoming "the operating
system one runs the database on".