Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: asmwarrior <asmwarrior@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tromey@redhat.com, gdb@sourceware.org
Subject: Re: Windows build cookbook
Date: Sun, 31 Jul 2011 12:34:00 -0000	[thread overview]
Message-ID: <4E354C1E.20100@gmail.com> (raw)
In-Reply-To: <E1QnOlY-0007ql-2O@fencepost.gnu.org>

On 2011-7-31 13:40, Eli Zaretskii wrote:
> Looking at your page, I see the following differences between your
> recommended setup and what I used:
>
>   . You use a mingw-w64 version of MSYS, while I used the 32-bit
>     version (as my machine is a 32-bit one).
There is not such "mingw-w64 MSYS", all the MSYS is 32bit.
look at the folder of the link, the link name is:
External binary packages (Win64 hosted)
which means all the packages is from other site, and only hosted on the 
mingw64 site.
So, the MSYS package was took from the official MSYS site. (as the 
official MSYS installer use the MinGW-get to fetch all the tools and 
libraries. Some developer of MinGW64 project just put a full MSYS 
package contains all the MSYS tools, and put it in the MinGW64 site)
In-fact, I use Windows XP 32bit too. I do not have a 64bit Windows system.

>   . You mounted the root directory of the MinGW installation on /mingw,
>     while I didn't (I thought the fact that its bin/ subdirectory being
>     on PATH will do the job).
That's the official way of using MinGW compiler suite under MSYS, 
because the path "/mingw" will have the highest priority on the MSYS's 
search path. If you have many MinGW pathes on your Windows PATH 
variable, that maybe cause some problem.:-)

Nowadays, I use the PCX's 32bit MinGW package, which contains all the 
necessary libraries to build the GDB.
see: http://code.google.com/p/pcxprj/downloads/list

asmwarrior
ollydbg from codeblocks' forum


  reply	other threads:[~2011-07-31 12:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-27 16:03 Eli Zaretskii
2011-07-27 16:07 ` Joel Brobecker
2011-07-27 16:27   ` Eli Zaretskii
2011-07-27 16:37     ` Joel Brobecker
2011-07-27 16:39       ` Joel Brobecker
2011-07-27 17:12         ` Eli Zaretskii
2011-07-27 18:06       ` Kai Tietz
2011-07-27 16:44 ` Tom Tromey
2011-07-27 17:13   ` Eli Zaretskii
2011-07-27 17:17     ` Tom Tromey
2011-07-31  2:18       ` asmwarrior
2011-07-31  7:54         ` Eli Zaretskii
2011-07-31 12:34           ` asmwarrior [this message]
2011-07-31 15:46             ` Eli Zaretskii
2011-07-31 15:54             ` Eli Zaretskii
2011-07-31 20:11         ` Petr Hluzín

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=4E354C1E.20100@gmail.com \
    --to=asmwarrior@gmail.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=tromey@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