Opened 3 years ago
Closed 3 years ago
#62903 closed defect (wontfix)
libgcc11 consuming large amounts of CPU and memory resources
| Reported by: | conradwt (Conrad Taylor) | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.6.4 |
| Keywords: | Cc: | cjones051073 (Chris Jones) | |
| Port: | libgcc11 |
Description
After performing sudo port install libgcc11, I noticed the libgcc11 is consuming a large amount of CPU and memory resources. Please see the attachments. Also, I noticed the following warning during the configuration process:
---> Configuring libgcc11 Warning: Applying '--without-build-config' workaround to Xcode 12.5 / CLT 12.5.0.0.1.1617976050 Warning: If versions > 12.5 please check if it is still required
Also, I noticed that there isn't a port maintainer listed and it takes over 30+ minutes to build this port on a MacBook Pro 15" (late 2013). I feel that any port that takes > 10 minutes to install should be installed as a binary instead of built from source.
Attachments (2)
Change History (6)
Changed 3 years ago by conradwt (Conrad Taylor)
| Attachment: | Screen Shot 2021-05-16 at 11.57.42 AM.png added |
|---|
Changed 3 years ago by conradwt (Conrad Taylor)
| Attachment: | Screen Shot 2021-05-16 at 12.06.23 PM.png added |
|---|
Memory Consumption Screenshot
comment:1 Changed 3 years ago by conradwt (Conrad Taylor)
| Priority: | Normal → High |
|---|
comment:2 Changed 3 years ago by reneeotten (Renee Otten)
| Keywords: | macOS 11.3.1 removed |
|---|---|
| Priority: | High → Normal |
well, building libgcc11 takes time, there is probably not much to do about that. You should get a binary though, provided that the buildbot had the time to build it already... If you do a port selfupdate and port upgrade outdated and the Portfile has been updated but the buildbot didn't finish yet for your OS, it will indeed build it from source.
There is some configuration option that you can set to only get binaries, or you can use the -b flag if you only want to use this occasionally. Of course that will prevent you to update/install any ports that can only be built from source.
comment:3 Changed 3 years ago by jmroot (Joshua Root)
| Cc: | cjones051073 added |
|---|
comment:4 Changed 3 years ago by cjones051073 (Chris Jones)
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
The buildbots sometimes have a backlog of ports to build, so depending on when you run your update, and when a particular commit was made, its always possible you will have to build from source something that later on will be available as a binary tarball. This I am afraid is inevitable. If you want to delay updating until a binary tarball is ready, just take a look at
CPU screenshot