Hello,

I'm involved in project using OpenRISC. My task is to modify GCC a bit and my current idea is to do this using new GCC plugin framework (supported since GCC v4.5.0).

I downloaded and successfully built or1ksim and toolchain from OpenCores SVN (I built toolchain using build-all.sh script).

Next step was to enable plugins support in GCC, so I added "--enable-plugin" argument to set of arguments passed to GCC's configure script and tried to recompile whole toolchain.

Compilation failed with error below:

---------------------------------------
Links are now set up to build a cross-compiler
from x86_64-unknown-linux-gnu to or32-unknown-elf.
checking for exported symbols... ../binutils/objdump: conftest: File format not recognized
checking for -rdynamic... ../binutils/objdump: conftest: File format not recognized
no
checking for library containing dlopen... -ldl
checking for -fPIC -shared... yes
configure: error:
Building GCC with plugin support requires a host that supports
-fPIC, -shared, -ldl and -rdynamic.
make: *** [configure-gcc] B��d 1
make (all-gcc) failed.
---------------------------------------

Is there any easy way to fix it? Did someone done any effort to use plugins in OpenCores GCC port or I'm first who want to use it :)

I was building only pure toolchain with command: "./bld-all.sh --force --prefix [PATH] --or1ksim-dir [PATH] --no-uclibc --no-or32-linux"

Hi goofacz

Plugins need shared object support, which is not in the GCC 4.5 OpenRISC tool chain. Peter Gavin, Stefan Kristiansson and others have been working on an updated GCC, based on the mainline (what will be GCC 4.8) code base, and I believe Stefan has a prototype version of binutils that supports shared objects.

You are probably best discussing on IRC. freenode.net, channels #opencores and #openrisc.

HTH

Jeremy

--
Tel: +44 (1590) 610184
Cell: +44 (7970) 676050
SkypeID: jeremybennett
Email: jeremy.bennett@embecosm.com
Web: www.embecosm.com

Why do you need to have shared library support on the _target_ to
use plugins?
I mean, he is building a cross-compiler which is to be run on
a x86_64.
Isn't the requirement to have shared library support there
so you can dynamically load the plugins when compiling?
I can't imagine that would be a problem on a x86_64.

Regarding or1k shared lib support, yes I've got something
very primitive working at this point, nothing very exciting yet.
The current WIP is here: https://github.com/skristiansson/or1k-src

@stekern:
Exactly, I think, that it doesn't have anything to do with target platform and it only depends on host platfrom. I'm running Arch Linux with GCC 4.7 compiled with plugins support and it works fine.

I read somewhere, that there was some issue about compiling with plugins support in GCC 4.5.x.

anyway, I'll check it on never version like jeremybennett said.

Hi goofacz, stekern,

Brain now rebooted. You are of course quite right!

The plugin stuff was still very new in GCC, and even now is still being shaken down. It doesn't help that RMS dislikes them (a way to circumvent the GPL), so their functionality is forever being challenged.

Best wishes,

Jeremy