Back to ast-ksh. I am not clear if there is sufficient interest in this among NetBSD users (or for other pkgsrc users, for that matter). I used to use it a lot under OpenSolaris over the years and was updating and building it under -current whenever it came to me. Last succesful build was about the and of April thus year. I pulled the updates from the git repo today and got a bunch of errors: ...... ../src/lib/libast/comp/conftab.c:74:6: error: '_SC_ADVISORY_INFO' undeclared here (not in a function) ../src/lib/libast/comp/conftab.c:98:6: error: '_SC_AIO_PRIO_DELTA_MAX' undeclared here (not in a function); did you mean '_SC_AIO_LISTIO_MAX'? ../src/lib/libast/comp/conftab.c:106:6: error: '_PC_ALLOC_SIZE_MIN' undeclared here (not in a function); did you mean '_PC_FILESIZEBITS'? ../src/lib/libast/comp/conftab.c:131:6: error: '_PC_ASYNC_IO' undeclared here (not in a function); did you mean '_PC_SYNC_IO'? ../src/lib/libast/comp/conftab.c:284:6: error: '_SC_XOPEN_CRYPT' undeclared here (not in a function); did you mean '_SC_XOPEN_SHM'? ../src/lib/libast/comp/conftab.c:332:6: error: '_SC_XOPEN_ENH_I18N' undeclared here (not in a function); did you mean '_SC_XOPEN_SHM'? ../src/lib/libast/comp/conftab.c:459:6: error: '_SC_IPV6' undeclared here (not in a function); did you mean '_UC_CPU'? ../src/lib/libast/comp/conftab.c:975:6: error: '_SC_PRIORITIZED_IO' undeclared here (not in a function); did you mean '_POSIX_PRIORITIZED_IO'? ../src/lib/libast/comp/conftab.c:991:6: error: '_PC_PRIO_IO' undeclared here (not in a function); did you mean '_PC_SYNC_IO'? ../src/lib/libast/comp/conftab.c:1055:6: error: '_SC_RAW_SOCKETS' undeclared here (not in a function); did you mean '_POSIX_RAW_SOCKETS'? ...... and more. The commit https://github.com/att/ast/commit/63e9edcb6084d4b164439065e2d71f3e900ec3c7 apparently now uses static conftab.c, which refers to a number of symbols missing from sysconf(3) and pathconf(2). I needed the attached patch to complete the build under -current. Following that, the tests mostly run: .... 125/278 arith FAIL 1.32 s (exit status 134 or signal 6 SIGABRT) 126/278 arith/shcomp FAIL 1.32 s (exit status 134 or signal 6 SIGABRT) 131/278 attributes FAIL 0.10 s (exit status 134 or signal 6 SIGABRT) 132/278 attributes/shcomp FAIL 0.13 s (exit status 134 or signal 6 SIGABRT) 169/278 functions FAIL 0.23 s (exit status 134 or signal 6 SIGABRT) 170/278 functions/shcomp FAIL 0.75 s (exit status 134 or signal 6 SIGABRT) 250/278 types FAIL 3.28 s (exit status 134 or signal 6 SIGABRT) 251/278 types/shcomp FAIL 3.29 s (exit status 134 or signal 6 SIGABRT) 252/278 ulimit FAIL 0.14 s (exit status 6) 253/278 ulimit/shcomp FAIL 0.16 s (exit status 5) 254/278 variables FAIL 11.30 s (exit status 1) 277/278 special-dev-paths FAIL 0.48 s (exit status 2) 278/278 special-dev-paths/shcomp FAIL 0.50 s (exit status 2) FAIL: 17 ..... so I guess it is usable. On Mon, 3 Sep 2018 at 16:42, Chavdar Ivanov <ci4ic4%gmail.com@localhost> wrote: > > Perhaps it’s better to be under heavy development and compiling and working, than stable and not compiling at all... > > On Mon, 3 Sep 2018 at 07:28, Andreas Kusalananda Kähäri <andreas.kahari%icm.uu.se@localhost> wrote: >> >> On Sun, Sep 02, 2018 at 11:43:48AM +0100, Chavdar Ivanov wrote: >> > I just noticed I have a successful build from pkgsrc last year: >> > --- >> > ls -l /usr/pkg/bin/ksh93 && file /usr/pkg/bin/ksh93 >> > 18-09-02 - 11:33:37 >> > -rwxr-xr-x 1 root wheel 1501856 Jun 17 2017 /usr/pkg/bin/ksh93 >> > /usr/pkg/bin/ksh93: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), >> > dynamically linked, interpreter /usr/libexec/ld.elf_so, for NetBSD 8.99.1, >> > stripped >> > .... >> > Anyway, I *think* it would be better to get the git version. I notice the >> > required build tools are already in, albeit a bit behind (py-meson and >> > ninja-build). >> > >> > >> > * ( 'think' being just an operative term ). >> >> Note that the GitHub master branch of the shell is under *heavy* >> development at the moment. >> >> >> -- >> Andreas Kusalananda Kähäri, >> National Bioinformatics Infrastructure Sweden (NBIS), >> Uppsala University, Sweden. >> >> >> >> >> >> >> >> >> När du har kontakt med oss på Uppsala universitet med e-post så innebär det att vi behandlar dina personuppgifter. För att läsa mer om hur vi gör det kan du läsa här: http://www.uu.se/om-uu/dataskydd-personuppgifter/ >> >> E-mailing Uppsala University means that we will process your personal data. For more information on how this is performed, please read here: http://www.uu.se/om-uu/dataskydd-personuppgifter/ > > -- > ---- -- ----
Attachment:
conftab-c.patch
Description: Binary data