Patrick Welche writes:
> On Wed, Feb 17, 2021 at 12:34:21AM -0800, Darrin B. Jewell wrote:
>>
>> I honestly hope this isn't related to your problem, but I did make a
>> change to the amd64 cdrom building recently that is in this area
>> and may be the issue.
>>
>>https://mail-index.netbsd.o
Updating src tree:
P src/distrib/sets/lists/man/mi
P src/distrib/sun2/miniroot/Makefile
P src/distrib/sun2/miniroot/list
P src/distrib/sun2/ramdisk/Makefile
P src/doc/3RDPARTY
P src/doc/CHANGES
P src/etc/rc.d/amd
P src/external/bsd/wpa/bin/hostapd/Makefile
P src/external/mit/ctwm/libexec/ctwm_app
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2021.03.01.21.01.39 jakllsch src/distrib/sets/lists/man/mi,v 1.1716
Logs can be found at:
http://releng.NetBSD.org/b5reports/i386/commits-2021.03.html
On 2/03/21 6:51 am, Riccardo Mottola wrote:
I thouht your cited entropy fix was a "once time" not to be reissued
again (when? at every reboot? kernel update?)
I don't think it is that user friendly to recularly "feed" this
entropy... and it gets lost at the next reboot? Could we have a script
Hi Lloyd and Chavdar,
Lloyd Parkes wrote:
>
> On 28/02/21 9:50 am, Riccardo Mottola wrote:
>> python38 hangs during build. I tried several times, it hangs in
>> exactly the same place again. I don't know of course where the issue
>> comes from, since all is new now :)
>
> Do you have any console
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2021.03.01.18.08.36.
An extract from the build.sh output follows:
--- check_DESTDIR ---
--- checkflist ---
c
On Wed, Feb 17, 2021 at 12:34:21AM -0800, Darrin B. Jewell wrote:
>
> I honestly hope this isn't related to your problem, but I did make a
> change to the amd64 cdrom building recently that is in this area
> and may be the issue.
>
>https://mail-index.netbsd.org/source-changes/2021/02/06/msg1
