Re: Python recompile

On 03/03/2025 10:44, Muttley@DastardlyHQ.org wrote:

On Mon, 3 Mar 2025 08:31:16 +0000
Richard Heathfield <rjh@cpax.org.uk> wibbled:

On 03/03/2025 08:13, Muttley@DastardlyHQ.org wrote:

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:
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.

 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.

What a load of narrow minded BS. Its not as if these groups get hundreds of
messages a day and the amount needs to be cut down.

Personally I'm not bothered, and would have answered if I could; I think some already have.
For a broader C forum, which is more tolerant than this one even though it is moderated, the OP could try the C_Programming subreddit of Reddit.
The question also seems a good fit for Stack Exchange.
There may even be specialist forums for building or developing CPython.
(Over a decade ago, I myself had a problem in building CPython on Windows. I posted about in comp.lang.python, but they were ******* useless. People there only knew how to write Python programs.)
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.

 

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

 No idea what gullible ears is supposed to mean.
 

an issue for a specific compiler group.

 So which group would that be then?

On usenet? That is pretty much dead.