Issue1524317
Created on 2006-07-18 07:44 by rambham, last changed 2006-07-19 00:05 by tim_one.
| Messages (4) | |||
|---|---|---|---|
| msg29198 - (view) | Author: Ram Bhamidipaty (rambham) | Date: 2006-07-18 07:44 | |
In Python-2.5b2 I tried to do this: ./configure --without-threads gmake The build will fail with an undefined reference to _PyThread_CurrentFrames |
|||
| msg29199 - (view) | Author: Matt Fleming (splitscreen) | Date: 2006-07-18 11:29 | |
Logged In: YES
user_id=1126061
I can confirm this error on Linux, below is the output,
gcc -Xlinker -export-dynamic -o python \
Modules/python.o \
libpython2.5.a -ldl -lutil -lm
libpython2.5.a(posixmodule.o): In function `posix_tmpnam':
./Modules/posixmodule.c:6701: warning: the use of `tmpnam'
is dangerous, better
use `mkstemp'
libpython2.5.a(posixmodule.o): In function `posix_tempnam':
./Modules/posixmodule.c:6654: warning: the use of `tempnam'
is dangerous, better
use `mkstemp'
libpython2.5.a(sysmodule.o): In function `sys_current_frames':
Python/sysmodule.c:675: undefined reference to
`_PyThread_CurrentFrames'
collect2: ld returned 1 exit status
make: *** [python] Error 1
Thanks, Matt
|
|||
| msg29200 - (view) | Author: Matt Fleming (splitscreen) | Date: 2006-07-18 17:54 | |
Logged In: YES user_id=1126061 Fix in patch #1524724. If someone gives it the thumbs up, I can commit it. Matt |
|||
| msg29201 - (view) | Author: Tim Peters (tim_one) | Date: 2006-07-19 00:05 | |
Logged In: YES user_id=31435 Fixed in rev 50708. That made _PyThread_CurrentFrames() available in all builds, and fiddled test_sys so that the test for sys._current_frames() passes with or without threads. test_sys still fails in a build without threads, but for an unrelated reason. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2006-07-18 07:44:58 | rambham | create | |