Andrej Borsenkow wrote:
>>get the same problem. It drives me crazy.
>>
>
> You have to install your program using
>
> libtool --mode=install
>
> There were reports about problems with automatic libtoolization used in
> Mandrake RPMs. I presume, libtoolize program does not catch all cases
> correctly. Here is how your install rule may look like:
>
> $(LIBTOOL) --mode=install $(INSTALL_PROGRAM) $$p
> $(DESTDIR)$(bindir)/`echo $$p|sed 's/$(EXEEXT)$$//'|sed
> '$(transform)'|sed 's/$$/$(EXEEXT)/'`
>
> -andrej
Thanks for your answer, Andrej, but I did not understand what I was
supposed to do with what you wrote... :( Well, I tried to add a
"libtool" line in my specfile but it complains about the file dvcont
now, as it is not a good libtool file or something like that...
Well, ermmm, I will upload the 2mdk package to /incoming, with still
*broken* test programs, since the library should work without them
anyway. And I will add a "TODO" in the changelog to state that I'm not
good enough to fix the binaries. Only hope is that the author of the
program comes with a simple solution to fix this problem (but I doubt it
is related to his program since it compiles fine from tarball, what is
wrong must be the $RPM_BUILD_ROOT that libtool does not use, or
something like this).
Anyway, I upload the SRPM at http://atlantid.org/rpms just in case
you're interested to see for yourself. Note that you will need to
install libraw1394 at the same location (the one in contribs will not
work). Those packages are safe regarding what is installed and
uninstalled, I've tested them.
Gr�goire
