On 15 March 2012 12:51, Jose-Marcio Martins da Cruz wrote:
>
> I usually (for 10 years or more...) build gcc outside of the source tree.
That's the correct way to do it.
> But I was puzzled because I couldn't do it for most gcc-4x...
>
> Let's say :
> * source code dir is at, say, /pathto/gcc-4.6.3
> * build dir is at, say, /pathto/obj
>
> Compile process stops at stage 3, saying that some files weren't found :
> * ext/pb_ds/detail/resize_policy/hash_load_check_resize_trigger_imp.hpp
> * ext/pb_ds/detail/bin_search_tree_/constructors_destructor_fn_imps.hpp
>
> This are, in fact, symbolic links pointing to the source tree :
>
> *
> /pathto/gcc-4.6.3/libstdc++-v3/include/ext/pb_ds/detail/resize_policy/hash_load_check_resize_trigger_imp.hpp
> *
> /pathto/gcc-4.6.3/libstdc++-v3/include/ext/pb_ds/detail/bin_search_tree_/constructors_destructor_fn_imps.hpp
>
> And, in fact the file names in the source tree are wrong : they have a bad
> extension : .hp instead of .hpp
Try using GNU tar to extract from the archives, this happens sometimes
with Solaris tar.
[Linux C Programming]
[Linux Kernel]
[eCos]
[Fedora Development]
[Fedora Announce]
[Autoconf]
[The DWARVES Debugging Tools]
[Yosemite Campsites]
[Yosemite News]
[Linux GCC]