From jonathanbusby at gmail.com Sun Jan 6 19:05:08 2019 From: jonathanbusby at gmail.com (Jonathan Busby) Date: Sun, 6 Jan 2019 12:05:08 -0600 Subject: [RPL/2] Build of 4.1.29 fails on Linux Mint 19 Cinnamon 64-bit Message-ID: Hello. I'm running a Linux Mint 19 Cinnamon 64-bit install with the output of "lsb_release -a" being : " Distributor ID: LinuxMint Description: Linux Mint 19 Tara Release: 19 Codename: tara " With the default configure options, the make operation fails with : " Makefile:494: recipe for target 'wmluiltok' failed " Here is a link to the full make log : http://www.mediafire.com/file/rwrazsdxjj9hgm9/make.log.tar.bz2/file Any help would be appreciated. Thanks, Jonathan -------------- next part -------------- An HTML attachment was scrubbed... URL: From joel.bertrand at systella.fr Mon Jan 7 07:06:51 2019 From: joel.bertrand at systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) Date: Mon, 7 Jan 2019 07:06:51 +0100 Subject: [RPL/2] Build of 4.1.29 fails on Linux Mint 19 Cinnamon 64-bit In-Reply-To: References: Message-ID: Jonathan Busby a ?crit?: > Hello. I'm running a Linux Mint 19 Cinnamon 64-bit install with the > output of "lsb_release -a" being : > > " > Distributor ID:??? LinuxMint > Description:??? Linux Mint 19 Tara > Release:??? 19 > Codename:??? tara > " > > With the default configure options, the make operation fails with : > > " > Makefile:494: recipe for target 'wmluiltok' failed > " > Here is a link to the full make log? : > http://www.mediafire.com/file/rwrazsdxjj9hgm9/make.log.tar.bz2/file > > Any help would be?appreciated. > Hello, I have no time in the next couple of days to have a look in your log file. If I remember, I have seen this kind of bug a long time ago. I'll come back, I hope, before end of week. Best regards, JKB From joel.bertrand at systella.fr Tue Jan 8 11:12:11 2019 From: joel.bertrand at systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) Date: Tue, 8 Jan 2019 11:12:11 +0100 Subject: [RPL/2] Build of 4.1.29 fails on Linux Mint 19 Cinnamon 64-bit In-Reply-To: References: Message-ID: <47bea3bb-519e-db5f-dbda-443d1a36f9fa@systella.fr> Jonathan Busby a ?crit?: > Hello. I'm running a Linux Mint 19 Cinnamon 64-bit install with the > output of "lsb_release -a" being : > > " > Distributor ID:??? LinuxMint > Description:??? Linux Mint 19 Tara > Release:??? 19 > Codename:??? tara > " > > With the default configure options, the make operation fails with : > > " > Makefile:494: recipe for target 'wmluiltok' failed > " > Here is a link to the full make log? : > http://www.mediafire.com/file/rwrazsdxjj9hgm9/make.log.tar.bz2/file OK... wmluiltok should be built by motif's Makefile. Can you enter in $(builddir)/tools/motifs-2.3.8/tools/wml and run make > make.log ? Best regards, JKB From jonathanbusby at gmail.com Tue Jan 8 19:08:56 2019 From: jonathanbusby at gmail.com (Jonathan Busby) Date: Tue, 8 Jan 2019 12:08:56 -0600 Subject: [RPL/2] Build of 4.1.29 fails on Linux Mint 19 Cinnamon 64-bit In-Reply-To: <47bea3bb-519e-db5f-dbda-443d1a36f9fa@systella.fr> References: <47bea3bb-519e-db5f-dbda-443d1a36f9fa@systella.fr> Message-ID: On Tue, Jan 8, 2019 at 4:12 AM BERTRAND Jo?l wrote: > Jonathan Busby a ?crit : > > Hello. I'm running a Linux Mint 19 Cinnamon 64-bit install with the > > output of "lsb_release -a" being : > > > > " > > Distributor ID: LinuxMint > > Description: Linux Mint 19 Tara > > Release: 19 > > Codename: tara > > " > > > > With the default configure options, the make operation fails with : > > > > " > > Makefile:494: recipe for target 'wmluiltok' failed > > " > > Here is a link to the full make log : > > http://www.mediafire.com/file/rwrazsdxjj9hgm9/make.log.tar.bz2/file > > OK... wmluiltok should be built by motif's Makefile. Can you enter > in > $(builddir)/tools/motifs-2.3.8/tools/wml and run make > make.log ? > > No problem :) ( see attachment ) Best regards, > > JKB > > Thank you for your help :) Jonathan > _______________________________________________ > RPL2 mailing list > RPL2 at rayleigh.systella.fr > https://www.systella.fr/cgi-bin/mailman/listinfo/rpl2 > http://www.rpl2.net > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: make.log.tar.bz2 Type: application/x-bzip Size: 1938 bytes Desc: not available URL: From jonathanbusby at gmail.com Tue Jan 8 19:22:53 2019 From: jonathanbusby at gmail.com (Jonathan Busby) Date: Tue, 8 Jan 2019 12:22:53 -0600 Subject: [RPL/2] Build of 4.1.29 fails on Linux Mint 19 Cinnamon 64-bit In-Reply-To: References: <47bea3bb-519e-db5f-dbda-443d1a36f9fa@systella.fr> Message-ID: On Tue, Jan 8, 2019 at 12:08 PM Jonathan Busby wrote: > > > On Tue, Jan 8, 2019 at 4:12 AM BERTRAND Jo?l > wrote: > >> Jonathan Busby a ?crit : >> > Hello. I'm running a Linux Mint 19 Cinnamon 64-bit install with the >> > output of "lsb_release -a" being : >> > >> > " >> > Distributor ID: LinuxMint >> > Description: Linux Mint 19 Tara >> > Release: 19 >> > Codename: tara >> > " >> > >> > With the default configure options, the make operation fails with : >> > >> > " >> > Makefile:494: recipe for target 'wmluiltok' failed >> > " >> > Here is a link to the full make log : >> > http://www.mediafire.com/file/rwrazsdxjj9hgm9/make.log.tar.bz2/file >> >> OK... wmluiltok should be built by motif's Makefile. Can you >> enter in >> $(builddir)/tools/motifs-2.3.8/tools/wml and run make > make.log ? >> >> > No problem :) ( see attachment ) > > Best regards, >> >> JKB >> >> > Thank you for your help :) > > Jonathan > > Oops -- I forgot to also include the make debug log ( ie. "make -d" ). Please see the attached file. Thanks, Jonathan > _______________________________________________ >> RPL2 mailing list >> RPL2 at rayleigh.systella.fr >> https://www.systella.fr/cgi-bin/mailman/listinfo/rpl2 >> http://www.rpl2.net >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: make-debug.log.tar.bz2 Type: application/x-bzip Size: 22289 bytes Desc: not available URL: From joel.bertrand at systella.fr Wed Jan 9 09:20:56 2019 From: joel.bertrand at systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) Date: Wed, 9 Jan 2019 09:20:56 +0100 Subject: [RPL/2] Build of 4.1.29 fails on Linux Mint 19 Cinnamon 64-bit In-Reply-To: References: <47bea3bb-519e-db5f-dbda-443d1a36f9fa@systella.fr> Message-ID: <48ef329e-b1b1-5049-c038-dce63b743610@systella.fr> Jonathan Busby a ?crit?: > > > On Tue, Jan 8, 2019 at 4:12 AM BERTRAND Jo?l > wrote: > > Jonathan Busby a ?crit?: > > Hello. I'm running a Linux Mint 19 Cinnamon 64-bit install with the > > output of "lsb_release -a" being : > > > > " > > Distributor ID:??? LinuxMint > > Description:??? Linux Mint 19 Tara > > Release:??? 19 > > Codename:??? tara > > " > > > > With the default configure options, the make operation fails with : > > > > " > > Makefile:494: recipe for target 'wmluiltok' failed > > " > > Here is a link to the full make log? : > > http://www.mediafire.com/file/rwrazsdxjj9hgm9/make.log.tar.bz2/file > > ? ? ? ? OK... wmluiltok should be built by motif's Makefile. Can > you enter in > $(builddir)/tools/motifs-2.3.8/tools/wml and run make > make.log ? > > > No problem :) ( see attachment ) > > ? ? ? ? Best regards, > > ? ? ? ? JKB > > > Thank you for your help :) Please not send output of make -d. This is not a makefile's bug but a trouble with your system. In make output, I see : libtool: link: gcc -g -O2 -O2 -fno-strict-overflow -malign-double -Wall -funsigned-char -Wno-pointer-sign -Wall -g -fno-strict-aliasing -Wno-unused -Wno-comment -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -pthread -o wmluiltok wmluiltok.o -lfontconfig /usr/lib/x86_64-linux-gnu/libfreetype.so -lXft -lpng -pthread /usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/Scrt1.o: In function `_start': (.text+0x20): undefined reference to `main' collect2: error: ld returned 1 exit status Makefile:494: recipe for target 'wmluiltok' failed make: *** [wmluiltok] Error 1 wmluiltok.o was compiled by following command : gcc -DHAVE_CONFIG_H -I. -I../../include -I../../lib/Xm -I../../lib -I./../../lib -I./../../include -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -g -O2 -O2 -fno-strict-overflow -malign-double -Wall -funsigned-char -Wno-pointer-sign -Wall -g -fno-strict-aliasing -Wno-unused -Wno-comment -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -MT wmluiltok.o -MD -MP -MF .deps/wmluiltok.Tpo -c -o wmluiltok.o wmluiltok.c Can you check that wmluiltok.c is not empty ? wmluiltok.c is created by flex. I have found that flex is faulty on several Linux system. If wmluiltok.c is not empty, you have to rebuild flex with -ffat-lto-objects option, allowing to use lto also on motif. Best regards, JKB From jonathanbusby at gmail.com Thu Jan 10 00:32:47 2019 From: jonathanbusby at gmail.com (Jonathan Busby) Date: Wed, 9 Jan 2019 17:32:47 -0600 Subject: [RPL/2] Fwd: Build of 4.1.29 fails on Linux Mint 19 Cinnamon 64-bit In-Reply-To: References: <47bea3bb-519e-db5f-dbda-443d1a36f9fa@systella.fr> <48ef329e-b1b1-5049-c038-dce63b743610@systella.fr> Message-ID: Seems my last reply was too large. Sorry about that. ---------- Forwarded message --------- From: Jonathan Busby Date: Wed, Jan 9, 2019 at 3:07 PM Subject: Re: [RPL/2] Build of 4.1.29 fails on Linux Mint 19 Cinnamon 64-bit To: RPL/2 mailing list On Wed, Jan 9, 2019 at 2:22 AM BERTRAND Jo?l wrote: > > > Please not send output of make -d. This is not a makefile's bug > but a > trouble with your system. > Well, if it's a problem with my system, then it's a problem with all the latest versions of Linux Mint 19 Cinnamon 64-bit. I've tested the code on another Linux Mint install and I get the same error. > > Can you check that wmluiltok.c is not empty ? wmluiltok.c is > created by > flex. > wmluiltok.c is not empty and contains a proper Flex scanner. > I have found that flex is faulty on several Linux system. If > wmluiltok.c is not empty, you have to rebuild flex with > -ffat-lto-objects option, allowing to use lto also on motif. > I guess I'll have to do what you suggest above. Just to make sure I understand, I need to build the latest version of Flex from the source and make sure to include the "-ffat-lto-objects" option to GCC? When you say "allowing to use lto also on motif" what do you mean exactly? Do I have to compile Motif from the sources in the archive and supply the same option to GCC as you suggested above? EDIT : After I typed the above, I compiled GNU Flex with the -ffat-lto-objects by modifying its configure.ac to get it to supply the option to GCC and then I tried compiling the Motif source that comes packaged with RPL/2 ( I also had to modify configure.ac ). Although your suggestions seem to have cleared up the previous problem with wmluiltok.c, I now get a new error : http://www.mediafire.com/file/v7wwlc8tuen6bt2/make-log-error-paste-1.asc/file I resolved the above just by issuing an "apt update && apt install libfl2" command and rebuilding the source. EDIT 2 : Well, this time all the X Windows and Motif related code built fine, but then the build failed with a new error : http://www.mediafire.com/file/hhx46jxfh3l39je/make-log-error-2.asc/file It looks like the main RPL/2 configure script is not calling the zlib configure script. When I manually corrected that, I got a new error when trying to compile zlib : " cc -shared -march=core2 -O2 -pipe -ffat-lto-objects -D_LARGEFILE64_SOURCE=1 -o libz.so.1.2.11 adler32.lo crc32.lo deflate.lo infback.lo inffast.lo inflate.lo inftrees.lo trees.lo zutil.lo compress.lo uncompr.lo gzclose.lo gzlib.lo gzread.lo gzwrite.lo -lc /usr/bin/ld: deflate.lo: relocation R_X86_64_PC32 against symbol `_length_code' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: Bad value collect2: error: ld returned 1 exit status Makefile:282: recipe for target 'libz.so.1.2.11' failed make: *** [libz.so.1.2.11] Error 1 " I added "-fPIC" via the usual environment variables but that didn't fix the build failure. I next modified the zlib Makefile.in and that fixed the problem. Then I restarted the RPL/2 build and it finally built! :D After running "sudo checkinstall" and installing the package I was able to "run" "rpl -i" but it exited with the error : "mint at mint:~$ rpl -i +++RPL/2 (R) version 4.1.29 (Wednesday 01/09/19, 14:41:11 CST) +++Copyright (C) 1989 to 2017, 2018 BERTRAND Joel +++This is a free software with absolutely no warranty. +++For details, type 'warranty'. +++Fatal : Hash code mismatch Function md5(/usr/local/bin/rpliconv) Computed hash code : 10a03ae9906b128e4e0acd855f3856f4 Expected hash code : 9a1e8ca96b5eab8831a59d31f11de7f8 +++Fatal : Error in compilation" I then removed the Debian package and I used the old school "sudo make install" and guess what, it now works! :D "mint at mint:~$ rpl -i +++RPL/2 (R) version 4.1.29 (Wednesday 01/09/19, 14:58:27 CST) +++Copyright (C) 1989 to 2017, 2018 BERTRAND Joel +++This is a free software with absolutely no warranty. +++For details, type 'warranty'. RPL/2> 1 1: 1 RPL/2> dup 2: 1 1: 1 RPL/2> + 1: 2 RPL/2> " :) Thanks and regards, Jonathan -------------- next part -------------- An HTML attachment was scrubbed... URL: From joel.bertrand at systella.fr Thu Jan 10 10:03:04 2019 From: joel.bertrand at systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) Date: Thu, 10 Jan 2019 10:03:04 +0100 Subject: [RPL/2] Fwd: Build of 4.1.29 fails on Linux Mint 19 Cinnamon 64-bit In-Reply-To: References: <47bea3bb-519e-db5f-dbda-443d1a36f9fa@systella.fr> <48ef329e-b1b1-5049-c038-dce63b743610@systella.fr> Message-ID: <73231aeb-3c32-4eb6-d27f-e6b14f68c3d8@systella.fr> Jonathan Busby a ?crit?: > Seems my last reply was too large. Sorry about that. > > ---------- Forwarded message --------- > From: *Jonathan Busby* > > Date: Wed, Jan 9, 2019 at 3:07 PM > Subject: Re: [RPL/2] Build of 4.1.29 fails on Linux Mint 19 Cinnamon 64-bit > To: RPL/2 mailing list > > > > > > On Wed, Jan 9, 2019 at 2:22 AM BERTRAND Jo?l > wrote: > > > > ? ? ? ? Please not send output of make -d. This is not a makefile's > bug but a > trouble with your system. > > > Well, if it's a problem with my system, then it's a problem with all the > latest versions of Linux Mint 19 Cinnamon 64-bit. I've tested the code > on another Linux Mint install and I get the same error. > > > ? ? ? ? Can you check that wmluiltok.c is not empty ? wmluiltok.c > is created by > flex. > > > wmluiltok.c is not empty and contains a proper Flex scanner. > > ? ? ? ? I have found that flex is faulty on several Linux system. If > wmluiltok.c is not empty, you have to rebuild flex with > -ffat-lto-objects option, allowing to use lto also on motif. > > > I guess I'll have to do what you suggest above. Just to make sure I > understand, I need to build the latest version of Flex from the source > and make sure to include the "-ffat-lto-objects" option to GCC? When you > say "allowing to use lto also on motif" what do you mean exactly? Do I > have to compile Motif from the sources in the archive and supply the > same option to GCC as you suggested above? I'm not a specialist of gcc options. LTO is 'link time optimizer' and I have seen there are some bugs in link stage when you try to link LTO with no LTO objects. > EDIT : After I typed the above, I compiled GNU Flex with the > -ffat-lto-objects by modifying its configure.ac to > get it to supply the option to GCC and then I tried compiling the Motif > source that comes packaged with RPL/2 ( I also had to modify > configure.ac ). Although your suggestions seem to > have cleared up the previous problem with wmluiltok.c, I now get a new > error : > > http://www.mediafire.com/file/v7wwlc8tuen6bt2/make-log-error-paste-1.asc/file > > I resolved the above just by issuing an "apt update && apt install > libfl2" command and rebuilding the source. > > EDIT 2 : Well, this time all the X Windows and Motif related code built > fine, but then the build failed with a new error : > > http://www.mediafire.com/file/hhx46jxfh3l39je/make-log-error-2.asc/file > > It looks like the main RPL/2 configure script is not calling the zlib > configure script. When I manually corrected that, I got a new error when > trying to compile zlib : zlib configure script is called by main configure script : if test ! -d tools/$ZLIB; then gunzip -c "$srcdir"/tools/$ZLIB.tar.gz | \ (cd tools && tar -xf - && cd $ZLIB && ./configure --static) fi If you want to clean your build tree, you can run 'make purge'. > " > cc -shared -march=core2 -O2 -pipe -ffat-lto-objects > -D_LARGEFILE64_SOURCE=1 -o libz.so.1.2.11 adler32.lo crc32.lo deflate.lo > infback.lo inffast.lo inflate.lo inftrees.lo trees.lo zutil.lo > compress.lo uncompr.lo gzclose.lo gzlib.lo gzread.lo gzwrite.lo? -lc > /usr/bin/ld: deflate.lo: relocation R_X86_64_PC32 against symbol > `_length_code' can not be used when making a shared object; recompile > with -fPIC > /usr/bin/ld: final link failed: Bad value > collect2: error: ld returned 1 exit status > Makefile:282: recipe for target 'libz.so.1.2.11' failed > make: *** [libz.so.1.2.11] Error 1 > " R_X86_64_PC32 ? 32 (on a 64 bits system) or 64 bits ? > I added "-fPIC" via the usual environment variables but that didn't fix > the build failure. I next modified the zlib Makefile.in and that fixed > the problem. Then I restarted the RPL/2 build and it finally built! :D > After running "sudo checkinstall"? and installing the package I was able > to "run" "rpl -i" but it exited with the error : > > "mint at mint:~$ rpl -i > +++RPL/2 (R) version 4.1.29 (Wednesday 01/09/19, 14:41:11 CST) > +++Copyright (C) 1989 to 2017, 2018 BERTRAND Joel > > +++This is a free software with absolutely no warranty. > +++For details, type 'warranty'. > > +++Fatal : Hash code mismatch > Function md5(/usr/local/bin/rpliconv) > Computed hash code : 10a03ae9906b128e4e0acd855f3856f4 > Expected hash code : 9a1e8ca96b5eab8831a59d31f11de7f8 > +++Fatal : Error in compilation" All external tools are signed (rpliconv, rplawk, rplpp...) and you have to use tools built by makefile. Best regards, JKB From jonathanbusby at gmail.com Mon Jan 14 18:19:24 2019 From: jonathanbusby at gmail.com (Jonathan Busby) Date: Mon, 14 Jan 2019 11:19:24 -0600 Subject: [RPL/2] Autoconf error in finding libm Message-ID: I have been racking my brain over what is causing this problem, but so far, I haven't figured out what the core cause is. When I pass "--enable-rplcas" to configure in 4.1.29 the configure script fails with "configure: error: Can not find libm !" . If I change configure.ac to use "AC_SEARCH_LIBS (exp, m , , AC_MSG_ERROR([Can not find libm !]))" and I comment out the AC_CHECK_LIB line, then the configure script finds libm, but, later in the configure script, when the configure scripts for some of the tools are being executed, I get the same error. After examining the autotools scripts, it seems that there is an error in the call to AC_CHECK_LIB for libm as main is not an exported function of libm, but, substituting something like "exp" still doesn't clear up the problem. Just to make sure that my system configuration wasn't the cause, I made a tiny test configure.ac and ran autoconf : " 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 for exp in -lm... yes configure: creating ./config.status " The test configure.ac is just : " AC_INIT([test],[0.01]) AC_CHECK_LIB(m, exp , , AC_MSG_ERROR([Can not find libm !])) AC_OUTPUT " As you can see it finds libm, but, if I tell it to look for main in libm, it fails. Do you know what the problem might be? Thanks, Jonathan -------------- next part -------------- An HTML attachment was scrubbed... URL: From joel.bertrand at systella.fr Mon Jan 14 18:43:18 2019 From: joel.bertrand at systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) Date: Mon, 14 Jan 2019 18:43:18 +0100 Subject: [RPL/2] Autoconf error in finding libm In-Reply-To: References: Message-ID: <55697e4a-9c7b-a83e-898a-08c8a2dd47a3@systella.fr> Jonathan Busby a ?crit?: > I have been racking my brain over what is causing this problem, but so > far, I haven't figured out what the core cause is. When I pass > "--enable-rplcas" to configure in 4.1.29 the configure script fails with > "configure: error: Can not find libm !" . If I change configure.ac > to use "AC_SEARCH_LIBS (exp, m , , > AC_MSG_ERROR([Can not find libm !]))" and I comment out the AC_CHECK_LIB > line, then the configure script finds libm, but, later in the configure > script, when the configure scripts for some of the tools are being > executed, I get the same error. After? examining the autotools scripts, > it seems that there is an error in the call to AC_CHECK_LIB for libm as > main is not an exported function of libm, but, substituting something > like "exp" still doesn't clear up the problem. Just to make sure that my > system configuration wasn't the cause, I made a tiny test configure.ac > and ran autoconf : > > " > 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 for exp? in -lm... yes > configure: creating ./config.status > " > > The test configure.ac is just : > > " > AC_INIT([test],[0.01]) > AC_CHECK_LIB(m, exp , , AC_MSG_ERROR([Can not find libm !])) > AC_OUTPUT > " > > As you can see it finds libm, but, if I tell it to look for main in > libm, it fails. > > Do you know what the problem might be? No idea. If you want to debug, please re-run unmodified configure.ac (./autogen.sh will rebuild regular configure script) and check error in config.log. Regards, JKB From jonathanbusby at gmail.com Tue Jan 15 22:18:05 2019 From: jonathanbusby at gmail.com (Jonathan Busby) Date: Tue, 15 Jan 2019 15:18:05 -0600 Subject: [RPL/2] Autoconf error in finding libm In-Reply-To: <55697e4a-9c7b-a83e-898a-08c8a2dd47a3@systella.fr> References: <55697e4a-9c7b-a83e-898a-08c8a2dd47a3@systella.fr> Message-ID: On Mon, Jan 14, 2019 at 11:45 AM BERTRAND Jo?l wrote: > > No idea. If you want to debug, please re-run unmodified > configure.ac > (./autogen.sh will rebuild regular configure script) and check error in > config.log. > I deleted the build directory, untared the source again, and ran configure with the "--enable-rplcas" option. I get the same error, which can be found in config.log " configure:7464: checking for main in -lm configure:7483: gcc -o conftest -g -O2 -O2 -fno-strict-overflow -pthread conftest.c -lm -lcurl >&5 /usr/bin/ld: cannot find -lcurl collect2: error: ld returned 1 exit status configure:7483: $? = 1 configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "rpl" | #define PACKAGE_TARNAME "rpl" | #define PACKAGE_VERSION "4.1.29" | #define PACKAGE_STRING "rpl 4.1.29" | #define PACKAGE_BUGREPORT "" | #define PACKAGE_URL "" | #define PACKAGE "rpl" | #define VERSION "4.1.29" | #define HAVE_INLINE 1 | /* end confdefs.h. */ | | | int | main () | { | return main (); | ; | return 0; | } configure:7492: result: no configure:7502: error: Can not find libm ! " The " usr/bin/ld: cannot find -lcurl" is strange since I have curl and libcurl installed. I have a feeling that the failure to link / find libcurl is the problem. EDIT 1 : Indeed, for some reason, the GNU autotools link against libcurl ( in the autoconf generated " gcc -o conftest -g -O2 -O2 -fno-strict-overflow -pthread conftest.c -lm -lcurl >&5 " ) and after I installed the development files for libcurl, the build "succeeded", in a way. After, starting the build again, when the motif source was being built, I received the build error : " Making install in Mrm make[4]: Entering directory '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib/Mrm' make install-am make[5]: Entering directory '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib/Mrm' make[6]: Entering directory '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib/Mrm' /bin/mkdir -p '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/install/lib' /bin/bash ../../libtool --mode=install /usr/bin/install -c libMrm.la '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/install/lib' libtool: error: error: cannot install 'libMrm.la' to a directory not ending in /usr/lib Makefile:435: recipe for target 'install-libLTLIBRARIES' failed make[6]: *** [install-libLTLIBRARIES] Error 1 make[6]: Leaving directory '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib/Mrm' Makefile:656: recipe for target 'install-am' failed make[5]: *** [install-am] Error 2 make[5]: Leaving directory '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib/Mrm' Makefile:650: recipe for target 'install' failed make[4]: *** [install] Error 2 make[4]: Leaving directory '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib/Mrm' Makefile:396: recipe for target 'install-recursive' failed make[3]: *** [install-recursive] Error 1 make[3]: Leaving directory '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib' Makefile:453: recipe for target 'install-recursive' failed make[2]: *** [install-recursive] Error 1 make[2]: Leaving directory '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8' Makefile:1215: recipe for target 'tools/motif-2.3.8/install/lib/libXm.a' failed make[1]: *** [tools/motif-2.3.8/install/lib/libXm.a] Error 2 make[1]: Leaving directory '/home/jdb2/src/rpl2/rpl-4.1.29' Makefile:964: recipe for target 'all' failed make: *** [all] Error 2 " After I typed "make" again, this time the build completed successfully. :) The problem I'm having now is that basic tests are failing. For example, if I untar tests/tests.tar.gz and run "rpl arith.rpl" I get the error : " +++Error : Undefined implicit name [92178] " Also, when I run "rpl --help" I get an error after the license text that reads : " +++Error : Any executable definition " Any thoughts? Thanks, Jonathan > Regards, > > JKB > _______________________________________________ > RPL2 mailing list > RPL2 at rayleigh.systella.fr > https://www.systella.fr/cgi-bin/mailman/listinfo/rpl2 > http://www.rpl2.net > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mamahd at gmail.com Tue Jan 15 22:24:08 2019 From: mamahd at gmail.com (Mamady Toure) Date: Tue, 15 Jan 2019 22:24:08 +0100 Subject: [RPL/2] Autoconf error in finding libm In-Reply-To: References: <55697e4a-9c7b-a83e-898a-08c8a2dd47a3@systella.fr> Message-ID: Hello sir, I am not programming any more Have a good day > On 15 Jan 2019, at 22:18, Jonathan Busby wrote: > > > >> On Mon, Jan 14, 2019 at 11:45 AM BERTRAND Jo?l wrote: >> >> No idea. If you want to debug, please re-run unmodified configure.ac >> (./autogen.sh will rebuild regular configure script) and check error in >> config.log. > > I deleted the build directory, untared the source again, and ran configure with the "--enable-rplcas" option. I get the same error, which can be found in config.log > > " > configure:7464: checking for main in -lm > configure:7483: gcc -o conftest -g -O2 -O2 -fno-strict-overflow -pthread conftest.c -lm -lcurl >&5 > /usr/bin/ld: cannot find -lcurl > collect2: error: ld returned 1 exit status > configure:7483: $? = 1 > configure: failed program was: > | /* confdefs.h */ > | #define PACKAGE_NAME "rpl" > | #define PACKAGE_TARNAME "rpl" > | #define PACKAGE_VERSION "4.1.29" > | #define PACKAGE_STRING "rpl 4.1.29" > | #define PACKAGE_BUGREPORT "" > | #define PACKAGE_URL "" > | #define PACKAGE "rpl" > | #define VERSION "4.1.29" > | #define HAVE_INLINE 1 > | /* end confdefs.h. */ > | > | > | int > | main () > | { > | return main (); > | ; > | return 0; > | } > configure:7492: result: no > configure:7502: error: Can not find libm ! > " > > The " usr/bin/ld: cannot find -lcurl" is strange since I have curl and libcurl installed. I have a feeling that the failure to link / find libcurl is the problem. > > EDIT 1 : Indeed, for some reason, the GNU autotools link against libcurl ( in the autoconf generated " gcc -o conftest -g -O2 -O2 -fno-strict-overflow -pthread conftest.c -lm -lcurl >&5 " ) and after I installed the development files for libcurl, the build "succeeded", in a way. > > After, starting the build again, when the motif source was being built, I received the build error : > > " > Making install in Mrm > make[4]: Entering directory '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib/Mrm' > make install-am > make[5]: Entering directory '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib/Mrm' > make[6]: Entering directory '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib/Mrm' > /bin/mkdir -p '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/install/lib' > /bin/bash ../../libtool --mode=install /usr/bin/install -c libMrm.la '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/install/lib' > libtool: error: error: cannot install 'libMrm.la' to a directory not ending in /usr/lib > Makefile:435: recipe for target 'install-libLTLIBRARIES' failed > make[6]: *** [install-libLTLIBRARIES] Error 1 > make[6]: Leaving directory '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib/Mrm' > Makefile:656: recipe for target 'install-am' failed > make[5]: *** [install-am] Error 2 > make[5]: Leaving directory '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib/Mrm' > Makefile:650: recipe for target 'install' failed > make[4]: *** [install] Error 2 > make[4]: Leaving directory '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib/Mrm' > Makefile:396: recipe for target 'install-recursive' failed > make[3]: *** [install-recursive] Error 1 > make[3]: Leaving directory '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib' > Makefile:453: recipe for target 'install-recursive' failed > make[2]: *** [install-recursive] Error 1 > make[2]: Leaving directory '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8' > Makefile:1215: recipe for target 'tools/motif-2.3.8/install/lib/libXm.a' failed > make[1]: *** [tools/motif-2.3.8/install/lib/libXm.a] Error 2 > make[1]: Leaving directory '/home/jdb2/src/rpl2/rpl-4.1.29' > Makefile:964: recipe for target 'all' failed > make: *** [all] Error 2 > " > > After I typed "make" again, this time the build completed successfully. :) > > The problem I'm having now is that basic tests are failing. For example, if I untar tests/tests.tar.gz and run "rpl arith.rpl" I get the error : > > " > +++Error : Undefined implicit name [92178] > " > > Also, when I run "rpl --help" I get an error after the license text that reads : > > " > +++Error : Any executable definition > " > > Any thoughts? > > Thanks, > > Jonathan > >> >> Regards, >> >> JKB >> _______________________________________________ >> RPL2 mailing list >> RPL2 at rayleigh.systella.fr >> https://www.systella.fr/cgi-bin/mailman/listinfo/rpl2 >> http://www.rpl2.net > _______________________________________________ > RPL2 mailing list > RPL2 at rayleigh.systella.fr > https://www.systella.fr/cgi-bin/mailman/listinfo/rpl2 > http://www.rpl2.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From joel.bertrand at systella.fr Wed Jan 16 07:14:41 2019 From: joel.bertrand at systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) Date: Wed, 16 Jan 2019 07:14:41 +0100 Subject: [RPL/2] Autoconf error in finding libm In-Reply-To: References: <55697e4a-9c7b-a83e-898a-08c8a2dd47a3@systella.fr> Message-ID: Jonathan Busby a ?crit?: > > > On Mon, Jan 14, 2019 at 11:45 AM BERTRAND Jo?l > > wrote: > > > ? ? ? ? No idea. If you want to debug, please re-run unmodified > configure.ac > (./autogen.sh will rebuild regular configure script) and check error in > config.log. > > > I deleted the build directory, untared the source again, and ran > configure with the "--enable-rplcas" option. I get the same error, which > can be found in config.log > > " > configure:7464: checking for main in -lm > configure:7483: gcc -o conftest -g -O2? -O2 -fno-strict-overflow? > -pthread conftest.c -lm? -lcurl >&5 > /usr/bin/ld: cannot find -lcurl > collect2: error: ld returned 1 exit status > configure:7483: $? = 1 > configure: failed program was: > | /* confdefs.h */ > | #define PACKAGE_NAME "rpl" > | #define PACKAGE_TARNAME "rpl" > | #define PACKAGE_VERSION "4.1.29" > | #define PACKAGE_STRING "rpl 4.1.29" > | #define PACKAGE_BUGREPORT "" > | #define PACKAGE_URL "" > | #define PACKAGE "rpl" > | #define VERSION "4.1.29" > | #define HAVE_INLINE 1 > | /* end confdefs.h.? */ > | > | > | int > | main () > | { > | return main (); > |?? ; > |?? return 0; > | } > configure:7492: result: no > configure:7502: error: Can not find libm ! > " > ? > The " usr/bin/ld: cannot find -lcurl" is strange since I have curl and > libcurl installed. I have a feeling that the failure to link / find > libcurl is the problem. Libcurl is mandatory to build RPL/CAS. I could modify configure.ac to check if curl is available on build system. > EDIT 1 : Indeed, for some reason, the GNU autotools link against libcurl > ( in the autoconf generated " gcc -o conftest -g -O2? -O2 > -fno-strict-overflow? -pthread conftest.c -lm? -lcurl >&5 " ) and after > I installed the development files for libcurl, the build "succeeded", in > a way. > > After, starting the build again, when the motif source was being built, > I received the build error : > > " > Making install in Mrm > make[4]: Entering directory > '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib/Mrm' > make? install-am > make[5]: Entering directory > '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib/Mrm' > make[6]: Entering directory > '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib/Mrm' > ?/bin/mkdir -p > '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/install/lib' > ?/bin/bash ../../libtool?? --mode=install /usr/bin/install -c?? > libMrm.la '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/install/lib' > libtool:?? error: error: cannot install 'libMrm.la' to a directory not > ending in /usr/lib > Makefile:435: recipe for target 'install-libLTLIBRARIES' failed > make[6]: *** [install-libLTLIBRARIES] Error 1 > make[6]: Leaving directory > '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib/Mrm' > Makefile:656: recipe for target 'install-am' failed > make[5]: *** [install-am] Error 2 > make[5]: Leaving directory > '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib/Mrm' > Makefile:650: recipe for target 'install' failed > make[4]: *** [install] Error 2 > make[4]: Leaving directory > '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib/Mrm' > Makefile:396: recipe for target 'install-recursive' failed > make[3]: *** [install-recursive] Error 1 > make[3]: Leaving directory > '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib' > Makefile:453: recipe for target 'install-recursive' failed > make[2]: *** [install-recursive] Error 1 > make[2]: Leaving directory > '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8' > Makefile:1215: recipe for target 'tools/motif-2.3.8/install/lib/libXm.a' > failed > make[1]: *** [tools/motif-2.3.8/install/lib/libXm.a] Error 2 > make[1]: Leaving directory '/home/jdb2/src/rpl2/rpl-4.1.29' > Makefile:964: recipe for target 'all' failed > make: *** [all] Error 2 > " > > After I typed "make" again, this time the build completed successfully. :) configure process is very complex as ./tools and ./rplcas directories contain all libraries required for basic RPL/2 (./tools) and RPL/CAS (./rplcas). Some libraries are often available on modern Unix systems but RPL/2 can be built on non Unix systems without these basic libraries (OpenSSL, ncurses...). They don't use autoconf nor automake. Thus, dependencies are not checked by autoconf/automake but only by Makefile's and, in cas of build error, you should run make purge and configure again. > The problem I'm having now is that basic tests are failing. For example, > if I untar tests/tests.tar.gz and run "rpl arith.rpl" I get the error : test directory is only for me ;-) > " > +++Error : Undefined implicit name [92178] > " arith.rpl has to abort with this error. If you want to run arith.rpl, you have to add "all" implicit after first '<<'. But there is a bug, arith.rpl aborts with "access violation" error. I'll fix this bug as soon as possible. > Also, when I run "rpl --help" I get an error after the license text that > reads : > > " > +++Error : Any executable definition > " What do you expect ? If you want to obtain a prompt, you have to start RPL/2 with rpl -i. If not, you should add a script name (or a shebang in script like !#/usr/local/bin/rpl -csp Best regards, JKB From jonathanbusby at gmail.com Wed Jan 16 17:51:48 2019 From: jonathanbusby at gmail.com (Jonathan Busby) Date: Wed, 16 Jan 2019 10:51:48 -0600 Subject: [RPL/2] Autoconf error in finding libm In-Reply-To: References: <55697e4a-9c7b-a83e-898a-08c8a2dd47a3@systella.fr> Message-ID: On Wed, Jan 16, 2019 at 12:15 AM BERTRAND Jo?l wrote: > Jonathan Busby a ?crit : > > > > > > On Mon, Jan 14, 2019 at 11:45 AM BERTRAND Jo?l > > > wrote: > > > > > > No idea. If you want to debug, please re-run unmodified > > configure.ac > > (./autogen.sh will rebuild regular configure script) and check error > in > > config.log. > > > > > > I deleted the build directory, untared the source again, and ran > > configure with the "--enable-rplcas" option. I get the same error, which > > can be found in config.log > > > > " > > configure:7464: checking for main in -lm > > configure:7483: gcc -o conftest -g -O2 -O2 -fno-strict-overflow > > -pthread conftest.c -lm -lcurl >&5 > > /usr/bin/ld: cannot find -lcurl > > collect2: error: ld returned 1 exit status > > configure:7483: $? = 1 > > configure: failed program was: > > | /* confdefs.h */ > > | #define PACKAGE_NAME "rpl" > > | #define PACKAGE_TARNAME "rpl" > > | #define PACKAGE_VERSION "4.1.29" > > | #define PACKAGE_STRING "rpl 4.1.29" > > | #define PACKAGE_BUGREPORT "" > > | #define PACKAGE_URL "" > > | #define PACKAGE "rpl" > > | #define VERSION "4.1.29" > > | #define HAVE_INLINE 1 > > | /* end confdefs.h. */ > > | > > | > > | int > > | main () > > | { > > | return main (); > > | ; > > | return 0; > > | } > > configure:7492: result: no > > configure:7502: error: Can not find libm ! > > " > > > > The " usr/bin/ld: cannot find -lcurl" is strange since I have curl and > > libcurl installed. I have a feeling that the failure to link / find > > libcurl is the problem. > > Libcurl is mandatory to build RPL/CAS. I could modify configure.ac > to > check if curl is available on build system. > The above would be a good idea as I didn't know that the problem with finding libm was the missing libcurl dev files. There should be a separate test for libcurl. > > EDIT 1 : Indeed, for some reason, the GNU autotools link against libcurl > > ( in the autoconf generated " gcc -o conftest -g -O2 -O2 > > -fno-strict-overflow -pthread conftest.c -lm -lcurl >&5 " ) and after > > I installed the development files for libcurl, the build "succeeded", in > > a way. > > > > After, starting the build again, when the motif source was being built, > > I received the build error : > > > > " > > Making install in Mrm > > make[4]: Entering directory > > '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib/Mrm' > > make install-am > > make[5]: Entering directory > > '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib/Mrm' > > make[6]: Entering directory > > '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib/Mrm' > > /bin/mkdir -p > > '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/install/lib' > > /bin/bash ../../libtool --mode=install /usr/bin/install -c > > libMrm.la '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/install/lib' > > libtool: error: error: cannot install 'libMrm.la' to a directory not > > ending in /usr/lib > > Makefile:435: recipe for target 'install-libLTLIBRARIES' failed > > make[6]: *** [install-libLTLIBRARIES] Error 1 > > make[6]: Leaving directory > > '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib/Mrm' > > Makefile:656: recipe for target 'install-am' failed > > make[5]: *** [install-am] Error 2 > > make[5]: Leaving directory > > '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib/Mrm' > > Makefile:650: recipe for target 'install' failed > > make[4]: *** [install] Error 2 > > make[4]: Leaving directory > > '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib/Mrm' > > Makefile:396: recipe for target 'install-recursive' failed > > make[3]: *** [install-recursive] Error 1 > > make[3]: Leaving directory > > '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8/lib' > > Makefile:453: recipe for target 'install-recursive' failed > > make[2]: *** [install-recursive] Error 1 > > make[2]: Leaving directory > > '/home/jdb2/src/rpl2/rpl-4.1.29/tools/motif-2.3.8' > > Makefile:1215: recipe for target 'tools/motif-2.3.8/install/lib/libXm.a' > > failed > > make[1]: *** [tools/motif-2.3.8/install/lib/libXm.a] Error 2 > > make[1]: Leaving directory '/home/jdb2/src/rpl2/rpl-4.1.29' > > Makefile:964: recipe for target 'all' failed > > make: *** [all] Error 2 > > " > > > > After I typed "make" again, this time the build completed successfully. > :) > > configure process is very complex as ./tools and ./rplcas > directories > contain all libraries required for basic RPL/2 (./tools) and RPL/CAS > (./rplcas). Some libraries are often available on modern Unix systems > but RPL/2 can be built on non Unix systems without these basic libraries > (OpenSSL, ncurses...). They don't use autoconf nor automake. Thus, > dependencies are not checked by autoconf/automake but only by Makefile's > and, in cas of build error, you should run make purge and configure again. > Well, I can't really run "make purge" as, to get the build to succeed on an Ubuntu / Linux Mint based system, I have to edit the GNU autotools scripts and definition files so that Motif is built with "-ffat-lto-objects" and zlib is built with "-fPIC". If I run "make purge" then these changes will be lost and the build will fail. > > > The problem I'm having now is that basic tests are failing. For example, > > if I untar tests/tests.tar.gz and run "rpl arith.rpl" I get the error : > > test directory is only for me ;-) > Oh, heh ;) > > " > > +++Error : Undefined implicit name [92178] > > " > > arith.rpl has to abort with this error. If you want to run > arith.rpl, > you have to add "all" implicit after first '<<'. But there is a bug, > arith.rpl aborts with "access violation" error. I'll fix this bug as > soon as possible. > > I tried placing an "all" as you described ( "ARITH all << ..." ) but I now just receive a "+++Fatal : Invalid definition name [20637]" error. I don't know if I'm doing something stupid or not. Thanks :) > Also, when I run "rpl --help" I get an error after the license text that > > reads : > > > > " > > +++Error : Any executable definition > > " > > What do you expect ? If you want to obtain a prompt, you have to > start > RPL/2 with rpl -i. Well, RPL/2's command line behavior needs to be modified to correspond with common Unix command line conventions. That is, if I type "cp --version", I don't receive an error. Running "rpl -v" should behave the same way. In addition, I had no idea what the error message was indicating -- it should be changed to something such as "Error : No RPL/2 program found" or something like that. If one just runs "rpl" then the command line syntax is indicated by "rpl [-options] [program]", which, in Unix based systems, means that both "options" and "program" are optional. I think it should be changed to something like " Usage : rpl [OPTIONS] FILE With no FILE, or when FILE is -, read standard input " But, all the above is just my opinion, and you'd probably have to do some recoding and it could break compatibility... I just think that the error messages are not very understandable... If not, you should add a script name (or a shebang in > script like !#/usr/local/bin/rpl -csp > Thanks for the tip! :) > Best regards, > > JKB > _______________________________________________ > RPL2 mailing list > RPL2 at rayleigh.systella.fr > https://www.systella.fr/cgi-bin/mailman/listinfo/rpl2 > http://www.rpl2.net > Thanks and regards, Jonathan -------------- next part -------------- An HTML attachment was scrubbed... URL: From joel.bertrand at systella.fr Wed Jan 16 18:08:19 2019 From: joel.bertrand at systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) Date: Wed, 16 Jan 2019 18:08:19 +0100 Subject: [RPL/2] Autoconf error in finding libm In-Reply-To: References: <55697e4a-9c7b-a83e-898a-08c8a2dd47a3@systella.fr> Message-ID: <9b450590-ae5d-1c6f-1d0b-b28f7923fb0b@systella.fr> Jonathan Busby a ?crit?: > > " > > +++Error : Undefined implicit name [92178] > > " > > ? ? ? ? arith.rpl has to abort with this error. If you want to run > arith.rpl, > you have to add "all" implicit after first '<<'. But there is a bug, > arith.rpl aborts with "access violation" error. I'll fix this bug as > soon as possible. > > > I tried placing an "all" as you described ( "ARITH all << ..." ) but I > now just receive a "+++Fatal : Invalid definition name [20637]" error. I > don't know if I'm doing something stupid or not. ARITH << "all" implicit 1 1 + disp 1 1.1 + disp 1.1 1 + disp ... But this test aborts with "access violation error". I don't have time to check before next week. > > > Also, when I run "rpl --help" I get an error after the license > text that > > reads : > > > > " > > +++Error : Any executable definition > > " > > ? ? ? ? What do you expect ? If you want to obtain a prompt, you > have to start > RPL/2 with rpl -i. > > > Well, RPL/2's command line behavior needs to be modified to correspond > with common Unix command line conventions. That is, if I type "cp > --version", I don't receive an error. Running "rpl? -v" should behave > the same way. In addition, I had no idea what the error message was > indicating -- it should be changed to something such as "Error : No > RPL/2 program found" or something like that. If one just runs "rpl" then > the command line syntax is indicated by "rpl [-options] [program]", > which, in Unix based systems, means that both "options" and "program" > are optional. I think it should be changed to something like > " > Usage : rpl [OPTIONS] FILE > With no FILE, or when FILE is -, read standard input > " You can try to run "man rpl" ;-) > But, all the above is just my opinion, and you'd probably have to do > some recoding and it could break compatibility... I just think that the > error messages are not very understandable... RPL/2 acts as regular RPL. You define some "definitions" in one or several files (#include can be used in RPL/2) : DEF1 << ... >> DEF2 << ... >> DEF3 << ... >> Program entry point is the first definition in file _after_ preprocessing stage. Regards, JKB