* Dave Korn wrote on Fri, Aug 14, 2009 at 04:30:27AM CEST: > Ralf Wildenhues wrote: > > > But in this particular case, I would argue that either you look at the > > libtool variables shlibpath_var and hardcode_action for "PATH" and > > "unsupported". > > On Cygwin, $hardcode_action = "immediate" in the generated libtool script. > Did you perhaps mean $hardcode_shlibpath_var, which is indeed "unsupported"?
Oh brother, yes, I forgot about those bogus hardcode_libdir_flag_spec settings. They fool _LT_LINKER_HARDCODE_LIBPATH. I don't remember whether they were needed in order to not break some semantics in ltmain (they probably were). Anyway, $hardcode_action = "immediate" is definitely wrong, but fixing that now is also way out of scope of this patch. So I guess we need to stick to host matching in the code, and work out a separate fix for the setting of $hardcode_libdir_flag_spec. Luckily at least my proposed text for the manual is written broadly enough not to need changes due to this ... Thanks, Ralf
