From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] nameless LOAD_DLL_DEBUG_EVENT causes ntdll.dll to be missing
Date: Fri, 13 Dec 2013 11:04:00 -0000 [thread overview]
Message-ID: <20131213110420.GA3255@adacore.com> (raw)
In-Reply-To: <52AADC1D.9060207@redhat.com>
> Not speaking for or against the plan, but I don't recall that the
> current restriction was based on directory structure. With
> ACX_CONFIGURE_DIR, we can build libiberty within gdbserver's build
> dir, like we do gnulib (see below), so it seems that's a non-issue
> (even if that was is not the cleanest). Rather, the main issue was
> that libiberty won't build out of the box on some of the gdbserver
> targets, like Windows CE and Lynx, IIRC. CE is probably already
> broken for a while, so it's fine with me to not have it block such a
> change.
The patch only configures libiberty without building it, but going into
that build subdirectory and doing "make", I get a libiberty.a archive
for both ppc-lynx178 and x86-lynx5. So, if CE is not a blocker,
I think we could go ahead.
But this would really only be used by Windows, though, so delay
for after the branch?
--
Joel
next prev parent reply other threads:[~2013-12-13 11:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 11:31 Joel Brobecker
2013-12-03 19:51 ` Pedro Alves
2013-12-03 20:11 ` Eli Zaretskii
2013-12-05 10:54 ` Joel Brobecker
2013-12-05 12:38 ` Pedro Alves
2013-12-09 11:33 ` Joel Brobecker
2013-12-09 17:08 ` Pedro Alves
2013-12-10 10:06 ` pushed: " Joel Brobecker
2013-12-10 10:06 ` Joel Brobecker
2013-12-10 10:56 ` Joel Brobecker
2013-12-10 13:41 ` Pedro Alves
2013-12-10 13:58 ` Pedro Alves
2013-12-12 18:18 ` Joel Brobecker
2013-12-12 18:51 ` Eli Zaretskii
2013-12-12 19:08 ` Pedro Alves
2013-12-12 22:06 ` Tom Tromey
2013-12-13 10:06 ` Pedro Alves
2013-12-13 11:04 ` Joel Brobecker [this message]
2013-12-13 11:21 ` Pedro Alves
2013-12-13 19:38 ` Tom Tromey
2013-12-13 14:17 ` Joel Brobecker
2013-12-13 14:42 ` Pedro Alves
2013-12-13 15:45 ` 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=20131213110420.GA3255@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--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