Hi all,
I've got an iMac Pro in my LAN with 16 vCores and 64GB or RAM which is
quite often idle.
I'm not privy with how our build system work, but if we could get to a
point where agents can be added, stopped, throttled, trusted members of our
community could volunteer the computational power they
I can definitely donate the facilities if not the talent.
I have a symmetrical fiber connection and a static ip. I also have battery
backup.
I’m in the final weeks of making the building legal and I haven’t configured
the final network set-up for the building. I was going to set-up a vlan on my
The MPI wrapper ports (openmpi, mpich) for Xcode avoid binary archives from
builders. The stated reason (currently in the mpiutil 1.0 portgroup) is that
the builder and user may have different Xcode versions. This goes back at least
to https://github.com/macports/macports-ports/commit/7c6fc1faa9
It’s quite possible that those binaries will work without issue. But without
further testing and validation - across all supported macOS releases (10.6
through Big Sur) - we simply can’t say for sure.
That being said, if our LLVM/toolchain experts (KenC, JeremyHu, etc) think it’s
safe, we can a
It was an issue where when the xcode versions were not aligned on the
builder and user that the resulting binary package did not work correctly.
I really can't speak to if this is still an issue we would run into; we
could always try re-enabling pre-compiled usage and see if anyone runs into
it ag
On May 20, 2021, at 11:51, Eric Borisch wrote:
> It was an issue where when the xcode versions were not aligned on the builder
> and user that the resulting binary package did not work correctly.
>
> I really can't speak to if this is still an issue we would run into; we could
> always try re-e
On May 19, 2021, at 19:22, Bjarne D Mathiesen wrote:
> #=> port outdated
> The following installed ports are outdated:
> snort 2.9.17_0 < 2.9.17.1_0
> root@MacPro 02:05:26 /Library/LaunchDaemons
> #=> port -cuNp upgrade snort
> ---> Computing dependencies for snort
> --->
On May 19, 2021, at 07:56, Bjarne D Mathiesen wrote:
> Ryan Schmidt wrote:
>> I personally am not comfortable adding other build machines to our buildbot
>> system that I do not control. When I control the machines, I know what is
>> installed on them and that they are set up correctly. Having b
On May 19, 2021, at 10:01, David Gilman wrote:
> but maybe the right mindset here is to do the best with what we've got.
We do, and have, for over ten years.
On May 17, 2021, at 06:13, Mojca Miklavec wrote:
> On Mon, 17 May 2021 at 10:39, Ruben Di Battista wrote:
>>
>> Just as a side note, here in France I just created a non-profit association
>> for a project I'm working on related to the organization of an event, and
>> the process is almost free
On May 19, 2021, at 12:38, Andrew Janke wrote:
> I have a small stack of Mac Minis I got to use as a buildbot farm for
> Octave.app; I might be able to have them pull double duty for MacPorts
> depending on your change volume.
On May 20, 2021, at 08:10, Enrico Maria Crisostomo wrote:
> I've g
On May 17, 2021, at 21:00, Perry E. Metzger wrote:
> On 5/17/21 19:06, Ryan Schmidt wrote
Meh. They have different priorities than we do. No reason for us to follow
what they do.
>>> In this instance, though, I think their reasoning is correct.
>> So you would like MacPorts to delete al
12 matches
Mail list logo