Path: ...!weretis.net!feeder9.news.weretis.net!news.quux.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: geodandw <geodandw@gmail.com>
Newsgroups: comp.lang.c,comp.lang.c++,comp.lang.python
Subject: Re: Python recompile
Date: Mon, 3 Mar 2025 11:24:13 -0500
Organization: A noiseless patient Spider
Lines: 44
Message-ID: <vq4l3d$1ck9e$1@dont-email.me>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Mon, 03 Mar 2025 17:24:13 +0100 (CET)
Injection-Info: dont-email.me; posting-host="a5c6552ea3f60fd274742764d0f13e5c";
	logging-data="1462574"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/zDzzacRHUWDnqp+13cUZc2lixCYZeykw="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:1GYoQeQNWyQK6hY8+EJG2iN9qVc=
Content-Language: en-US
In-Reply-To: <vq4hf2$1brf7$1@dont-email.me>
Bytes: 3425

On 3/3/25 10:22, James Kuyper wrote:
> 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:
>>>
>>>> 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.
> 
> Without computers, keyboards and monitors most C programs wouldn't be
> much use, either. That doesn't make a malfunctioning computer monitor a
> C problem. And it doesn't make a linkage problems a C problem either.
> 
>>> 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.
> 
> The indentations of the first message cross-posted to comp.lang.c and
> comp.lang.c++ suggest that it was the latest in a series of earlier
> messages posted somewhere else (comp.lang.python?). Those earlier
> messages might have contained additional information. If that
> information was relevant, it should have been included when the message
> was first cross-posted to comp.lang.c or comp.lang.c++. You might be
> right about it being "Python source code ... written in C", but nothing
> in the messages that were posted here makes that obvious.
> 
>   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?