Re: installing Info documentation

2020-04-30 Thread Arthur A. Gleckler
On Thu, Apr 30, 2020 at 7:14 PM Taylor R Campbell wrote: > cd mit-scheme/doc > autoconf > ./configure > make > make install > Thanks! Amazingly, after all these years, I don't think I had ever run autoconf, at least not manually.

Re: installing Info documentation

2020-04-30 Thread Taylor R Campbell
> Date: Thu, 30 Apr 2020 18:23:07 -0700 > From: "Arthur A. Gleckler" > > What's the standard way to install Info documentation these days? I see > doc/Makefile.in, but no Makefile nor .info files. cd mit-scheme/doc autoconf ./configure make make install That should install: -

installing Info documentation

2020-04-30 Thread Arthur A. Gleckler
What's the standard way to install Info documentation these days? I see doc/Makefile.in, but no Makefile nor .info files. Thanks.

Re: *.bci missing

2020-04-30 Thread Arthur A. Gleckler
On Thu, Apr 30, 2020 at 12:12 AM Taylor R Campbell wrote: > git pull and try again? > Thank you so much! That worked. Debugging is so much harder when almost every stack frame looks like this: ... 17 ;compiled code 18 ;compiled code 19

Re: *.bci missing

2020-04-30 Thread Chris Hanson
When cross compiling, aren’t they named .icb or something like that? On Apr 30, 2020, 12:12 AM -0700, Taylor R Campbell , wrote: > > Date: Wed, 29 Apr 2020 23:46:40 -0700 > > From: "Arthur A. Gleckler" > > > > *.bci files aren't installed when I do make install (sudo make install, in > > fact). I

Re: *.bci missing

2020-04-30 Thread Taylor R Campbell
> Date: Wed, 29 Apr 2020 23:46:40 -0700 > From: "Arthur A. Gleckler" > > *.bci files aren't installed when I do make install (sudo make install, in > fact). I see bug 33898 , which > reports that they aren't installed, but in my case, they don't even seem to

*.bci missing

2020-04-30 Thread Arthur A. Gleckler
*.bci files aren't installed when I do make install (sudo make install, in fact). I see bug 33898 , which reports that they aren't installed, but in my case, they don't even seem to have been generated, at least not in the directories where install expects