checking for buggy gcc versions... no checking for compiler version information... x86_64-pc-linux-gnu-gcc (Gentoo 9.2.0-r4 p5) 9.2.0 checking for standard C library version information... ls: cannot access '/lib/libc-*.so': No such file or directory checking for malloc_set_state... no checking whether __after_morecore_hook exists... yes ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_no-multilib-20200227-131806 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.2.0 * llvm: 9.0.1 Available Python interpreters, in order of preference: [1] python3.8 [2] python3.6 [3] python3.7 (fallback) [4] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) * ghc: The Glorious Glasgow Haskell Compilation System, version 8.0.2 repository: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Fri, 28 Feb 2020 02:12:36 +0000 emerge -qpvO app-editors/xemacs [ebuild N ] app-editors/xemacs-21.5.34-r4 USE="berkdb gdbm neXt png -X -Xaw3d -alsa -athena -canna -debug -dnd -eolconv -freewnn -gif -gpm -jpeg -ldap -libressl -motif -mule -nas -pop -postgres -tiff -xface -xft -xim"
Created attachment 616466 [details] emerge-info.txt
Created attachment 616468 [details] app-editors:xemacs-21.5.34-r4:20200228-033921.log
Created attachment 616470 [details] emerge-history.txt
Created attachment 616472 [details] environment
Created attachment 616474 [details] etc.portage.tbz2
Created attachment 616476 [details] logs.tbz2
Created attachment 616478 [details] temp.tbz2
The ebuild app-editors/xemacs-21.5.34-r5 is added which addresses the configure problem where the version of libc where not picked up from libc installed in /lib64. The problem with the core dump remains the same as has been reported before in other tickets. I can still unfortunately not recreate that problem and upstream has no solution for this.
The ebuild app-editors/xemacs-21.5.34-r5 resolved the issue with not finding libc. Since this ticket is about the check for libc and not the core dump that occurs later I'm closing this as resolved.
