Issue 745320: threads broke on FreeBSD current (original) (raw)

Issue745320

Created on 2003-05-29 03:46 by tpx, last changed 2022-04-10 16:08 by admin. This issue is now closed.

Messages (4)
msg16195 - (view)	Author: Till Plewe (tpx)	Date: 2003-05-29 03:46
default configuration builts with the snapshot taken at 05-24-230001 but not with the snapshot from 05-26-230001 (--without-threads builts) I get the following compiler complaint when trying to build python_2003-05-26-230001: c++ -Wl,--export-dynamic -o python Modules/python.o libpython2.3.a -lutil - lm libpython2.3.a(posixmodule.o): In function `posix_tmpnam': Modules/posixmodule.c:5785: warning: tmpnam() possibly used unsafely; consider u sing mkstemp() libpython2.3.a(posixmodule.o): In function `posix_tempnam': Modules/posixmodule.c:5738: warning: tempnam() possibly used unsafely; consider using mkstemp() libpython2.3.a(thread.o): In function `PyThread_start_new_thread': Python/thread_pthread.h:217: undefined reference to `pthread_create' Python/thread_pthread.h:253: undefined reference to `pthread_detach' *** Error code 1
msg16196 - (view)	Author: Andrew I MacIntyre (aimacintyre) *	Date: 2003-06-01 07:27
Logged In: YES user_id=250749 I think what's missing here is the correct library reference. I don't have a 5.x box at the moment, so can't check, but as I recall, there are 2 options at the moment:- - libkse; - libthr. Could you check my recollection and try adding the appropriate library reference to the Makefile to see whether you get a viable build? Some autoconf-fu would then be required to make the setting stick. As the FreeBSD core team haven't yet designated anything from the 5.x line as stable, this makes keeping track of the non-trivial threading changes hard.
msg16197 - (view)	Author: Till Plewe (tpx)	Date: 2003-06-02 02:57
Logged In: YES user_id=782552 adding LIBC=-lkse to the Makefile seems to do the trick. Python builds without any further problems (I didn't use autoconf)
msg16198 - (view)	Author: Martin v. Löwis (loewis) *	Date: 2003-06-28 07:45
Logged In: YES user_id=21627 Fixed with patch #758910.