From: Cavit Cahit VURAL <ccvural@yahoo.com>
To: gdb@sources.redhat.com
Subject: Re: MinGW
Date: Fri, 01 Oct 2004 14:51:00 -0000 [thread overview]
Message-ID: <20041001145126.52217.qmail@web11906.mail.yahoo.com> (raw)
In-Reply-To: <5.2.0.9.1.20041001163438.01cf58e0@NT_SERVER>
The Environment :
Windows XP Prof SP1
512MB RAM
MSyS 1.0.11
gcc 3.4.2
binutils 2.15.91
autoconf 2.59
automake 1.8.2
gdb sources 6.2.1
Here is configuration :
creating cache ./config.cache
checking host system type... i686-pc-mingw32
checking target system type... i686-pc-mingw32
checking build system type... i686-pc-mingw32
checking for a BSD compatible install... /bin/install
-c
checking whether ln works... yes
checking whether ln -s works... no
checking for gcc... 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... yes
checking whether gcc accepts -g... yes
checking for gnatbind... no
checking whether compiler driver understands Ada... no
checking how to compare bootstrapped objects... 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... no
checking for gnum4... no
checking for m4... m4
checking for flex... flex
checking for flex... flex
checking for makeinfo... makeinfo
checking for i686-pc-mingw32-ar... no
checking for ar... ar
checking for i686-pc-mingw32-as... no
checking for as... as
checking for i686-pc-mingw32-dlltool... no
checking for dlltool... dlltool
checking for i686-pc-mingw32-ld...
C:/MinGW/bin/../lib/gcc/mingw32/3.4.2/../../../../mingw32/bin/ld.exe
checking for i686-pc-mingw32-nm... no
checking for nm... nm
checking for i686-pc-mingw32-ranlib... no
checking for ranlib... ranlib
checking for i686-pc-mingw32-windres... no
checking for windres... windres
checking for i686-pc-mingw32-objcopy... no
checking for objcopy... objcopy
checking for i686-pc-mingw32-objdump... no
checking for objdump... objdump
checking for i686-pc-mingw32-ar... no
checking for ar... ar
checking for i686-pc-mingw32-as... no
checking for as... as
checking for i686-pc-mingw32-dlltool... no
checking for dlltool... dlltool
checking for i686-pc-mingw32-ld... no
checking for ld... ld
checking for i686-pc-mingw32-nm... no
checking for nm... nm
checking for i686-pc-mingw32-ranlib... no
checking for ranlib... ranlib
checking for i686-pc-mingw32-windres... no
checking for windres... windres
checking whether to enable maintainer-specific
portions of Makefiles... no
checking if symbolic links between directories work...
yes
updating cache ./config.cache
creating ./config.status
creating Makefile
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail
next prev parent reply other threads:[~2004-10-01 14:51 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 ` Cavit Cahit VURAL [this message]
2004-10-01 14:56 ` Building GDB with MinGW Cavit Cahit VURAL
2004-10-01 15:10 ` Building GDB with MinGW (2) Cavit Cahit VURAL
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=20041001145126.52217.qmail@web11906.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