> On Feb 9, 2021, at 12:04 AM, Ken Cunningham
> wrote:
>
>
> PS — any feedback on the success of the cross building, or any failures
> encountered, would be much appreciated. I believe this is the only setup
> that currently allows meson cross building on BigSur that is available for
>
as meson was currently broken on older systems I pushed through a fix for this
just now.
We can revise it to whatever upstream wants to do when they get around to it,
if they want to do anything about it.
I took the opportunity to also add a cross file similar to the ones I added
previously
> On Feb 6, 2021, at 4:47 AM, Ryan Schmidt wrote:
>
>
>
> On Feb 6, 2021, at 02:14, Ken Cunningham wrote:
>
>> On Feb 5, 2021, at 10:04 PM, Ryan Schmidt wrote:
>>
>>> That sounds like what Craig is saying: that meson is now adding a compiler
>>> flag that old compilers don't understand.
On Feb 6, 2021, at 02:14, Ken Cunningham wrote:
> On Feb 5, 2021, at 10:04 PM, Ryan Schmidt wrote:
>
>> That sounds like what Craig is saying: that meson is now adding a compiler
>> flag that old compilers don't understand. Meson should check whether a
>> compiler supports a flag before it
> On Feb 5, 2021, at 10:04 PM, Ryan Schmidt wrote:
>
> That sounds like what Craig is saying: that meson is now adding a compiler
> flag that old compilers don't understand. Meson should check whether a
> compiler supports a flag before it adds it. We should not be responsible for
> fixing
On Feb 4, 2021, at 11:26, Ken Cunningham wrote:
> wait, I could have missed the issue...if meson is now adding a default
> argument to all checks that means it can never build anything with the
> default compilers on <10.10, that would be something we should consider
> fixing in meson, even
wait, I could have missed the issue...if meson is now adding a default argument
to all checks that means it can never build anything with the default compilers
on <10.10, that would be something we should consider fixing in meson, even if
upstream doesn't want to.
So if testing shows that all
successful build with current meson on 10.6
https://build.macports.org/builders/ports-10.6_x86_64-builder/builds/47455/steps/install-port/logs/stdio
On Feb 4, 2021, at 08:48, Craig Treleaven wrote:
>> On Feb 3, 2021, at 10:01 PM, Joshua Root wrote:
>>
>> On 2021-2-4 12:19 , Ken Cunningham
well don't forget it builds just fine with the current meson on 10.6 using
clang-9.0.
so...nothing to do with meson, I would say.
Really, let's just blacklist older clangs and move alonglife is short.
Ken
On Feb 4, 2021, at 08:48, Craig Treleaven wrote:
>> On Feb 3, 2021, at 10:01 PM,
> On Feb 3, 2021, at 10:01 PM, Joshua Root wrote:
>
> On 2021-2-4 12:19 , Ken Cunningham wrote:
>>> On Feb 3, 2021, at 11:49 AM, Craig Treleaven
>>> wrote:
>>>
>>> But configure still failed on 10.7 and 10.8:
>> Oh no! It looked so great! I was really learning some things there. Perhaps
>>
On 2021-2-4 12:19 , Ken Cunningham wrote:
On Feb 3, 2021, at 11:49 AM, Craig Treleaven wrote:
But configure still failed on 10.7 and 10.8:
Oh no! It looked so great! I was really learning some things there. Perhaps it
can be tweaked still.
If not, I guess we can still use the
> On Feb 3, 2021, at 11:49 AM, Craig Treleaven wrote:
>
> But configure still failed on 10.7 and 10.8:
Oh no! It looked so great! I was really learning some things there. Perhaps it
can be tweaked still.
If not, I guess we can still use the compiler_blacklist_versions approach and
That was a very nice fix...good to see how to do it properly now and then!
K
> On Feb 3, 2021, at 6:24 AM, Joshua Root wrote:
>
> On 2021-2-3 23:49 , Ken Cunningham wrote:
>> dav1d is failing on 10.7 and 10.8 on the configure test for atomic.
>> it's building on 10.6 with clang 9.0, so
On 2021-2-3 23:49 , Ken Cunningham wrote:
dav1d is failing on 10.7 and 10.8 on the configure test for atomic.
it's building on 10.6 with clang 9.0, so probably needs to blacklist clangs
older than 10.9's clang.
nothing to do with meson, looks to me...
It's claimed to be written in C99, but
sorry, another look, 10.9 fails so blacklist clangs older that 10.10's clang
should do it.
> On Feb 2, 2021, at 7:26 PM, Craig Treleaven wrote:
>
> Anyway, I have 'port test meson' running on my 10.10 system even though I
> don’t expect anything. I don’t have a working virtualization system at the
> moment. Perhaps tomorrow I can get that back up and try the tests on 10.9
> and
On Feb 2, 2021, at 18:27, Craig Treleaven wrote:
> In the dav1d PR, CI didn’t produce results for the older OS versions. I
> thought the CI system was just being grumpy.
Our CI system uses publicly available build infrastructure from GitHub, which
only offers build machines running current
Ken:
I wasn’t trying to suggest that anybody failed at anything. The problem may be
specific to dav1d...but if it was more general, I wanted to alert others.
That’s all; I meant no offence to anyone.
And I could see how this might escape notice since it only affects meson on
older OS
I will try it.
If I might say — I would expect that anyone submitting a PR has at least built
the software on their local system, and used it enough to be sure it at least
basically works, if not ran the whole test suite.
SO — meson must have worked properly on at least the system that was
Hi:
It might be that the meson update and/or the switch to python39 has broken
builds on older Mac OS versions. Specifically, I updated dav1d to 0.8.1 and it
no longer configures successfully on 10.9 and older versions. Upstream says
that the now-failing configure test (a simple test to see
20 matches
Mail list logo
