Hi Bill,
I suppose you did not (re-) run ./configure after updating to the
latest svn or git update?
There is also a make target that does it:
make SVNUP
Best Regards,
Jürgen
On 3/27/21 8:33 PM, Bill Heagy wrote:
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 convenien
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 `te
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-
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
, 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 yo
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 b
