Re: Can't build evbarm

On Fri, Jan 26, 2024 at 09:09:30PM +0100, Adam wrote: > Simple and elegant. No hacks involved. Because the declaration in the relevant header is already there, and the order does not matter. But the #ifdef around the declaration needs to do the right thing. No need to move things around and its li

Re: Can't build evbarm

On Sat, Jan 27, 2024 at 03:33:06PM +0700, Robert Elz wrote: > Now that Christos moved the function around, that declaration in the > header is just noise, and could be removed. Yes, that would be consistent then (but isn't it against the new style rules?) Martin

Re: sysinst

On Wed, Sep 05, 2018 at 05:10:01PM +0100, Patrick Welche wrote: > For once I thought I would try sysinst. After selecting ld0 as the (nvme) > disk, > I see: > > Status: openpty() failed > Command: sh -c 'cat /tmp/disktab.* > /tmp/disktab' A bit of context would certainly help. This usually mea

Re: HEADS-UP: Recent atari install floppy overflow

On Thu, Sep 13, 2018 at 04:49:31PM +0700, Robert Elz wrote: > Note that if I do (2) (the clean/correct way) the fallout will affect *all* > ports that use a -DSMALL (or perhaps -DTINY) /bin/sh anywhere in > the installation builds. I prefer this option. The SMALL or TINY shell is still functional

Re: small sysinst(8) without extended partitioning support

On Thu, Sep 20, 2018 at 09:32:21PM +0900, Rin Okuyama wrote: > > > > > > I've confirmed sysinst(8) with and without this option works on amd64. > > > > Go for it. > > Thanks, committed! How about this? Can you please give a bit more time before such changes? I am working on huge diffs to sysins

Re: small sysinst(8) without extended partitioning support

On Thu, Sep 20, 2018 at 10:16:49PM +0900, Rin Okuyama wrote: > Oops, sorry, I will revert it for now, and rework after your > changes are committed. No, please don't revert it - I'll deal with the merge. Martin

Re: small sysinst(8) without extended partitioning support

On Thu, Sep 20, 2018 at 10:23:00PM +0900, Rin Okuyama wrote: > On 2018/09/20 22:17, Martin Husemann wrote: > > On Thu, Sep 20, 2018 at 10:16:49PM +0900, Rin Okuyama wrote: > > > Oops, sorry, I will revert it for now, and rework after your > > > changes are committed

Re: sys/arch/evbarm/conf/majors.evbarm missing in -current

On Sun, Sep 30, 2018 at 09:40:00AM +0200, Tom Ivar Helbekkmo wrote: > Running 'postinstall check' on a Raspberry Pi 3B+ with a current (well, > as of just before the openssl upgrade of a few days ago) evbarm64 > installation complains about a missing majors file: > > makedev check: > ERROR: can't

Re: progress(1) and "*.tar.xz" sets

On Fri, Sep 28, 2018 at 12:58:52PM -0500, John D. Baker wrote: > Has any consideration been given to augmenting the 'progress(1)' utility > to handle more compression formats than just "gzip"? > > When updating, I have been in the habit of using something like: > > for file in foo.tgz bar.tgz ;

Re: flist issue for current build

On Mon, Oct 08, 2018 at 10:38:19AM +0200, Adam wrote: > Greetings, > > This is what I get while trying to build amd64 or i386 (today sources). > > === 3 extra files in DESTDIR = > Files in DESTDIR but missing from flist. > File is obsolete or flist is out of date ? > ---

Re: flist issue for current build

On Mon, Oct 08, 2018 at 11:38:02AM +0200, Adam wrote: > > Did you start with an empty destdir? > > > > Martin > > Yes. I usually point the destdir to a ram-disk, so it's always empty. > Also, I cross-build on macOS, but that shouldn't matter, right? This is strange, the auto builds worked, my lo

Re: flist issue for current build

On Mon, Oct 08, 2018 at 05:43:05PM +0800, Paul Goyette wrote: > Hmmm, since you are building on macos, it could be a case-sensitive file > system issue. I have a hmac man page in section 3, but not HMAC. Yeah, but *.3.gz ? Martin > > > > This is what I get while trying to build amd64 or i386 (t

Re: flist issue for current build

On Mon, Oct 08, 2018 at 02:21:25PM +0200, Adam wrote: > They come from: > - src/crypto/external/bsd/openssl/lib/libcrypto/man/Makefile (upper-case > man-pages) > - src/crypto/external/bsd/openssl/lib/libdes/Makefile (lower-case man-pages) But why are you getting .3.gz files? If it were plain .3 f

Re: Automated report: NetBSD-current/i386 test failure

On Sun, Sep 30, 2018 at 06:13:41PM +, NetBSD Test Fixture wrote: > This is an automatically generated notice of new failures of the > NetBSD test suite. > > The newly failing test cases are: > > net/ipsec/t_ipsec_natt:ipsec_natt_transport_null > net/ipsec/t_ipsec_natt:ipsec_natt_trans

Re: Minor sysutils/sysupgrade mod

On Thu, Nov 01, 2018 at 09:40:33AM -0400, Greg Troxel wrote: > It needs to support both, because 7/8 are still .tar.gz. Also not all architectures did switch to .tar.xz (the decompressor needs quite a bit of memory). Martin

Re: build.sh distribution failure for evbarm

On Fri, Nov 02, 2018 at 01:04:33PM +, Chavdar Ivanov wrote: > The last (third) attempt was with fresh obj directory; I also did > 'make cleandir' in the src directory just in case (in the past this > has helped). It is best to check the autobuild results in such cases, they fail the same (and

Re: Install with new tar.xz extension

On Sun, Nov 04, 2018 at 08:49:03AM -0600, Robert Nestor wrote: > Tried downloading and installing 8.99.25 this morning and noticed > that it fails because the installation utility (sysinst) doesn?t > support the new tar.xz extension. PR pkg/53697 seems to address this > in the sysutil/sysupgrade u

Re: Install with new tar.xz extension

Ooops, accidently did not reply to all.. On Mon, Nov 05, 2018 at 02:17:51PM +0100, Martin Husemann wrote: > On Mon, Nov 05, 2018 at 06:49:00AM -0600, Robert Nestor wrote: > > > I?m thinking now that the ?install.sh? script on the CD image just > > ran the ?sysinst? that was

Re: Install with new tar.xz extension

On Mon, Nov 05, 2018 at 08:36:37AM -0600, Robert Nestor wrote: > Two issues though: 1) pkgin install reported an error - no > libcrypt.so found, and 2) pkgsrc install failed as it downloaded in > ?.tar.gz? format (I think), but expected a ?.tar.xz? format for > unpacking. The first is a pkgsrc iss

Re: Install with new tar.xz extension

On Mon, Nov 05, 2018 at 09:20:56AM -0600, Robert Nestor wrote: > On the pkgsrc install I?ve verified that it does indeed download > pkgsrc.tgz into the /targetroot/INSTALL directory, but then fails > attempting to unpack pkgsrc.tar.xz. So it appears it is only looking > for the latter format for u

Re: Rust, pkgsrc

On Tue, Nov 06, 2018 at 07:50:18PM +0100, Havard Eidnes wrote: > The last version I managed to build on one of my NetBSD/macppc > 8.0 machines (a single-core 1.5GHz G4 Mac Mini, 1GB memory) was > 1.29.2, the build took nearly 29 hours wallclock time. This one > doesn't have a tmpfs, and has a sing

Re: upgrading via source from 7.1.2 dependencies

On Sun, Nov 11, 2018 at 06:41:19PM +0100, os...@fessel.org wrote: > indeed, this is conditional. > Unfortunately, at least in my copy, MKX11 gets only set to yes with build.sh > -x. > The documented ?MKX11 defaults to no? is nowhere explicitly set. In share/mk/bsd.own.mk search for _MKVARS.no

Re: Local {amd,sparc}64 builds revert to *.tgz sets?

On Wed, Nov 21, 2018 at 03:13:57AM -0600, John D. Baker wrote: > ISTR something about USE_PIGZ_GZIP being at odds with *.tar.xz sets > but can't find where that was. I have had USE_PIGZ_GZIP=yes for > quite some time. > > I see autobuilds are producing *.tar.xz for amd64 and sparc64. Pigz can no

Re: Local {amd,sparc}64 builds revert to *.tgz sets?

On Wed, Nov 21, 2018 at 02:10:01PM -, Michael van Elst wrote: > I'd rather reverse that logic. Chose the output format and > ignore USE_PIGZ_GZIP when it doesn't apply to that format. Maybe. I don't really care for anything but the autobuilds and internal consistency (i.e. sysinst getting the

Re: Local {amd,sparc}64 builds revert to *.tgz sets?

On Wed, Nov 21, 2018 at 03:24:28PM +, David Brownlee wrote: > Maybe abort the build with an error - its asking for an unresolvable > combination. Anything else violates the POLS. I disagree - it just works (independend of which option wins). Who cares what compression format is used in the end

Re: Local {amd,sparc}64 builds revert to *.tgz sets?

On Wed, Nov 21, 2018 at 03:52:29PM +, David Brownlee wrote: > Why would I as a user expect USE_PIGZGZIP to break USE_XZ_SETS, or conversely > USE_XZ_SETS to silently ignore USE_PIGZGZIP. That reeks of hidden magic. because that document says so a few lines further down ;-) USE_XZ_SETS If

