Summary: | app-admin/metalog-3-r2 - fseterr.c:77:3: error: #error "Please port gnulib fseterr.c to your platform! Look at the definitions of ferror and clearerr on your system, then report this to bug-gnulib." | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | tt_1 <herrtimson> |
Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alexey+gentoo, hossie, peter_sliepenbeek, zmedico |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 682842 | ||
Bug Blocks: | 663916 | ||
Attachments: |
build.log
emerge --info config.log |
Created attachment 570690 [details]
emerge --info
checking for __fseterr... no Could you please attach config.log as well? Created attachment 570692 [details]
config.log
Yes, I'm also seeing this in a new install. This seems to be glibc-2.28 related, see https://lists.gnu.org/r/bug-gnulib/2018-03/msg00000.html. As the op said that ~20181125 worked fine, maybe we should just mark this as stable. I experienced this with glibc-2.28-r5, and metalog-20181125 builds for me. it's fixed for main arches, closing |
Created attachment 570688 [details] build.log the build chokes on this: x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -O2 -march=znver1 -pipe -c vfprintf.c fseterr.c: In function ‘fseterr’: fseterr.c:77:3: error: #error "Please port gnulib fseterr.c to your platform! Look at the definitions of ferror and clearerr on your system, then report this to bug-gnulib." #error "Please port gnulib fseterr.c to your platform! Look at the definitions of ferror and clearerr on your system, then report this to bug-gnulib." ^~~~~ This happened during an emerge -e world, which I started after upgrading gcc and glibc to its recent stable on amd64 (8.2.0-r6 and 2.28-r5) metalog-20181125 seems to be ok