Bug 669694 – 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.

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Toralf Förster 2018-10-26 18:42:43 UTC]

x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../..     -O2 -pipe -march=native  -c fseterr.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."
   ^~~~~
make[4]: *** [Makefile:1550: fseterr.o] Error 1

  -------------------------------------------------------------------

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 17.0-desktop-gnome-systemd_abi32+64_20181025-203518

  -------------------------------------------------------------------

  Please see the tracker bug for details.

gcc-config -l:
 [1] x86_64-pc-linux-gnu-8.2.0 *

Available Python interpreters, in order of preference:
  [1]   python3.6
  [2]   python2.7 (fallback)
Available Ruby profiles:
  [1]   ruby23 (with Rubygems) *



emerge -qpvO app-admin/metalog
[ebuild  N    ] app-admin/metalog-3-r2  USE="unicode"

[Comment 1 Toralf Förster 2018-10-26 18:42:46 UTC]

Created attachment 553210 [details]
emerge-info.txt

[Comment 2 Toralf Förster 2018-10-26 18:42:48 UTC]

Created attachment 553212 [details]
app-admin:metalog-3-r2:20181026-183138.log

[Comment 3 Toralf Förster 2018-10-26 18:42:51 UTC]

Created attachment 553214 [details]
emerge-history.txt

[Comment 4 Toralf Förster 2018-10-26 18:42:54 UTC]

Created attachment 553216 [details]
environment

[Comment 5 Toralf Förster 2018-10-26 18:42:57 UTC]

Created attachment 553218 [details]
etc.portage.tbz2

[Comment 6 Toralf Förster 2018-10-26 18:42:59 UTC]

Created attachment 553220 [details]
logs.tbz2

[Comment 7 Toralf Förster 2018-10-26 18:43:02 UTC]

Created attachment 553222 [details]
temp.tbz2

[Comment 8 Ionen Wolkens 2018-11-15 06:46:57 UTC]

Unless here's concerns with newer versions (technically not marked as "stable"), this can be fixed by simply updating metalog, metalog-3 is 6 years old and current version (released last month) doesn't even use gnulib anymore and has additional features such as remote logging (which is reported as a missing feature on the wiki still).

I did not experiment much, but new version does not appear to break old configurations either and can just be swapped in save for needing to run autogen stuff now.

https://github.com/hvisage/metalog/releases

[Comment 9 Larry the Git Cow 2018-11-15 22:53:47 UTC]

The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e89960b35cf778df12786199f79b7634746de3ec

commit e89960b35cf778df12786199f79b7634746de3ec
Author:     Patrick McLean <[e-mail]>
AuthorDate: 2018-11-15 22:50:32 +0000
Commit:     Patrick McLean <[e-mail]>
CommitDate: 2018-11-15 22:52:08 +0000

    app-admin/metalog: Version bump to 20181125 (bug #664344)
    
    Update HOMEPAGE to GitHub site
    
    Closes: https://bugs.gentoo.org/664344
    Closes: https://bugs.gentoo.org/669694
    Bug: https://bugs.gentoo.org/210711
    Bug: https://bugs.gentoo.org/670757
    Package-Manager: Portage-2.3.51, Repoman-2.3.12
    Signed-off-by: Patrick McLean <[e-mail]>

 app-admin/metalog/Manifest                |  1 +
 app-admin/metalog/files/metalog.initd-r1  | 28 ++++++++++++++
 app-admin/metalog/metalog-20181125.ebuild | 64 +++++++++++++++++++++++++++++++
 3 files changed, 93 insertions(+)