Re: current fails to build on amd64

On Mon, 21 Sep 2020 at 19:09, Chavdar Ivanov wrote: > $ uname -a > NetBSD ymir 9.99.73 NetBSD 9.99.73 (GENERIC) #7: Sat Sep 19 10:58:21 > BST 2020 sysbuild@ymir > :/home/sysbuild/amd64/obj/home/sysbuild/src/sys/arch/amd64/compile/GENERIC > amd64 > $ gcc --version > gcc (nb1 20200907) 9.3.0 >

Re: Failure to build Current amd64

On Thu, 17 Sep 2020 at 11:47, matthew green wrote: > > In file included from > > usr/src/external/gpl3/gcc/dist/libstdc++-v3/src/c++17/cow-fs_dir.cc:26: > > /libstdc++-v3/src/c++17/fs_dir.cc:29:10: fatal error: > > bits/largefile-config.h: No such file or directory > >29 | #include > >

Failure to build Current amd64

I just pulled down sources at about 10:00 am BST. Here is the follow error: # create libstdc++-v3/cow-fs_dir.d ... In file included from usr/src/external/gpl3/gcc/dist/libstdc++-v3/src/c++17/cow-fs_dir.cc:26: /libstdc++-v3/src/c++17/fs_dir.cc:29:10: fatal error: bits/largefile-config.h: No

Strange behavior with CVS

I'm using amd64 current 9.99.69. I noticed recently that when I update src with "cvs -q update -dP", that sometimes the screen will freeze. I run X with gkrellm and I notice all the monitors freeze. Also during this time there doesn't seem to be any transmission through the router as no lights

Failure to build current amd64

This was updated from cvs about 10:00 am BST. The failure seems to happen when trying to link libgssapi with compat/amd64/i386 libraries. The error message(s) below: dependall ===> compat/amd64/i386/../../../lib/../crypto/external/bsd/heimdal/lib/libheimntlm dependall ===>

Failure in latest current build

I updated /usr/src at about 11:30 am BST on Sunday. I used build.sh -O ../obj -T ../tools -x -u distribution, with /usr/obj cleaned out before hand. The breakage happened at: dependall ===> external/bsd/atf/tests/atf/test-programs nbmake[9]: don't know how to make cpp_helpers.cc. Stop.

Re: firefox-73.0 build fails under -current

I can confirm that I get the same result as Chavdar. On Wed, 19 Feb 2020 at 11:50, Chavdar Ivanov wrote: > Hi, > > With fully updated pkgsrc tree and several pkg_rolling-replace runs, > firefox-73.0 fails build for me under > # cat /kern/version > NetBSD 9.99.47 (GENERIC) #8: Tue Feb 18

Unable to build amd64 snapshot from 20200117

I was having trouble updating my system with the latest source updates so I decided to go back to scratch, delete /usr/src and /usr/xsrc, download the snapshot from 20200117 and try again. Unfortunately, I get a new error when the system is trying to build "tests." It throws and error at the

Xdm problems

I recently built the latest Current for amd64, (9.99.25), and I included the xsrc code with the build. I use ./build.sh -O ../obj -T ../tools -x distribution and then ./build.sh -O ../obj -T ../tools -x install=/ after building the new kernel. When I run the postinstall program everything cleans

build.sh flag "-u"

I have some uncertainty about the application of the "-u" flag in build.sh. The docs say it prevents "make clean." But without it will rebuild everything, including tools. I've used the flag before without problems, but recently I've had the build break on a couple of occasions. I'm not doing

Re: Question about open ports

Thanks everyone! On Mon, 25 Feb 2019 at 13:21, Greg Troxel wrote: > > Run 'rpcinfo -p'. >

Question about open ports

I'm using amd64 Current, (8.99.34), which I use as a desktop machine as well as an NFS file server. When I scan the ports, I see the ones I expect, sun rpc, (111), and nfsd, (2049), but I also see 1021 - 1023 as listening ports. When I look these up on IANA, they are mentioned as experimental.

kernel error with drm

This is not a serious problem, but I thought I would let developers know. I'm using amd64 Current, (8.99.26), and run the Xserver through the Xorg modular builds. I have noticed periodically that I get and error in my xconsole that reads: kern error:

Re: Rust, pkgsrc

Yes. I had a similar problem. The build would fill up the /tmp/ directory and die from exhausted resources. I had /tmp/ created with tmpfs and had a constraint of 64M. The answer for me was to create /tmp in /etc/fstab with tmpfs and no size constraint. Then Rust would build, but it still took

Re: Problems using cvs after last update

Maya, Thanks. It's working now. On Fri, 28 Sep 2018 at 23:26, wrote: > On Fri, Sep 28, 2018 at 09:03:08PM +0100, Arthur Barlow wrote: > > I am using Current amd64. Last Friday, (the 22nd of September), I > updated > > my /usr/src directory with anonymous cvs and reco

Problems using cvs after last update

I am using Current amd64. Last Friday, (the 22nd of September), I updated my /usr/src directory with anonymous cvs and recompiled the lastest distribution and kernel build. After rebooting and updating all my files with postinstall and etcupdate, I again rebooted and the system seemed to run just