Hi again!
With wgcc (again ;o)) i now tell libtool, that hardcoding is
"unsupported". Configure tells this too now, so everything seems to be
ok. But when i run hardcode.test:
= Searching for hardcoded library directories in each program
.libs was not hardcoded in `hc-direct', as libtool expected
.libs was not hardcoded in `hc-libflag', which fooled libtool
.libs was not hardcoded in `hc-libpath', as libtool expected
.libs was not hardcoded in `hc-minusL', as libtool expected
FAIL: hardcode.test
Err... When hardcoding is unsupported, why the ... Does libtool expect
hardcoded paths? Libtool looks like this:
hardcode_action=unsupported
hardcode_into_libs=yes
hardcode_libdir_flag_spec="\${wl}-rpath,\$libdir"
hardcode_libdir_flag_spec_ld=""
hardcode_libdir_separator=""
hardcode_direct=no
hardcode_minus_L=no
hardcode_shlibpath_var=no
hardcode_automatic=no
I know i will set hardcode_into_libs to no in the future, but i don't
think this is the reason, or could this be?
Cheers, markus
_______________________________________________
http://lists.gnu.org/mailman/listinfo/libtool
