Opened 3 years ago

Closed 2 years ago

#63312 closed defect (fixed)

gcc11: jit build failure on macOS 11: Bootstrap comparison failure

Reported by: i0ntempest Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.7.1
Keywords: Cc: cjones051073 (Chris Jones), kencu (Ken), cooljeanius (Eric Gallager)
Port: gcc11

Attachments (1)

gcc11.main.log.txt.gz (2.3 MB) - added by mouse07410 (Mouse) 3 years ago.

Change History (12)

Changed 3 years ago by mouse07410 (Mouse)

Attachment: gcc11.main.log.txt.gz added

comment:1 Changed 3 years ago by mouse07410 (Mouse)

Concur - same problem here. :-(

:info:build Comparing stages 2 and 3
:info:build warning: gcc/cc1obj-checksum.o differs
:info:build warning: gcc/cc1objplus-checksum.o differs
:info:build Bootstrap comparison failure!
:info:build gcc/jit/jit-recording.o differs
:info:build make[2]: *** [compare] Error 1
:info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/gcc11/work/build'
:info:build make[1]: *** [stage3-bubble] Error 2
:info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/gcc11/work/build'
:info:build make: *** [bootstrap-lean] Error 2
:info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/gcc11/work/build'
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/gcc11/work/build" && /usr/bin/make -j20 -w bootstrap-lean 
:info:build Exit code: 2
:error:build Failed to build gcc11: command execution failed

Consistent on different machines (different CPUs, but all Intel and running macOS 11.5.1 with Xcode-12.5.1).

comment:2 Changed 3 years ago by i0ntempest

Cc: kencu added

Adding C expert Ken in to see if he got any ideas

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

Description: modified (diff)

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

Just pushed

https://github.com/macports/macports-ports/commit/22eeac18aba56f3c4d9edb7b62151dc90c720aab#diff-76e6422da629a86ac355b575a860262565d29a16740e1593f6d21f06fb394828

which for now disabled the jit build on Darwin 20+.

Lets leave this ticket open so can track a future fix to try and re-enable jit.

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

Summary: gcc11: build failure on macOS 11: Bootstrap comparison failuregcc11: jit build failure on macOS 11: Bootstrap comparison failure

comment:6 Changed 3 years ago by wyuenho (Jimmy Yuen Ho Wong)

Disabling jit broke emacs-devel and emacs-app-devel now. Are we able to revert gcc11 to the previous version?

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

Not without bumping the epoch which I would like to avoid. Long term, we should alway keep up with the latest versions so that is also not a solution.

I would prefer to focus on fixing the issue with 11.2. I just didn't have time to do so right now so temporarily disabled jit. Please feel free to investigate yourself.

Last edited 3 years ago by cjones051073 (Chris Jones) (previous) (diff)

comment:8 Changed 3 years ago by kencu (Ken)

the approach to these bootstrap comparison failures used by upstream is to disassemble the two non-matching objects and diff them. Then sort out what went wrong to make them different.

99% of them I have seen relate to different debugging format assumptions, but other hiccups can happen.

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

I've added a comment to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100340 to say the --without-build-config workaround no longer works properly. Lets see what they say.

comment:10 Changed 3 years ago by cooljeanius (Eric Gallager)

Cc: cooljeanius added

comment:11 Changed 2 years ago by cjones051073 (Chris Jones)

Resolution: fixed
Status: newclosed

Should be fixed in the latest builds.

Note: See TracTickets for help on using tickets.