| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
wcstombs(). These tests have already found two libc bugs.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
errors/warnings related to crud in said test block.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
subdirectories, and ended up making us loop forever.
Add the username to the md5 of the commit to make it slightly more
unique.
Make the 'cvs' run quietly.
|
|
|
|
| |
Sponsored by: DARPA & NAI Labs.
|
|
|
|
| |
Sponsored by: DARPA & NAI Labs.
|
|
|
|
| |
Sponsored by: DARPA & NAI Labs
|
|
|
|
|
| |
Today, I wrote a program to tell me where the partitions used to be.
Now I have my /media filesystem back.
|
| |
|
|
|
|
| |
PR: bin/40846
|
|
|
|
|
|
| |
Fix a couple of reference data which were found to be in error.
Sponsored by: DARPA & NAI Labs.
|
| |
|
|
|
|
| |
All old sorts understand -k too.
|
|
|
|
|
|
| |
this DOES NOT WORK YET. (well it kind-of-does but it's unsafe)
Submitted by: davidxu
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
under way to move the remnants of the a.out toolchain to ports. As the
comment in src/Makefile said, this stuff is deprecated and one should not
expect this to remain beyond 4.0-REL. It has already lasted WAY beyond
that.
Notable exceptions:
gcc - I have not touched the a.out generation stuff there.
ldd/ldconfig - still have some code to interface with a.out rtld.
old as/ld/etc - I have not removed these yet, pending their move to ports.
some includes - necessary for ldd/ldconfig for now.
Tested on: i386 (extensively), alpha
|
|
|
|
|
|
| |
Allow the script to operate on any convenient kernel.
Submitted by: "Matthew Emmerton" <matt@gsicomp.on.ca>
|
|
|
|
| |
50% of the active ingredients in these Makefiles.
|
|
|
|
|
|
|
| |
If somebody wanted to, this could for the beginning of a "libkernel"
which could be used to run kernel code in userland.
Sponsored by: DARPA & NAI Labs.
|
|
|
|
| |
Sponsored by: DARPA & NAI Labs.
|
|
|
|
| |
Sponsored by: DARPA & NAI Labs.
|
|
|
|
| |
Sponsored by: DARPA & NAI Labs.
|
|
|
|
| |
Sponsored by: DARPA & NAI Labs.
|
|
|
|
|
| |
Submitted by: Hiten Pandya <hiten@uk.FreeBSD.org>
Obtained from: NetBSD
|
|
|
|
|
|
|
|
|
|
| |
(I skipped those in contrib/, gnu/ and crypto/)
While I was at it, fixed a lot more found by ispell that I
could identify with certainty to be errors. All of these
were in comments or text, not in actual code.
Suggested by: bde
MFC after: 3 days
|
|
|
|
|
| |
this isn't just for the sake of testing behaviour, and that things really
do break if this regression occurs.
|
|
|
|
| |
symbols as well.
|
| |
|
|
|
|
|
|
| |
initial setup anymore (since process.c rev. 1.25). Add $FreeBSD$.
MFC after: 2 weeks
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
behavior. Add the bcb regression test which checks for failures due
to a backslash ('\') coinciding with the very last character of the
command buffer. The regression test is cf. this PR (which I did not
know about) and has a different fix for the bug.
PR: bin/22351
Submitted by: Stefan Duerholt <stefan.duerholt@t-online.de>
|
|
|
|
| |
transliterate to use echo -n to supress newline and a simple string.
|
|
|
|
|
|
|
| |
handle printing of the PASS/FAIL messages. Suffix PASS/FAIL/FATAL with the
string (in $directory) where $directory is ${.CURDIR} from make(1), to
make it easier to use grep(1) and a bit of sed/awk to do statistics of
failure for some utilities over time, etc.
|
|
|
|
|
|
|
| |
at an EOL/EOF, and therefore should catch the broken behaviour fixed by
Tim J. Robbins in sed(1) recently.
Suggested by: obrien
|
|
|
|
| |
even slightly. Grrr CVS.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
make(1): Does not work like the other tests. Its Makefile is
self-testing.
m4(1): It uses complex voodo to test GNU m4(1) features.
To the new framework. I had worried about passing the binary data that
uudecode(1)'s test passes to diff(1) might give a user something nasty,
but this is unlikely to happen as even with an unmodified old nasty
diff(1) which doesn't recognise many binary files, these binary files
are recognised. Using $DIFF instead of `diff' in the library and making
it possible to override this with `cmp -s' might be nice some day, but
as of this second, there's no immediate need.
|
|
|
|
| |
ungracefully.
|
|
|
|
| |
might be able to figure out how to write some of these tests (hint hint).
|
|
|
|
| |
Goodbye, duplicated code, you will certainly not be missed.
|
|
|
|
|
|
|
| |
to handle the ones which output to stdout and have output in regress.$test.out,
etc. More freeform macros should and will be written, but these are the most
prominent and most straightforward sort of tests we have around, so it makes
sense to try to accomodate them.
|
|
|
|
| |
the right thing in every case. Yuck.
|