"Elliott Slaughter" <elliottslaughter@...> writes:
> On Sat, Jul 5, 2008 at 1:44 AM, Nikodemus Siivola
> <nikodemus@...> wrote:
>> On Sat, Jul 5, 2008 at 2:24 AM, Elliott Slaughter
>> <elliottslaughter@...> wrote:
>>> which I am similarly stumped by. I am tempted to just wrap these and
>>> other similar instances with "#ifndef LISP_FEATURE_WIN32" but I am not
>>> sure if I need to implement equivalent code for win32 or not.
>> Depends on how thread stacks will work on Windows. The post mortem
>> stuff is there to deal with freeing thread stacks after the thread has
>> You can #ifdef if out for now, and later, when you know if you need it
>> or not, you can deal with it appropriately.
> Thanks. Based on your advice I completed the rest of the merge,
> punting on most of hard problems for now. I have put up my current
> progress at http://repo.or.cz/w/sbcl/eslaughter.git (so Christophe has
> something to look at for midterm evaluations ;-).
> Tomorrow I think I'll try to compiling on Linux first to make sure I
> haven't made any regressions, then see how far I get on win32 before
> it breaks. (Quick question: does SBCL compile with threads by default
> on Linux/x86? Or is there an option I need to pass to make.sh?)
You need to create a file called customize-target-features.lisp in the
sbcl source directory, containing something like
(lambda (list) (list* :sb-thread list))
(see section 2.2 of the INSTALL file)