Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 834447 - htons() gives warning if compiled with gcc -Wconversion [due to generic byteswap, non-x86/x86_64 platforms]
Summary: htons() gives warning if compiled with gcc -Wconversion [due to generic bytes...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: 17
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jeff Law
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 834449 834450 (view as bug list)
Depends On:
Blocks: ARMTracker 817555
TreeView+ depends on / blocked
 
Reported: 2012-06-21 21:54 UTC by Alex Chernyakhovsky
Modified: 2016-11-24 15:55 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-21 23:29:54 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Sourceware 12194 0 None None None Never

Description Alex Chernyakhovsky 2012-06-21 21:54:09 UTC 
glibc fixed a bug in 2010 in which htons() would give a conversion warning when compiled with -Wconversion due to the implementation of the byte-swapping functions. Unfortunately, this fix was only for x86/x86_64 platforms. The fix has now been updated to include the generic byteswap functions.

Please apply this patch to the glibc in Fedora.

For reference, please see http://sourceware.org/bugzilla/show_bug.cgi?id=12194
Comment 1 Alex Chernyakhovsky 2012-06-21 22:02:51 UTC 
*** Bug 834449 has been marked as a duplicate of this bug. ***
Comment 2 Alex Chernyakhovsky 2012-06-21 22:09:52 UTC 
*** Bug 834450 has been marked as a duplicate of this bug. ***
Comment 3 Jeff Law 2012-06-21 23:29:54 UTC 
I just resynced with the upstream sources which include a fix for this problem.
Note You need to log in before you can comment on or make changes to this bug.