Bug 1544448

Summary:	sphinxtrain-1.0.8-39.fc28 FTBFS: fst/fstlib.h header not found
Product:	[Fedora] Fedora	Reporter:	Petr Pisar <ppisar>
Component:	sphinxtrain	Assignee:	Jerry James <loganjerry>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	28	CC:	loganjerry
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://apps.fedoraproject.org/koschei/package/sphinxtrain?collection=f28
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-20 15:35:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.