Daniel Shahaf wrote on Mon, Jul 13, 2015 at 23:12:16 +0000: > Nico Kadel-Garcia wrote on Sun, Jul 12, 2015 at 14:08:25 -0400: > > On Sun, Jul 12, 2015 at 3:09 AM, Daniel Shahaf <d...@daniel.shahaf.name> > > wrote: > > > Nico Kadel-Garcia wrote on Sun, Jul 12, 2015 at 01:24:56 -0400: > > >> +if [ -L "$ltpath" -a "$ltpath" = "/bin" ]; then > > >> + # Avoid "/bin" symlink to "/usr/bin" confusion > > >> + ltpath=/usr/bin > > >> +fi > > > > > > We can't presume that /usr/bin is the target of /bin when the latter is > > > a symlink. That's not necessarily true everywhere. > > > > Can you think of a specific instance where "libtool" is in > > "/bin/libtool" where this would not apply? In all circumstance I know > > of where "/bin" is a symlink with "libtoolize" in it, it's the case, > > > > Actually I can, but that's besides the point. We need autogen.sh to > work no matter what the /bin symlink points to.
In more words: it's entirely possible that there is a system where /bin is a symlink that points to some location other than /usr/bin, and we need to work on that system too — even if we don't know about it. (Of course this whole sub-discussion becomes moot if we use --print-ac-dir, as discussed elsethread.) Cheers, Daniel
