[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: incorrect "cannot install xxx to a directory not ending in yyy" erro
Re: incorrect "cannot install xxx to a directory not ending in yyy" error
Wed, 02 Dec 2009 10:24:40 +0100
On Wed, 2009-12-02 at 07:05 +0000, Ralf Wildenhues wrote:
> Hi Patrick,
> * Patrick Ohly wrote on Mon, Nov 30, 2009 at 06:41:03PM CET:
> > $ /bin/sh ../../../libtool --mode=install /usr/bin/install -c
> > syncecal.la syncebook.la
> > '/work/runtests/head-gcc-4.3-i386/install/usr/lib/syncevolution/backends/'
> > libtool: install: error: cannot install `syncecal.la' to a directory not
> > ending in /usr/lib/syncevolution/backends/
> > Clearly my install directory *does* end in the expected path, so what
> > the heck?
> Yeah, that looks like a bug. Which libtool version are you looking at?
> I'd like to have a test to expose it, but the following testsuite
> addition passes just fine for me;
The situation in my case was that the .la compiled earlier with libtool
had the slash at the end, which then was used when trying to install it.
I'm not sure whether your test recreates that situation, so I've
attached the two files necessary to trigger the error:
$ /bin/sh ./libtool --mode=install /usr/bin/install -c syncecal.la
libtool: install: error: cannot install `syncecal.la' to a directory not ending
> OTOH, I don't recall us fixing this
> yet, so there's probably something missing.
I had checked the git repo before reporting this, the sed expression was
unchanged. Perhaps libdir was sanitized elsewhere; I haven't actually
tried using libtool from git.
> Can you show more of your build log so we can inspect it, or try out git
> Libtool plus the patch?
If you can't reproduce it with the example files, then I can dig out
more information. Right now both the build machine and myself are
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.