On 25 May 2016 at 18:47, Joseph, Matthew wrote: > Sorry about that Jonathan, I wasn't paying attention to what was above it. Sadly the system is on a closed LAN so it's tough to get the information over so I need to type it out. As you know the GCC outputs are quite large. > If need be I can get the full log over, just takes time. > > /tmp/gcc-4.1.1/install-sh: /tmp/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/tree_assoc_cntnr/constructor_destructor_fn_imps.hpp does not exist > /tmp/gcc-4.1.1/install-sh: /tmp/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/basic_assoc_cntnr/constructor_destructor_fn_imps.hpp does not exist > /tmp/gcc-4.1.1/install-sh: /tmp/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/basic_assoc_cntnr/constructor_destructor_fn_imps.hpp does not exist > /tmp/gcc-4.1.1/install-sh: /tmp/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/basic_hash_assoc_cntnr/constructor_destructor_fn_imps.hpp does not exist > /tmp/gcc-4.1.1/install-sh: /tmp/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/basic_hash_assoc_cntnr/constructor_destructor_fn_imps.hpp does not exist > > Above those lines are a couple paragraphs of commands. They don't seem to contain any errors/warnings. > Let me know though if those are not the output that we need. OK I've seen this before: it's a bug in the Solaris tar command which means those files were not extracted properly and their filenames were truncated. Use GNU tar (it's often installed as gtar, or maybe as /usr/sfw/bin/tar) to extract the GCC sources and it should work.
