Tuesday, 25 November 2014

Re: [gccsdk] Trunk binutils configuration options

On 21/11/14 19:08, John-Mark Bell wrote:
> All,
>
> Last weekend we played around with using GCC 4.7.4 to cross compile
> NetSurf (we're still using 4.1.2r2 for CI builds). Mostly this worked
> fine without much additional effort (full details in the most recent
> four commits on [1]).
>
> One oddity I'd like some input on, however, is the changeset at [2].
> Specifically, without this change (which enables binutils plugins),
> we cannot use the toolchain to compile OpenSSL (it runs into
> difficulty when linking the OpenSSL command line tools).
>
> I'd like to know if this change is safe

Looking at the binutils source, it seems to be the usual plugin type
code using dlopen, dlsym, etc in libdl, so I don't see this causing
any problems.

> and also whether it's actually something that should be the default
> in GCCSDK itself?

Looks like --enable-plugins now defaults to on in mainline binutils:

<https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=log;h=b879806f2fdd2eca7092d7b854d6cbbbbbd0493b>

We might need some tweaks to the native binutils so that it gets the
plugin location right, but the linker already depends on libdl, so
enabling plugin support shouldn't be a problem.

Lee.


_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK

No comments:

Post a Comment