Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Lew Pitcher <lew.pitcher@digitalfreehold.ca>
Newsgroups: comp.lang.c,comp.lang.c++,comp.lang.python
Subject: Re: Python recompile
Date: Sun, 2 Mar 2025 15:54:19 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 24
Message-ID: <vq1uvb$qbuq$1@dont-email.me>
References: <vq1qas$j22$1@gallifrey.nk.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Sun, 02 Mar 2025 16:54:20 +0100 (CET)
Injection-Info: dont-email.me; posting-host="170d7ee7c35bd306f2f1c7de4fd26062";
	logging-data="864218"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+rFQxPQGemG7LuYQZVq+se3S8mOF4ACLY="
User-Agent: Pan/0.139 (Sexual Chocolate; GIT bf56508
 git://git.gnome.org/pan2)
Cancel-Lock: sha1:eILzn2SMt4Iu4LHforrH2QtNjcM=
Bytes: 1728


First off, this isn't really on-topic for comp.lang.c, as it is a question regarding a linker, interacting
with the results of various options given to a specific compiler.

However...

On Sun, 02 Mar 2025 14:35:08 +0000, The Doctor wrote:

> How do I compensate for
> 
> ld: error: relocation R_X86_64_32 cannot be used against symbol '_PyRuntime'; recompile with -fPIC

The error message tells you exactly how to fix the problem: recompile the module using the
  -fPIC
option to the compiler. -fPIC tells your compiler to generate a specific type of position-independant
code, which your linker (apparently) requires for a specific type of relocation.


[snip]

HTH
-- 
Lew Pitcher
"In Skills We Trust"