Thomas,<div>Everything you said is correct as far as I know.</div><div>I did logs for the configure process in both compilations: slack 32 and slack64.</div><div>Take a look at these logs and some info of my slack-x86_64 system I'm attaching to this message.</div>
<div>Regards</div><div>Gilcio<br><br><div class="gmail_quote">2011/9/27 Thomas Ronayne <span dir="ltr"><<a href="mailto:ronayne.thomas@gmail.com">ronayne.thomas@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<u></u>
<div bgcolor="#ffffff" text="#000000">
Are you sure you're compiling the 64-bit version of Tellico?<br>
<br>
If you copy-paste this into a shell prompt (and hit the enter key),
you'll see the ARCH value:<br>
<blockquote>if [ -z "$ARCH" ]; then<br>
case "$( uname -m )" in<br>
i?86) ARCH=i486 ;;<br>
arm*) ARCH=arm ;;<br>
*) ARCH=$( uname -m ) ;;<br>
esac<br>
fi<br>
echo ${ARCH}<br>
<br>
x86_64<br>
</blockquote>
The above is the top section of tellico-SlackBuild that
automagically sets the ARCH value -- and the Tellico build will look
in the right places for libraries.<br>
<br>
The section of the SlackBuild right below the above is where
compiler flags and the search path gets set; i.e.,<br>
<blockquote>if [ "$ARCH" = "i486" ]; then<br>
SLKCFLAGS="-O2 -march=i486 -mtune=i686"<br>
LIBDIRSUFFIX=""<br>
elif [ "$ARCH" = "i686" ]; then<br>
SLKCFLAGS="-O2 -march=i686 -mtune=i686"<br>
LIBDIRSUFFIX=""<br>
elif [ "$ARCH" = "x86_64" ]; then<br>
SLKCFLAGS="-O2 -fPIC"<br>
LIBDIRSUFFIX="64"<br>
else<br>
SLKCFLAGS="-O2"<br>
LIBDIRSUFFIX=""<br>
fi<br>
</blockquote>
If you watch Tellico as it compiles, you should see the "-O2 -fPIC"
flags on any of the C or CC compile lines that are displayed. And
you do not need to edit anything in tellico.Slackbuild for that to
happen.<br>
<br>
If you're using AlienBob's multilib package I cannot imagine that it
would cause this -- the linker is only going to look in /lib64 and
/usr/lib64 during a 64-bit compile (far as I know, anyway).<br>
<br>
Only other thing I can think of is if you've defined LD_LIBRARY_PATH
to search first in /lib and /usr/lib or your /etc/ld.so.conf file
may be defined that way?<div class="im"><br>
<br>
Hope this helps some.<br>
<pre cols="72">A riddle, wrapped in a mystery, inside an enigma but that's my story and I'm stickin' to it.
</pre>
<br></div><div><div></div><div class="h5">
On 09/27/2011 10:17 AM, Gilcio Amaral-Martins wrote:
<blockquote type="cite">Thomas,
<div>I have 2 separate partitions for slack 32 and slack64.</div>
<div>In slack32 exempi package is as follows (from
/var/log/packages):</div>
<div><br>
</div>
<div>
<div>PACKAGE NAME: exempi-2.1.1-i486-1_SBo</div>
<div>
COMPRESSED PACKAGE SIZE: 948K</div>
<div>UNCOMPRESSED PACKAGE SIZE: 2630K</div>
<div>PACKAGE LOCATION: /tmp/exempi-2.1.1-i486-1_SBo.tgz</div>
<div>PACKAGE DESCRIPTION:</div>
<div>exempi: exempi (an implementation of adobe's XMP)</div>
<div>exempi: </div>
<div>exempi: Exempi is an implementation of XMP. Version 1.99.x
is based on Adobe </div>
<div>exempi: XMP SDK 4.1.1 and released under a BSD-style
license like Adobe's. </div>
<div>exempi: </div>
<div>
exempi: The Adobe Extensible Metadata Platform (XMP) is a
standard for </div>
<div>exempi: processing and storing standardized and proprietary
metadata, </div>
<div>exempi: created by Adobe Systems Inc..</div>
<div>exempi:</div>
<div>exempi: Homepage: <a href="http://libopenraw.freedesktop.org/wiki/Exempi" target="_blank">http://libopenraw.freedesktop.org/wiki/Exempi</a></div>
<div>exempi:</div>
<div>FILE LIST:</div>
<div>./</div>
<div>install/</div>
<div>install/slack-desc</div>
<div>install/doinst.sh</div>
<div>usr/</div>
<div>usr/doc/</div>
<div>usr/doc/exempi-2.1.1/</div>
<div>usr/doc/exempi-2.1.1/INSTALL</div>
<div>usr/doc/exempi-2.1.1/exempi.SlackBuild</div>
<div>usr/doc/exempi-2.1.1/AUTHORS</div>
<div>usr/doc/exempi-2.1.1/ChangeLog</div>
<div>usr/doc/exempi-2.1.1/NEWS</div>
<div>usr/doc/exempi-2.1.1/COPYING</div>
<div>usr/doc/exempi-2.1.1/README</div>
<div>usr/include/</div>
<div>usr/include/exempi-2.0/</div>
<div>usr/include/exempi-2.0/exempi/</div>
<div>usr/include/exempi-2.0/exempi/xmperrors.h</div>
<div>usr/include/exempi-2.0/exempi/xmpconsts.h</div>
<div>usr/include/exempi-2.0/exempi/xmp.h</div>
<div>usr/lib/</div>
<div>usr/lib/pkgconfig/</div>
<div>usr/lib/pkgconfig/exempi-2.0.pc</div>
<div>usr/lib/<a href="http://libexempi.la" target="_blank">libexempi.la</a></div>
<div>usr/lib/libexempi.so.3.2.1</div>
<div>usr/lib/libexempi.a</div>
<div><br>
</div>
<div>And in slack64 it was installed as:</div>
<div><br>
</div>
<div>
<div>PACKAGE NAME: exempi-2.1.1-x86_64-1_SBo</div>
<div>COMPRESSED PACKAGE SIZE: 1000K</div>
<div>UNCOMPRESSED PACKAGE SIZE: 3.1M</div>
<div>PACKAGE LOCATION: /tmp/exempi-2.1.1-x86_64-1_SBo.tgz</div>
<div>PACKAGE DESCRIPTION:</div>
<div>exempi: exempi (an implementation of adobe's XMP)</div>
<div>exempi: </div>
<div>exempi: Exempi is an implementation of XMP. Version
1.99.x is based on Adobe </div>
<div>exempi: XMP SDK 4.1.1 and released under a BSD-style
license like Adobe's. </div>
<div>exempi: </div>
<div>
exempi: The Adobe Extensible Metadata Platform (XMP) is a
standard for </div>
<div>exempi: processing and storing standardized and
proprietary metadata, </div>
<div>exempi: created by Adobe Systems Inc..</div>
<div>exempi:</div>
<div>exempi: Homepage: <a href="http://libopenraw.freedesktop.org/wiki/Exempi" target="_blank">http://libopenraw.freedesktop.org/wiki/Exempi</a></div>
<div>exempi:</div>
<div>FILE LIST:</div>
<div>./</div>
<div>install/</div>
<div>install/doinst.sh</div>
<div>install/slack-desc</div>
<div>usr/</div>
<div>usr/lib64/</div>
<div>usr/lib64/libexempi.so.3.2.1</div>
<div>usr/lib64/libexempi.a</div>
<div>usr/lib64/<a href="http://libexempi.la" target="_blank">libexempi.la</a></div>
<div>usr/lib64/pkgconfig/</div>
<div>usr/lib64/pkgconfig/exempi-2.0.pc</div>
<div>usr/doc/</div>
<div>usr/doc/exempi-2.1.1/</div>
<div>usr/doc/exempi-2.1.1/README</div>
<div>usr/doc/exempi-2.1.1/COPYING</div>
<div>usr/doc/exempi-2.1.1/AUTHORS</div>
<div>usr/doc/exempi-2.1.1/ChangeLog</div>
<div>usr/doc/exempi-2.1.1/exempi.SlackBuild</div>
<div>usr/doc/exempi-2.1.1/NEWS</div>
<div>usr/doc/exempi-2.1.1/INSTALL</div>
<div>usr/include/</div>
<div>usr/include/exempi-2.0/</div>
<div>usr/include/exempi-2.0/exempi/</div>
<div>usr/include/exempi-2.0/exempi/xmp.h</div>
<div>usr/include/exempi-2.0/exempi/xmperrors.h</div>
<div>usr/include/exempi-2.0/exempi/xmpconsts.h</div>
</div>
<div><br>
</div>
<div>As you can see they are different packages. Major
difference is that libexempi and pkgconfig/exempi-2.0.pc are
installed in /usr/lib (slack32) and in /usr/lib64 (slack64)</div>
<div>Tellico configure found exempi in slack32 but not in
slack64. Maybe it was looking for /usr/lib and not for
/usr/lib64. If this is true the configure needs a patch to
look for the correct directory.</div>
<div>So I have compiled and installed succesffully tellico-2.3.4
in slack32 and slack64 but exempi was configured only in
slack32. No problems with qjson and yaz.</div>
<div>
Many thanks for your attention</div>
<div>Gilcio Amaral</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<br>
<div class="gmail_quote">2011/9/27 Thomas Ronayne <span dir="ltr"><<a href="mailto:ronayne.thomas@gmail.com" target="_blank">ronayne.thomas@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">Check exempi.SlackBuild; you want it to
look like this for a 64-bit build:<br>
<br>
PRGNAM=exempi<br>
VERSION=${VERSION:-2.1.1}<br>
*ARCH=${ARCH:-x86_64}*<br>
BUILD=${BUILD:-1}<br>
TAG=${TAG:-_SBo}<br>
<br>
If you did not do the above, you built a 32-bit version (and
that ain't gonna work, obviously) and you need to remove
that then build and install the 64-bit version. See note
below.<br>
<br>
So, first thing, remove the package you installed (probably
removepkg exempi-2.1.1-x86-1_SBo, check with ls
/var/log/packages/exempi* to make sure of the name).<br>
<br>
Then<br>
<br>
exempi.SlackBuild<br>
wait a while<br>
mv /tmp/exempi-2.1.1-x86_64-1_SBo.tgz .<br>
installpkg exempi-2.1.1-x86_64-1_SBo.tgz<br>
cd <wherever the Tellico source is><br>
tellico.SlackBuild<br>
<br>
and so on.<br>
<br>
Note: almost all the SlackBuilds have been change to
automagically determine the ARCH setting; however a few have
not and you may need to check the SlackBuild. Bear in mind
that the SlackBuild.org is all-volunteer and it might take
some time for things to catch up.<br>
<br>
Hope this helps some.<br>
<br>
A riddle, wrapped in a mystery, inside an enigma but that's
my story and I'm stickin' to it.<br>
<br>
_______________________________________________<br>
tellico-users mailing list<br>
<a href="mailto:tellico-users@kde.org" target="_blank">tellico-users@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/tellico-users" target="_blank">https://mail.kde.org/mailman/listinfo/tellico-users</a><br>
</blockquote>
</div>
<br>
</div>
</blockquote>
</div></div></div>
</blockquote></div><br></div>