Am 03.03.2024 um 19:55 schrieb Paul Goyette:
> I have two 2TB nvme devices, configured with ``ccdconfig ccd0 64
> none /dev/dk1 /dev/dk0''
> then i mount the ccd on /mnt
> and then ccdconfig -g goes boom!!
>
> prevented access to 0x7f7fff9e7fbc (SMAP)
> ccd_info_sysctl+77
>
> The instru
Hi,
I found /usr/bin/checknr and tried it:
$ checknr /usr/share/man/man1/*.1
It spit out an enormous amount of error messages and crashed on 68 of
the files. Its source code hasn't essentially been modified for 18
years, and the code still contains several out-of-bounds memory
accesses, after so
Am 24.05.2024 um 22:05 schrieb B Harder:
>
>
>> On May 24, 2024, at 13:01, Roland Illig wrote:
>>
>> Hi,
>>
>> I found /usr/bin/checknr and tried it:
>>
>> $ checknr /usr/share/man/man1/*.1
>>
>> It spit out an enormous amount of error
On 08.05.2020 16:44, Ron Georgia wrote:
Installed current NetBSD 9.99.60 (GENERIC) #0 and pkgsrc current on
05/08/2020 at about 0900 EST. I tried to build dbus but got an error
when it tried to build perl5.
sh: 1: Syntax error: Word "/d"p" unexpected (expecting ")")
That was a bug in mk/subst.
On 08.05.2020 18:36, Ron Georgia wrote:
Thank you for pointing that out. I am updating now.
I downloaded the NetBSD-9.99.60-amd64-install.img (date stamped May 07,
2020) this morning and installed on my Lenovo X200. I did select the
option to download pkgsrc. I changed the path from stable to c
On 09.05.2020 12:53, Roland Illig wrote:
On 08.05.2020 18:36, Ron Georgia wrote:
Thank you for pointing that out. I am updating now.
I downloaded the NetBSD-9.99.60-amd64-install.img (date stamped May
07, 2020) this morning and installed on my Lenovo X200. I did select
the option to download
On 19.07.2020 19:34, Andreas Gustafsson wrote:
> The build is still broken as of source date 2020.07.19.16.22.44:
>
>
> http://releng.netbsd.org/b5reports/i386/commits-2020.07.html#2020.07.19.16.22.44
I'm sorry, I should have had a build running in parallel to my changes
all the time.
I just c
On 07.12.2020 07:42, Andreas Gustafsson wrote:
The build is now failing differently:
=== 2 extra files in DESTDIR =
Files in DESTDIR but missing from flist.
File is obsolete or flist is out of date ?
--
./usr/tests/usr.bin/make
On 03.01.2021 21:00, 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.01.03.19.15.36.
An extract from the build.sh output follows:
On 23.01.2021 19:34, 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.01.23.17.58.03.
An extract from the build.sh output follows:
On 26.01.2021 13:45, Christian Groessler wrote:
Hi,
dependall ===> tools/lint1
# compile lint1/tyname.lo
86 | intern(const char *name)
Thanks for the notice, I had added the __noinline accidentally.
I removed it again in tyname.c 1.26.
Roland
On 26.01.2021 15:41, Mateusz Guzik wrote:
I had a look with truss at what bmake is doing and I think a lot of
the syscalls can be easily avoided. Examples come from FreeBSD with
bmake-20210110 and I don't know to what extent they are representative
for other systems.
1. spurious waitpid
when do
On 29.01.2021 23:22, Roland Illig wrote:
On 26.01.2021 15:41, Mateusz Guzik wrote:
3. avoidable temp files
JobOpenTmpFile opens a file and later checks if anything was written
to it. Not an actual patch, but a hack to demonstrate the fix can be
found at the end. Looks like checking can be done
On 31.01.2021 19:28, David Holland wrote:
(I'm not sure how much of the jobs/non-jobs copypasting you've cleaned
up lately, if any, since I'm way behind on reading the diffs.)
That's exactly my point here. I've already cleaned up the part where
the shell programs are written in jobs mode, and
01.02.2021 07:58:26 Simon J. Gerraty :
> Martin Husemann wrote:
>
>> [External Email. Be cautious of content]
>>
>>
>> On Sun, Jan 31, 2021 at 12:41:47PM -0800, Simon J. Gerraty wrote:
>>> David Holland wrote:
"static volatile sig_atomic_t reap_children;"
>>>
>>> I chose int (which is wha
On 07.02.2021 01:33, NetBSD Test Fixture wrote:
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
usr.bin/make/t_make:archive
usr.bin/make/t_make:cmdline
I will take care of these.
Roland
On 22.03.2021 01:56, bch wrote:
First thought is to alert rillig@, who’s been working a lot on make/lint
It's true that I've been working a lot there, but in this case I'm
innocent. :)
This is really about the wrong command line in sys.mk. Here are the
relevant parts:
OBJECT_TARGET ?= -o $
Am 07.06.2021 um 16:12 schrieb Dmitrii Postolov:
> Hi! Sorry for my bad English...
>
> NetBSD 9.99.83 GENERIC Sun Jun 6 2021
>
> After install NetBSD 9.99.83 and download and unpack pkgsrc-current, I try to
> build some apps
> from pkgsrc, for example 'editors/nano'. Afrer 'make install clean' the
Hi,
I am running tests/lib/libc/stdio/t_intr on NetBSD 9.99.88/amd64 inside
VirtualBox. The test fails spuriously.
Since I didn't want to dive into the internals of bin/dd, I modified
t_intr by replacing dd with cat. The test still fails spuriously.
I find this surprising since cat uses raw I/O.
Am 07.09.2021 um 22:40 schrieb RVP:
> On Tue, 7 Sep 2021, Roland Illig wrote:
>
>> I am running tests/lib/libc/stdio/t_intr on NetBSD 9.99.88/amd64 inside
>> VirtualBox. The test fails spuriously.
>>
>> I find this surprising since cat uses raw I/O. Or is it maybe
Hi,
I installed
https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/202204091610Z/amd64/installation/cdrom/boot.iso
on a freshly set up VM with the default settings, using VirtualBox
6.1.32 on Windows 11.
The installation went smooth, and NetBSD booted quickly when the VM had
only 1 CPU configured.
Hi,
NetBSD-current fails for me in a VirtualBox with more than 1 CPU.
https://gnats.netbsd.org/56883
https://gnats.netbsd.org/56884
https://gnats.netbsd.org/56885
NetBSD 9.2 from 2020-02-14 works fine.
NetBSD 9.99.97 from 2022-06-14 doesn't work.
There's more than 2 years of active develop
Am 15.06.2022 um 12:45 schrieb Valery Ushakov:
On Wed, Jun 15, 2022 at 00:05:43 +, Chavdar Ivanov wrote:
On 14 June 2022 23:06:56 (+01:00), Roland Illig wrote:
NetBSD-current fails for me in a VirtualBox with more than 1 CPU.
http://virtualbox.org/manual/ch08.html#vboxmanage-modifyvm
Hi,
Out of curiosity, I ran the following commands on NetBSD-current/amd64:
cd /usr/share/man
printf '%s\n' */*.*
| xargs grep -n '^\.Xr ' \
| while read src topic section rest; do
test -f "man$section/$topic.$section" \
|| echo "${src%:*}: missing $topic $section"; \
done
This
Hi,
Do any of the releng builds and tests run with MALLOC_CONF=junk:true?
Background story: I'm tired of finding memory allocation bugs myself
when there is a really simple way of doing the same thing automatically.
How much time would it cost to run the NetBSD build and the tests with
memory a
Am 27.11.2022 um 14:28 schrieb Lizbeth Mutterhunt, Ph.D:
No matter I try, if I use ./build./sh I get a compile/install error at @
“liblua””
Hello Lizbeth,
Whenever the build fails for you, please post the _exact_ output from
the build. In many cases, the last few lines already give enough hin
Am 17.01.2023 um 17:41 schrieb Robert Elz:
https://austingroupbugs.net/view.php?id=1436#c5496
Adds the -j option to make. I doubt there's anything in this which
is different than what we do, but someone familiar with make should
take a look and make sure.
I've read th
Am 24.02.2023 um 22:55 schrieb Greywolf:
worked.
Glad that it worked out. Your first try was:
TAR=/usr/local/bin/gtar make -e TAR=/usr/local/bin/gtar extract
This approach would have worked for some of the commands that are listed
in pkgtools/bootstrap-mk-files/files/sys.mk.
In pkgsrc, the
Am 20.10.2023 um 22:38 schrieb Thomas Klausner:
> Hi!
>
> I'm trying to find out what a program does, and found it does a lot of
> unlink syscalls, so I wanted to see what it unlinks.
Did you try 'ktruss | grep NAMI' before diving deep into dtrace?
Roland
Am 18.12.2024 um 12:52 schrieb Martin Husemann:
> See ctype(3) and search for CAVEATS:
>
> Clearly casting EOF to unsigned char will give an invalid input value to
> any ctype function.
To clarify, the input value will be in the correct range, but the return
value will not be the expected one, as
Am 05.04.2025 um 02:11 schrieb Greg A. Woods:
> I dunno how useful xlint libraries are as I've been more accustomed to
> the old Unix lint libraries (which are even useful standalone, see
> below), but perhaps if productive work is being on xlint, and it is
> gaining enough utility, then maybe it m
Am 06.04.2025 um 00:22 schrieb Greg A. Woods:
> I haven't played enough with xlint in a post C89 world yet to know if it
> will also still catch all the same things (including missing prototypes,
> and mis-matches between prototypes and definitions).
Feel free to look at usr.bin/xlint/lint1/README
I fixed the SIGPIPE problem in usr.bin/make/job.c 1.488 from a few
minutes ago. The test cases you provided run successfully for me now.
Thank you for preparing the tests, I'll add a fast variant of them to
the test suite later.
Roland
Am 06.03.2025 um 04:17 schrieb Greg A. Woods:
> At Wed, 05 Mar 2025 17:40:11 -0800, "Greg A. Woods" wrote:
> Subject: Re: parallel build failure with .c.o rule interrupted mid-step!
>>
>> H maybe there's a clue to this problem in the fact the child
>> shell's output is to a pipe which must
Am 05.03.2025 um 22:09 schrieb Greg A. Woods:
> Ah ha!
>
> I can reproduce the problem frequently now with the makefile below, both
> with the patched make on NetBSD and as nbmake on macOS.
>
> I cannot reproduce any problem, not even left-over intermediate files,
> with bmake-20200524nb1 from pkgs
Am 24.02.2025 um 21:04 schrieb Greg A. Woods:
> In jobs mode make is supposed to feed the whole rule's script to one
> invocation of a shell, and in theory that invocation should run to
> completion even if some other parallel branch of make encounters an
> error.
That's how it _should_ work.
I m
Am 24.02.2025 um 21:04 schrieb Greg A. Woods:
> Somehow when a failure occurred during a parallel build the rule for
> .c.o was interrupted mid-step and left an empty .o:
>
> $ ll hist*
> 16 -rw-r--r-- 1 woods staff - 7671 Feb 23 18:59 hist.d
> 0 -rw-r--r-- 1 woods staff - 0 Feb 23
Am 21.07.2025 um 23:13 schrieb Thomas Klausner:
> Hi!
>
> I've tried packaging Guitar (see wip/Guitar). But when I run it, it
> fails with
>
> ctype(3) isupper: invalid input: -61
>
> I tried running it in gdb, but then gdb hangs or dumps core too.
>
> I looked at all isupper() uses in the Gui
38 matches
Mail list logo
