From: "Yakov Lerner" <iler.ml@gmail.com>
To: gdb-patches@sourceware.org
Subject: fix compilation error under gcc 3.2.3 (warning treated as error)
Date: Thu, 14 Feb 2008 07:37:00 -0000 [thread overview]
Message-ID: <f36b08ee0802132337p2a1e7992i535cb3ac80f32c4b@mail.gmail.com> (raw)
Fix "duplicate const" compilation error (warning treated as error)
under gcc 3.2.3 (AS3 Linux, gcc version 3.2.3 20030502 (Red Hat Linux
3.2.3-20)).
Typedef for reloc_howto_type already has const, remove
unnecessary const at line 1174 bfd/elf32-i386.c
*** ./bfd/elf32-i386.c Thu Feb 14 10:07:44 2008
--- ./bfd/elf32-i386.c.000 Thu Feb 14 10:07:34 2008
***************
*** 1171,1177 ****
symtab_hdr, sym_hashes,
from_type, rel, relend))
{
! reloc_howto_type *from, *to;
from = elf_i386_rtype_to_howto (abfd, from_type);
to = elf_i386_rtype_to_howto (abfd, to_type);
--- 1171,1177 ----
symtab_hdr, sym_hashes,
from_type, rel, relend))
{
! const reloc_howto_type *from, *to;
from = elf_i386_rtype_to_howto (abfd, from_type);
to = elf_i386_rtype_to_howto (abfd, to_type);
[1]
/bin/sh ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
-I.././bfd -I. -DTRAD_CORE -I. -I.././bfd -I.././bfd/../include
-W -Wall -Wstrict-prototypes -Wmissing-prototypes -Werror -g -O2 -c -o
elf32-i386.lo elf32-i386.c
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.././bfd -I. -DTRAD_CORE
-I. -I.././bfd -I.././bfd/../include -W -Wall -Wstrict-prototypes
-Wmissing-prototypes -Werror -g -O2 -c elf32-i386.c -o elf32-i386.o
cc1: warnings being treated as errors
elf32-i386.c: In function `elf_i386_tls_transition':
elf32-i386.c:1174: warning: duplicate `const'
elf32-i386.c:1174: warning: duplicate `const'
make[4]: *** [elf32-i386.lo] Error 1
next reply other threads:[~2008-02-14 7:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 7:37 Yakov Lerner [this message]
2008-02-14 16:48 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f36b08ee0802132337p2a1e7992i535cb3ac80f32c4b@mail.gmail.com \
--to=iler.ml@gmail.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox