4:20 p.m.
Hi,
I'm encountering the following problem (after doing make clean,
configure, and make successfully) with "make pdfdocs". This is on
current git, or actually, the file doc/tex/pkgbook.tex is also changed
here and not yet pushed, but it doesn't look as if that's the problem.
I'm using Linux on a virtual machine running under Windows here, if that
matters.
thanks
sven
---
make[1]: Entering directory '/ ... /gretl-git/doc'
make -C tex
make[2]: Entering directory '/ ... /gretl-git/doc/tex'
make[2]: stat: ../../doc/tex/persistent.tex: Too many levels of symbolic
links
make[2]: *** No rule to make target '../../doc/tex/persistent.tex',
needed by 'date.tex'. Stop.
make[2]: Leaving directory '/ ... /gretl-git/doc/tex'
make[1]: *** [Makefile:11: tex] Error 2
make[1]: Leaving directory '/ ... /gretl-git/doc'
make: *** [Makefile:72: pdfdocs] Error 2
7:26 p.m.
On Sat, 20 Nov 2021, Sven Schreiber wrote:
I'm encountering the following problem (after doing make clean,
configure, and make successfully) with "make pdfdocs". This is on
current git, or actually, the file doc/tex/pkgbook.tex is also changed
here and not yet pushed, but it doesn't look as if that's the problem.
I'm using Linux on a virtual machine running under Windows here, if that
matters.
make[1]: Entering directory '/ ... /gretl-git/doc'
make -C tex
make[2]: Entering directory '/ ... /gretl-git/doc/tex'
make[2]: stat: ../../doc/tex/persistent.tex: Too many levels of symbolic
links
make[2]: *** No rule to make target '../../doc/tex/persistent.tex',
You need to do "make clean" and rerun the configure script.
Allin
11:09 a.m.
Am 20.11.2021 um 20:26 schrieb Allin Cottrell:
On Sat, 20 Nov 2021, Sven Schreiber wrote:
>
> make[1]: Entering directory '/ ... /gretl-git/doc'
> make -C tex
> make[2]: Entering directory '/ ... /gretl-git/doc/tex'
> make[2]: stat: ../../doc/tex/persistent.tex: Too many levels of symbolic
> links
> make[2]: *** No rule to make target '../../doc/tex/persistent.tex',
You need to do "make clean" and rerun the configure script.
Actually I had done that, and now I've done it again, and still getting
the same error. Will check on a native Linux machine with a "cleaner"
git state.
thanks
sven
11:24 a.m.
On Sun, 21 Nov 2021, Sven Schreiber wrote:
Actually I had done that, and now I've done it again, and still
getting
the same error. Will check on a native Linux machine with a "cleaner"
git state.
"make pdfdocs" is working fine here. Are you on the master branch?
-------------------------------------------------------
Riccardo (Jack) Lucchetti
Dipartimento di Scienze Economiche e Sociali (DiSES)
Università Politecnica delle Marche
(formerly known as Università di Ancona)
r.lucchetti(a)univpm.it
http://www2.econ.univpm.it/servizi/hpp/lucchetti
-------------------------------------------------------
2:01 p.m.
Am 21.11.2021 um 12:24 schrieb Riccardo (Jack) Lucchetti:
On Sun, 21 Nov 2021, Sven Schreiber wrote:
> Actually I had done that, and now I've done it again, and still getting
> the same error. Will check on a native Linux machine with a "cleaner"
> git state.
"make pdfdocs" is working fine here. Are you on the master branch?
This really seems to be a problem of the virtual machine context and/or
the underlying file system. On native Linux it works OK. Actually, I
wasn't totally exact, it's not a VM, it's Linux running under Windows'
"Subsystem for Linux" (command-line only). But it has always worked fine
so far.
BTW, I'm noticing that the configure script produces the following
warning message:
./configure: line 16896: test: too many arguments
yes
But that's probably unrelated, I guess.
thanks
sven
8:15 p.m.
On Sun, Nov 21, 2021 at 9:01 AM Sven Schreiber <svetosch(a)gmx.net> wrote:
Am 21.11.2021 um 12:24 schrieb Riccardo (Jack) Lucchetti:
> On Sun, 21 Nov 2021, Sven Schreiber wrote:
>
>> Actually I had done that, and now I've done it again, and still getting
>> the same error. Will check on a native Linux machine with a "cleaner"
>> git state.
>
> "make pdfdocs" is working fine here. Are you on the master branch?
>
This really seems to be a problem of the virtual machine context and/or
the underlying file system.
Probably the underlying file system (lacking symlinks). It should work to blow
away doc/tex under your build tree and start over (with configure).
Allin
9:55 p.m.
Am 21.11.2021 um 21:15 schrieb Cottrell, Allin:
On Sun, Nov 21, 2021 at 9:01 AM Sven Schreiber
<svetosch(a)gmx.net> wrote:
> This really seems to be a problem of the virtual machine context and/or
> the underlying file system.
Probably the underlying file system (lacking symlinks). It should work to blow
away doc/tex under your build tree and start over (with configure).
Indeed, a little bit to my surprise it worked to delete that and then do
"git restore doc/tex/*", followed by the configure script and so on.
thanks
sven
10:31 p.m.
On Sun, 21 Nov 2021, Sven Schreiber wrote:
Am 21.11.2021 um 21:15 schrieb Cottrell, Allin:
> On Sun, Nov 21, 2021 at 9:01 AM Sven Schreiber <svetosch(a)gmx.net> wrote:
>> This really seems to be a problem of the virtual machine context and/or
>> the underlying file system.
> Probably the underlying file system (lacking symlinks). It should work to
> blow
> away doc/tex under your build tree and start over (with configure).
Indeed, a little bit to my surprise it worked to delete that and then do
"git restore doc/tex/*", followed by the configure script and so on.
If you had to use "git restore" that suggests that you're doing your
build inside the git source tree. That's not recommended, though
it's not actually banned yet. Better to build outside the source
tree.
Allin
9:42 p.m.
Am 21.11.2021 um 23:31 schrieb Allin Cottrell:
On Sun, 21 Nov 2021, Sven Schreiber wrote:
> Indeed, a little bit to my surprise it worked to delete that and
then do
> "git restore doc/tex/*", followed by the configure script and so on.
If you had to use "git restore" that suggests that you're doing your
build inside the git source tree. That's not recommended, though it's
not actually banned yet. Better to build outside the source tree.
Yeah, I know ;-)
I just checked and Appendix section B.4 of the guide doesn't seem to
explain how to actually perform the build outside of the source tree. I
know there will be a million search hits on the internet for this
question, but one or two sentences there might be nice.
thanks
sven
1:10 a.m.
On Sun, Nov 21, 2021 at 5:41 PM Sven Schreiber <svetosch(a)gmx.net> wrote:
Am 21.11.2021 um 23:31 schrieb Allin Cottrell:
> On Sun, 21 Nov 2021, Sven Schreiber wrote:
>> Indeed, a little bit to my surprise it worked to delete that and then do
>> "git restore doc/tex/*", followed by the configure script and so on.
>
> If you had to use "git restore" that suggests that you're doing your
> build inside the git source tree. That's not recommended, though it's
> not actually banned yet. Better to build outside the source tree.
Yeah, I know ;-)
I just checked and Appendix section B.4 of the guide doesn't seem to
explain how to actually perform the build outside of the source tree. I
know there will be a million search hits on the internet for this
question, but one or two sentences there might be nice.
Good point, that should be fixed. But it's quite simple: the invocation
of the configure script has to take into account the relative path. So if
your build directory is inside (underneath) the source tree it's
../configure <options>
while if it's in a parallel tree it would be (something like)
../gretl-git/configure <options>
Allin
1155
days inactive
1157
days old
9 comments
4 participants
participants (4)
-
Allin Cottrell -
Cottrell, Allin
-
Riccardo (Jack) Lucchetti -
Sven Schreiber