barebones config file

[Mark Brethen]

> On Nov 22, 2015, at 3:28 PM, Ryan Schmidt <ryandesign at macports.org> wrote:
> 
> 
> On Nov 21, 2015, at 4:46 PM, Mark Brethen wrote:
> 
>> I have source that uses perl and a simple configure script like so:
>> 
>> #! /bin/sh
>> # thunk
>> 
>> exec perl -wS ./configure.pl ${1+"$@"}
>> 
>> The configure phase fails since it doesn’t know what to do with the prefix. I can override this, but what about env variables?
>> 
>> <configure.pl><main.log>
> 
> What about the env variables? Are the env variables MacPorts sets at configure time interfering with this configure script in some way?
> 
> I'm confused by the log you attached because it does not contain an "Assembled command" line for the configure phase. Are you overriding the configure phase? If so, why?
> 

It does not appear that the env variables are set as the Makefile generated contained gcc, g++ etc. I followed https://trac.macports.org/wiki/UsingTheRightCompiler and replaced with "$(CC)” etc. in the Makefile, in combination with setting ${build.args}. Attached is a recent build log. Now I’m having to deal with failures associated with bison.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: main.log
Type: application/octet-stream
Size: 20758 bytes
Desc: not available
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20151122/93e6f372/attachment-0001.obj>
-------------- next part --------------


Mark