XPost: comp.lang.c, comp.lang.python

On Sun, 2 Mar 2025 15:54:19 -0000 (UTC)
Lew Pitcher <[email protected]> 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? No? Then its a perfectly valid post.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: comp.lang.c, comp.lang.python

On Sun, 02 Mar 2025 16:58:20 +0000, Muttley wrote:

On Sun, 2 Mar 2025 15:54:19 -0000 (UTC)
Lew Pitcher <[email protected]> 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?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: comp.lang.c, comp.lang.python

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.

--
Waldek Hebisch

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: comp.lang.c, comp.lang.python

James Kuyper <[email protected]> writes:

On Sun, 02 Mar 2025 16:58:20 +0000, Muttley wrote:

On Sun, 2 Mar 2025 15:54:19 -0000 (UTC)
Lew Pitcher <[email protected]> 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?

Frankly, I'd rather read about issues in the linker here than the
interminable useless arguments about the precision and accuracy of
fmod, which belong elsewhere (such as email), or pointless musings
about the halting problem.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: comp.lang.c, comp.lang.python

On 02/03/2025 17: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.

I have written hundreds of thousands of lines of real-world code
in standard C, all of which would be topical here. The real world
is bigger than you think.

--
Richard Heathfield
Email: rjh at cpax dot org dot uk
"Usenet is a strange place" - dmr 29 July 1999
Sig line 4 vacant - apply within

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: comp.lang.c, comp.lang.python

On 03/03/2025 08:13, [email protected] wrote:

On Sun, 2 Mar 2025 12:30:53 -0500
James Kuyper <[email protected]> wibbled:

On Sun, 02 Mar 2025 16:58:20 +0000, Muttley wrote:

On Sun, 2 Mar 2025 15:54:19 -0000 (UTC)
Lew Pitcher <[email protected]> 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.

And without people to write it and buildings in which to work it
wouldn't even be that, so by your argument everything from
demographics to urban planning would be topical here.

It's an old argument, but it has never been a good one.

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.

Then you have very gullible ears. Building the Python source is
an issue for a specific compiler group.

--
Richard Heathfield
Email: rjh at cpax dot org dot uk
"Usenet is a strange place" - dmr 29 July 1999
Sig line 4 vacant - apply within

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: comp.lang.c, comp.lang.python

On Mon, 3 Mar 2025 12:20:35 +0000
bart <[email protected]> wibbled:

On 03/03/2025 10:44, [email protected] 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.

Yes, thats kind of the point. You wouldn't get these errors if it was written in Java or 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.

[snip]

On usenet? That is pretty much dead.

Not dead but certainly not buzzing yet I presume thats how you like it given you don't want any "everyday development issues" relating to C mentioned here.

Or are you another one who thinks usenet should be for the exclusive discussion of high brow issues only of interest to you?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: comp.lang.c, comp.lang.python

On 03/03/2025 19:33, geodandw wrote:

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.

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 is this group so intolerant?

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.

I don't know what your experience with C is - if you have posted
anything in c.l.c. that indicates that, it must have been too long ago
for me to remember. But a number of people with decades long experience
of not only working with C, but helping people in c.l.c. with their C
problems, have made it clear that this is /not/ a C question. They also
did their best to help the OP - giving what help they could despite this
being the wrong place and the question being off-topic, and they did
their best to redirect the OP to places where he might get more useful help.

B.Because some people in this group are arrogant. rude, and
insulting..If the shoe fits, wear it.

Originally, people /politely/ pointed out that the post was off-topic,
and the OP was unlikely to get good help here. Indeed, I don't think
anyone has been other than polite to the OP.

But there have been two people in this thread who have perhaps been
rude, arrogant and insulting - insisting that /they/ know better than
the regulars about what is topical and not topical for the group. Those posters have not in any way been helpful, and are just a waste of
bandwidth for everyone else.

I don't know what you think you are trying to achieve here. Do you
think that your complaints will somehow magically make the OP's problem
about the C programming language, rather than the build process for a particular and specific complex piece of software? Do you think that by posting repeatedly, someone here will suddenly realise they know
something that could help the OP? Do you think you will change the
group topicality?

All you have achieved is annoying some people, and ensuring that the
thread can't develop topically.

If you want to understand what is topical or not for this group,
consider if a question could conceivably by used as an example or an
exercise in a published book about learning or using the C programming language. Then it is probably on-topic. If you'd only find it in a
book called "C programming for Windows", or "Systems programming in
Unix", or "C development with gcc", then it is likely to be too
specific. The OP's question is far too niche for any kind of book at
all - he needs to look at build instructions for Python to understand
what is going on.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)