gen405 status?

[Chris Caudle]

On Wednesday 01 February 2006 12:01, you wrote:
> For C++ to work completely, the bsp_specs and linker
> script have to be just so.  C++ works on the powerpc
> but this BSP might have a tweak or two.

When the CVS sources are built on the test machine, are all options still 
turned on?  I found that --enabledocs also stops the build on the CVS head 
sources, looking for a VERSION variable which was not set.

But back to the original question I had about --enable-cxx failing, I believe 
on closer examination that actually the build of the RTEMS executive 
completes, and the iostream sample application is failing.

Here is my configure call:
../rtems/configure \
--target=powerpc-rtems4.7 \
--disable-itron \
--enable-cxx \
--enable-rdbg \
--disable-docs \
--enable-networking \
--enable-rtemsbsp="gen405"

Here are the tools I have installed:
> rpm -qa | grep rtems | grep powerpc
rtems-4.7-powerpc-rtems4.7-gdb-6.3-1
rtems-4.7-powerpc-rtems4.7-binutils-2.16.1-3
rtems-4.7-powerpc-rtems4.7-gcc-gcc4.0.1newlib1.13.0-4
rtems-4.7-powerpc-rtems4.7-c++-gcc4.0.1newlib1.13.0-4

Here is the last part of the output of "make all" 

powerpc-rtems4.7-g++ -B../../../../../gen405/lib/ -specs bsp_specs -qrtems 
-mcpu=403 -D_OLD_EXCEPTIONS -Dp
pc405 -O4 -fno-keep-inline-functions -g       -o iostream.exe 
init.o ../../../../../gen405/lib/no-dpmem.re
l ../../../../../gen405/lib/no-event.rel ../../../../../gen405/lib/no-msg.rel ../../../../../gen405/lib/no
-mp.rel ../../../../../gen405/lib/no-part.rel ../../../../../gen405/lib/no-signal.rel ../../../../../gen40
5/lib/no-timer.rel ../../../../../gen405/lib/no-rtmon.rel
/opt/rtems-4.7/lib/gcc/powerpc-rtems4.7/4.0.1/../../../../powerpc-rtems4.7/bin/ld: 
error: no memory region
 specified for loadable section `.gnu.linkonce.sb._ZGVNSt7collateIcE2idE'
collect2: ld returned 1 exit status
gmake[5]: *** [iostream.exe] Error 1
gmake[5]: Leaving directory 
`/home/chris/Src/RTEMS/rtems-4.7-build-ppc/powerpc-rtems4.7/c/gen405/testsuite
s/samples/iostream'


I can provide the full config log and build log if anyone is interested in 
looking at this and can't replicate the same failure.
I tried looking at the linkcmds files for the BSP, but it is mostly wildcards, 
and I'm not familiar enough with the format to know how gnu.linkonce.sb.* 
gets expanded into gnu.linkonce.sb._ZGVNSt7collateIcE2idE, or how the 
specific iostream application interacts with the BSP linkcmds file.

I'm happy to do more investigation if someone can point me in the right 
direction, but if left to my own at the moment I'm planning on moving ahead 
with my --disable-cxx configuration until that causes problems, and coming 
back to this later.

-- 
Chris Caudle