> On Nov 22, 2015, at 10:22 PM, Mark Brethen <[email protected]> wrote:
>
>>>>>
>>>>> 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.
>>
>> Could you show me your portfile?
>>
>
> <Portfile>
Ok, so you have overridden the configure phase. Why?
configure {
system -W ${worksrcpath}/src "${configure.cmd}"
}
I'd instead use the default configure phase, just changing it to suit your
needs. For example, use:
configure.dir ${worksrcpath}/src
If this configure script doesn't understand --prefix=${prefix}, use:
configure.pre_args
If this configure script doesn't understand --disable-dependency-tracking, use:
configure.universal_args
Also, you should use the github portgroup, since this software is hosted at
github.
_______________________________________________
macports-dev mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-dev