Re: Local {amd,sparc}64 builds revert to *.tgz sets?

On Wed, Nov 21, 2018 at 11:23:31AM -0600, John D. Baker wrote: > Then I suppose I misunderstood the effect of USE_PIGZGZIP. I was under > the impression that it only affected the selection of the tool used to > provide "gzip"-type compression (use 'pigz'/'nbpigz' versus actual 'gzip' > or 'nbgzip'

Re: Automated report: NetBSD-current/i386 test failure

On Fri, Nov 30, 2018 at 03:16:00PM +0200, Andreas Gustafsson wrote: > The NetBSD Test Fixture wrote: > > This is an automatically generated notice of a new failure of the > > NetBSD test suite. > > > > The newly failing test case is: > > > > lib/libc/sys/t_sendmmsg:sendmmsg_basic This test h

Re: issues with touchpad after update

On Sat, Dec 01, 2018 at 11:58:13PM +0100, Riccardo Mottola wrote: > Hi, > > after updating system to current yesterday (kernel + userland) I noticed > that the TouchPad in X11 is essentially unusable. > It overreacts and clicks at random. What I think is that it attempts > "scrolling" because just

Re: issues with touchpad after update

Btw, the X log is mostly useless, please post your dmesg output for pms and wsmouse0. Thanks, Martin

Re: issues with touchpad after update

On Sun, Dec 02, 2018 at 01:21:11PM +0100, Riccardo Mottola wrote: > Hallo Martin, > > Martin Husemann wrote: > > I have seen that but Brett's latest synaptics commit mostly fixed it for > > me. Before that, I had > > Latest... more than 2 days ago? You m

Re: mfii0 kudos to bouyer@ Was Re: dmesg | grep -c "not configured" = 240...

On Tue, Dec 04, 2018 at 07:17:59PM +, Mike Pumford wrote: > One thing that surprised me was that I was testing with the USB install > image but instead of landing in sysinst I ended up at a a login prompt which > was unexpected. Could this be because the USB disk that was my root device > ended

Re: issues with touchpad after update

On Thu, Dec 06, 2018 at 07:52:52AM +1030, Brett Lymn wrote: > I think Martin said he was going to look at this - again, I only have a > clickpad on my laptop so it is hard to test. Yes. > > I think it is just a software feature, maybe not even convenient - I am > > not accustomed to it because e

Re: How to boot in UEFI mode: practically no documentation

On Tue, May 29, 2018 at 08:15:43AM +, Thomas Mueller wrote: > Where do I find documentation on how to boot NetBSD amd64 or possibly i386 in > UEFI mode? I'm working on a wiki page (and will change the NetBSD 8.0 install docs to point to that). I can't answer how to boot into alternative oper

Re: ./build.sh -k feature request (was Re: GENERIC Kernel Build errors with -fsanitize=undefined option enabled)

On Mon, Jun 25, 2018 at 10:44:36PM +0200, Kamil Rytarowski wrote: > I propose to ensure that MAKEFLAGS is possible to be set from a command > line, from the ./build.sh command line using -V. > > The build process has various stages and after a single failure there > can be false positives in next

Re: Driver for Raspberry Pi 3B+ ethernet adapter (Microchip LAN75xx/LAN78xx)

On Sat, Aug 25, 2018 at 01:55:08PM +0900, Rin Okuyama wrote: > I'd like to commit it in this weekend if there's no objection. Great! Please commit, we can improve it in-tree. Martin

Re: netbsd-7 build error?

On Thu, Jan 03, 2019 at 05:05:42PM +0100, Havard Eidnes wrote: > Hi, > > I just updated one of my source trees to netbsd-7, and did a > fresh rebuild (empty obj and dest, host oldish 7.1_STABLE), but > got: For what value of "just"? You need something from today around noon UTC or newer. > Anyon

Re: netbsd-7 build error?

On Thu, Jan 03, 2019 at 05:15:10PM +0100, Havard Eidnes wrote: > >> I just updated one of my source trees to netbsd-7, and did a > >> fresh rebuild (empty obj and dest, host oldish 7.1_STABLE), but > >> got: > > > > For what value of "just"? You need something from today around noon UTC > > or newe

Re: debugging symbols and gdb

The most simple way to get debug symbols is to (manually) install the debug and xdebug sets. If you build locally, use build.sh -V MKDEBUG=yes. Martin

Re: debugging symbols and gdb

On Fri, Jan 04, 2019 at 10:43:52AM +, Patrick Welche wrote: > I can try that as well, but my point is that I have them - file > shows that they are built in, gdb says it loaded them. That no > function of Xorg appears named in the backtrace is unlikely. Yeah, true - orthogonal issue. But it w

Re: What happened to lmc

On Tue, Jan 15, 2019 at 02:28:20PM +0100, Riccardo Mottola wrote: > Hi, > > I updated and am compiling a new kernel... > > /usr/src/sys/arch/amd64/conf/HP620:791: lmc*: unknown device `lmc' > *** Stop. The code has been removed, just drop that line from your kernel config. Martin

Re: Current build failure on AMD64

On Tue, Jan 29, 2019 at 09:30:13AM +0100, Fekete Zoltán wrote: > Hi There, > > My current's build breaks with the message below for 2 weeks now. Could you > please help to resolve? > > /usr/tools/lib/gcc/x86_64--netbsd/6.5.0/../../../../x86_64--netbsd/bin/ld: > libgcc_s_pic.a(enable-execute-stack

Re: varshm check in postinstall

On Thu, Jan 31, 2019 at 05:23:45PM +0900, Masanobu SAITOH wrote: > - if ${GREP} -w "/var/shm" "${DEST_DIR}/etc/fstab" >/dev/null 2>&1; > + if ${GREP} -E "^var_shm_symlink" "${DEST_DIR}/etc/rc.conf" >/dev/null > 2>&1; > + then > + failed=0; > + elif ${GREP} -w "/var/shm"

Re: build.sh ... distribution fails (amd64)

On Mon, Feb 11, 2019 at 08:39:51PM +0100, K. Schreiner wrote: > Hi, > > with current source cvs'uped some minutes ago: Sigh - it compiled for me as I was building for debug, but with release optimizations on gcc is smarter. Will fix in a minute. Martin

Re: gcc 7 warning

On Tue, Feb 12, 2019 at 04:35:02PM +, Patrick Welche wrote: > Bemused by: > > xenpmd.c:90:36: error: '%s' directive output may be truncated writing up to > 511 bytes into a region of size 271 [-Werror=format-truncation=] > #define BATTERY_INFO_FILE_PATH "/tmp/battery/%s/info" >

Re: gcc 7 warning

On Tue, Feb 12, 2019 at 06:13:00PM +0100, Joerg Sonnenberger wrote: > snprintf *does* guarantee that. You are confusing this with strncpy. As I said, I fail to parse the gcc warning. But using the return value quells it. But of course you are right and it makes absolutely no sense at all to me. M

Re: problems with USB/CDC serial (umodem) - devices work with Linux, Mac OS X, and FreeBSD, but not NetBSD

Please show us more details, like: - kernel messages how the devices attach - maybe kernel messages from somewhere else (FreeBSD?) You can use ktrace on the daemon process to see the communication it does via the serial device. First important part: which device node is it opening? E.g. it coul

Re: current fails to boot on VirtualBox

On Sun, Feb 17, 2019 at 09:23:41AM +0100, Adam wrote: > VirtualBox does not support SVS. I am not sure how to parse that - what part of Virtual Box would need to "support" the NetBSD guest kernel's SVS option? Martin

Re: problems with USB/CDC serial (umodem) - devices work with Linux, Mac OS X, and FreeBSD, but not NetBSD

On Sun, Feb 17, 2019 at 08:21:23PM -0800, Rob Newberry wrote: > > Please show us more details, like: > > > > - kernel messages how the devices attach > > On NetBSD: > > umodem0 at uhub2 port 1 configuration 1 interface 1 > umodem0: Nordic Semiconductor (0x1915) nRF52840 OpenThread De

Re: problems with USB/CDC serial (umodem) - devices work with Linux, Mac OS X, and FreeBSD, but not NetBSD

On Mon, Feb 18, 2019 at 09:24:33AM +0100, Martin Husemann wrote: > Note that your FreeBSD installation writes something completely different > to the device. It has been pointed out off list that the FreeBSD ascii version is just differently encoded (with "." for unprintable cha

Re: problems with USB/CDC serial (umodem) - devices work with Linux, Mac OS X, and FreeBSD, but not NetBSD

On Mon, Feb 18, 2019 at 09:11:51AM -0800, Rob Newberry wrote: > I'm pretty sure there are differences in how NetBSD's USB modem class > driver interacts with the device from how other platforms do. For the > time being, I'm trying to read the code of the NetBSD and the FreeBSD > drivers, along wit

Re: XEN3_DOMU no longer shutting down or rebooting

On Tue, Feb 19, 2019 at 03:28:23PM +, Chavdar Ivanov wrote: > Any bells ringing? I think this already has been fixed by Cherry? Martin

Re: Panic on current on mac68k

On Sun, Feb 24, 2019 at 09:33:36PM +, John Klos wrote: > On a Quadra 605 which has been running netbsd-8 without issues for ages, it > seems -current isn't happy. I don't see any obvious recent changes which > might cause this. Ideas? My Quadra runs 8.99.34 from Feb 18 just fine - but that is

Re: Panic on current on mac68k

On Tue, Feb 26, 2019 at 05:20:58PM +0900, Rin Okuyama wrote: > Martin, do you use GENERIC? GENERIC kernel with and without > the patch does not work on my Quadra 840AV. I observe what you > reported before: > > https://mail-index.netbsd.org/tech-kern/2018/10/17/msg024139.html Duh, I forgot about

Re: zsh crash in recent -current

On Tue, Mar 12, 2019 at 03:33:26PM +, Chavdar Ivanov wrote: > Hi, > > On amd64 -curent from yesterday (and a couple of days earlier) I > started to get zsh crashes when tab-completing (files, directories, > packages), similar to > . > Core was generated by `zsh'. > Program terminated with

Re: zsh crash in recent -current

On Wed, Mar 13, 2019 at 10:06:42AM +, Chavdar Ivanov wrote: > I saw the one with the trashed history as well. > > I don't think it is zsh's problem, though. As I mentioned above, I've > used v5.7 since it came out without any problems until perhaps 3-4 > days ago. It still is very likely a zs

Re: xdm receives no input

On Wed, Mar 13, 2019 at 10:44:46AM +, Patrick Welche wrote: > I stared at /etc/X11/xdm/Xresources, and > https://gitlab.freedesktop.org/xorg/app/xdm/blob/master/config/Xresources.in > and didn't spot additional fields (just our fonts are smaller and we > fiddle with the NetBSD logo) - what shou

Re: xentools411 fails build

On Sat, Mar 16, 2019 at 10:18:48AM +, Chavdar Ivanov wrote: > xenpmd.c: In function 'get_next_battery_file': > xenpmd.c:90:36: error: '%s' directive output may be truncated writing > up to 511 bytes into a region of size 271 [-Werror=format-truncation=] > #define BATTERY_INFO_FILE_PATH "/t

Re: xentools411 fails build

On Mon, Mar 18, 2019 at 11:30:49AM +1100, matthew green wrote: > Martin Husemann writes: > > IMO the most stupid warning ever added to gcc. I would just disable it for > > newer gcc. > > i don't agree. some times it is very difficult to avoid and > it sometimes mi

Re: /dev/stdin: Device not configured

On Thu, Mar 21, 2019 at 09:42:16AM +0100, Adam wrote: > crw--w 1 root tty 5, 0 Mar 21 09:39 /dev/fd/0 > > Nothing special, right? :) For what arch is that supposed to be? For i386 I would expect 22, 0 instead of 5, 0. Martin

