#4230 build error, missing file: maxima-index-html.lisp

[ZOO]

I get the following error when I build from git source, or when I build from the 5.47.0 tarball.

WARNING: Maxima is unable to set up the help system.
(Details: CL-INFO::LOAD-PRIMARY-INDEX: Couldn't load
"/home/packages/SOURCE/maxima-code/sbcl_build/doc/info/./maxima-index-html.lisp":
file does not exist.)
file_search1: build-html-index.lisp not found in file_search_maxima,file_search_lisp.
-- an error. To debug this try: debugmode(true);

In the tarball for 5.47.0, this file exists in ./doc/info/maxima-index-html.lisp and I can simply copy it to where I need it. (cp ./doc/info/maxima-index-html.lisp ./sbcl_build/doc/info/). However the source tree from git seems to no longer have this file. It appears it may not be getting generated.

Has anyone else run into this?

[Raymond Toy]

At stage of the build does this message appear? The very first time you build the docs, this message will appear because the build runs the newly built maxima image and this file doesn't exist yet because it's being created now. It's harmless unless you see such a message when you run maxima after doing the full build.

[ZOO]

It happens at the very end of the build. But re-running 'make' will still stop with the same error message, unless I copy the file by hand to the necessary location in my build directory.

From the maxima-code/ directory I can also do:
cp doc/info/build-html-index.lisp sbcl_build/doc/info/
and the build will complete.

[Wolfgang Dautermann]

Ah, you are trying an out-of-source build (subdirectory "sbcl_build")? I think that is not fully supported now, although it would be very nice.
For now, it should work when calling ./configure, make, etc. directly from the source directory.
Best regards, Wolfgang

[ZOO]

OK, thank you! Best, Eric

[Wolfgang Dautermann]

With commit [edfcc0] I added some basic 'out-of-source-build' features. Not finished yet.

[Robert Dodier]

Since this message appears to be in reference to the out-of-tree build, which is an unfinished feature, I am closing this report as "won't fix", since that feature is not expected to work yet. If I've misunderstood what's going on, anyone can reopen this report.