[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug binutils/14028] New: Need to #include both <string.h> and <strings.
From: |
skunk at iskunk dot org |
Subject: |
[Bug binutils/14028] New: Need to #include both <string.h> and <strings.h> on AIX |
Date: |
Fri, 27 Apr 2012 20:14:00 +0000 |
http://sourceware.org/bugzilla/show_bug.cgi?id=14028
Bug #: 14028
Summary: Need to #include both <string.h> and <strings.h> on
AIX
Product: binutils
Version: 2.23 (HEAD)
Status: NEW
Severity: normal
Priority: P2
Component: binutils
AssignedTo: address@hidden
ReportedBy: address@hidden
Classification: Unclassified
Created attachment 6378
--> http://sourceware.org/bugzilla/attachment.cgi?id=6378
Patch against current binutils CVS source
I encountered some trouble building binutils 2.22 on AIX 4.3; specifically,
str[n]casecmp() would come up as an implicitly-defined function, causing the
build to fail due to -Werror.
str[n]casecmp() is declared in <strings.h>. If you look in binutils/bfd/, the
configure script invokes ACX_HEADER_STRING, and sysdep.h #includes both
<string.h> and <strings.h> if STRING_WITH_STRINGS is defined. This is exactly
what needs to happen to get str[n]casecmp() along with the usual string.h
functions on many systems.
The problem is, this does not currently happen in binutils/binutils/,
binutils/gas/, binutils/ld/ and binutils/opcodes/. Thus there is breakage.
The attached patch, against current CVS, is a first stab at addressing the
issue.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Bug binutils/14028] New: Need to #include both <string.h> and <strings.h> on AIX,
skunk at iskunk dot org <=