Bug 1012408 - x86_64 version depends on /usr/include/gnu/stubs-32.h
Summary: x86_64 version depends on /usr/include/gnu/stubs-32.h
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: sparse
Version: 18
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jeff Layton
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-26 12:23 UTC by Jindrich Luza
Modified: 2014-06-18 07:43 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-09-26 14:38:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jindrich Luza 2013-09-26 12:23:48 UTC
Description of problem:
after run "]$ sparse *.c" appears error message:
/usr/include/gnu/stubs.h:7:12: error: unable to open 'gnu/stubs-32.h'

head of /usr/include/gnu/stubs.h:
/* This file is automatically generated.                                        
   This file selects the right generated file of `__stub_FUNCTION'macros
   based on the architecture being compiled for.  */

#if !defined __x86_64__                                                         
# include <gnu/stubs-32.h>                                                      
#endif   

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

How reproducible:
install sparse. Run on some *.c file

Steps to Reproduce:
1. yum install sparse
2. sparse *.c

Actual results:
/usr/include/gnu/stubs.h:7:12: error: unable to open 'gnu/stubs-32.h'

Expected results:
normal sparse output

Additional info:
yum whatprovides /usr/include/gnu/stubs-32.h

glibc-devel-2.16-24.fc18.i686 : Object files for development using standard C libraries.
Repo        : fedora
Matched from:
Filename    : /usr/include/gnu/stubs-32.h

glibc-devel-2.16-34.fc18.i686 : Object files for development using standard C libraries.
Repo        : updates
Matched from:
Filename    : /usr/include/gnu/stubs-32.h

Comment 1 Jindrich Luza 2013-09-26 14:38:12 UTC
sparse on .c file without include works fine. So problem above it's probably correct behaviour of sparse.


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