From: Cavit Cahit VURAL <ccvural@yahoo.com>
To: gdb@sources.redhat.com
Subject: Re: Building GDB with MinGW (2)
Date: Fri, 01 Oct 2004 15:10:00 -0000 [thread overview]
Message-ID: <20041001151052.70124.qmail@web11904.mail.yahoo.com> (raw)
In-Reply-To: <20041001145612.9419.qmail@web11903.mail.yahoo.com>
And built bfd directory.
C:/MSyS/bin/sh.exe ./../move-if-change tofiles ofiles
touch stamp-ofiles
C:/MSyS/bin/sh.exe ./libtool --mode=link gcc -W -Wall
-Wstrict-prototypes -Wmissing-prototypes -g -O2 -o
libbfd.la -rpath /usr/local/lib -release 2.15.91
archive.lo archures.lo bfd.lo bfdio.lo bfdwin.lo
cache.lo coffgen.lo corefile.lo format.lo init.lo
libbfd.lo opncls.lo reloc.lo section.lo syms.lo
targets.lo hash.lo linker.lo srec.lo binary.lo
tekhex.lo ihex.lo stabs.lo stab-syms.lo merge.lo
dwarf2.lo simple.lo archive64.lo `cat ofiles`
mkdir .libs
libtool: link: warning: undefined symbols not allowed
in i686-pc-mingw32 shared libraries
ar cru .libs/libbfd.a archive.o archures.o bfd.o
bfdio.o bfdwin.o cache.o coffgen.o corefile.o format.o
init.o libbfd.o opncls.o reloc.o section.o syms.o
targets.o hash.o linker.o srec.o binary.o tekhex.o
ihex.o stabs.o stab-syms.o merge.o dwarf2.o simple.o
archive64.o pe-i386.o peigen.o cofflink.o pei-i386.o
elf32-i386.o elf32.o elf.o elflink.o elf-strtab.o
elf-eh-frame.o dwarf1.o elf32-gen.o cpu-i386.o
ranlib .libs/libbfd.a
creating libbfd.la
(cd .libs && rm -f libbfd.la && ln ../libbfd.la
libbfd.la)
libtooldir=`C:/MSyS/bin/sh.exe ./libtool --config |
sed -n -e 's/^objdir=//p'`; \
if [ -f $libtooldir/libbfd.a ]; then \
cp $libtooldir/libbfd.a libbfd.tmp; \
ranlib libbfd.tmp; \
C:/MSyS/bin/sh.exe ./../move-if-change libbfd.tmp
libbfd.a; \
else true; fi
touch stamp-lib
C:\MinGW\bin\make.exe[2]: Leaving directory
`C:/MSyS/gdb-6.2.1/bfd'
make[1]: Leaving directory `C:/MSyS/gdb-6.2.1/bfd'
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
next prev parent reply other threads:[~2004-10-01 15:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 14:25 MinGW Cavit Cahit VURAL
2004-10-01 14:36 ` MinGW Fabian Cenedese
2004-10-01 14:51 ` MinGW Cavit Cahit VURAL
2004-10-01 14:56 ` Building GDB with MinGW Cavit Cahit VURAL
2004-10-01 15:10 ` Cavit Cahit VURAL [this message]
2004-10-01 15:16 ` Building GDB with MinGW (3) Cavit Cahit VURAL
2004-10-01 16:51 ` Joel Brobecker
2004-10-02 2:21 ` Dan Mosedale
2004-10-02 3:37 ` Christopher Faylor
2004-10-02 9:03 ` Building GDB with MinGW (4) Cavit Cahit VURAL
2004-10-02 5:20 ` Cavit Cahit VURAL
2004-10-02 15:14 ` Building GDB with MinGW (3) Dan Mosedale
2004-10-07 12:36 ` Building GDB with MinGW Cavit Cahit VURAL
2004-10-07 12:23 ` Cavit Cahit VURAL
2004-10-07 12:42 ` Cavit Cahit VURAL
2004-10-07 12:48 ` Cavit Cahit VURAL
2004-10-01 20:23 ` Building GDB with MinGW (3) Eli Zaretskii
2004-10-01 21:22 ` Cavit Cahit VURAL
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=20041001151052.70124.qmail@web11904.mail.yahoo.com \
--to=ccvural@yahoo.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