From: Joel Sherrill <Joel.Sherrill@OARcorp.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"vapier@gentoo.org" <vapier@gentoo.org>,
Chris Johns <chrisj@rtems.org>
Subject: Re: one week to gdb-7.6 release?
Date: Fri, 29 Mar 2013 12:53:00 -0000 [thread overview]
Message-ID: <d3juvfb1q08s06stnna8337p.1364522909961@email.android.com> (raw)
Does this mean that you can't build a mingw hosted cross compiler either natively on mingw or via Canadian cross?
If so, I would consider that a serious regression and blocker.
If I read your comment correctly, you consider it a blocker also.
And is there a list somewhere of mingw issues? Like dv-socker.o, simulators using POSIX signals and termios, etc.. Seems like a good GSOC project.
--joel
RTEMS
Joel Brobecker <brobecker@adacore.com> wrote:
> > The
> > code in main.c already does
> >
> > #ifdef __MINGW32__
> > /* On Windows, argv[0] is not necessarily set to absolute form when
> > GDB is found along PATH, without which relocation doesn't work. */
> > gdb_program_name = windows_get_absolute_argv0 (argv[0]);
> > #else
> > gdb_program_name = xstrdup (argv[0]);
> > #endif
> >
> > Is moving that to posix-hdep.c just to avoid an ifdef?
>
> The main purpose is to move the code away out of windows-nat, which
> is only linked in native debuggers, not cross ones - so that building
> a cross debugger hosted on Windows will work again. Basically, your
> new function is really only dependent on the host, whereas the -nat
> file makes the assumption that host & target are Windows.
I have added this item to the TODO list for the 7.6 release, so as not
to forget.
I was wondering if this discussion was stalled, or if it was just
a matter of not finding the time to do the implementation. I could
possibly take care of it tomorrow if you'd like. There is not real
rush, however, as I will be off next week, and thus unable to create
a release at least until Tue Apr 9th.
--
Joel
next reply other threads:[~2013-03-29 2:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 12:53 Joel Sherrill [this message]
2013-03-29 14:15 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2013-03-20 16:09 Joel Brobecker
2013-03-20 16:14 ` Pedro Alves
2013-03-20 17:06 ` Jan Kratochvil
2013-03-20 17:08 ` Joel Sherrill
2013-03-20 17:20 ` Eli Zaretskii
2013-03-23 22:59 ` Eli Zaretskii
2013-03-24 0:01 ` Joel Brobecker
2013-03-24 0:07 ` Eli Zaretskii
2013-03-25 16:58 ` Joel Brobecker
2013-03-25 17:46 ` Eli Zaretskii
2013-03-25 18:10 ` Joel Brobecker
2013-03-29 8:02 ` Joel Brobecker
2013-03-29 14:03 ` Eli Zaretskii
2013-03-29 19:53 ` Joel Brobecker
2013-04-02 18:05 ` Eli Zaretskii
2013-04-05 13:03 ` Eli Zaretskii
2013-03-29 15:23 ` Ralf Corsepius
2013-03-25 19:08 ` Mark Kettenis
2013-03-25 19:12 ` Eli Zaretskii
2013-04-06 21:49 ` Pedro Alves
2013-04-07 3:58 ` Eli Zaretskii
2013-03-23 23:38 ` Joel Sherrill
2013-03-24 0:12 ` Mike Frysinger
2013-03-20 18:23 ` Ralf Corsepius
2013-04-01 19:56 ` Mike Frysinger
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=d3juvfb1q08s06stnna8337p.1364522909961@email.android.com \
--to=joel.sherrill@oarcorp.com \
--cc=brobecker@adacore.com \
--cc=chrisj@rtems.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=vapier@gentoo.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