Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Kaz Kylheku <643-408-1753@kylheku.com>
Newsgroups: comp.lang.c
Subject: Re: Python recompile
Date: Tue, 4 Mar 2025 17:56:23 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 39
Message-ID: <20250304094244.247@kylheku.com>
References: <vq1qas$j22$1@gallifrey.nk.ca> <vq1uvb$qbuq$1@dont-email.me>
 <vq22nc$rvb8$1@dont-email.me> <vq24kd$rg6i$1@dont-email.me>
 <vq3oag$18iv6$1@dont-email.me> <vq4hf2$1brf7$1@dont-email.me>
 <vq4l3d$1ck9e$1@dont-email.me> <vq4m0u$1ctpn$1@dont-email.me>
 <vq4n05$1d5dv$1@dont-email.me> <vq4om7$1dbo2$2@dont-email.me>
 <vq6dqh$1pskk$1@dont-email.me> <vq6f8p$1pmnk$1@dont-email.me>
 <vq6gqc$1qcp8$1@dont-email.me> <vq6ips$1pmnk$2@dont-email.me>
 <vq6j5h$1qosf$1@dont-email.me> <vq6kdt$1pmnk$4@dont-email.me>
 <vq6nk7$1rga6$1@dont-email.me> <vq6rj4$1s39e$1@dont-email.me>
 <vq6ude$1sn38$1@dont-email.me>
Injection-Date: Tue, 04 Mar 2025 18:56:25 +0100 (CET)
Injection-Info: dont-email.me; posting-host="513561c181a980206f31ea7942edad9d";
	logging-data="2077472"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+NNAAiqrs5SUE2szPWXVyMm/I0FkJF0vs="
User-Agent: slrn/pre1.0.4-9 (Linux)
Cancel-Lock: sha1:cUq1jp/yL3WWMop8U4AojE4LwAQ=
Bytes: 3088

On 2025-03-04, Muttley@DastardlyHQ.org <Muttley@DastardlyHQ.org> wrote:
> On Tue, 4 Mar 2025 12:27:17 +0000
> bart <bc@freeuk.com> wibbled:
>>On 04/03/2025 11:19, Muttley@DastardlyHQ.org wrote:
>>> Well do feel free to suggest which group might be appropriate for C
>>compilation
>>> issues.
>>
>>It wasn't a C compilation issue. That is, not a syntax error, not a type 
>>error, and no violation of the language rules.
>
> Linking is part of the compilation process.

If linking doesn't work, how that can be a C problem is that the code
has external references to symbols which are not defined.

Why some symbols are not defined when you you're building someone's
program with with a certain toolchain on a certain target environment is
completely off topic here.

Linking problems not related to ref/def are also off topic; they have to
do with some limitations of the target environment, or some other
problem like a mismatch between object file formats or other issue.

Someone who knows how to fix that sort of thing is likely going to need
to set up an identical environment and reproduce the issue.

Otherwise it will involve an large number of rounds of "try this command
and report the full output", and "show me the contents of this file",
leading to a long thread full of artifacts from an extended remote debug
session that isn't a legitimate newsgroup discussion topic.

It should be conducted over e-mail.

How about:

"I'm looking to debug a Python package build problem in my environment
with the help of someone willing to exchange numerous e-mails comprising
a remote debug session, or possibly with remote access to my system.."