From: Zhihua Che <zhihua.che@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: gdb@sourceware.org
Subject: Re: [Buiding Error] git version 238a89c5e410f61d2786cffca0a55dcf50325cd4
Date: Sun, 25 Mar 2012 12:07:00 -0000 [thread overview]
Message-ID: <CABexPfHjjutZA-KtwKKsGaEDn4HxnSbbm0bprT61zj_XH3kMNQ@mail.gmail.com> (raw)
In-Reply-To: <m262dvmcui.fsf@igel.home>
在 2012年3月24日 上午1:44，Andreas Schwab <schwab@linux-m68k.org> 写道：
> Zhihua Che <zhihua.che@gmail.com> writes:
>
>> WARNING: `makeinfo' is missing on your system. You should only need it if
>> you modified a `.texi' or `.texinfo' file, or any other file
>> indirectly affecting the aspect of the manual. The spurious
>> call might also be the consequence of using a buggy `make' (AIX,
>> DU, IRIX). You might want to install the `Texinfo' package or
>> the `GNU make' package. Grab either from any GNU archive site.
>> make[3]: *** [bfd.info] Error 1
>>
>> Does anybody build and fail like this ever?
>
> If you are building from the repository then makeinfo is a required
> dependency. Prebuilt info files are only present in release and
> snapshot tarballs.
>
> Andreas.
After installing texinfo and flex, I made a little progress, but
another problem arise.
I updated the code to version c338d4bceb084a629b479e1ac36ab2b42737e1c2
and compiling failed with a 'simple' error
gcc -g -O2 -I. -I../../gdb/gdb -I../../gdb/gdb/common
-I../../gdb/gdb/config
-DLOCALEDIR="\"/home/harvey/open-projects/local/gdb2/share/locale\""
-DHAVE_CONFIG_H -I../../gdb/gdb/../include/opcode
-I../../gdb/gdb/../opcodes/.. -I../../gdb/gdb/../readline/.. -I../bfd
-I../../gdb/gdb/../bfd -I../../gdb/gdb/../include -I../libdecnumber
-I../../gdb/gdb/../libdecnumber -I../../gdb/gdb/gnulib -Ignulib
-DTUI=1 -I/usr/include/python2.7 -I/usr/include/python2.7 -Wall
-Wdeclaration-after-statement -Wpointer-arith -Wformat-nonliteral
-Wno-pointer-sign -Wno-unused -Wunused-value -Wunused-function
-Wno-switch -Wno-char-subscripts -Wmissing-prototypes -Werror -c -o
c-exp.o -MT c-exp.o -MMD -MP -MF .deps/c-exp.Tpo c-exp.c
c-exp.c:1:1: error: return type defaults to ‘int’ [-Werror=return-type]
In build-directory I found a c-exp.c, in which there is only one line
main() { return 0; }
I guess this is a bug.
next prev parent reply other threads:[~2012-03-25 12:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 14:10 Zhihua Che
2012-03-23 17:09 ` Joel Brobecker
2012-03-23 17:45 ` Andreas Schwab
2012-03-25 12:07 ` Zhihua Che [this message]
2012-03-25 19:32 ` Andreas Schwab
[not found] ` <CABexPfHbrq2Zukp2XrepTonLhRoBVr1EAT4rZhqfaAwt7EPMVA@mail.gmail.com>
2012-03-26 2:51 ` Zhihua Che
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=CABexPfHjjutZA-KtwKKsGaEDn4HxnSbbm0bprT61zj_XH3kMNQ@mail.gmail.com \
--to=zhihua.che@gmail.com \
--cc=gdb@sourceware.org \
--cc=schwab@linux-m68k.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).