Opened 3 years ago

Last modified 3 years ago

#45681 assigned defect

libgcc @4.9.2: build fails with 10 parallel jobs

Reported by: michelle.lynn.gill@… Owned by: larryv (Lawrence Velázquez)
Priority: Normal Milestone:
Component: ports Version: 2.3.2
Keywords: mavericks Cc: mww@…
Port: libgcc

Description

I am attempting to compile libgcc on 10.9.5 with Xcode 6.1.

The errors seem to start around line 2747 and pertain to the file system.h:

:info:build In file included from /Volumes/Files/macports/var/macports/build/_Volumes_Files_macports_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc49/libgcc/work/gcc-4.9.1/gcc/gcc-ar.c:22:
:info:build /Volumes/Files/macports/var/macports/build/_Volumes_Files_macports_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc49/libgcc/work/gcc-4.9.1/gcc/system.h:506:20: error: functions that differ only in their return type cannot be overloaded
:info:build extern const char *strsignal (int);
:info:build                    ^
:info:build /usr/include/string.h:134:7: note: previous declaration is here
:info:build char    *strsignal(int sig);
:info:build          ^
:info:build rm -f mm_malloc.h
:info:build TARGET_CPU_DEFAULT="" \
:info:build 	HEADERS="auto-host.h ansidecl.h" DEFINES="USED_FOR_TARGET " \
:info:build 	/bin/sh /Volumes/Files/macports/var/macports/build/_Volumes_Files_macports_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc49/libgcc/work/gcc-4.9.1/gcc/mkconfig.sh tconfig.h
:info:build cat /Volumes/Files/macports/var/macports/build/_Volumes_Files_macports_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc49/libgcc/work/gcc-4.9.1/gcc/config/i386/gmm_malloc.h > mm_malloc.h
:info:build In file included from /Volumes/Files/macports/var/macports/build/_Volumes_Files_macports_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc49/libgcc/work/gcc-4.9.1/gcc/gcc-ar.c:22:
:info:build In file included from /Volumes/Files/macports/var/macports/build/_Volumes_Files_macports_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc49/libgcc/work/gcc-4.9.1/gcc/system.h:1064:
:info:build /Volumes/Files/macports/var/macports/build/_Volumes_Files_macports_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc49/libgcc/work/gcc-4.9.1/gcc/hwint.h:244:12: error: use of undeclared identifier 'CHAR_BIT'
:info:build     return HOST_BITS_PER_WIDE_INT;
:info:build            ^
:info:build /Volumes/Files/macports/var/macports/build/_Volumes_Files_macports_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc49/libgcc/work/gcc-4.9.1/gcc/hwint.h:60:35: note: expanded from macro 'HOST_BITS_PER_WIDE_INT'
:info:build #   define HOST_BITS_PER_WIDE_INT HOST_BITS_PER_LONG
:info:build                                   ^

There are many of the "use of undeclared identifier" errors, so I've only pasted the first couple.

I do not see any related libgcc errors listed in open tickets, so I believe this is a new error.

This is for a new MacPorts installation (non-default path) on a Mac Pro running Mavericks. I was able to compile libgcc with my laptop using Xcode 6.1 on Yosemite just fine.

Please let me know if I can provide further info.

Attachments (7)

main.log (388.4 KB) - added by michelle.lynn.gill@… 3 years ago.
main_libgcc4.9.2.log (417.9 KB) - added by michelle.lynn.gill@… 3 years ago.
Log from build of version 4.9.2 of libgcc
main_libgcc_4.9.2_buildjob1.log (20.7 MB) - added by michelle.lynn.gill@… 3 years ago.
Log from successful build of libgcc 4.9.2 with one thread.
main_libgcc4.9.2_buildjobs8.log (20.7 MB) - added by michelle.lynn.gill@… 3 years ago.
Build log from successful build with 8 threads
main_libgcc4.9.2_buildjobs10.log (415.5 KB) - added by michelle.lynn.gill@… 3 years ago.
Build log from unsuccessful build with 10 threads
main_libgcc4.9.2_buildjobs10_try2.log (417.3 KB) - added by michelle.lynn.gill@… 3 years ago.
Tray #2 at attaching the build log of 10 threaded build
config_libgcc4.9.2_buildjobs10_try2.tgz (93.2 KB) - added by michelle.lynn.gill@… 3 years ago.
Config logs from second attempt at 10 threaded build

Change History (24)

comment:1 Changed 3 years ago by michelle.lynn.gill@…

Please wait to investigate this ticket--after posting, I discovered that an OS update hadn't actually installed and I was previously running 10.9.4. Though I'm sure I downloaded the correct command line tools from Apple, the update did included changes to the command tools, so I've restarted the build. I will update on its success or failure. I apologize for the mistake on my part.

comment:2 Changed 3 years ago by michelle.lynn.gill@…

Update--the build still fails for me and the errors look similar. I am going to replace the log file with the one from the correctly updated version of Mavericks.

Last edited 3 years ago by michelle.lynn.gill@… (previous) (diff)

Changed 3 years ago by michelle.lynn.gill@…

