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.
On Sun, 2 Mar 2025 15:54:19 -0000 (UTC)
Lew Pitcher <lew.pitcher@digitalfreehold.ca> gabbled:
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.
Is there a comp.lang.c.linker group?
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
On Sun, 02 Mar 2025 16:58:20 +0000, Muttley wrote:
On Sun, 2 Mar 2025 15:54:19 -0000 (UTC)
Lew Pitcher <lew.pitcher@digitalfreehold.ca> gabbled:
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.
Is there a comp.lang.c.linker group?
comp.lang.c is about using the C programming language. Linkers are >independent of the programming language, and can be used to link
together programs written in many different languages. The subject line
and the text of the error messages indicate that it's a Python program,
so why would a group devoted to C be in any way appropriate?
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.
On Sun, 2 Mar 2025 12:30:53 -0500
James Kuyper <jameskuyper@alumni.caltech.edu> wibbled:
On Sun, 02 Mar 2025 16:58:20 +0000, Muttley wrote:
On Sun, 2 Mar 2025 15:54:19 -0000 (UTC)
Lew Pitcher <lew.pitcher@digitalfreehold.ca> gabbled:
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.
Is there a comp.lang.c.linker group?
comp.lang.c is about using the C programming language. Linkers are
independent of the programming language, and can be used to link
Without compilers and linkers a C program would just be a load of text.
together programs written in many different languages. The subject line
and the text of the error messages indicate that it's a Python program,
so why would a group devoted to C be in any way appropriate?
If you'd taken 2 seconds to look at it you'd realise the issue was building the Python source code which is written in C. That sounds like a C issue to me.
On 03/03/2025 10:44, Muttley@DastardlyHQ.org wrote:
On Mon, 3 Mar 2025 08:31:16 +0000
Really? So if a compiler gives an error thats not a C problem? Go ask a
group for the specific compiler?
The errors reported by the OP were like this:
ld: error: relocation R_X86_64_32 cannot be used against symbol
'_PyRuntime'; recompile with -fPIC
'ld' is a program that can be used to link programs in any language.
The problem appears to be do with generating position independent code
since these days linkers like to generate programs that can loaded at an >arbitrary address in high memory.
I can't see anything to do with C here, other than the source in
question may have been written in C.
I expect however you'd be OK with this forum being full of everyday >development issues associated with a million different applications, but >which just happen to be written in C, or which are partly in C.
On usenet? That is pretty much dead.
On 3/3/25 12:19, Richard Heathfield wrote:
On 03/03/2025 16:24, geodandw wrote:
On 3/3/25 10:22, James Kuyper wrote:
That sounds like a C issue to me.Why is this group so intolerant?
If it were a C problem, then the C source code that produced the
problem
should have been shown. It's hard to debug code that you can't see.
Why are you so intolerant of other people's wish to keep this group
topical?
A. Because the problem is apparently using the right options on the
compiler, which seems like a C question to me.
B.Because some people in this group are arrogant. rude, and
insulting..If the shoe fits, wear it.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 497 |
Nodes: | 16 (2 / 14) |
Uptime: | 07:00:44 |
Calls: | 9,780 |
Calls today: | 21 |
Files: | 13,748 |
D/L today: |
1 files (1K bytes) |
Messages: | 6,186,854 |