On 2019-10-10 07:28 , Ryan Schmidt wrote:
>
>
> On Oct 9, 2019, at 12:04, Ken Cunningham wrote:
>
>> On Tue, Oct 8, 2019 at 1:59 AM Ryan Schmidt wrote:
>>
>>> No... it's the other way around...
>>>
>>> If you want to modify LDFLAGS, do so by modifying configure.ldflags.
>>> MacPorts will set th
On 2019-10-09, at 1:28 PM, Ryan Schmidt wrote:
> do whatever additional work is necessary to communicate that variable to the
> build system, e.g. by using `build.args-append LDFLAGS="${configure.ldflags}
> [get_canonical_archflags ld]"` or whatever.
>
Perhaps I'll try a new approach to thi
Mark Anderson wrote:
> Sorry I was a bit short there. What I mean is to use the mailing list. I’m
> not certain when we’re going to release the 10.15 installer. My best advice
> for now is to install it from source using the 2.6.0 tag on the macports-base
> repo.
2.6.1 is current. You should
On Oct 9, 2019, at 12:04, Ken Cunningham wrote:
> On Tue, Oct 8, 2019 at 1:59 AM Ryan Schmidt wrote:
>
>> No... it's the other way around...
>>
>> If you want to modify LDFLAGS, do so by modifying configure.ldflags.
>> MacPorts will set the LDFLAGS environment variable to the value of
>> c
Sorry I was a bit short there. What I mean is to use the mailing list. I’m
not certain when we’re going to release the 10.15 installer. My best advice
for now is to install it from source using the 2.6.0 tag on the
macports-base repo.
On Wed, Oct 9, 2019 at 3:34 PM Omer An wrote:
> I am not sure
Catalina has been released, please use the lists now.
On Wed, Oct 9, 2019 at 3:31 PM Omer An wrote:
> Hi,
>
> Any news when will the Macports installer for Catalina be available?
>
> Thanks.
> Best.
>
>
>
> Ömer AN, PhD
> Bioinformatician Research Scientist
> Cancer Science Inst
Quite right, and that's of course what I usually do. And it works most of
the time.
But in some cases, ports don't run a configure phase, or it is not fully
honored due to internal software tricks or malfeasance, or similar. So it
is necessary to get the extra variables into the environment direct
I wouldn't suggest raising an error. It's certainly useful to do at times.
Lots of software doesn't run a configure phase, for example.
I still don't think we have this properly sorted out. Look at what Marcus
had to do here, for example <
https://github.com/macports/macports-ports/pull/5463/commi
