Yaakov (Cygwin/X) wrote: > On 28/07/2009 05:56, Dave Korn wrote: >> Yeh, me too. I have a horrible hack in the distro gcc that ascends >> directories until it finds ...../lib/ and replaces that with ..../bin/ > > I'm not sure how you did it, so I just made the attached patch to do > just that. It's a bit of a hack but I don't think it's so horrible. > Chuck, what do you think?
Your patch does basically what Dave's horrible hack did, except his also works if you're installing somewhere other than under THE libdir. His patch "walks" up the directory tree from the .la file location, until it finds a great-uncle ../../../bin directory. > >> add a --bindir= option to libtool This part is not messy >> and modify automake or >> libtoolise to >> ensure it gets passed by the makefiles when they invoke libtool. > > It might be more correct, but implementing this would be *VERY* messy. > Trust me. The first solution would be much, much easier. This part is messy -- and unnecessary for the intended use case. In gcc, all you need to do is explicitly modify the Makefile.am's to pass the necessary option. You don't need to do anything to automake or libtoolize, AFAICT. Which brings me to my question: Yaakov, what is the use case you have for this functionality? Something other than gcc? -- Chuck -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
