Default compiler suite (was
blair at orcaware.com
Sun Sep 2 17:51:52 PDT 2007
Ryan Schmidt wrote:
> On Sep 2, 2007, at 12:11, Weissmann Markus wrote:
>> On 01.09.2007, at 22:52, Ryan Schmidt wrote:
>>> On Sep 1, 2007, at 12:45, Landon Fuller wrote:
>>>> On Sep 1, 2007, at 6:07 AM, Weissmann Markus wrote:
>>>>> 'portconfigure.tcl' from trunk will chose a default for darwin
>>>>> 7/8/9 (gcc3.3/4.0/4.0). Please test it! Just replacing
>>>>> /opt/local/share/macports/Tcl/port1.0/portconfigure.tcl with
>>>>> manually should do the trick.
>>>>> This version also fixes a bug that when using configure.compiler
>>>>> every user-added compiler selection (e.g. 'configure.cc /bin/true')
>>>>> was overwritten.
>>>> This is going to break ports that require a different compiler, but
>>>> specify the compiler using configure.env, or arguments to configure
>>>> via configure.args.
>>> Then we should start cleaning ports. All those that specify a
>>> different compiler via configure.env should be updated to use
>>> configure.cc, etc. Those that use configure.args (or build.args I've
>>> also seen) should... I don't know, be tested to see if they can
>>> instead use configure.cc (or build.cc, etc.; do we have that?).
>> Indeed. "configure.env" is not officially supported anymore anyway...
>> some ports cant do without, but most can. Please everybody clean your
> Why isn't configure.env supported anymore?
Yes, the qt3-mac port needs it, and actually, the it's been broken for a while
due to the configure.env and build.env not honoring it.
If somebody could fix MacPorts (and not the Portfile) to honor it, I would
See this ticket for information on when the *.env broke:
Blair Zajac, Ph.D.
CTO, OrcaWare Technologies
<blair at orcaware.com>
Subversion training, consulting and support
More information about the macports-dev