The Bellinghman (bellinghman) wrote,
The Bellinghman
bellinghman

Clue needed

OK, I need a clue or two.

Has anyone successfully compiled GCC 4.2.0 under Solaris 8, using GCC 3.3.2? I'm getting several hours into the build, and then getting a failure:

In file included from /export/spare/dev/gcc-4.2.0/sparc-sun-solaris2.8/libstdc++-v3/include/ext/pb_ds/detail/standard_policies.hpp:51,
from /export/spare/dev/gcc-4.2.0/sparc-sun-solaris2.8/libstdc++-v3/include/ext/pb_ds/assoc_container.hpp:52,
from /export/spare/dev/gcc-4.2.0_src/libstdc++-v3/include/precompiled/extc++.h:59:
/export/spare/dev/gcc-4.2.0/sparc-sun-solaris2.8/libstdc++-v3/include/ext/pb_ds/hash_policy.hpp:57:87: error: ext/pb_ds/detail/resize_policy/hash_load_check_resize_trigger_size_base.hpp: No such file or directory


What's confusing me is that the file does, so far as I can tell, exist.

bash-2.03$ cd /export/spare/dev/gcc-4.2.0/sparc-sun-solaris2.8/libstdc++-v3/include
bash-2.03$ ls -l ext/pb_ds/detail/resize_policy/hash_load_check_resize_trigger_size_base.hpp
lrwxrwxrwx 1 alan dev 128 Jun 11 17:56 ext/pb_ds/detail/resize_policy/hash_load_check_resize_trigger_size_base.hpp -> /export/spare/dev/gcc-4.2.0_src/libstdc++-v3/include/ext/pb_ds/detail/resize_policy/hash_load_check_resize_trigger_size_base.hpp


Is this OS too old for me to build this, or what? (I'll note that the other inclusions from that source file from that directory work fine - is it a filename length?) I'll candidly admit that I've not tried to use Solaris before, and I've never tried to build gcc either.

ETA: OK, I think I know the answer. When I extracted the sources from the tar file, tar itself truncated some file names. So though the links exist, the linkees don't ... not when the names are very long.

Currently building Gnu tar, and will then use that to reextract all the sources
Subscribe
  • Post a new comment

    Error

    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

    Your IP address will be recorded 

  • 2 comments