macOS 10.15.7
nmh version : 1.7+dev
host os : x86_64-apple-darwin19.6.0
compiler : cc
compiler flags : -g -O2 -Wall -Wextra
linker flags : -Qunused-arguments
-L/usr/local/Cellar/openssl@3/3.0.3/lib
preprocessor flags : -I/usr/local/Cellar/openssl@3/3.0.3/include
cc =
Apple clang version 12.0.0 (clang-1200.0.32.29)
Target: x86_64-apple-darwin19.6.0
1 of 117 tests failed
(1 test was not run) -- valgrind test not run
Failed test was mhfixmsg
*** /Users/foo/Src/nmh/test/testdir/test-mhfixmsg58801.expected 2022-05-04
02:22:53.000000000 +0000
--- /Users/foo/Src/nmh/test/testdir/test-mhfixmsg58801.actual 2022-05-04
02:22:53.000000000 +0000
***************
*** 4,12 ****
--mime-boundary
Content-Type: text/plain; charset="utf-8"
! Content-Transfer-Encoding: 8bit
! νμχ
--mime-boundary
Content-Transfer-Encoding: 7bit
--- 4,12 ----
--mime-boundary
Content-Type: text/plain; charset="utf-8"
! Content-Transfer-Encoding: 7bit
! nmx
--mime-boundary
Content-Transfer-Encoding: 7bit
./test/mhfixmsg/test-mhfixmsg: test failed, outputs are in
/Users/foo/Src/nmh/test/testdir/test-mhfixmsg58801.expected and
/Users/foo/Src/nmh/test/testdir/test-mhfixmsg58801.actual.
first named test failure: use correct encoding for new text/plain part
FAIL: test/mhfixmsg/test-mhfixmsg
It's using elinks:
ELinks 0.11.7 (built on Oct 14 2019 00:45:54)
Features:
Standard, IPv6, gzip, bzip2, Periodic Saving, Timer, Cascading Style Sheets,
Protocol (File, FTP, HTTP, URI rewrite, User protocols), SSL (OpenSSL),
MIME (Option system, Mailcap, Mimetypes files), LED indicators, Bookmarks,
Cookies, Form History, Global History, Goto URL History, Search History
Switching to lynx passes the check:
Lynx Version 2.8.9rel.1 (08 Jul 2018)
libwww-FM 2.14, SSL-MM 1.4.1, OpenSSL 1.1.1n, ncurses 5.7.20081102
Built on darwin19.6.0 (Mar 4 2022 02:54:49).
Same thing happens on macOS 12.3.1 with Apple clang 13.1.6 on
arm64-apple-darwin21.4.0 (i.e. lynx works, elinks breaks).
On Tue, Apr 19, 2022 at 10:19 PM David Levine <levinedl@acm.org> wrote:
Ken wrote:
I'd like to clean up file descriptor handling (basically, set
close-on-exec
for most everything unless it is necessary).
Sounds good and low risk.
In the meantime, if those who build from the repo could pull and
report the results of "make check", that will help reveal areas
that we need to address. Platforms such as the BSDs and Debian
are blind spots for me.
David
--
Email: david.w.h.chin@gmail.com
Mobile: 734.709.9119
https://linuxfollies.blogspot.com/ https://github.com/prehensilecode