Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#264 Threads not available even if enabled (OpenBSD)

Stable_release
open
nobody
None
5
2013-07-22
2013-07-18
Anonymous
No

There seems to be bugs lurking in the configure. Even if the threads are enabled and build completes successfully, features won't list threads. Also the "mp" functions are not defined. I'd assume somewhere ECL_THREADS won't get defined.

The ECL on OpenBSD is build against system gmp and boehm-gc. Boehm-gc port is build with threads enabled. You can check the patches and configure options from the port at http://www.openbsd.org/cgi-bin/cvsweb/ports/lang/ecl/

Discussion


  • Anonymous
    2013-07-18

    Nevermind, This is caused by typo in the ports Makefile. Instead of "--enable-threads=pthreads" ECL uses "--enable-threads=yes".

     

  • Anonymous
    2013-07-19

    That's not it I think. Building with "--enable-threads=yes" or "--enable-threads=auto" seems to work okay until you get to here:

    ;;;
    ;;; Welcome to bare.lsp. Let's bring this instance up!
    ;;;
    ;;;
    ;;; About to load lsp/load.lsp
    ;;;
    ;;; Loading src:lsp;export.lsp
    ;;; Loading src:lsp;defmacro.lsp
    ;;; Loading src:lsp;helpfile.lsp
    ;;; Loading src:lsp;evalmacros.lsp
    ;;; Loading src:lsp;cmuutil.lsp
    ;;; Loading src:lsp;setf.lsp
    ;;; Loading src:lsp;predlib.lsp

    At this point the build just freezes. So this bug is still a bug.

     
  • Timo Myyrä
    Timo Myyrä
    2013-07-22

    Well, my original complain was about the configure process which silently makes assumption that if enable-threads arg is not auto|yes it is 'no'.

    But yes, the threads itself won't work when enabled. Tested on OpenBSD-current (amd64). Stuck on same phase. Seems to lock itself, 'top' shows no CPU use.

     


Anonymous


Cancel   Add attachments