This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: new plugin bfd_target breaks gdb with --enable-targets=all
On Wednesday 27 May 2009 10:42:21, Rafael Espindola wrote:
> > (using weak in libbfd cries out hack to me, but well)
>
> It is. Since the plugin target already has the bfd_plugin_set_plugin
> function, it would probably be better for it to have a
> bfd_plugin_set_program_name. Would you prefer that solution?
I would prefer that. We do the similar thing for
libiberty's xmalloc (xmalloc_set_program_name). Could
also be new bfd_set_program_name|bfd_get_program_name pair, the
former called even if not supporting plugins, but I'm not a
binutils maintainer, so that's just a suggestion.
> > It looks like something else is still wrong, because otherwise,
> > should gdb be building plugin.c at all if the user doesn't
> > specify --enable-plugins?
>
> The plugin is just a strange target. That is why it is included in
> --enable-targets=all.
:-) That's not an explanation, but I guess it's fine to have it
included in --enable-targets=all as long as it doesn't try
to get built on non -dl capable hosts.
--
Pedro Alves