Re: Python recompile

[email protected] (Scott Lurndal)
Newsgroups comp.lang.c,comp.lang.c++,comp.lang.python
Organization UsenetServer - www.usenetserver.com
Message-ID <[email protected]>
[email protected] (Waldek Hebisch) writes:
>In comp.lang.c James Kuyper <[email protected]> wrote:
>> On 3/2/25 12:54, Waldek Hebisch wrote:
>>> In comp.lang.c The Doctor <[email protected]> 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?.
>
>The question is about C implementation. 

So why are you cross posting to comp.lang.c++ and comp.lang.python?
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.