Boot path doesn't account for non-standard install locations about chezscheme HOT 13 CLOSED

Is this approach acceptable? #25

from chezscheme.

I ran into the same problem trying to install to /usr/lib64 on my slackware system. The search path referred to in the output is hard-coded in c/scheme.c in the definition defaultsystemheappath , so try changing that and doing the build again. I also made adjustments to configure and makefiles/Mf-install.in on my system so I didn't have to keep re-tweaking my build files after running configure.

from chezscheme.

This is the same issue as #16

from chezscheme.

rain-1, which did not exist at the time we posted. ;-)

from chezscheme.

@Cathartes, would you be interested in sharing your fixes as a pull request?

from chezscheme.

My own fixes are just duct tape. Ideally, scheme.c should reference a defaultsystemheappath generated for the platform by configure. I can submit a few tweaks, but I've only had a few hours to look at the source tree--someone with a better understanding of the build system would do a better job. If someone (e.g., dybvig) doesn't beat me to it, I'll see what I can do!

from chezscheme.

looking into this a little, is it really a problem given the SCHEMEHEAPDIRS variable?

from chezscheme.

As a stopgap, it's fine. But, in my opinion, that variable is for overriding a normal (and working) default for a special use case, not for just getting the scheme to run.

from chezscheme.

I applied your patch to my openbsd repo and used:

./configure --nogzip-man-pages --installman=pwd/out --installprefix=pwd/out

and make, make install worked great as a regular user. scheme finds the boot files too!

I don't know why the gzip-man-pages stage is failing though.

Looks great!

from chezscheme.

Thank you, @combinatorylogic. I put a pull request on your changes (rather than the cisco master), with hope of maybe solving the man page issue that @rain-1 mentioned. Seems to work well on my system, hopefully (both of) yours?

from chezscheme.

I'm guessing the changes didn't meet standards, since the PR is just sitting there. I'm probably to blame for that because of my messy commit messages. Sorry!!

from chezscheme.

@Cathartes I can't speak for everyone else, but I've just not had a chance to look through and test the changes in your PR in detail yet.

from chezscheme.

@Cathartes Kent and I went through the PR #25. We ended up making a few additional changes.

1. Changed the name of the header file to config.h (it is now entirely generated from the configure script)
2. Added --installbin, --installschemename, --installpetitename, and --installscriptname to try to complete our configuration options.
3. A variety of smaller, related changes to try to make some of these configuration changes work a bit smoother.

See the comments on df4194c for more details.

Thanks again for the PR!

from chezscheme.