comment:3 Changed 3 years ago by mf2k (Frank Schima)

  • Owner changed from macports-tickets@… to mww@…

In the future, please Cc the port maintainers (port info --maintainers libgcc).

comment:4 Changed 3 years ago by larryv (Lawrence Velázquez)

  • Cc larryv@… added

Cc Me!

comment:5 Changed 3 years ago by michelle.lynn.gill@…

Any update on this or can I provide more information? I ended up having to install Yosemite on this Mac Pro and then had to roll back to Mavericks. In the course of this process, I was able to further verify that libgcc builds fine with Xcode 6.1 on Yosemite, but it again failed to build on Mavericks. I was also able to verify that I have to install MacPorts in a custom location and, thus, need to build libgcc from source. Unfortunately, MacPorts gcc (and, thus, libgcc) are required for the primary ports that I use and, though I like to troubleshoot many of my MacPorts installation issues, I think this one is over my head. Thank you.

comment:6 Changed 3 years ago by larryv (Lawrence Velázquez)

  • Cc mww@… added; larryv@… removed
  • Keywords mavericks added
  • Owner changed from mww@… to larryv@…
  • Status changed from new to assigned

I’ll try to look into this within the next day or two.

comment:7 Changed 3 years ago by michelle.lynn.gill@…

Thank you--greatly appreciated. I'm quite proficient at tinkering with ports, so I'm happy to help test patches if you don't have a system available.

comment:8 follow-up: Changed 3 years ago by michelle.lynn.gill@…

Any luck with this? Thank you!

comment:9 in reply to: ↑ 8 Changed 3 years ago by larryv (Lawrence Velázquez)

I’m sorry, I got caught up in some other things and haven’t looked at this yet. I did just update libgcc to 4.9.2; could you try to reproduce the issue with the new version?

comment:10 follow-up: Changed 3 years ago by michelle.lynn.gill@…

No problem. The build of libgcc 4.9.2 also fails, unfortunately. There are similar "use of undeclared identifier" errors that start around line 3144. I've attached the updated log if that's helpful. If for some reason you think this is a different issue with 4.9.2, I'm happy to open a different ticket. Just let me know.

Last edited 3 years ago by michelle.lynn.gill@… (previous) (diff)

Changed 3 years ago by michelle.lynn.gill@…

Log from build of version 4.9.2 of libgcc

comment:11 in reply to: ↑ 10 Changed 3 years ago by larryv (Lawrence Velázquez)

It looks like the same error, but I can’t reproduce it in my Mavericks VM. Could you post a log from a single-threaded build? It’s hard to compare parallelized logs.

$ sudo port clean libgcc
$ sudo port build libgcc build.jobs=1

comment:12 follow-up: Changed 3 years ago by michelle.lynn.gill@…

Interestingly, when I performed the build job with one thread, it completed without error. I was then able to successfully install the results of the single-threaded build. I did manage to save the log from the single-threaded build and will upload it. If you'd like me to test anything else, just let me know. I'm happy to help.

Thank you for your assistance thus far, too.

Changed 3 years ago by michelle.lynn.gill@…

Log from successful build of libgcc 4.9.2 with one thread.

comment:13 in reply to: ↑ 12 Changed 3 years ago by larryv (Lawrence Velázquez)

Replying to michelle.lynn.gill@…:

Interestingly, when I performed the build job with one thread, it completed without error.

Huh. You do have quite a few logical cores; I have 8 but never encountered this issue. Can you reliably reproduce the failure with parallel building? Perhaps the makefile dependency graph isn’t quite right.

comment:14 follow-up: Changed 3 years ago by michelle.lynn.gill@…

I just tried with

port build libgcc build.jobs=8

and

port build libgcc build.jobs=10

The one with 8 threads works fine (consistent with your findings), but the one with 10 didn't. The errors in the build with 10 threads are similar to the ones I saw before. I've uploaded both logs.

Also interesting to note--I briefly had Yosemite on this computer and was running MacPorts configured in the same way. There was no problem building libgcc there with all of the cores.

If I can test other scenarios, let me know.

Changed 3 years ago by michelle.lynn.gill@…

Build log from successful build with 8 threads

Changed 3 years ago by michelle.lynn.gill@…

Build log from unsuccessful build with 10 threads

comment:15 in reply to: ↑ 14 Changed 3 years ago by larryv (Lawrence Velázquez)

The 10-thread log is incomplete; could you clean and upload a new one? Could you also upload the config.log files? You can archive them into one file, if you’d like.

% find $(port work libgcc)/build -name config.log

comment:16 Changed 3 years ago by michelle.lynn.gill@…

Sorry for the delay--I was away for the holiday. I have rebuilt libgcc with 10 build jobs and attached the log and a tar/gzipped archive of all the config.log files.

Changed 3 years ago by michelle.lynn.gill@…

Tray #2 at attaching the build log of 10 threaded build

Changed 3 years ago by michelle.lynn.gill@…

Config logs from second attempt at 10 threaded build

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

  • Summary changed from libgcc fails to build on Mavericks 10.9.5 with XCode 6.1 to libgcc @4.9.2: build fails with 10 parallel jobs
Note: See TracTickets for help on using tickets.