Bug 638588 – app-shells/ksh-93.20160110 : ./ast_stdio.h:82:15: error: conflicting types for _sfio_FILE

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Toralf Förster 2017-11-23 18:58:36 UTC]

                 from /var/tmp/portage/app-shells/ksh-93.20160110/work/ast-c506cb548d9b4bcebef92c86e948657728760e15/src/lib/libast/include/ast.h:34,
                 from /var/tmp/portage/app-shells/ksh-93.20160110/work/ast-c506cb548d9b4bcebef92c86e948657728760e15/src/lib/libast/misc/state.c:26:
./ast_stdio.h:82:15: error: conflicting types for '_sfio_FILE'
 #define FILE  _sfio_FILE
               ^
./ast_stdio.h:80:24: note: previous declaration of '_sfio_FILE' was here

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

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 13.0-no-multilib_libressl_20171119-113915

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

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

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



emerge -qpv app-shells/ksh
[ebuild  N    ] app-shells/ksh-93.20160110

[Comment 1 Toralf Förster 2017-11-23 18:58:39 UTC]

Created attachment 505910 [details]
emerge-info.txt

[Comment 2 Toralf Förster 2017-11-23 18:58:43 UTC]

Created attachment 505912 [details]
app-shells:ksh-93.20160110:20171122-224130.log.bz2

[Comment 3 Toralf Förster 2017-11-23 18:58:46 UTC]

Created attachment 505914 [details]
emerge-history.txt

[Comment 4 Toralf Förster 2017-11-23 18:58:49 UTC]

Created attachment 505916 [details]
environment

[Comment 5 Toralf Förster 2017-11-23 18:58:52 UTC]

Created attachment 505918 [details]
etc.portage.tbz2

[Comment 6 Toralf Förster 2017-11-23 18:58:55 UTC]

Created attachment 505920 [details]
temp.tbz2

[Comment 7 Ulrich Müller 2017-12-01 16:15:54 UTC]

I see this with gcc-6.4.0 too (occured during the 17.0 rebuild).

[Comment 8 Ulrich Müller 2017-12-01 17:03:49 UTC]

This seems to be caused by a change in glibc.

The following patch from upstream fixes the issue for me:
https://github.com/att/ast/pull/63/commits/1647f750138ca167f0348fff08c82301baac8dfc

[Comment 9 Mike Gilbert 2017-12-01 18:20:35 UTC]

(In reply to Ulrich Müller from comment #8)

Oh, upstream is finally active again; it was dead for over a year.

I'll cut a new snapshot shortly.

[Comment 10 Mike Gilbert 2018-01-29 23:23:47 UTC]

I added ksh-93.20180129 to the tree.