Re: init died

On Thu, Mar 21, 2019 at 09:42:59AM +, Patrick Welche wrote: > Just updated a amd64 box from 8.99.30 -> 8.99.36. > - successfully booted with new kernel+modules > - fail after updating userland with: > > [ 7.9567598] kern.module.path=/stand/amd64/8.99.36/modules > [ 7.9767685] init path (de

Re: xentools411 fails build

This kind of warning (used with -Werror) breaks all sysutils/xentools* builds with gcc >= 7. I started fixing some for xentools48, but ran out of time and gave up on xen instead. Martin $NetBSD$ Elide string truncation warning with newer gcc. --- tools/xenpmd/xenpmd.c.orig 2018-01-23 14:49:58.

Re: init died

On Fri, Mar 22, 2019 at 04:09:27PM +, Patrick Welche wrote: > I see how this happened: ~forever was just last November. > > - /dev/MAKEDEV exists on the disk after original installation > - forget to cd /dev && sh MAKEDEV all > - on boot, /sbin/init creates mfs partition and mounts over /dev >

Re: /usr/tests/modules usage

On Sat, Apr 06, 2019 at 09:00:37AM -0700, Jason Thorpe wrote: > I originally but the thread pool test harness module in the kern/ > subdirectory, but then it got moved. > > *shrug* Originally I thought we would get very few modules for this kind of tests and put them in the standard modules set

Re: pkgsrc/doc/guide build failure on -current (more jemalloc fallout)

On Sun, Apr 07, 2019 at 08:21:07PM +0100, Chavdar Ivanov wrote: > : > /home/sysbuild/src/external/bsd/jemalloc/lib/../dist/src/arena.c:271: > Failed assertion: "bitmap_get(slab_data->bitmap, > &bin_info->bitmap_info, regind)" > *** Signal 6 Can you build tex with debug info and get a backtrace fr

Re: Funky Display Output

On Thu, Apr 11, 2019 at 11:01:52PM -0500, John D. Baker wrote: > On the two intel-graphics machines I've tried now, I have the same > problem I originally mentioned in: > > http://mail-index.netbsd.org/current-users/2019/04/11/msg035551.html Just to make sure it is clear: the xdm glitches are

Re: com(4) dialout device behavior change?

On Mon, Apr 15, 2019 at 01:17:52AM -0500, John D. Baker wrote: > Turns out there's something wrong with the: > > com* at acpi? Since those don't do much, please check how the acpi variants interrupt and whethere you get one of those interrupts ever. Not much point in bisecting this to a update

Re: (too) big font on console?

On Sat, Apr 20, 2019 at 08:31:29PM +, m...@netbsd.org wrote: > I understand it's meant to aim for 80x25, which is what we used to have. > There were some complaint threads about how much smaller DRM/KMS made > things, but perhaps people got used to it. It is way too big on my old 14" pinebook

Branch for netbsd 9 upcoming, please help and test -current

Folks, once again we are quite late for branching the next NetBSD release (NetBSD 9). Initially planned to happen early in February 2019, we are now aproaching May and it is unlikely that the branch will happen before that. On the positive side, lots of good things landed in -current in between,

Re: current long build time

See also PR toolchain/54136. Martin

Re: iwm driver leads to kernel crash

On Sat, Apr 27, 2019 at 04:18:20PM +, n...@n0.is wrote: > It's an T440s, so one module can be exchanged, the other is soldered > to the board. > > I can give exchanging the replacable one a try. I have had good experience with running memtest+ from pkgsrc (I had to use an older binary, newer

Re: X Window issues

On Sat, May 11, 2019 at 11:25:42PM +0100, Chavdar Ivanov wrote: > There is definitely some recent problem with the new Intel driver. A few > days ago, still under 8.99.37, it worked very well for me (Intel 530). > glmark2 completed with no problems, videos were played as expected by > Firefox 66.0.

Re: jemalloc fallout for i386 on amd64?

On Sun, May 12, 2019 at 04:43:45AM +0300, Valery Ushakov wrote: > I have an old i386 kmk binary built on 6.1 > Core was generated by `kmk'. > Program terminated with signal SIGSEGV, Segmentation fault. > #0 0xf618abc9 in je_tcache_bin_flush_large () from /usr/lib/i386/libc.so.12 > (gdb) bt > #0

Re: KUBSan & alignment

On Fri, May 17, 2019 at 12:15:16PM -0500, David Young wrote: > On Fri, May 17, 2019 at 05:19:40PM +0100, Patrick Welche wrote: > > What should one do about > > > > UBSan: Undefined Behavior in > > ../../../../external/bsd/acpica/dist/events/evregion.c:611:14, load of > > misaligned address 0xfff

What to do with base X11 for netbsd-9 ?

Hey folks, I would like to get your feedback about the current state of the base X11, as there have been lots of threads about various issues and I have lost the overview of what works in -current and what does not. We *really* need to branch netbsd-9 very soon now, and it is unclear (at least to

Re: What to do with base X11 for netbsd-9 ?

On Wed, May 29, 2019 at 06:15:52PM -, Christos Zoulas wrote: > >> - we have very obvious display bugs at first sight in xdm > > > >let's revert to the old xdm for now. this one should be easy. > >can someone work on it please? > > Are those display bugs though? Or is it just that the right d

Re: What to do with base X11 for netbsd-9 ?

On Thu, May 30, 2019 at 12:25:42PM +0100, Chavdar Ivanov wrote: > > Michael looked into it, and it seems to be code bugs (calculating the > > edit field sizes and border coordinates). It is not just resource changes. > > > > This should be easy to fix and also (as it seems to be local to xdm itself

Re: What to do with base X11 for netbsd-9 ?

On Thu, May 30, 2019 at 07:22:08PM +0200, Joerg Sonnenberger wrote: > On Wed, May 29, 2019 at 09:12:42AM +0200, Martin Husemann wrote: > > - self hosting builds on 4 GB amd64 machines are not really possible > >any more (due to LLVM runtime dependencies, which can not even be

Re: building base with clang

On Wed, Jun 05, 2019 at 07:48:25AM +, n...@n0.is wrote: > Hi, > > how good or bad is the base system with clang (ie, since > gcc is the default is enough care taken to make the cvs > build with clang without major breakages)? Depends on your architecture. You can see a few of those builds at

Re: 8.1; sbin/postinstall 'fix' removes libc.so.12

On Thu, Jun 06, 2019 at 07:18:57PM +, m...@netbsd.org wrote: > Most likely, you had: > libc.so.12.207, libc.so.12.208 > >From unpacking older sets, you gained a symlink to an older minor: > libc.so.12 -> libc.so.12.207 > Postinstall apparently sees, "old minors! I can get rid of it!" > > It sh

Re: Enabling xdm in sysinst breaks console login?

On Sat, Jun 08, 2019 at 10:00:16PM +0100, David Brownlee wrote: > So the next question is - what should the default be - as shipping a > system which has an option to enable xdm when then breaks console > login is... suboptimal :) The question is why you got a broken Xservers file. It should use v

Re: Enabling xdm in sysinst breaks console login?

On Sun, Jun 09, 2019 at 10:49:58AM +0100, David Brownlee wrote: > I think this is the getty on console fighting with xdm's xconsole. > > This could be avoided by editing /etc/ttys to disable console and > enable ttyE0, but that breaks serial consoles. Would it just be better > to run getty on cons

Help needed: I likely broke your installer

I just commited a (huge) change to the NetBSD installer[1] that likely will break it for you, especially if you use one of the less common architectures. There will likely be a bit build fallout (for size issues), I hope to get that fixed quickly. The change was needed as sysinst was mostly unusa

Re: Help needed: I likely broke your installer

On Wed, Jun 12, 2019 at 08:48:14AM +0200, Martin Husemann wrote: > The current state is: known broken: macppc and some ofppc. Maybe > broken: amiga, netwinder (and everything needing some special boot > partition setup). All others should just work :-) Actually it is mac68k that is kno

Re: NetBSD-current/amd64 build release failure

On Wed, Jun 19, 2019 at 12:39:48PM +0900, Motoyuki OHMORI wrote: > --- a/sys/compat/netbsd32/netbsd32_syscalls_autoload.c > +++ b/sys/compat/netbsd32/netbsd32_syscalls_autoload.c > @@ -64,8 +64,10 @@ static struct sc_autoload netbsd32_syscalls_autoload[] = { > { NETBSD32_SYS_compat_43_n

Re: usr.sbin/sysinst compile error

On Wed, Jun 26, 2019 at 08:28:21AM +, n...@n0.is wrote: > Christos Zoulas transcribed 234 bytes: > > In article <20190625191514.qbcastohka3nxfos@uptimegirl>, > > wrote: > > >Hi, > > > > > >has someone commited a fix for this in the last 8 hours or so > > >since I've been compiling src? > >

Re: usr.sbin/sysinst compile error

On Wed, Jun 26, 2019 at 09:11:46AM +, n...@n0.is wrote: > This is with ./build.sh ... -U distribution > with the host system being on 8.99.42, built with clang, > and this being relevant parts of mk.conf: Is there a "-u" in the "..." part of the build.sh invocation? Can you try to remove the

Re: usr.sbin/sysinst compile error

On Wed, Jun 26, 2019 at 09:30:41AM +, n...@n0.is wrote: > Okay, and how would I proceed without the build.sh running clean in obj first > then? > I've reads bits of build.sh but I am not sure if it was obvious to find. It does not do a clean in obj/tools alwasys, which might be what causes th

Re: tpcalib build error

On Wed, Jul 10, 2019 at 11:19:22AM +0100, Patrick Welche wrote: > I see > > ld -Map netbsd.map --cref -T netbsd.ldscript -Ttext 0x8020 -e > start -z max-page-size=0x20 -X -o netbsd ${SYSTEM_OBJ:[@]:Nswapnetbsd.o} > ${EXTRA_OBJ} vers.o swapnetbsd.o > ld: hidms.o: in function `hidm

Re: run(4) fails to scan

On Mon, Jul 15, 2019 at 07:25:45PM +0200, Manuel Bouyer wrote: > Hello, > I'm trying to use this wifi USB adapter: > run0 at uhub7 port 1 > run0: Ralink (0x148f) 802.11 n WLAN (0x5370), rev 2.00/1.01, addr 3 > run0: MAC/BBP RT5390 (rev 0x0502), RF RT5592 (MIMO 1T1R), address > e8:4e:e8:4e:af:44 >

Re: run(4) fails to scan

On Mon, Jul 15, 2019 at 07:16:17PM +0100, Robert Swindells wrote: > >OpenBSD works fine, and there are quite a few differences for this variant > >in the driver. > > Maybe try the patch here: > > I'll try that. > I had a patch b

Re: How to fix missing files in flist but missing from DESTDIR ?

On Wed, Jul 24, 2019 at 11:39:20PM -0700, Michael Cheponis wrote: > How is the ./build.sh error, below, fixed? > > == 2 missing files in DESTDIR > Files in flist but missing from DESTDIR. > File wasn't installed ? > -- > ./usr/share/man/html8/

How to best build a smalle libcurses for tiny crunched installers?

Hey folks, we used to get away in tiny crunched binaries w/o most of the locale support in libc via src/distrib/utils/libhack overriding the relevant functions with simpler versions. This seems to not work any more - one fallout is non buildable boot floppies for atari and overflowing install ima

Re: How to best build a smalle libcurses for tiny crunched installers?

On Sat, Jul 27, 2019 at 04:10:42AM +0300, Valery Ushakov wrote: > I have also added HAVE_WCHAR ifdefs to slk.c, which I forgot about. > >From a quick visual inspection the DISABLE_WCHAR curses no longer > refers to anything untoward. Great, together with my distrib hacks that gave me a working ata

Re: How to best build a smalle libcurses for tiny crunched installers?

On Sat, Jul 27, 2019 at 04:03:17PM +0200, Martin Husemann wrote: > Sun3 still fails as we need a non-WCHAR version of nvi for that. > Any takers? Interestingly only a single missing symbol: > > src/external/bsd/nvi/dist/cl/cl_funcs.c:65: undefined reference to `waddnwstr' ...

Re: How to best build a smalle libcurses for tiny crunched installers?

So I ened up doing both: 1) add missing tiny wrappers to distrib/utils/libhack untill the main locale references to libc disappeared (that is most of the multibyte locale code got not pulled in any more) 2) create a makefile hack to build libcurses and nvi w/o WCHAR support The resulti

Looking for UEFI setups booting from MBR

I have a kinda strange request: if you have an amd64 system with UEFI firmware that boots in UEFI mode and the disk is not partitioned with GPT, could you mail me the output of "fdisk -v wd0" (or whatever disk it boots from, often it will be ld0 for the first NVME device). It does NOT need to boo

Re: How do I deal with this file?

On Tue, Jul 30, 2019 at 10:44:07PM +0700, Robert Elz wrote: > Check your mk.conf and whatever you use to generate builds. > If anything has MKBSDTAR=yes that would explain it. The default > (and so what the releng builds use), is MKBSDTAR=no . This has recently changed, it now is MKBSDTAR=yes.

Re: How do I deal with this file?

On Tue, Jul 30, 2019 at 04:50:19PM +0100, Chavdar Ivanov wrote: > The releng build from yesterday still has /bin/tar hard-linked to > /bin/cpio. Which build is that? Maybe you used the .../latest/ symlink and got a build from last week, as we haven't had a full working build for a week or so. > I

Re: NetBSD 9.0 release process has started

On Thu, Aug 01, 2019 at 04:27:29PM -0700, Hisashi T Fujinaka wrote: > Oh, duh, I think I remember that the real issue is that you can't run as > many $JOBS. Before it would be better about throttling things. If you have a concrete example (like: on netbsd-8 I can build rust with MAKE_JOBS=12 on th

<    1   2   3   4   5   6   7   8   >