From: Eli Zaretskii <eliz@gnu.org>
To: Pavel Chupin <pavel.v.chupin@gmail.com>
Cc: gdb-patches@sourceware.org, hjl.tools@gmail.com
Subject: Re: [PATCH] Fix libtool.m4 dlopen lookup for mingw
Date: Tue, 27 Nov 2012 14:58:00 -0000 [thread overview]
Message-ID: <83lidnxfbn.fsf@gnu.org> (raw)
In-Reply-To: <CANwJu1-ObTbjMgehfWOY7xTtkaEx3=3Kw-eqfhPJLA3f91MA1A@mail.gmail.com>
> Date: Tue, 27 Nov 2012 11:05:17 +0400
> From: Pavel Chupin <pavel.v.chupin@gmail.com>
>
> Attached patch removes mingw from special cases of dlopen lookup. It
> allows dlopen to be found later in libdl and have it added properly as
> -ldl in bfd and sim builds.
What effect will this have on native builds, where both host and
target are MinGW? Will it require to have libdl installed? AFAIR, it
doesn't require that now.
If this problem only happens with this combination of host, target,
and build:
> ../configure --enable-plugins --target=arm-linux-android
> --host=i586-pc-mingw32msvc --build=i386-linux-gnu
then wouldn't it be better to fix only that combination?
prev parent reply other threads:[~2012-11-27 14:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 7:05 Pavel Chupin
2012-11-27 8:11 ` Joel Brobecker
2012-11-27 8:16 ` Kai Tietz
2012-11-27 12:17 ` Pavel Chupin
2012-11-27 13:33 ` Joel Brobecker
2012-11-27 14:58 ` Eli Zaretskii [this message]
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=83lidnxfbn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=pavel.v.chupin@gmail.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