Re: Python recompile

On 3/2/25 19:42, The Doctor wrote:

In article <vq2j3n$v2fk$1@dont-email.me>,
James Kuyper  <jameskuyper@alumni.caltech.edu> wrote:

On 3/2/25 12:54, Waldek Hebisch wrote:

In comp.lang.c The Doctor <doctor@doctor.nl2k.ab.ca> wrote:

How do I compensate for
>
ld: error: relocation R_X86_64_32 cannot be used against symbol

'_PyRuntime'; recompile with -fPIC

defined in /usr/local/lib/libpython3.13.a(pylifecycle.o)
referenced by thread_pthread.h:138 (Python/thread_pthread.h:138)
              thread.o:(PyThread_init_thread) in archive

/usr/local/lib/libpython3.13.a

>

>
This is real world question and as such is considered off-topic
in comp.lang.c.  However, you could try '-no-pie' to the compiler.

>
Real world questions about the C programming language are entirely
on-topic here. Note, however, that many questions posted here are not
about C itself, but about the quirks of particular implementations of C.
You can get better answers to such questions by asking in forums
specific to the relevant implementation, and helpful people will remind
your of that. It's a misunderstanding of those redirections to conclude
that c.l.c is not for real world questions.
>
However Python is NOT an implementation of C, not even by the loosest
reasonable interpretation, so why should it be discussed here?.
>

 
Note the C error!

The message indicates that PyRuntime is referenced inside
Python/thread_pthread.h, which is likely to have been #included in some
C code. However, the error message indicates that the problem is not
about the C code, but about linkage. The C code is just one of the two
things that need to be linked together. The solution is a linker option,
not a change anything in the C code.