> Other than having a shortage of disk space for heap images containing extra
> debugging symbols (for which there is a fairly cheap solution these days),
> were there any other specific problems anyone had building scsh under linux?
>Well, twice in the last two weeks I've heard from Linux users who were
>trying to build scsh with a corrupted make(1) program. I don't know how
>make got borked, or if it's a common failure mode, but it was a striking
>coincidence. The sympton was the same in both cases: make wouldn't recognise
>the existence of the Makefile. And it prevented you from using make to build
>*any* software system, not just scsh, of course.
I wonder if those people forgot to run configure, or configure couldn't
write the makefile successfully because of some other problem.
Some versions of GNU sed are hosed, but 2.05 (which is the one I'm using)
If either of the people who reported this problem see my message, would you
please do the following?
1) run "sh -x configure" in the scsh sources and send me the entire
output. If you're using a bourne shell to begin with, you can do
sh -x configure > configure.output 2>&1
If you're using csh, do
sh -x configure >& configure.out
Mail me the configure.out file.
2) Mail me the file `config.log' created from running configure.
3) Run "sed --version" and tell me which version it reports.
4) Run "make --version" and tell me which version it reports.