Bug 163131

Summary:	code fails to compile when _IO_MTSAFE_IO is defined
Product:	[Fedora] Fedora	Reporter:	Balbir Singh <bsingharora>
Component:	glibc	Assignee:	Jakub Jelinek <jakub>
Status:	CLOSED DUPLICATE	QA Contact:	Brian Brock <bbrock>
Severity:	low	Docs Contact:
Priority:	medium
Version:	4
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-07-13 11:16:04 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Balbir Singh 2005-07-13 08:29:52 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050531 Firefox/1.0+

Description of problem:
The file lowlevellock.h is not distributed along with the binary rpm. The source rpm has this file. lowlevellock.h is included when _IO_MTSAFE_IO is defined.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Compile the lates Usagi (www.linux-ipv6.org) libraries with _IO_MTSAFE_IO enabled (which is the default)
2.
3.
  

Actual Results:  We get a failure "lowlevellock.h - No such file or directory"

Expected Results:  The file should have been found and included or if the file is internal to glibc, the standard headers should not include it

Additional info:

Comment 1 Jakub Jelinek 2005-07-13 11:16:04 UTC

Usagi is seriously buggy if it uses <bits/stdio-lock.h>.  That header is
certainly not intended for use by random programs/libraries, only included
to make prehistoric versions of GCC to compile.

*** This bug has been marked as a duplicate of 162634 ***