From: Paul Gilliam <pgilliam@us.ibm.com>
To: gdb@sources.redhat.com
Subject: Can't build on PowerPC-64
Date: Wed, 06 Jul 2005 21:47:00 -0000 [thread overview]
Message-ID: <200507061503.26454.pgilliam@us.ibm.com> (raw)
On a linux system, running a 64-bit PowerPC kernel, I get the following when I try to build the latest CVS snapshot:
<snip>
gcc -m64 -DHAVE_CONFIG_H -I. -I../../src/bfd -I. -I. -I../../src/bfd -I../../src/bfd/../include -I../../src/bfd/../intl -I../intl -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Werror -g -O2 -c ../../src/bfd/elf64-ppc.c -o elf64-ppc.o
../../src/bfd/elf64-ppc.c: In function `ppc64_elf_get_sec_type_attr':
../../src/bfd/elf64-ppc.c:2525: warning: duplicate `const'
make[3]: *** [elf64-ppc.lo] Error 1
make[3]: Leaving directory `/home/gdb-ppc64-testing/adhoc-testing/build-64/bfd'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/gdb-ppc64-testing/adhoc-testing/build-64/bfd'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/gdb-ppc64-testing/adhoc-testing/build-64/bfd'
make: *** [all-bfd] Error 2
Same thing for 'gcc -m32'.
If I do a cvs update first, I get this:
<snip>
Making all in po
make[3]: Entering directory `/home/gdb-ppc64-testing/nightly-runs/6.3.50.20050705-20050706/build-64/bfd/po'
file=../../../src/bfd/po/`echo fr | sed 's,.*/,,'`.gmo \
&& rm -f $file && PATH=../src:$PATH /usr/bin/msgfmt -o $file ../../../src/bfd/po/fr.po
file=../../../src/bfd/po/`echo tr | sed 's,.*/,,'`.gmo \
&& rm -f $file && PATH=../src:$PATH /usr/bin/msgfmt -o $file ../../../src/bfd/po/tr.po
file=../../../src/bfd/po/`echo ja | sed 's,.*/,,'`.gmo \
&& rm -f $file && PATH=../src:$PATH /usr/bin/msgfmt -o $file ../../../src/bfd/po/ja.po
file=../../../src/bfd/po/`echo es | sed 's,.*/,,'`.gmo \
&& rm -f $file && PATH=../src:$PATH /usr/bin/msgfmt -o $file ../../../src/bfd/po/es.po
file=../../../src/bfd/po/`echo sv | sed 's,.*/,,'`.gmo \
&& rm -f $file && PATH=../src:$PATH /usr/bin/msgfmt -o $file ../../../src/bfd/po/sv.po
file=../../../src/bfd/po/`echo da | sed 's,.*/,,'`.gmo \
&& rm -f $file && PATH=../src:$PATH /usr/bin/msgfmt -o $file ../../../src/bfd/po/da.po
file=../../../src/bfd/po/`echo zh_CN | sed 's,.*/,,'`.gmo \
&& rm -f $file && PATH=../src:$PATH /usr/bin/msgfmt -o $file ../../../src/bfd/po/zh_CN.po
file=../../../src/bfd/po/`echo ro | sed 's,.*/,,'`.gmo \
&& rm -f $file && PATH=../src:$PATH /usr/bin/msgfmt -o $file ../../../src/bfd/po/ro.po
file=../../../src/bfd/po/`echo rw | sed 's,.*/,,'`.gmo \
&& rm -f $file && PATH=../src:$PATH /usr/bin/msgfmt -o $file ../../../src/bfd/po/rw.po
make[3]: *** No rule to make target `vi.po', needed by `vi.gmo'. Stop.
make[3]: Leaving directory `/home/gdb-ppc64-testing/nightly-runs/6.3.50.20050705-20050706/build-64/bfd/po'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/gdb-ppc64-testing/nightly-runs/6.3.50.20050705-20050706/build-64/bfd'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/gdb-ppc64-testing/nightly-runs/6.3.50.20050705-20050706/build-64/bfd'
make: *** [all-bfd] Error 2
Is someone actively working on gdb's bfd tree?
What can I do to work-around this?
-=# Paul #=-
next reply other threads:[~2005-07-06 21:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 21:47 Paul Gilliam [this message]
2005-07-06 21:55 ` Paul Gilliam
2005-07-06 21:55 ` Daniel Jacobowitz
2005-07-07 0:03 ` Paul Gilliam
2005-07-07 0:21 ` Daniel Jacobowitz
2005-07-07 20:38 ` Paul Gilliam
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=200507061503.26454.pgilliam@us.ibm.com \
--to=pgilliam@us.ibm.com \
--cc=gdb@sources.redhat.com \
/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