Hello,

On 2024-12-28 13:51 +03:00, Cyril Brulebois wrote:
> Hi!
> 
> Kentaro HAYASHI <ken...@xdump.org> (2024-12-28):
>> * What led up to the situation?
>>
>>   According to README [1], to know a list of available targets,
>>   need to execute "make", but it takes huge amount of times.
>>
>> * What exactly did you do (or not do) that was effective (or
>>   ineffective)?
>>
>>   Follow instruction in README [2] in advance, then execute make.
>>
>>   $ time make
>>
>>   ...(omit list of available targets)...
>>   
>>   real    12m55.928s
>>   user    10m15.047s
>>   sys     2m44.828s
>>
>>   (on 4vCPU, 16GB memory)
>>
>>   d-i/installer revision:
>>   9f06d60d3 sh4: Don't unversion the kernel as multiple flavors are
>>   supported
>>
>> * What was the outcome of this action?
>>
>>   make returns a list of available targets (expected).
>>   It is expected and result is fine, but it is not expected that it
>>   takes over 10 minutes.
>>
>> * What outcome did you expect instead?
>>
>>   make returns a list of available targets in less times.
>>
>>   If I'm missing something prerequisite, feedback is welcome.
> 
> Thanks for turning this known problem into an actual bug report, that's
> been detected a few days ago, and I've sent my last reply to that thread
> just a few hours ago.
> 
> You can find more details here:
>   https://lists.debian.org/debian-boot/2024/12/msg00154.html
>   https://lists.debian.org/debian-boot/2024/12/msg00161.html
>   https://lists.debian.org/debian-boot/2024/12/msg00217.html
> 
> Right now there are a bunch of things happening for the Trixie Alpha 1
> release. I might look into that once that's been published.

I searched a bit and found a bug report [1] that looks like what we are
running into, with exporting variables and using $(shell). Setting the
variables with := makes `make list` fast again. So I've opened a merge
request [2], hoping it makes sense.

[1] https://savannah.gnu.org/bugs/index.php?64746

[2]
https://salsa.debian.org/installer-team/debian-installer/-/merge_requests/56/

Reply via email to