On Thu, 7 May 2020 23:11:22 -0400 Robert Huff roberth...@rcn.com said
Hello:
On a system running:
FreeBSD 13.0-CURRENT #0 r354131: Mon Oct 28 17:27:33 EDT 2019 amd64
Today around noon I downloaded a fresh copy of the source tree
(for base/head) to r360785.
make.conf:
Hello:
On a system running:
FreeBSD 13.0-CURRENT #0 r354131: Mon Oct 28 17:27:33 EDT 2019 amd64
Today around noon I downloaded a fresh copy of the source tree
(for base/head) to r360785.
make.conf:
#WITH_DEBUG=yes
SENDMAIL_CFLAGS=-I/usr/local/include/sasl -DSASL
SENDM
[mountd failure example: also at sz_size2index_lookup assert
for the same zero'd memory problem.]
> On 2020-May-7, at 00:46, Mark Millard wrote:
>
> [__je_sz_size2index_tab seems messed up in 2 of the
> asserting contexts: first 384 are zero in both. More
> before that is also messed up (all zer
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2020-05-03
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2020-04-27 to 2020-05-03.
During this period, we have:
* 2099 buil
On Thu, May 7, 2020 at 10:38 AM Eric van Gyzen wrote:
> If I were to clean up obsolete ${COMPILER_VERSION} tests in the tree,
> which ones should I keep? I would probably confine it to head, so I
> could prune quite a few.
>
Anything in the bootstrap path should remain, especially in the instal
On Thu, May 7, 2020 at 10:35 AM Rodney W. Grimes <
freebsd-...@gndrsh.dnsmgr.net> wrote:
> > Hello everyone,
> >
> > I can't find any proper rationale in our history (maybe I missed it)
> which
> > explains why our ncurses is stuck on using termcap(5) instead of
> terminfo(5)
> > Except an argumen
If I were to clean up obsolete ${COMPILER_VERSION} tests in the tree,
which ones should I keep? I would probably confine it to head, so I
could prune quite a few.
Eric
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/lis
> Hello everyone,
>
> I can't find any proper rationale in our history (maybe I missed it) which
> explains why our ncurses is stuck on using termcap(5) instead of terminfo(5)
> Except an argument in the Makefile that builds ncurses:
> "Used instead of the hideous read_termcap.c abomination."
>
>
On Thu, May 07, 2020 at 03:22:20PM +0200, Mateusz Piotrowski wrote:
> Hi,
>
> On 5/7/20 2:41 PM, Baptiste Daroussin wrote:
> > Hello everyone,
> >
> > I can't find any proper rationale in our history (maybe I missed it) which
> > explains why our ncurses is stuck on using termcap(5) instead of te
Hi,
On 5/7/20 2:41 PM, Baptiste Daroussin wrote:
Hello everyone,
I can't find any proper rationale in our history (maybe I missed it) which
explains why our ncurses is stuck on using termcap(5) instead of terminfo(5)
Except an argument in the Makefile that builds ncurses:
"Used instead of the h
Just my one cent.
Baptiste Daroussin wrote in
<20200507124126.g4z5op4cyv45p...@ivaldir.net>:
|I can't find any proper rationale in our history (maybe I missed it) which
|explains why our ncurses is stuck on using termcap(5) instead of terminf\
|o(5)
...
|I would like to make the move from ter
Hello everyone,
I can't find any proper rationale in our history (maybe I missed it) which
explains why our ncurses is stuck on using termcap(5) instead of terminfo(5)
Except an argument in the Makefile that builds ncurses:
"Used instead of the hideous read_termcap.c abomination."
Which I do not
[__je_sz_size2index_tab seems messed up in 2 of the
asserting contexts: first 384 are zero in both. More
before that is also messed up (all zero). I show the
details later below.]
On 2020-May-6, at 16:57, Mark Millard wrote:
> [This explores process crashes that happen during system
> shutdown,
13 matches
Mail list logo
