On Thu, Mar 20, 2014 at 10:31 AM, Stefan Wallentowitz <[email protected]> wrote: > > On 20.03.2014 08:40, Stefan Kristiansson wrote: >> >> On Thu, Mar 20, 2014 at 9:29 AM, Stefan Wallentowitz >> <[email protected]> wrote: >>> >>> On 03/20/2014 01:45 AM, Christian Svensson wrote: >>>> >>>> On Sun, Mar 16, 2014 at 6:10 PM, Stefan Wallentowitz >>>> <[email protected] <mailto:[email protected]>> wrote: >>>> >>>> Hi all, >>>> >>>> can anyone point me out what is missing to make libstdc++ and >>>> -shared work together? I have been playing around and end up with >>>> the "common error". Is there anything fundamentally missing? >>>> Otherwise, may there be a way I could solve this? >>>> >>>> >>>> Are you using uclibc or glibc? I think I had this working in glibc. >>>> If you give me a test case I can test it using glibc and see if it >>>> works. >>>> >>> I try to use uclibc, but the building procedure of libstdc++ does not >>> work when enabling shared libraries as also stated here: >>> http://openrisc.net/toolchain-build.html >>> Where can I find the glibc port? If it supports shared c++, I would use >>> glibc instead.. >>> >>> >> uClibc together with shared libstdc++ works just fine, >> but there are loads of information missing here. >> What toolchain are you speaking about? >> The or32 toolchain that is handled in the build instructions you are >> linking to doesn't support shared libraries at all. >> The or1k toolchain on the other hand does, there are build >> instructions (that are very similar to the ones you linked to) here: >> >> http://opencores.org/or1k/OpenRISC_GNU_tool_chain#Linux_.28uClibc.29_toolchain_.28or1k-linux-uclibc.29 >> >> Stefan > > Hi Stefan, > > sorry for the missing input. I first tried building the or1k toolchain on > the current development heads, but with both toolchains I am facing the > following error: > > checking dynamic linker characteristics... configure: error: Link tests are > not allowed after GCC_NO_EXECUTABLES. > make[1]: *** [configure-target-libstdc++-v3] Error 1 >
Is that when following the exact instructions on the opencores wiki? I think I have seen that error too at some point and I have some vague memory of building without -j argument to make solved it. Also, I myself haven't tested the current gcc head, I bet it's fine, but to rule out everything, you could try the or1k-4.8.1 branch that I'm certain this worked on. Stefan _______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
