public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Sveta" <zhenja@zlo.ee>
To: binutils@sources.redhat.com
Subject: error building binutils on cygwin
Date: Mon, 19 Jun 2006 10:41:00 -0000	[thread overview]
Message-ID: <e732bh$v61$1@sea.gmane.org> (raw)

I have fresh cygwin installation withour any customisations.

I need to build binutils. Tried different versions from 2.16.1 to 2.16.94.
Always the same problem, which is shown in the log below. Please give me the
hint - how to solve that.

mkdir .libs
gcc -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Werror -g -O2 -o
ld-new.exe ldgram.o ldlex.o
lexsup.o ldlang.o mri.o ldctor.o ldmain.o ldwrite.o ldexp.o ldemul.o ldver.o
ldmisc.o ldfile.o ldcre
f.o ei386pe.o deffilep.o pe-dll.o  ../bfd/.libs/libbfd.a
../libiberty/libiberty.a
deffilep.o: In function `main':
/projects/crosstool-0.42/build/i686-pc-cygwin/gcc-4.1.1-/build-binutils/ld/d
effilep.c:1: multiple de
finition of `_main'
ldmain.o:/projects/crosstool-0.42/build/i686-pc-cygwin/gcc-4.1.1-/binutils/l
d/ldmain.c:183: first de
fined here
ei386pe.o: In function `gld_i386pe_unrecognized_file':
/projects/crosstool-0.42/build/i686-pc-cygwin/gcc-4.1.1-/build-binutils/ld/e
i386pe.c:1299: undefined
 reference to `_def_file_parse'
pe-dll.o: In function `pe_implied_import_dll':
/projects/crosstool-0.42/build/i686-pc-cygwin/gcc-4.1.1-/binutils/ld/pe-dll.
c:2632: undefined refere
nce to `_def_get_module'
/projects/crosstool-0.42/build/i686-pc-cygwin/gcc-4.1.1-/binutils/ld/pe-dll.
c:2660: undefined refere
nce to `_def_file_add_import'
/projects/crosstool-0.42/build/i686-pc-cygwin/gcc-4.1.1-/binutils/ld/pe-dll.
c:2617: undefined refere
nce to `_def_file_empty'
pe-dll.o: In function `pe_dll_build_sections':
/projects/crosstool-0.42/build/i686-pc-cygwin/gcc-4.1.1-/binutils/ld/pe-dll.
c:528: undefined referen
ce to `_def_file_add_directive'
/projects/crosstool-0.42/build/i686-pc-cygwin/gcc-4.1.1-/binutils/ld/pe-dll.
c:628: undefined referen
ce to `_def_file_add_export'
/projects/crosstool-0.42/build/i686-pc-cygwin/gcc-4.1.1-/binutils/ld/pe-dll.
c:581: undefined referen
ce to `_def_file_add_export'
/projects/crosstool-0.42/build/i686-pc-cygwin/gcc-4.1.1-/binutils/ld/pe-dll.
c:515: undefined referen
ce to `_def_file_empty'
collect2: ld returned 1 exit status
make[4]: *** [ld-new.exe] Error 1
make[4]: Leaving directory
`/projects/crosstool-0.42/build/i686-pc-cygwin/gcc-4.1.1-/build-binutils/
ld'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/projects/crosstool-0.42/build/i686-pc-cygwin/gcc-4.1.1-/build-binutils/
ld'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/projects/crosstool-0.42/build/i686-pc-cygwin/gcc-4.1.1-/build-binutils/
ld'
make[1]: *** [all-ld] Error 2
make[1]: Leaving directory
`/projects/crosstool-0.42/build/i686-pc-cygwin/gcc-4.1.1-/build-binutils'

make: *** [all] Error 2




             reply	other threads:[~2006-06-19  9:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19 10:41 Sveta [this message]
2006-06-19 11:44 ` Dave Korn
2006-06-22 14:11 ` Nick Clifton
2006-06-26  2:52   ` Sveta

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='e732bh$v61$1@sea.gmane.org' \
    --to=zhenja@zlo.ee \
    --cc=binutils@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).