On Jul 19, 2016, at 7:13 AM, Ryan Schmidt wrote:

> On Jul 17, 2016, at 12:31 AM, Watson Ladd wrote:
> 
>> The problem is that
>> they want you to run configure with an argument indicating the install
>> prefix, then don't seem to support DESTROOT. I've gone to upstream to
>> report this, but I understand there is black magic we could use
>> instead.
> 
> Looking in 
> https://github.com/cisco/ChezScheme/blob/master/makefiles/Mf-install.in, it 
> looks like this project's Makefile supports a variable TempRoot which is 
> equivalent to what other projects call DESTROOT. So you can set:
> 
> destroot.destdir TempRoot=${destroot}

Sorry, I see I'm late to the party, and Josh already mentioned that this 
project's configure script has a flag for specifying temproot.

This is one of the problems with projects that roll their own nonstandard 
configure scripts and Makefiles -- they don't work the way anybody unfamiliar 
with that project expects. Developers would do well to adopt standard configure 
script and Makefiles made with autotools since everyone already knows how they 
work and using standardized well-tested tools like autotools avoids problems 
project developers may not even know exist.

_______________________________________________
macports-dev mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-dev

Reply via email to