Sujet : Re: Python recompile
De : 643-408-1753 (at) *nospam* kylheku.com (Kaz Kylheku)
Groupes : comp.lang.c comp.lang.c++ comp.lang.pythonDate : 04. Mar 2025, 18:42:27
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <20250304092827.708@kylheku.com>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
User-Agent : slrn/pre1.0.4-9 (Linux)
On 2025-03-04,
Muttley@DastardlyHQ.org <
Muttley@DastardlyHQ.org> wrote:
On Tue, 4 Mar 2025 09:57:16 +0000
Richard Heathfield <rjh@cpax.org.uk> wibbled:
On 04/03/2025 09:23, Muttley@DastardlyHQ.org wrote:
because plenty of compilation issues are caused by code issues.
>
Undoubtedly true, and equally undoubtedly irrelevant in this
case. Were it relevant, the OP would by now have shown us the
problem code.
>
So what you're saying is you can't troubleshoot linking problems. Do you
get someone else to compile your code for you?
Python is not "your code" for any value of "your" referring to any
regular here in comp.lang.c.
A compiler is a compiler, a linker is a linker. Troubleshooting both is part
of the development process of any competent C dev. But we know already you
don't consider that to be the case because its beyond your abilities.
Troubleshooting an open source package build problem is often a complex
problem that in most cases requires direct access to the environment
where the problem is happening.
It's actually a case of porting. When Python does not build in some OS
distro with certain compilers, that's a kind of porting challenge.
The program in question almost certainly doesn't have a C language
problem. It has a build system portability problem. Even though
some build system portability problems intersect with C topics, This
isn't a build system portability problem newsgroup.
"Port this big package for me to my environment because I don't know
what I'm doing" is not a suitable discussion topic here for reasons like
people not having that exact environment ot be able to reproduce the
problem, and people not coming here to discuss that sort of thing.
It's a lot better to take it to either a mailing list for the platform
where you are trying to port the program, or else the mailing list for
that program.
The build issue could be something that recurs for other programs
being ported to the same environment.
-- TXR Programming Language: http://nongnu.org/txrCygnal: Cygwin Native Application Library: http://kylheku.com/cygnalMastodon: @Kazinator@mstdn.ca