<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font size="2">But this suggest me another question, do macports
binaries upload from my computer the results of the compilation
that happened, to help the community in later installations ?</font><br>
</p>
<div class="moz-cite-prefix">Le 29/10/2024 à 10:28, Fabien Auréjac a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:54262f04-9ceb-4f44-adc0-b73bd10ccd74@gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p><font size="2">Thank you, I was not aware of this. Excuse me
for the mistake, I'm quite new to </font><font size="2">
language </font><font size="2">compilation concepts.<br>
</font></p>
<div class="moz-cite-prefix">Le 29/10/2024 à 10:23, Chris Jones
via macports-users a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:a338cc94-d776-4300-a7dc-82153682249f@hep.phy.cam.ac.uk"> <br>
<br>
On 29/10/2024 1:11 am, Fabien Auréjac wrote: <br>
<blockquote type="cite">Hello, after upgrading to Sequoia, all
worked flawlessly without need of anything, but when I tried
to update macports via port selfupdate, it asked for a
migration. <br>
<br>
All seems to be working well, but I'm quite surprised about
the time it takes... for 500+ ports, more than 8 hours of
compilation on a macMini M1, and it's not finished...? <br>
<br>
On Sonoma compiling seemed to be really faster... Is this due
to the process of migration ? <br>
<br>
Or is it a regression of performance due to some sort of macOS
performance or security clamping ? <br>
</blockquote>
<br>
You are comparing Apples with Oranges... Currently there are no
binary tarballs for any ports on macOS15 with arm, as the
buildbot has not yet been commissioned. So consequently you have
to build everything from source which obviously takes a lot
longer than a binary install. macOS14 arm does have binary
tarballs. <br>
<br>
Chris <br>
</blockquote>
</blockquote>
</body>
</html>