Bug 235909

Summary: libnl headers have error on i386
Product: [Fedora] Fedora Reporter: Dennis Gilmore <dennis>
Component: libnlAssignee: Neil Horman <nhorman>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
URL: http://buildsys.fedoraproject.org/logs/fedora-development-extras/31346-knetworkmanager-0.1-0.8.svn20070409.fc7/i386/build.log
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-08-29 15:01:25 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 Dennis Gilmore 2007-04-10 18:51:49 UTC
Description of problem:
Trying to build knetworkmanager update for Fedora and build fails as the 
headers are incorrect 
/usr/include/netlink/rtnetlink-kernel.h:498: error: '__u64' does not name a 
type

build was fine on x86_64 so it seems to be some 32bit  issue

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:
build fails

Expected results:
build to succeed 

Additional info:

Comment 1 Neil Horman 2007-04-10 20:18:02 UTC
This strikes me as more of a knetworkmanager issue.  knetworkmanager should not
include rtnetlink-kernel.h directly, but rather netlink.h, which includes
linux/types.h -> asm/types.h, where __u64  is definately defined.  It may be
that knetworkmanager is defining  __STRICT_ANSI__ during its build, which would
cause its lack of definition, but I don't think kde utils define that nominally.
 Likewise, if you were using a compiler other than gcc, __GNUC__ wouldn't be
defined, and you wouldn't get __u64 defined.  Either way, figure out which of
those macros is or isn't defined properly, fix that up, and your problem should
go away. 

Comment 2 Neil Horman 2007-08-29 14:52:51 UTC
ping.  Any update?

Comment 3 Dennis Gilmore 2007-08-29 15:01:25 UTC
sorry forgot about this bug.  I fixed it.  i had to pass an additional switch 
to knetworkmanager which fixed it.

Thanks for the reminder.