From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: jan.kratochvil@redhat.com
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: [patch] Fix --enable-plugins --without-python
Date: Fri, 05 Nov 2010 09:08:00 -0000 [thread overview]
Message-ID: <201011050907.oA597VRG012579@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <20101105015148.GA24699@host0.dyn.jankratochvil.net> (message from Jan Kratochvil on Thu, 4 Nov 2010 15:51:49 -1000)
> Date: Thu, 4 Nov 2010 15:51:49 -1000
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
>
> On Tue, 02 Nov 2010 08:43:41 -1000, Joel Brobecker wrote:
> > Grumpf! It would be nice if BFD was telling us which libraries we need
> > to link against bfd, just as Gtk+, Python, etc, do.
>
> I agree we should port the sourceware tree to pkg-config. :-)
Oh dear god, no!
> > I'm a little concern that this is a bit primitive, and good enough only
> > on GNU/Linux or maybe Unix. Or rather, that this might break the build
> > on some platforms such as Windows. But that's not the case, since
> > the user would need to use --enable-plugins to enable plugins (it's
> > not automatic), so I don't see a better solution that's actually
> > worth the effort.
>
> bfd/Makefile.am also just adds `-ldl' (into *_LIBADD) so while I do not
> understand what everything is emulated on these non-UNIX platforms I guess it
> is either broken for --enable-plugins already even for bfd/ or it should work
> even in gdb/ .
Ugh, no, this is broken. On OpenBSD for example, there is no libdl, since
dlopen(3) and friends are available in libc.
prev parent reply other threads:[~2010-11-05 9:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-17 10:41 Jan Kratochvil
2010-11-02 18:43 ` Joel Brobecker
2010-11-05 1:52 ` Jan Kratochvil
2010-11-05 9:08 ` Mark Kettenis [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=201011050907.oA597VRG012579@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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