Bug 1544448 - sphinxtrain-1.0.8-39.fc28 FTBFS: fst/fstlib.h header not found
Summary: sphinxtrain-1.0.8-39.fc28 FTBFS: fst/fstlib.h header not found
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: sphinxtrain
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jerry James
QA Contact: Fedora Extras Quality Assurance
URL: https://apps.fedoraproject.org/kosche...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-12 14:24 UTC by Petr Pisar
Modified: 2018-02-20 15:35 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-20 15:35:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Petr Pisar 2018-02-12 14:24:04 UTC
sphinxtrain-1.0.8-39.fc28 fails to build in F28:

checking for fst/fstlib.h... no
configure: WARNING: fst/fstlib.h: present but cannot be compiled
configure: WARNING: fst/fstlib.h:     check for missing prerequisite headers?
configure: WARNING: fst/fstlib.h: see the Autoconf documentation
configure: WARNING: fst/fstlib.h:     section "Present But Cannot Be Compiled"
configure: WARNING: fst/fstlib.h: proceeding with the compiler's result
configure: error: fst/fstlib.h header not found

This package fails to build since upgrading GCC from 7.2.1-7.fc28 to 7.3.1-1.fc28 <https://apps.fedoraproject.org/koschei/build/4067674>, but that does not have to be the cause.

Comment 1 Fedora End Of Life 2018-02-20 15:28:48 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'.

Comment 2 Jerry James 2018-02-20 15:35:07 UTC
Whatever caused it appears to have gone away again.  I updated openfst and opengrm-ngram last night, then did a sphinxtrain rebuild due to those changes.  The rebuild went through without any difficulty.  It must have been a problem somewhere in the toolchain, apparently now fixed.


Note You need to log in before you can comment on or make changes to this bug.