David Holland wrote:
> On Mon, Jul 19, 2021 at 10:32:20AM +0900, Rin Okuyama wrote:
> > Logs below are usually more helpful.
>
> Right... I wonder what happened to bracket's error-matching script; it
> usually does better than that.
There are multiple causes, but a major one is that since babylo
Updating src tree:
P src/doc/3RDPARTY
P src/external/cddl/osnet/dist/uts/common/fs/zfs/zfs_vnops.c
P src/external/cddl/osnet/sys/sys/vnode.h
P src/sys/arch/alpha/common/sgmap_common.c
P src/sys/arch/alpha/common/sgmap_typedep.c
P src/sys/arch/alpha/include/bus_defs.h
P src/sys/arch/alpha/pci/cia_
On Sun, 18 Jul 2021, Chavdar Ivanov wrote:
The main difference is indeed
... (RPATH) Library rpath:
[$ORIGIN/:$ORIGIN/../../lib/libast:$ORIGIN/cmds:$ORIGIN/../../lib/libdll]
I have to read more to understand it though...
$ORIGIN? That's yet another way to locate shared librarie
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2021.07.19.01.06.14 thorpej src/sys/arch/alpha/pci/cia_dma.c,v 1.37
2021.07.19.01.06.14 thorpej src/sys/arch/alpha/pci/ciavar.h,v 1.22
2021.07.19.01.
On Mon, Jul 19, 2021 at 01:28:06AM +, David Holland wrote:
> that is... less than helpful :-(
>
> it looks like CVS randomly didn't commit some of my changes,
> investigating...
Yeah, not sure what happened; something caused it to, apparently,
think a few of the files in the second change
On 2021/07/19 10:28, David Holland wrote:
that is... less than helpful :-(
it looks like CVS randomly didn't commit some of my changes,
investigating...
Logs below are usually more helpful.
On 2021/07/19 9:42, NetBSD Test Fixture wrote:
Logs can be found at:
http://releng.NetBSD.org/b
On Mon, Jul 19, 2021 at 12:42:49AM +, NetBSD Test Fixture wrote:
> 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.07.18.23.57.34.
>
> An extract
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.07.18.23.57.34.
An extract from the build.sh output follows:
${MAKEDIRTARGET} . ${SUBDIR_GROUP.${:U}:C/
The Qlogic ISP SCSI / FC driver PCI front-end appears to universally support
using 64-bit PCI DMA addresses, based on my reading of this code block in
isp_pci_dmasetup():
if (sizeof (bus_addr_t) > 4) {
if (rq->req_header.rqs_entry_type == RQSTYPE_T2RQS) {
Hi,
Today I upgraded my current setup from the latest nycdn image (amd64)
using sysinst (update flow) and I was surprised that netbsd kernel was
copied to file with unusual /netbsdIleNEk name instead of /netbsd.
Thus, I needed to recopy it manually to netbsd. Unfortunately, I
didn't have time to d
On Sun, 18 Jul 2021, Chavdar Ivanov wrote:
# file ksh93
ksh93: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /usr/libexec/ld.elf_so, for NetBSD
9.99.45, with debug_info, not stripped
# ldd ./ksh93
./ksh93:
-lm.0 => /usr/lib/libm.so.0
-lc.12 =>
On Sun, 18 Jul 2021 at 10:26, RVP wrote:
>
> On Sun, 18 Jul 2021, Chavdar Ivanov wrote:
>
> > # file ksh93
> > ksh93: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
> > dynamically linked, interpreter /usr/libexec/ld.elf_so, for NetBSD
> > 9.99.45, with debug_info, not stripped
> > # ldd ./k
Hi,
Not really a problem, but is bugging me, I have no clue why this
happens. I used to follow the ksh93 development branch and regularly
used to build it for -current. The last one I built was circa February
2020 (${.sh.version} -> 2020.0.0-beta1-222-g8cf92b28), apparently for
NetBSD 9.99.45. It
13 matches
Mail list logo
