From: Dean Margell <dean99@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Error
Date: Wed, 13 Apr 2005 22:39:00 -0000 [thread overview]
Message-ID: <3892147f05041315394b7746b1@mail.gmail.com> (raw)
I am trying to build a cross compiler on my Windows XP host that will
compile executable binaries that I can run on my Linux Red Hat 9.0
target, but I get compile errors when building the binutils. I am
running cygwin 1.5.14, and gcc 3.3.3-3.
I have created a /crossgcc/build-binutils directory, and from it I
first execute the "configure" command:
$ ../../usr/src/binutils-20041229-1/configure
--target=$TARGET--host=$HOST --build=$BUILD --prefix=$PREFIX -v
Where:
TARGET=i686-pc-linux-gnu
HOST=i686-pc-cygwin
BUILD=i686-pc-cygwin
PREFIX=/crossgcc
and then, this is the error I get when I run 'make':
...
/crossgcc/build-binutils/binutils/arlex.c:1: multiple definition of `_main'
arparse.o(.text+0x0):/crossgcc/build-binutils/binutils/arparse.c:1:
first defined here
ar.o(.text+0x7d0): In function `main':
/crossgcc/build-binutils/binutils/../../../usr/src/binutils-20041229-1/binutils/ar.c:342:
multiple definition of `_main'
arparse.o(.text+0x0):/crossgcc/build-binutils/binutils/arparse.c:1:
first defined here
ar.o(.text+0x27): In function `mri_emul':
/crossgcc/build-binutils/binutils/../../../usr/src/binutils-20041229-1/binutils/ar.c:148:
undefined reference to `_yyparse'
collect2: ld returned 1 exit status
make[3]: *** [ar.exe] Error 1
make[3]: Leaving directory `/crossgcc/build-binutils/binutils'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/crossgcc/build-binutils/binutils'
make[1]: *** [all-recursive-am] Error 2
make[1]: Leaving directory `/crossgcc/build-binutils/binutils'
make: *** [all-binutils] Error 2
Any help would be Greatly appreciated (I'm new).
============== start of output from "configure" command ================
$ ../../usr/src/binutils-20041229-1/configure --target=$TARGET --host=$HOST --b
uild=$BUILD --prefix=$PREFIX -v
loading cache ./config.cache
checking host system type... i686-pc-cygwin
checking target system type... i686-pc-linux-gnu
checking build system type... i686-pc-cygwin
checking for a BSD compatible install... (cached) /usr/bin/install -c
checking whether ln works... (cached) yes
checking whether ln -s works... (cached) yes
-v: not found
checking for gcc... (cached) gcc
checking whether the C compiler (gcc ) works... yes
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gnatbind... no
checking whether compiler driver understands Ada... (cached) no
checking how to compare bootstrapped objects... (cached) cmp --ignore-initial=16
$$f1 $$f2
checking for correct version of gmp.h... no
checking for bison... no
checking for bison... no
checking for byacc... no
checking for yacc... no
checking for gm4... (cached) m4
checking for flex... no
checking for flex... no
checking for lex... no
checking for makeinfo... (cached) makeinfo
*** removing intl/Makefile to force reconfigure
*** removing libiberty/Makefile to force reconfigure
*** removing opcodes/Makefile to force reconfigure
*** removing bfd/Makefile to force reconfigure
*** removing binutils/Makefile to force reconfigure
checking for i686-pc-cygwin-ar... no
checking for ar... (cached) ar
checking for i686-pc-cygwin-as... no
checking for as... (cached) as
checking for i686-pc-cygwin-dlltool... no
checking for dlltool... (cached) dlltool
checking for i686-pc-cygwin-ld... (cached) /usr/lib/gcc-lib/i686-pc-cygwin/3.3.3
/../../../../i686-pc-cygwin/bin/ld.exe
checking for i686-pc-cygwin-nm... no
checking for nm... (cached) nm
checking for i686-pc-cygwin-ranlib... (cached) ranlib
checking for i686-pc-cygwin-windres... no
checking for windres... (cached) windres
checking for i686-pc-cygwin-objcopy... no
checking for objcopy... (cached) objcopy
checking for i686-pc-cygwin-objdump... no
checking for objdump... (cached) objdump
checking for i686-pc-linux-gnu-ar... no
checking for i686-pc-linux-gnu-as... no
checking for i686-pc-linux-gnu-dlltool... no
checking for i686-pc-linux-gnu-ld... no
checking for i686-pc-linux-gnu-nm... no
checking for i686-pc-linux-gnu-ranlib... no
checking for i686-pc-linux-gnu-windres... no
checking whether to enable maintainer-specific portions of Makefiles... no
checking if symbolic links between directories work... (cached) yes
updating cache ./config.cache
creating ./config.status
creating Makefile
============== end of output from "configure" command ================
next reply other threads:[~2005-04-13 22:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 22:39 Dean Margell [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-22 0:45 error Bill Cunningham
2019-11-01 1:44 Error pen1979871192
2007-10-13 1:09 error jay caverte
2007-10-13 1:25 ` error Brian Dessent
2002-05-12 8:50 Error Rahul it
2002-05-12 9:27 ` Error bjorn rohde jensen
2002-05-12 20:44 ` Error David Dudley
2001-05-28 3:36 error Torsten Becker
2001-05-28 14:36 ` error Alexandre Oliva
2001-05-28 3:22 error Torsten Becker
2001-02-07 7:57 error Edmond Kereku
2000-01-14 14:03 Error DarkSprrow
2000-04-01 0:00 ` Error DarkSprrow
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=3892147f05041315394b7746b1@mail.gmail.com \
--to=dean99@gmail.com \
--cc=gcc-help@gcc.gnu.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).