Opened 7 months ago

Closed 6 months ago

#69559 closed defect (fixed)

libgcc13 @13.2.0_4: won't build

Reported by: rbeyer (Ross Beyer) Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.9.1
Keywords: Cc: MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Port: libgcc13

Description

I have a new M3 Max system running macOS 14.3.1 and I was going about installing my "usual" first MacPorts, which includes ImageMagick, and ran into this problem. ImageMagick wouldn't install because libgcc13 won't build. I did a clean --all and tried libgcc13 on its own, and got the same result.

There are a lot of warnings about possible linker errors, but the errors in the attached log are about missing semi-colons and what it considers to be incorrect argument signatures.

I've had some other issues with getting ports built on this new system.

Attachments (1)

libgcc13_main.log (9.3 MB) - added by rbeyer (Ross Beyer) 7 months ago.
main.log after port clean --all libgcc13

Change History (6)

Changed 7 months ago by rbeyer (Ross Beyer)

Attachment: libgcc13_main.log added

main.log after port clean --all libgcc13

comment:1 Changed 7 months ago by kencu (Ken)

although it's useful having you find all these new build issues on the latest system installation, and all these will in course of time get fixed ---

your life will be 1000x easier if you just used the default prefix of /opt/local and installed all the prebuilt binaries.

I presume there is some good reason you aren't doing that.

Homebrew, for example, provides no support for users building from source. These new build issues only really get found when something is updated -- at that point in time, it is confirmed to build (and fixed to build) as widely as possible by the person doing the updating, and binaries are built and stored on the binaries server.

Until the next time the port is updated by a MacPorts contributor, building it on your own is a crapshoot. It may, it may not, depending on many different things (system updates, dependency updates, etc).

So -- you are going to see LOTS of problems building everything yourself in your custom prefix, just so you know.

Sure, they all will get fixed in time. It's just a question of whether you have the stomach for the heartburn you will be going through.

comment:2 Changed 7 months ago by kencu (Ken)

in this particular case, it looks to me like gcc13 won't build yet against the very latest MacOSX14.sdk.

Iain will probably have to fix that and provide us with some more patches. Let me take a look and see if he has done that yet.

comment:3 in reply to:  1 Changed 7 months ago by ryandesign (Ryan Carsten Schmidt)

Replying to kencu:

Homebrew, for example, provides no support for users building from source.

MacPorts, of course, does support building from source.

comment:4 Changed 6 months ago by rbeyer (Ross Beyer)

This problem appears to have been addressed. After a fresh port selfupdate today this port now builds under these conditions. Thank you.

comment:5 Changed 6 months ago by ryandesign (Ryan Carsten Schmidt)

Cc: MarcusCalhoun-Lopez added
Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.