gcc5 @5.4.0_0: ld: warning: could not create compact unwind for __Unwind_RaiseException: non-standard register 0 being saved in prolog

[ryandesign (Ryan Carsten Schmidt)]

Has duplicates #51795, #51810. Jeremy?

[jeremyhu (Jeremy Huddleston Sequoia)]

What's the output of /opt/local/bin/ld -v? Can you try a different variant of ld64?

[jeremyhu (Jeremy Huddleston Sequoia)]

Witout much triage, I'm assuming that this is somehow a regression from my recent ld64 bump. The above should possibly confirm that.

[dliessi (Davide Liessi)]

Replying to jeremyhu@…:

What's the output of /opt/local/bin/ld -v?

$ /opt/local/bin/ld -v
@(#)PROGRAM:ld  PROJECT:ld64-136
configured to support archs: i386 x86_64 armv7 armv7s
LTO support using: LLVM version 3.4.2

Can you try a different variant of ld64?

$ port installed ld64
The following ports are currently installed:
  ld64 @2_0+ld64_136 (active)

I'm on Snow Leopard. Should I try +ld64_236?

[home@…]

I'm experiencing the same issue and have this ld and am running on El Capitan 10.11.5

/opt/local/bin/ld -v
@(#)PROGRAM:ld  PROJECT:ld64-264.3.102
configured to support archs: i386 x86_64 x86_64h armv6 armv7 armv7s armv7m armv7k arm64 (tvOS)
LTO support using: LLVM version 3.3

main.log.bz2 attached.

[home@…]

log file for port gcc5 returned: command execution failed

[home@…]

Cc Me!

[jeremyhu (Jeremy Huddleston Sequoia)]

Ok, thanks. Then that means it's not because of changes in ld64.

[gnw3]

Cc Me!

[kobayos]

Cc Me!

[kobayos]

I am building gcc-6.1.0 by using tools that are installed by MacPorts on El Capitan 10.11.5 and experienced the same problems.

I could avoid this problem by reverting ld64-latest to 253.9_0+llvm37 and cctools to 877.8_0+llvm37.

If only ld64-latest is reverted to 253.9_0+llvm37, the problem was not solved.

I am wondering that this problem is caused by the latest cctools although I have not checked a case in which only cctools is reverted.

[mndavidoff (Monte Davidoff)]

After a selfupdate and rebuilding outdated ports, I was able to successfully build libgcc, gcc5, and gcc6. Recent changes may have fixed the problem.

$ port installed cctools gcc5 gcc6 ld64 ld64-latest libgcc
The following ports are currently installed:
  cctools @886_2+llvm37 (active)
  gcc5 @5.4.0_0 (active)
  gcc6 @6.1.0_0 (active)
  ld64 @2_0 (active)
  ld64-latest @264.3.102_0+llvm37 (active)
  libgcc @6.1.0_0 (active)

[home@…]

Replying to md14-macports@…:

After a selfupdate and rebuilding outdated ports, I was able to successfully build libgcc, gcc5, and gcc6. Recent changes may have fixed the problem.

$ port installed cctools gcc5 gcc6 ld64 ld64-latest libgcc
The following ports are currently installed:
  cctools @886_2+llvm37 (active)
  gcc5 @5.4.0_0 (active)
  gcc6 @6.1.0_0 (active)
  ld64 @2_0 (active)
  ld64-latest @264.3.102_0+llvm37 (active)
  libgcc @6.1.0_0 (active)

The issue has been resolved for me as well...

root# ./port installed cctools gcc5 gcc6 ld64 ld64-latest libgcc
The following ports are currently installed:
  cctools @886_1+llvm33+universal
  cctools @886_2+llvm33+universal (active)
  gcc5 @5.3.0_1+universal
  gcc5 @5.4.0_0+universal (active)
  ld64 @2_0+universal (active)
  ld64-latest @264.3.102_0+llvm33+universal (active)
  libgcc @6.1.0_0+universal (active)

[dliessi (Davide Liessi)]

After the latest selfupdate and upgrade outdated yesterday morning, I was able to build gcc5 @5.4.0_0 successfully.

[dliessi (Davide Liessi)]

(Just for the record, comment:14 is still by me: I was logged in with the wrong account.)

[jeremyhu (Jeremy Huddleston Sequoia)]

So this is fixed then, yes?

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #49258.