From: David Lamy-Charrier <david.lamy@gmail.com>
To: gdb@sourceware.org
Subject: Re: GNU 68HC11 & 68HC12 Sources Packages
Date: Thu, 15 Dec 2005 08:24:00 -0000 [thread overview]
Message-ID: <6541ed4c0512150024w6770f6c4v2f32e7c29be7619@mail.gmail.com> (raw)
In-Reply-To: <43A07996.6090403@nerim.fr>
Unfortunaltely,
I tested it yesterday evening with latest snapshot
(gdb-6.4.50.20051214.tar.bz2) from FTP site, but without success.
I got an error "*** Gdb does not support native target
i686-pc-mingw32" while configuring it.
Could you please let me know if you are lucky on your side.
Regards,
David
On 12/14/05, Stephane Carrez <stcarrez@nerim.fr> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Daniel Jacobowitz wrote:
> > On Tue, Dec 13, 2005 at 08:59:43PM +0100, Stephane Carrez wrote:
> >
> >>If the Mingw32 fixes could be integrated (but this must be done by
> >>Mingw group, not me), I will really appreciate. In fact, this is the only
> >>reason why I still use a gdb 6.2 (:-
> >
> >
> > HEAD GDB (and 6.4) should now build on mingw32; have you tried lately?
> >
> I've not tried yet. This is good news!
>
> Thanks,
>
> Stephane
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFDoHmWNyQxO2LzKT0RAkF1AKC+bx20bk/7I10PkXJ7iJ9pqDAl3ACguZqz
> vu6FVlafD4Bc0vu7luhi4rA=
> =aEiv
> -----END PGP SIGNATURE-----
>
next prev parent reply other threads:[~2005-12-15 8:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-13 1:50 Jim Blandy
2005-12-13 19:59 ` Stephane Carrez
2005-12-13 23:01 ` Daniel Jacobowitz
2005-12-14 19:59 ` Stephane Carrez
2005-12-15 8:24 ` David Lamy-Charrier [this message]
2005-12-15 9:20 ` Joel Brobecker
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=6541ed4c0512150024w6770f6c4v2f32e7c29be7619@mail.gmail.com \
--to=david.lamy@gmail.com \
--cc=gdb@sourceware.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