Opened 4 years ago

Closed 4 years ago

#59523 closed defect (wontfix)

libgcc-devel @10-20191006: error: expected initializer before '__OSX_AVAILABLE_STARTING'

Reported by: dlamija (Muhammed Ramiza) Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.6.2
Keywords: catalina Cc:
Port: libgcc-devel

Description 

006/libstdc++-v3/libsupc++/del_opnt.cc:38:
/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/sys/resource.h:443:34: error: expected initializer before '__OSX_AVAILABLE_STARTING'
  443 | int     getiopolicy_np(int, int) __OSX_AVAILABLE_STARTING(__MAC_10_5, __IPHONE_2_0);
      |                                  ^~~~~~~~~~~~~~~~~~~~~~~~
/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/sys/resource.h:449:39: error: expected initializer before '__OSX_AVAILABLE_STARTING'
  449 | int     setiopolicy_np(int, int, int) __OSX_AVAILABLE_STARTING(__MAC_10_5, __IPHONE_2_0);
      |

Change History (3)

comment:1 Changed 4 years ago by mf2k (Frank Schima)

Keywords: catalina added; Catalina removed

comment:2 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)

Summary: libgcc-devel @10-20191006 failed to buuild on 10.15.1 → libgcc-devel @10-20191006: error: expected initializer before '__OSX_AVAILABLE_STARTING'

comment:3 Changed 4 years ago by cjones051073 (Chris Jones)

Resolution: → wontfix
Status: new → closed

Not unexpected. gcc10 is a development versions, the port is there just to allow testing of gcc snapshots. Its not intended to be a production compiler, for that I recommend using gcc9 instead.

The issues affecting the gcc builds are discussed in detail in

​https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90835

​https://github.com/macports/macports-ports/commit/368383b4263282656853b68965c3db455333c5bd#diff-bf5951877cf7f70968394fcc87aa5721

I guess the fixes upstream are developing are not in the gcc10 snapshot currently being built. I will update that to a newer one, but whether or not it works on macOS10.15, you should use a production release version instead, unless you specifically need to test the gcc snapshots.

Note: See TracTickets for help on using tickets.