Opened 5 years ago
Last modified 4 years ago
#58260 closed defect
libgcc8 build fails due to "Atomic" error on Mojave — at Initial Version
| Reported by: | physicsbeany | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.5.4 |
| Keywords: | mojave | Cc: | |
| Port: | gcc9 gcc8 gcc7 gcc6 libgcc-devel libgcc8 libgcc7 libgcc6 |
Description
Recently upgraded to MacOS Mojave from High Sierra, and followed general Macports instructions for migrating my old ports. Things went fine until libgcc8 (needed to do my py27-scipy installation). Initially, this failed because of Unwind issues. I solved this by following the advice in ticket #57198.
Now, however, the compilation fails because of an "Atomic" error. Specifically, the first instance of the Error in the log file is:
:info:build /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/ucred.h:94:2: error: '_Atomic' does not name a type :info:build _Atomic u_long cr_ref; /* reference count */
Full logfile attached
Some Googling indicates that this may be avoided by defining STDC_NO_ATOMICS, but I'm not certain this is the right answer (and I don't know how to do this as part of a Macports installation).
Change History (1)
Changed 5 years ago by physicsbeany
| Attachment: | libgcc8_INSTALLFAILURE_TRUNCATED.log added |
|---|
Note: See
TracTickets for help on using
tickets.
last 50K lines of log file (whole thing is 64 MB)