Re: ./configure error
Hi Bill, thanks. The duplicate block should have been removed but wasn't. Hopefully fixed in SVN 1446. Best Regards, Jürgen On 3/27/21 4:12 AM, Bill Heagy wrote: Looking at this further, there's a whole block in buildtag.sh that duplicates definitions in configure and resets apl_top. I think this block can be deleted (but I haven't worked with bash scripts for "awhile", so please check my logic). On 3/26/21 10:55 PM, Bill Heagy wrote: I think the "f" variable in the do loop near the end of "configure" is being reset in "source buildtag.sh", which also uses "f". Changing one of these do something else, e.g. "", seems to work. (It's easier to change the one in buildtag.sh: it only appears once.) On 3/26/21 9:38 PM, Peter Teeson wrote: Sorry I am not the right person to help. I’m on Mac OS. On Mar 26, 2021, at 8:48 PM, Bill Heagy wrote: $ uname -v #1 SMP Debian 5.10.24-1 (2021-03-19) On 3/26/21 8:06 PM, Peter Teeson wrote: Sorry.. .Please provide uname -v On Mar 26, 2021, at 6:05 PM, Bill Heagy wrote: It looks like there's a path problem with ./configure in the latest update. ... config.status: creating wslib5/Makefile config.status: creating wslib5/APLComponentFiles/Makefile config.status: creating wslib5/iso-apl-cf/Makefile config.status: creating config.h config.status: config.h is unchanged config.status: executing depfiles commands config.status: executing libtool commands configure: creating buildtag.hh... svn: E155007: '/src/Archive.cc' is not a working copy configure: top-level apl directory is: /home configure: creating /home/makefile.h ... cp: cannot create regular file '../../../../makefile.h': Permission denied configure: creating /home/configure_args.cc ./configure: line 22964: ../../../../configure_args.cc: Permission denied configure: saving configure options in ../../../../configure_options ./configure: line 22983: ../../../../configure_options: Permission denied
Re: ./configure error
Builds and works fin now. Thanks! Blake McBride On Sat, Mar 27, 2021 at 6:17 AM Dr. Jürgen Sauermann < mail@jürgen-sauermann.de> wrote: > Hi Bill, > > thanks. The duplicate block should have been removed but wasn't. > Hopefully fixed in *SVN 1446*. > > Best Regards, > Jürgen > > > > On 3/27/21 4:12 AM, Bill Heagy wrote: > > Looking at this further, there's a whole block in buildtag.sh that > duplicates definitions in configure and resets apl_top. I think this block > can be deleted (but I haven't worked with bash scripts for "awhile", so > please check my logic). > > On 3/26/21 10:55 PM, Bill Heagy wrote: > > I think the "f" variable in the do loop near the end of "configure" is > being reset in "source buildtag.sh", which also uses "f". Changing one of > these do something else, e.g. "", seems to work. (It's easier to > change the one in buildtag.sh: it only appears once.) > > On 3/26/21 9:38 PM, Peter Teeson wrote: > > Sorry I am not the right person to help. I’m on Mac OS. > > > On Mar 26, 2021, at 8:48 PM, Bill Heagy > wrote: > > $ uname -v > #1 SMP Debian 5.10.24-1 (2021-03-19) > > On 3/26/21 8:06 PM, Peter Teeson wrote: > > Sorry.. .Please provide > uname -v > > On Mar 26, 2021, at 6:05 PM, Bill Heagy > wrote: > > It looks like there's a path problem with ./configure in the latest > update. > ... > config.status: creating wslib5/Makefile > config.status: creating wslib5/APLComponentFiles/Makefile > config.status: creating wslib5/iso-apl-cf/Makefile > config.status: creating config.h > config.status: config.h is unchanged > config.status: executing depfiles commands > config.status: executing libtool commands > > configure: creating buildtag.hh... > svn: E155007: '/src/Archive.cc' is not a working copy > configure: top-level apl directory is: /home > configure: creating /home/makefile.h ... > cp: cannot create regular file '../../../../makefile.h': Permission denied > configure: creating /home/configure_args.cc > ./configure: line 22964: ../../../../configure_args.cc: Permission denied > > configure: saving configure options in ../../../../configure_options > ./configure: line 22983: ../../../../configure_options: Permission denied > > > > > > >
GNU APL build system changes
Hi, as some of you have noticed, I made some changes to the GNU APL build system. Some of these changes were simplifications of the build system (some automatically generated .cc and .hh files like configure_args.cc are gone for good), while other changes were needed to support Autoconf VPATH builds. Also all files generated by ./configure now stored in the top-level directory so that the subdirectory src (which is shared by all VPATH builds) is no longer muddied with ./configure results. The purpose of VPATH builds is to be able to build several ./configure variants in parallel. Different VPATH builds are needed to discover build problems, in particular with rarely used ./configure variants before these problems are committed to the savannah SVN server. There could still be glitches in the new build structure, so please keep reporting them. SVN 1449. Best Regards, Jürgen
Re: GNU APL build system changes
Builds fine on my 64-bit LinuxMint 19.3 box. Thanks! Blake On Sat, Mar 27, 2021 at 12:04 PM Dr. Jürgen Sauermann < mail@jürgen-sauermann.de> wrote: > Hi, > > as some of you have noticed, I made some changes to the GNU APL build > system. > > Some of these changes were simplifications of the build system (some > automatically > generated .cc and .hh files like *configure_args.cc* are gone for good), > while other changes > were needed to support Autoconf VPATH builds. Also all files generated by > ./configure > now stored in the top-level directory so that the subdirectory *src* > (which is shared by all > VPATH builds) is no longer muddied with ./configure results. > > The purpose of VPATH builds is to be able to build several ./configure > variants in > parallel. Different VPATH builds are needed to discover build problems, in > particular with > rarely used ./configure variants before these problems are committed to > the savannah > SVN server. > > There could still be glitches in the new build structure, so please keep > reporting > them. > > SVN *1449*. > > Best Regards, > Jürgen > >
RE: GNU APL build system changes
All good on OpenBSD as well. ~Brian Brian Robert Callahan, Ph.D. Lecturer, ITWS@RPI Office: Amos Eaton 132 From: Bug-apl [bug-apl-bounces+callab5=rpi@gnu.org] on behalf of Blake McBride [blake1...@gmail.com] Sent: Saturday, March 27, 2021 1:14 PM To: Dr. Jürgen Sauermann Cc: bug-apl@gnu.org Subject: Re: GNU APL build system changes Builds fine on my 64-bit LinuxMint 19.3 box. Thanks! Blake On Sat, Mar 27, 2021 at 12:04 PM Dr. Jürgen Sauermann mailto:mail@j%C3%BCrgen-sauermann.de>> wrote: Hi, as some of you have noticed, I made some changes to the GNU APL build system. Some of these changes were simplifications of the build system (some automatically generated .cc and .hh files like configure_args.cc are gone for good), while other changes were needed to support Autoconf VPATH builds. Also all files generated by ./configure now stored in the top-level directory so that the subdirectory src (which is shared by all VPATH builds) is no longer muddied with ./configure results. The purpose of VPATH builds is to be able to build several ./configure variants in parallel. Different VPATH builds are needed to discover build problems, in particular with rarely used ./configure variants before these problems are committed to the savannah SVN server. There could still be glitches in the new build structure, so please keep reporting them. SVN 1449. Best Regards, Jürgen
Re: Notes about git-svn source control in macOS
Hi Peter, thanks for sharing this. Non-MAC users (?) should be warned that git svn clone seems to be a new (?) or MAC specific (?) git feature; my git (version 2.17.1) complains: eedjsa@server68:/tmp$ git svn clone --preserve-empty-dirs -r HEAD https://svn.savannah.gnu.org/svn/apl/trunk git: 'svn' is not a git command. See 'git --help'. The --preserve-empty-dirs looks like a long needed bug-fix for git which could improve git from being an annoyance to being a mere nuisance. In my experience, though, empty directories in git are already dropped on commit rather than on clone and therefore --preserve-empty-dirs should IMHO be an option for git commit rather than for git clone (and maybe it is already?). For that reason a straight git clone https://git.savannah.gnu.org/git/apl.git might be more predictable than a "git svn clone". Best Regards, Jürgen On 3/26/21 6:55 PM, Peter Teeson wrote: Hi Jürgen: Hope the following can be useful and perhaps even remove the extra maintenance burden of git. I don’t understand enough about the various configure files (.ac, .sub, etc etc) etc to modify buildtag myself. respect Peter For macOS users TL:DNR // download svn repo using git clone Gandalf:~ pteeson$ git svn clone --preserve-empty-dirs -r HEAD https://svn.savannah.gnu.org/svn/apl/trunk > git-log 2>&1 // for build tag script mods // Are we on macOS and which version Gandalf:trunk-git pteeson$ sw_vers |grep "ProductName" ProductName: Mac OS X Gandalf:trunk-git pteeson$ sw_vers | grep "ProductVersion" ProductVersion: 10.14.6 // which svn Gandalf:trunk-git pteeson$ git svn info | grep "Revision:" Revision: 1440 Details Because Apple no longer distributes svn as part of its Developer tools (Xcode and Command Line Tools) macOS users should use git or take responsibility for installing svn. Of course this is not a big deal. But for those who wish to use Apple’s tools I have been doing some deep diving over the last many days and learned a few things. (1) Compare downloading the GNU APL repository using svn vs git Gandalf:~ pteeson$ svn co http://svn.savannah.gnu.org/svn/apl/trunk > svn-log 2>&1 Gandalf:~ pteeson$ git svn clone --preserve-empty-dirs -r HEAD https://svn.savannah.gnu.org/svn/apl/trunk > git-log 2>&1 git notes: (a) if you do not specify the -r HEAD option you will be downloading all 1440 svns. This is usually NOT what you want!
Re: GNU APL build system changes
Works as well on Fedora release 33, Linux 5.10.17-100.fc32.x86_64 #1 SMP I don't know if it's significant, but I used git clone to pull down the source code for 1449 and that results in a ./configure message of: *** current directory is not a svn checkout: keeping old buildtag and an `apl --version` of BUILDTAG: - Project: GNU APL Version / SVN: 1.8 / 1410M Build Date: 2021-01-19 19:59:14 UTC Build OS: Linux 4.15.0-123-generic x86_64 config.status: '--enable-maintainer-mode' 'DEVELOP_WANTED=yes' Archive SVN: 1406 On 3/27/21 1:14 PM, Blake McBride wrote: Builds fine on my 64-bit LinuxMint 19.3 box. Thanks! Blake On Sat, Mar 27, 2021 at 12:04 PM Dr. Jürgen Sauermann mailto:mail@j%C3%BCrgen-sauermann.de>> wrote: Hi, as some of you have noticed, I made some changes to the GNU APL build system. Some of these changes were simplifications of the build system (some automatically generated .cc and .hh files like *configure_args.cc* are gone for good), while other changes were needed to support Autoconf VPATH builds. Also all files generated by ./configure now stored in the top-level directory so that the subdirectory *src* (which is shared by all VPATH builds) is no longer muddied with ./configure results. The purpose of VPATH builds is to be able to build several ./configure variants in parallel. Different VPATH builds are needed to discover build problems, in particular with rarely used ./configure variants before these problems are committed to the savannah SVN server. There could still be glitches in the new build structure, so please keep reporting them. SVN *1449*. Best Regards, Jürgen OpenPGP_0xDA6C0193083E.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: GNU APL build system changes
Hi Chris, it is generally OK to get "*** current directory is not a svn checkout: keeping old buildtag" if you fetch GNU APL with anything other than SVN, e.g. with git clone or by unpacking a tar file. At least as long as you don't switch back-and-forth between SVN and git with the same checkout directory. However, the fallback file that was used below was incorrect because I had forgotten to "git add" the buildtag.hh (typical mistake of SVN users where this is automatic). Therefore you got your own last buildtag (1410M from the savannah SVN) instead of my last buildtag (17930). This should be fixed now. Best Regards, Jürgen On 3/27/21 6:54 PM, Chris Moller wrote: Works as well on Fedora release 33, Linux 5.10.17-100.fc32.x86_64 #1 SMP I don't know if it's significant, but I used git clone to pull down the source code for 1449 and that results in a ./configure message of: *** current directory is not a svn checkout: keeping old buildtag and an `apl --version` of BUILDTAG: - Project: GNU APL Version / SVN: 1.8 / 1410M Build Date: 2021-01-19 19:59:14 UTC Build OS: Linux 4.15.0-123-generic x86_64 config.status: '--enable-maintainer-mode' 'DEVELOP_WANTED=yes' Archive SVN: 1406 On 3/27/21 1:14 PM, Blake McBride wrote: Builds fine on my 64-bit LinuxMint 19.3 box. Thanks! Blake On Sat, Mar 27, 2021 at 12:04 PM Dr. Jürgen Sauermannwrote: Hi, as some of you have noticed, I made some changes to the GNU APL build system. Some of these changes were simplifications of the build system (some automatically generated .cc and .hh files like configure_args.cc are gone for good), while other changes were needed to support Autoconf VPATH builds. Also all files generated by ./configure now stored in the top-level directory so that the subdirectory src (which is shared by all VPATH builds) is no longer muddied with ./configure results. The purpose of VPATH builds is to be able to build several ./configure variants in parallel. Different VPATH builds are needed to discover build problems, in particular with rarely used ./configure variants before these problems are committed to the savannah SVN server. There could still be glitches in the new build structure, so please keep reporting them. SVN 1449. Best Regards, Jürgen
Re: GNU APL build system changes
On debian 32-bit: make [.] mv -f .deps/apl-LvalCell.Tpo .deps/apl-LvalCell.Po g++ -DHAVE_CONFIG_H -I. -I..-Wall -I sql -I /home/wheagy/tmp/apl_svn/trunk -I/usr/include -g -O2 -I /home/wheagy/tmp/apl_svn/trunk -MT apl-Macro.o -MD -MP -MF .deps/apl-Macro.Tpo -c -o apl-Macro.o `test -f 'Macro.cc' || echo './'`Macro.cc mv -f .deps/apl-Macro.Tpo .deps/apl-Macro.Po g++ -DHAVE_CONFIG_H -I. -I..-Wall -I sql -I /home/wheagy/tmp/apl_svn/trunk -I/usr/include -g -O2 -I /home/wheagy/tmp/apl_svn/trunk -MT apl-Missing_Libraries.o -MD -MP -MF .deps/apl-Missing_Libraries.Tpo -c -o apl-Missing_Libraries.o `test -f 'Missing_Libraries.cc' || echo './'`Missing_Libraries.cc Missing_Libraries.cc: In function ‘Token missing_files(const char*, const char**, const char**, const char**)’: Missing_Libraries.cc:90:13: error: ‘CONFIGURE_ARGS’ was not declared in this scope 90 | " " << CONFIGURE_ARGS << "\n\n"; | ^~ make[3]: *** [Makefile:4331: apl-Missing_Libraries.o] Error 1 make[3]: *** Waiting for unfinished jobs mv -f .deps/apl-Nabla.Tpo .deps/apl-Nabla.Po make[3]: Leaving directory '/home/wheagy/tmp/apl_svn/trunk/src' make[2]: *** [Makefile:5331: all-recursive] Error 1 make[2]: Leaving directory '/home/wheagy/tmp/apl_svn/trunk/src' make[1]: *** [Makefile:541: all-recursive] Error 1 make[1]: Leaving directory '/home/wheagy/tmp/apl_svn/trunk' make: *** [Makefile:429: all] Error 2 On 3/27/21 3:00 PM, Dr. Jürgen Sauermann wrote: Hi Chris, it is generally OK to get "*** current directory is not a svn checkout: keeping old buildtag" if you fetch GNU APL with anything other than SVN, e.g. with git clone or by unpacking a tar file. At least as long as you don't switch back-and-forth between SVN and git with the same checkout directory. However, the fallback file that was used below was incorrect because I had forgotten to "git add" the buildtag.hh (typical mistake of SVN users where this is automatic). Therefore you got your own last buildtag (*1410M* from the savannah SVN) instead of my last buildtag (*17930*). This should be fixed now. Best Regards, Jürgen On 3/27/21 6:54 PM, Chris Moller wrote: Works as well on Fedora release 33, Linux 5.10.17-100.fc32.x86_64 #1 SMP I don't know if it's significant, but I used git clone to pull down the source code for 1449 and that results in a ./configure message of: *** current directory is not a svn checkout: keeping old buildtag and an `apl --version` of BUILDTAG: - Project:GNU APL Version / SVN: 1.8 / 1410M Build Date: 2021-01-19 19:59:14 UTC Build OS: Linux 4.15.0-123-generic x86_64 config.status: '--enable-maintainer-mode' 'DEVELOP_WANTED=yes' Archive SVN:1406 On 3/27/21 1:14 PM, Blake McBride wrote: Builds fine on my 64-bit LinuxMint 19.3 box. Thanks! Blake On Sat, Mar 27, 2021 at 12:04 PM Dr. Jürgen Sauermann mailto:mail@j%C3%BCrgen-sauermann.de>> wrote: Hi, as some of you have noticed, I made some changes to the GNU APL build system. Some of these changes were simplifications of the build system (some automatically generated .cc and .hh files like *configure_args.cc* are gone for good), while other changes were needed to support Autoconf VPATH builds. Also all files generated by ./configure now stored in the top-level directory so that the subdirectory *src* (which is shared by all VPATH builds) is no longer muddied with ./configure results. The purpose of VPATH builds is to be able to build several ./configure variants in parallel. Different VPATH builds are needed to discover build problems, in particular with rarely used ./configure variants before these problems are committed to the savannah SVN server. There could still be glitches in the new build structure, so please keep reporting them. SVN *1449*. Best Regards, Jürgen
Re: GNU APL build system changes
Cool--I just wasn't sure how consistent you wanted the builds to be across download mechanisms. It's awkward that git doesn't directly support a straight-forward version-number mechanism that could inherit SVN revision numbers--a ridiculous-number-of-digits SHA1 string isn't terribly convenient. On 3/27/21 3:00 PM, Dr. Jürgen Sauermann wrote: Hi Chris, it is generally OK to get "*** current directory is not a svn checkout: keeping old buildtag" if you fetch GNU APL with anything other than SVN, e.g. with git clone or by unpacking a tar file. At least as long as you don't switch back-and-forth between SVN and git with the same checkout directory. However, the fallback file that was used below was incorrect because I had forgotten to "git add" the buildtag.hh (typical mistake of SVN users where this is automatic). Therefore you got your own last buildtag (*1410M* from the savannah SVN) instead of my last buildtag (*17930*). This should be fixed now. Best Regards, Jürgen On 3/27/21 6:54 PM, Chris Moller wrote: Works as well on Fedora release 33, Linux 5.10.17-100.fc32.x86_64 #1 SMP I don't know if it's significant, but I used git clone to pull down the source code for 1449 and that results in a ./configure message of: *** current directory is not a svn checkout: keeping old buildtag and an `apl --version` of BUILDTAG: - Project: GNU APL Version / SVN: 1.8 / 1410M Build Date: 2021-01-19 19:59:14 UTC Build OS: Linux 4.15.0-123-generic x86_64 config.status: '--enable-maintainer-mode' 'DEVELOP_WANTED=yes' Archive SVN: 1406 On 3/27/21 1:14 PM, Blake McBride wrote: Builds fine on my 64-bit LinuxMint 19.3 box. Thanks! Blake On Sat, Mar 27, 2021 at 12:04 PM Dr. Jürgen Sauermann mailto:mail@j%C3%BCrgen-sauermann.de>> wrote: Hi, as some of you have noticed, I made some changes to the GNU APL build system. Some of these changes were simplifications of the build system (some automatically generated .cc and .hh files like *configure_args.cc* are gone for good), while other changes were needed to support Autoconf VPATH builds. Also all files generated by ./configure now stored in the top-level directory so that the subdirectory *src* (which is shared by all VPATH builds) is no longer muddied with ./configure results. The purpose of VPATH builds is to be able to build several ./configure variants in parallel. Different VPATH builds are needed to discover build problems, in particular with rarely used ./configure variants before these problems are committed to the savannah SVN server. There could still be glitches in the new build structure, so please keep reporting them. SVN *1449*. Best Regards, Jürgen OpenPGP_0xDA6C0193083E.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature