I put the source back where "apl --show_src_dir" expects it. I am getting:
pstat.c: In function ‘get_pstat’: pstat.c:187:3: error: ignoring return value of ‘asprintf’, declared with attribute warn_unused_result [-Werror=unused-result] asprintf(&path, "/proc/%d/stat", pid); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ pstat.c:205:3: error: ignoring return value of ‘asprintf’, declared with attribute warn_unused_result [-Werror=unused-result] asprintf(&path, "/proc/%d/stat", pid); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ cc1: all warnings being treated as errors As with GNUAPL, because of the combination of their overzealous warnings and your insistence on no warnings, it doesn't build. I suppose I'll have to use a special command to build your system as I have to build GNUAPL. For GNUAPL, I use: CXXFLAGS="-Wno-maybe-uninitialized -Wno-class-memaccess" ./configure The same trick doesn't seem to be working with aplwrap. Thanks. Blake On Sun, Jun 28, 2020 at 1:53 PM Chris Moller <mol...@mollerware.com> wrote: > aplwrap needs to have the GNU APL source around to get stuff out of > Avec.hh. Normally, it gets the location of that directory by running > > apl --show_src_dir > > and if that doesn't work for whatever reason, it can't build. A long time > ago, I had a ./configure option "--with-apl-source-dir" to manually set > that, but the option seems to have vanished. I'll stick it back in, but a > quick work-around would be to manually set the path at line 7 of ./ > configure.ac > > On 2020-06-28 14:31, Blake McBride wrote: > > $ ./autogen.sh > autoreconf: Entering directory `.' > autoreconf: configure.ac: not using Gettext > autoreconf: running: aclocal --force > autoreconf: configure.ac: tracing > autoreconf: configure.ac: not using Libtool > autoreconf: running: /usr/bin/autoconf --force > autoreconf: running: /usr/bin/autoheader --force > autoreconf: running: automake --add-missing --copy --force-missing > autoreconf: Leaving directory `.' > $ ./configure > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... /bin/mkdir -p > checking for gawk... gawk > checking whether make sets $(MAKE)... yes > checking whether make supports nested variables... yes > checking for gcc... gcc > checking whether the C compiler works... yes > checking for C compiler default output file name... a.out > checking for suffix of executables... > checking whether we are cross compiling... no > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ISO C89... none needed > checking whether gcc understands -c and -o together... yes > checking for style of include used by make... GNU > checking dependency style of gcc... gcc3 > checking whether to enable maintainer-specific portions of Makefiles... yes > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for GTK... yes > checking that generated files are newer than configure... done > configure: creating ./config.status > config.status: creating Makefile > config.status: creating src/Makefile > config.status: creating config.h > config.status: config.h is unchanged > config.status: executing depfiles commands > $ make > make all-recursive > make[1]: Entering directory '/home/blake/Backup/aplwrap.git' > Making all in src > make[2]: Entering directory '/home/blake/Backup/aplwrap.git/src' > ./buildinfo > build.h-new > diff build.h build.h-new 2>/dev/null || mv build.h-new build.h > rm -f build.h-new > make all-am > make[3]: Entering directory '/home/blake/Backup/aplwrap.git/src' > gcc -DHAVE_CONFIG_H -I. -I.. > -DMANUALS_PATH=\"/usr/local/share/doc/aplwrap\" -std=c99 -Wall -Werror > -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 > -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 > -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 > -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 > -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 > -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 > -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/home/blake/Backup/apl/src -g -O2 -MT aplwrap-aplwrap.o -MD -MP -MF > .deps/aplwrap-aplwrap.Tpo -c -o aplwrap-aplwrap.o `test -f 'aplwrap.c' || > echo './'`aplwrap.c > In file included from aplwrap.c:11:0: > Avec.h:32:10: fatal error: Avec.def: No such file or directory > #include <Avec.def> > ^~~~~~~~~~ > compilation terminated. > Makefile:396: recipe for target 'aplwrap-aplwrap.o' failed > make[3]: *** [aplwrap-aplwrap.o] Error 1 > make[3]: Leaving directory '/home/blake/Backup/aplwrap.git/src' > Makefile:281: recipe for target 'all' failed > make[2]: *** [all] Error 2 > make[2]: Leaving directory '/home/blake/Backup/aplwrap.git/src' > Makefile:434: recipe for target 'all-recursive' failed > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory '/home/blake/Backup/aplwrap.git' > Makefile:333: recipe for target 'all' failed > make: *** [all] Error 2 > > On Sun, Jun 28, 2020 at 1:20 PM Chris Moller <mol...@mollerware.com> > wrote: > >> Try running >> >> ./autogen.sh >> >> from the top level aplwrap directory and then re-run >> >> ./configure >> >> Most likely, you have a different version of automake installed and >> running autogen.sh will rebuild the ./configure file to match your system. >> >> HTH, >> >> Chris >> >> On 2020-06-28 13:36, Blake McBride wrote: >> >> Hi Chris, >> >> I'd like to try aplwrap on my LinuxMint 19.3 system but I get: >> >> $ ./configure >> checking for a BSD-compatible install... /usr/bin/install -c >> checking whether build environment is sane... yes >> checking for a thread-safe mkdir -p... /bin/mkdir -p >> checking for gawk... gawk >> checking whether make sets $(MAKE)... yes >> checking whether make supports nested variables... yes >> checking for gcc... gcc >> checking whether the C compiler works... yes >> checking for C compiler default output file name... a.out >> checking for suffix of executables... >> checking whether we are cross compiling... no >> checking for suffix of object files... o >> checking whether we are using the GNU C compiler... yes >> checking whether gcc accepts -g... yes >> checking for gcc option to accept ISO C89... none needed >> checking whether gcc understands -c and -o together... yes >> checking whether make supports the include directive... yes (GNU style) >> checking dependency style of gcc... gcc3 >> checking whether to enable maintainer-specific portions of Makefiles... >> yes >> checking for pkg-config... /usr/bin/pkg-config >> checking pkg-config is at least version 0.9.0... yes >> checking for GTK... yes >> checking that generated files are newer than configure... done >> configure: creating ./config.status >> config.status: creating Makefile >> config.status: creating src/Makefile >> config.status: creating config.h >> config.status: config.h is unchanged >> config.status: executing depfiles commands >> $ make >> cd . && /bin/bash /home/blake/Backup/aplwrap.git/missing automake-1.16 >> --foreign >> /home/blake/Backup/aplwrap.git/missing: line 81: automake-1.16: command >> not found >> WARNING: 'automake-1.16' is missing on your system. >> You should only need it if you modified 'Makefile.am' or >> 'configure.ac' or m4 files included by 'configure.ac'. >> The 'automake' program is part of the GNU Automake package: >> <https://www.gnu.org/software/automake> >> It also requires GNU Autoconf, GNU m4 and Perl in order to run: >> <https://www.gnu.org/software/autoconf> >> <https://www.gnu.org/software/m4/> >> <https://www.perl.org/> >> Makefile:338: recipe for target 'Makefile.in' failed >> make: *** [Makefile.in] Error 1 >> >> >> I didn't modify any files - and I have automake 1.15.1 installed (what >> comes with this version of the OS). >> >> Thanks! >> >> Blake McBride >> >> >> On Sun, Jun 28, 2020 at 10:03 AM Chris Moller <mol...@mollerware.com> >> wrote: >> >>> I haven't any if idea if anyone is still using the aplwrap thing David >>> Lamkins and I hacked together a few years ago, but I just updated it, which >>> mostly consisted of replacing a couple of GTK+/glib things that had been >>> deprecated. You can also set the foreground and background colours now, >>> in case you want your screen(s) to be more attention-getting. >>> >>> Anyway: https://github.com/ChrisMoller/aplwrap >>> >>> Chris Moller >>> >> >> >
