http://bugzilla.moblin.org/show_bug.cgi?id=5061
--- Comment #5 from mcepl <mcepl(a)redhat.com> 2009-08-05 15:31:07 ---
(In reply to comment #4)
How? As far as I know, this is something which comes automatically
with
libtool. If there is a workaround, then I'd be happy to apply patches for it,
but I suspect that this depends on the build environment and thus must be
solved by distro packagers.
Same with your request to build with a different libtool version. Which one
should I use and why is the one I was using so far (from Ubuntu 8.04 LTS)
causing problems?
The answer to both questions, is that generally it should be OK to use any
libtool anywhere, but unfortunately too old (and non-Fedorish) libtools don't
work with multilib. They understand that /usr/lib is directory where libraries
live per default, but they treat /usr/lib64 as any other non-standard directory
(say something like /opt/syncevolution if it existed) and put rpath to it. And
no, comparing to Debian /usr/lib64 and /usr/lib are not one symlink to other (I
am not sure in which direction it goes on Debian/amd64). So yes, if you can
upgrade libtool, you would save us some effort, but otherwise I can just
regenerate libtool in .spec file (it wouldn't be the first package in Fedora
where it is done ... many non-Fedora distros have ancient libtools).
However, that first sed command with ACLOCAL_AMFLAGS is just a bug in autofoo,
so it should be fixed.
--
Configure bugmail:
http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.