Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: bart <bc@freeuk.com>
Newsgroups: comp.lang.c
Subject: Re: Python recompile
Date: Sun, 9 Mar 2025 15:37:35 +0000
Organization: A noiseless patient Spider
Lines: 35
Message-ID: <vqkcju$pvlg$1@dont-email.me>
References: <vq1qas$j22$1@gallifrey.nk.ca> <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>
 <20250304092827.708@kylheku.com> <vq7g1p$1vmg5$1@dont-email.me>
 <vq94dt$2boso$1@dont-email.me> <vqcsk7$23bfo$1@paganini.bofh.team>
 <vqefn1$3flpt$1@dont-email.me> <vqeu5c$3imil$1@dont-email.me>
 <vqeun4$3iqbq$1@dont-email.me> <vqfcbe$3lkkc$1@dont-email.me>
 <vqh569$3e9d$1@dont-email.me> <vqhj2e$5u26$1@dont-email.me>
 <vqhp18$75es$1@dont-email.me> <vqhs8o$7o8n$1@dont-email.me>
 <vqii9g$bq1o$6@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Sun, 09 Mar 2025 16:37:35 +0100 (CET)
Injection-Info: dont-email.me; posting-host="69b69def121069d466e382fb0133eb9e";
	logging-data="851632"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18LHjyGnX+SsjV893GUw70v"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:B9ECf7llS27pC54kBl1fCuNuCws=
Content-Language: en-GB
In-Reply-To: <vqii9g$bq1o$6@dont-email.me>
Bytes: 3303

On 08/03/2025 23:02, Lawrence D'Oliveiro wrote:
> On Sat, 8 Mar 2025 16:46:14 +0000, bart wrote:
> 
>> What Make does is take a mountain of complexity called a 'makefile',
>> which is special kind of arcane language, and tries to run it. It might
>> work, it might fail immediately, or it might grind away for several
>> minutes and then it stops.
> 
> All too common with Windows, I’m afraid.
> 
> I remember when the LibreOffice project was set up as a fork from the
> moribund OpenOffice, there was a blog post reporting on initial progress,
> from Michael Meeks I think it was, saying that the Windows build still
> suffered from mysterious intermittent failures, such that retrying the
> build would usually succeed.
> 
> That kind of thing is unheard of on proper *nix systems.


So, what you are saying is that some software that is developed using 
one particular environment, regarding its tools, resources, and testing, 
may fail on an alien environment.

That would not be unexpected. But what is wrong is to trash that other 
environment for being different.

In this case, /why/ was that build failing? Was it even using Windows, 
or some extra layers to emulate Linux on Windows?

You'd need to pinpoint the exact reason for failure before laying blame. 
Maybe the build process is 10 times more elaborate than is necessary, 
and it's going wrong in that 90% that you don't really need anyway.

For example, there's some steps there that might be relevant for some 
obscure corner of Linux, but are meaningless elsewhere.