From: Daniel Jacobowitz <drow@false.org>
To: Davide Viti <zinosat@tiscali.it>
Cc: gdb@sourceware.org
Subject: Re: error cross-compiling gdbserver
Date: Wed, 14 May 2008 11:42:00 -0000 [thread overview]
Message-ID: <20080514114218.GB5721@caradoc.them.org> (raw)
In-Reply-To: <20080514111812.GA19455@slurpy>
On Wed, May 14, 2008 at 01:18:12PM +0200, Davide Viti wrote:
> libtool: compile: arm-wrs-linux-gnueabi-arm-glibc_full-gcc -DHAVE_CONFIG_H -I. -I../../../gdb-6.8/bfd -I. -I. -I../../../gdb-6.8/bfd -I../../../gdb-6.8/bfd/../include -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Werror -mlittle-endian -mcpu=arm926ej-s -mthumb -c -DDEFAULT_VECTOR=bfd_elf32_littlearm_vec "-DSELECT_VECS=&bfd_elf32_littlearm_vec,&bfd_elf32_bigarm_vec,&bfd_elf32_little_generic_vec,&bfd_elf32_big_generic_vec" "-DSELECT_ARCHITECTURES=&bfd_arm_arch" -DHAVE_bfd_elf32_littlearm_vec -DHAVE_bfd_elf32_bigarm_vec -DHAVE_bfd_elf32_little_generic_vec -DHAVE_bfd_elf32_big_generic_vec ../../../gdb-6.8/bfd/archures.c -o archures.o
> arm-wrs-linux-gnueabi-gcc.exe: no input files
>
> 'bfd_elf32_littlearm_vec' is not recognized as an internal or external command,
You have some sort of mismatch between your build tools and your
shell. Possibly the version of shell being used by the current
version of make. I know that the compiler you reference is a native
Windows application rather than a Cygwin one; if something else
involved is native Windows it may be handling the quotes and ampersand
differently than expected.
Fortunately this is not a problem. Run gdb/gdbserver/configure
instead of the top level configure script if all you need for the
target is gdbserver.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-05-14 11:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 11:30 Davide Viti
2008-05-14 11:42 ` Daniel Jacobowitz [this message]
2008-05-14 12:16 ` Davide Viti
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=20080514114218.GB5721@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=zinosat@tiscali.it \
/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