python portfile issue with running setup.py twice

[Joshua Root]

On 2010-10-1 04:28 , Ryan Schmidt wrote:
> On Sep 29, 2010, at 13:54, Joshua Root wrote:
>> On 2010-9-30 03:48 , Ryan Schmidt wrote:
>>>
>>> This, and the problem before it with the python library, apparently both stem from setting LDFLAGS, which the python26 portgroup does. According to the following post, setting LDFLAGS overrides vital settings, contrary to how we expect LDFLAGS to work, which is to append settings to those already defined by the software.
>>>
>>> http://mail.scipy.org/pipermail/scipy-dev/2009-November/013414.html
>>>
>>> So, the python26 portgroup appears to need some changes to not set LDFLAGS like that.
>>
>> You mean like "python.add_archflags no"?
> 
> Well, perhaps. But it seems like ANY adding of LDFLAGS in ANY case would be enough to cause a problem, for some python modules that use LDFLAGS for their own purpose.
> 
> See, this problem was just reported again against py26-numpy:
> 
> http://lists.macosforge.org/pipermail/macports-users/2010-September/022078.html

These two modules treat LDFLAGS in the environment differently than
every normal distutils setup.py does, as the very message you linked to
above acknowledges. There's nothing wrong with the portgroup here.

- Josh