public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: kamaraju kusumanchi <raju.mailinglists@gmail.com>
To: binutils@sourceware.org
Subject: implicit declaration of function `compressBound'
Date: Mon, 14 Feb 2011 17:37:00 -0000	[thread overview]
Message-ID: <AANLkTikWMDPAHWo_=+oUVO_mv8UPkwTJAkKSUwezpWCu@mail.gmail.com> (raw)

I am trying to compile binutils 2.21 on Solaris 2.10 using gcc 3.4.3.
The compilation fails with the following error

Making all in po
make[4]: Entering directory `<munge1>/compileHere/binutils_2.21/bfd/po'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory `<munge1>/compileHere/binutils_2.21/bfd/po'
make[4]: Entering directory `<munge1>/compileHere/binutils_2.21/bfd'
/bin/bash ./libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.
-I<munge1>/unZipped/binutils-2.21/bfd -I.
-I<munge1>/unZipped/binutils-2.21/bfd
-I<munge1>/unZipped/binutils-2.21/bfd/../include
-DHAVE_bfd_elf32_sparc_sol2_vec -DHAVE_bfd_elf64_sparc_sol2_vec
-DHAVE_sunos_big_vec -DHAVE_bfd_elf64_little_generic_vec
-DHAVE_bfd_elf64_big_generic_vec -DHAVE_bfd_elf32_little_generic_vec
-DHAVE_bfd_elf32_big_generic_vec
-DBINDIR='"<munge1>/myroot/binutils_2.21/bin"'  -W -Wall
-Wstrict-prototypes -Wmissing-prototypes -Werror -g -O2 -MT
compress.lo -MD -MP -MF .deps/compress.Tpo -c -o compress.lo
<munge1>/unZipped/binutils-2.21/bfd/compress.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I.
-I<munge1>/unZipped/binutils-2.21/bfd -I.
-I<munge1>/unZipped/binutils-2.21/bfd
-I<munge1>/unZipped/binutils-2.21/bfd/../include
-DHAVE_bfd_elf32_sparc_sol2_vec -DHAVE_bfd_elf64_sparc_sol2_vec
-DHAVE_sunos_big_vec -DHAVE_bfd_elf64_little_generic_vec
-DHAVE_bfd_elf64_big_generic_vec -DHAVE_bfd_elf32_little_generic_vec
-DHAVE_bfd_elf32_big_generic_vec
-DBINDIR=\"<munge1>/myroot/binutils_2.21/bin\" -W -Wall
-Wstrict-prototypes -Wmissing-prototypes -Werror -g -O2 -MT
compress.lo -MD -MP -MF .deps/compress.Tpo -c
<munge1>/unZipped/binutils-2.21/bfd/compress.c -o compress.o
<munge1>/unZipped/binutils-2.21/bfd/compress.c: In function
`bfd_compress_section_contents':
<munge1>/unZipped/binutils-2.21/bfd/compress.c:100: warning: implicit
declaration of function `compressBound'
make[4]: *** [compress.lo] Error 1
make[4]: Leaving directory `<munge1>/compileHere/binutils_2.21/bfd'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `<munge1>/compileHere/binutils_2.21/bfd'
make[2]: *** [all] Error 2
make[2]: Leaving directory `<munge1>/compileHere/binutils_2.21/bfd'
make[1]: *** [all-bfd] Error 2
make[1]: Leaving directory `<munge1>/compileHere/binutils_2.21'
make: *** [all] Error 2

$ gcc --version
gcc (GCC) 3.4.3
Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Is it a bug or am I missing something?


raju
--
Kamaraju S Kusumanchi
http://malayamaarutham.blogspot.com/

             reply	other threads:[~2011-02-14 17:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-14 17:37 kamaraju kusumanchi [this message]
2011-02-14 23:05 ` Alan Modra
2011-02-15  3:54   ` kamaraju kusumanchi
2011-02-15  3:55     ` kamaraju kusumanchi
2011-02-15  7:44       ` Alan Modra

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='AANLkTikWMDPAHWo_=+oUVO_mv8UPkwTJAkKSUwezpWCu@mail.gmail.com' \
    --to=raju.mailinglists@gmail.com \
    --cc=binutils@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).