I don't think so. MULTILIB_OSDIRNAMES controls multilib build, cri.o,
crtn.o do not belong to multilib.
Here's a walk a round way:
Modify the contents of file
"build-open64-svn/osprey-gcc-4.2.0/host-unknown/gcc/specs":
*startfile:
%{!shared: %{pg|p|profile:gcrt1.o%s;pie:Scrt1.o%s;:crt1.o%s}}
*/usr
There should be a file named config.log in the libstdc++-v3 and you may get
more clues fro there. Now the build scripts has built the gcc 4.2
(/home/nancy/work/build-open64-svn/osprey-gcc-4.2.0/host-unknown/gcc/xgcc)
and tried to use it to build the libstdc++ shipped with gcc 4.2 (otherwise
there w
