Interesting. both of you have same error but different OS' although both 
Linux’s.

I just downloaded latest, i.e. svn 1445, using git and ./configure gives me the 
same error.
(my earlier experiments were with svn 1440 and all was OK.)

What did you use to download - svn? or tarball? or git?

config.status: executing libtool commands

configure: creating buildtag.hh...
*** current directory is not an SVN checkout: keeping old buildtag
readlink: illegal option -- f
usage: readlink [-n] [file ...]
configure: top-level apl directory is: 
configure: creating /makefile.h ...
cp: ../../../../makefile.h: Permission denied
configure: creating /configure_args.cc
./configure: line 22972: ../../../../configure_args.cc: Permission denied
 
configure: saving configure options in ../../../../configure_options
./configure: line 22991: ../../../../configure_options: Permission denied

> On Mar 26, 2021, at 9:12 PM, Blake McBride <blake1...@gmail.com> wrote:
> 
> Greetings,
> 
> I am running 64-bit LinuxMint 19.3.  I am getting an error on ./configure as 
> follows:
> 
> # rm -rf *
> # svn update
> # ./configure
> [...]
> config.status: creating wslib3/Makefile
> config.status: creating wslib4/Makefile
> 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: 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: /
> configure: creating //makefile.h ...
> cp: cannot create regular file '../../../../makefile.h': Permission denied
> configure: creating //configure_args.cc
> ./configure: line 22972: ../../../../configure_args.cc: Permission denied
>  
> configure: saving configure options in ../../../../configure_options
> ./configure: line 22991: ../../../../configure_options: Permission denied
> #
> 
> Thanks!
> 
> Blake McBride
> 

Reply via email to