On 02/02/2012 12:41 AM, Earl Chew wrote:
Some environments don't support symbolic links :-(If ln -s is not supported, configure can figure it out, and as a last resort uses: LN_S = cp -p I've found two problems with this. The first problem is that LN_S is not propagated past the top-level Makefile. This can manifest as strange GCC_NO_EXECUTABLES messages: Link tests are not allowed after GCC_NO_EXECUTABLES The patch (against an older gcc 4.2.4) addresses this first problem. The second is that: cp -p $1 $2 mimics ln -s $1 $2 only if $1 is an absolute path, or $2 does not contain any path separators. This is not always true. For example: gcc/gcc/config/t-slibgcc-elf-ver: $(LN_S) $(SHLIB_SONAME) $(SHLIB_DIR)/$(SHLIB_SOLINK) There doesn't seem to be any straightforward way around this except diligence: cd $(SHLIB_DIR)&& $(LN_S) $(SHLIB_SONAME) $(SHLIB_SOLINK)
Additionally building in directory libada requires symlinking directories, so 'cp -p' in not enough. I have tried to use there
'cp -pR' instead. Andris PS. I have not tested with 4.7 yet, but with 4.6 it was so
