Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#51789 closed defect (fixed)

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

Reported by: dliessi (Davide Liessi) Owned by: mww@…
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: mndavidoff (Monte Davidoff), chrisjogorman, jeremyhu (Jeremy Huddleston Sequoia), home@…, gnw3, kobayos
Port: libgcc, gcc5

Description


Attachments (2)

main.log.bz2 (45.6 KB) - added by dliessi (Davide Liessi) 8 years ago.
main.log.2.bz2 (4.3 KB) - added by home@… 8 years ago.
log file for port gcc5 returned: command execution failed

Download all attachments as: .zip

Change History (19)

Changed 8 years ago by dliessi (Davide Liessi)

Attachment: main.log.bz2 added

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

Cc: mww@… removed
Keywords: snowleopard added
Owner: changed from macports-tickets@… to mww@…

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

Cc: md14-macports@… chrisgorman@… jeremyhu@… added
Keywords: snowleopard removed
Port: libgcc added
Summary: gcc5 @5.4.0_0: build failure on Snow Leopardgcc5 @5.4.0_0: ld: warning: could not create compact unwind for __Unwind_RaiseException: non-standard register 0 being saved in prolog

Has duplicates #51795, #51810. Jeremy?

comment:3 Changed 8 years ago by jeremyhu (Jeremy Huddleston Sequoia)

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

comment:4 Changed 8 years ago by 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.

comment:5 in reply to:  3 Changed 8 years ago by 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?

comment:6 Changed 8 years ago by 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.

Changed 8 years ago by home@…

Attachment: main.log.2.bz2 added

log file for port gcc5 returned: command execution failed

comment:7 Changed 8 years ago by home@…

Cc: home@… added

Cc Me!

comment:8 Changed 8 years ago by jeremyhu (Jeremy Huddleston Sequoia)

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

comment:9 Changed 8 years ago by gnw3

Cc: gnwiii@… added

Cc Me!

comment:10 Changed 8 years ago by kobayos

Cc: kobayos@… added

Cc Me!

comment:11 Changed 8 years ago by 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.

comment:12 Changed 8 years ago by 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)

comment:13 in reply to:  12 Changed 8 years ago by 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)

comment:14 Changed 8 years ago by dliessi (Davide Liessi)

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

comment:15 Changed 8 years ago by dliessi (Davide Liessi)

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

comment:16 Changed 8 years ago by jeremyhu (Jeremy Huddleston Sequoia)

Resolution: fixed
Status: newclosed

So this is fixed then, yes?

comment:17 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)

Has duplicate #49258.

Note: See TracTickets for help on using tickets.