Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.os.vms    |    DEC's VAX* line of computers & VMS.    |    264,096 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 263,335 of 264,096    |
|    hb0815 to All    |
|    Re: PZMQ    |
|    15 Sep 25 13:14:10    |
      From: mw40171@mucweb.de              On 9/13/25 16:11, Arne Vajhøj wrote:              >> $ pas s3       >> $ link/thread s3 + pzmqdir:pzmq + pzmqdir:common + zmq$root:       >> [lib]libzmq64/lib       >       > /thread is not strictly needed, but without it breaking the       > infinite loop with CTRL/Y exits a bit hard.              /THREAD enables upcalls and multiple kernel threads.              The linker was changed to enable Upcalls whenever it sees that threads       are used and no /THREAD was given. In this case the linker prints an       informational message.              If you link without /THREAD, do you see the linker message? The shown       "Upcalls are disabled. Multiple kernel threads are disabled" indicates       you did not.              If you do not see the message, then I assume the threaded code is in a       shareable image. The linker does not check whether threads are used in       shareables. From the shown link command I don't see that a threaded       shareable image is involved.              It would be interesting to know whether /THREAD=UPCALLS is enough to       make this work. I suspect it is.              Do you have any idea where threaded code is used? What is ICTX?              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca