[Tellico-users] exempi.SlackBuild

Gilcio Amaral-Martins gilcio.amaral at gmail.com
Wed Sep 28 00:53:03 UTC 2011 

Thomas,
Everything you said is correct as far as I know.
I did logs for the configure process in both compilations: slack 32 and
slack64.
Take a look at these logs and some info of my slack-x86_64 system I'm
attaching  to this message.
Regards
Gilcio

2011/9/27 Thomas Ronayne <ronayne.thomas at gmail.com>

> **
> Are you sure you're compiling the 64-bit version of Tellico?
>
> If you copy-paste this into a shell prompt (and hit the enter key), you'll
> see the ARCH value:
>
> if [ -z "$ARCH" ]; then
>   case "$( uname -m )" in
>     i?86) ARCH=i486 ;;
>     arm*) ARCH=arm ;;
>        *) ARCH=$( uname -m ) ;;
>   esac
> fi
> echo ${ARCH}
>
> x86_64
>
> 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.
>
> The section of the SlackBuild right below the above is where compiler flags
> and the search path gets set; i.e.,
>
> if [ "$ARCH" = "i486" ]; then
>     SLKCFLAGS="-O2 -march=i486 -mtune=i686"
>     LIBDIRSUFFIX=""
> elif [ "$ARCH" = "i686" ]; then
>     SLKCFLAGS="-O2 -march=i686 -mtune=i686"
>     LIBDIRSUFFIX=""
> elif [ "$ARCH" = "x86_64" ]; then
>     SLKCFLAGS="-O2 -fPIC"
>     LIBDIRSUFFIX="64"
> else
>   SLKCFLAGS="-O2"
>   LIBDIRSUFFIX=""
> fi
>
> 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.
>
> 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).
>
> 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?
>
>
> Hope this helps some.
>
> A riddle, wrapped in a mystery, inside an enigma but that's my story and I'm stickin' to it.
>
>
> On 09/27/2011 10:17 AM, Gilcio Amaral-Martins wrote:
>
> Thomas,
> I have 2 separate partitions for slack 32 and slack64.
> In slack32 exempi package is as follows (from /var/log/packages):
>
>  PACKAGE NAME:     exempi-2.1.1-i486-1_SBo
>  COMPRESSED PACKAGE SIZE:     948K
> UNCOMPRESSED PACKAGE SIZE:     2630K
> PACKAGE LOCATION: /tmp/exempi-2.1.1-i486-1_SBo.tgz
> PACKAGE DESCRIPTION:
> exempi: exempi (an implementation of adobe's XMP)
> exempi:
> exempi: Exempi is an implementation of XMP. Version 1.99.x is based on
> Adobe
> exempi: XMP SDK 4.1.1 and released under a BSD-style license like Adobe's.
> exempi:
>  exempi: The Adobe Extensible Metadata Platform (XMP) is a standard for
> exempi: processing and storing standardized and proprietary metadata,
> exempi: created by Adobe Systems Inc..
> exempi:
> exempi: Homepage: http://libopenraw.freedesktop.org/wiki/Exempi
> exempi:
> FILE LIST:
> ./
> install/
> install/slack-desc
> install/doinst.sh
> usr/
> usr/doc/
> usr/doc/exempi-2.1.1/
> usr/doc/exempi-2.1.1/INSTALL
> usr/doc/exempi-2.1.1/exempi.SlackBuild
> usr/doc/exempi-2.1.1/AUTHORS
> usr/doc/exempi-2.1.1/ChangeLog
> usr/doc/exempi-2.1.1/NEWS
> usr/doc/exempi-2.1.1/COPYING
> usr/doc/exempi-2.1.1/README
> usr/include/
> usr/include/exempi-2.0/
> usr/include/exempi-2.0/exempi/
> usr/include/exempi-2.0/exempi/xmperrors.h
> usr/include/exempi-2.0/exempi/xmpconsts.h
> usr/include/exempi-2.0/exempi/xmp.h
> usr/lib/
> usr/lib/pkgconfig/
> usr/lib/pkgconfig/exempi-2.0.pc
> usr/lib/libexempi.la
> usr/lib/libexempi.so.3.2.1
> usr/lib/libexempi.a
>
>  And in slack64 it was installed as:
>
>  PACKAGE NAME:     exempi-2.1.1-x86_64-1_SBo
> COMPRESSED PACKAGE SIZE:     1000K
> UNCOMPRESSED PACKAGE SIZE:     3.1M
> PACKAGE LOCATION: /tmp/exempi-2.1.1-x86_64-1_SBo.tgz
> PACKAGE DESCRIPTION:
> exempi: exempi (an implementation of adobe's XMP)
> exempi:
> exempi: Exempi is an implementation of XMP. Version 1.99.x is based on
> Adobe
> exempi: XMP SDK 4.1.1 and released under a BSD-style license like Adobe's.
> exempi:
>  exempi: The Adobe Extensible Metadata Platform (XMP) is a standard for
> exempi: processing and storing standardized and proprietary metadata,
> exempi: created by Adobe Systems Inc..
> exempi:
> exempi: Homepage: http://libopenraw.freedesktop.org/wiki/Exempi
> exempi:
> FILE LIST:
> ./
> install/
> install/doinst.sh
> install/slack-desc
> usr/
> usr/lib64/
> usr/lib64/libexempi.so.3.2.1
> usr/lib64/libexempi.a
> usr/lib64/libexempi.la
> usr/lib64/pkgconfig/
> usr/lib64/pkgconfig/exempi-2.0.pc
> usr/doc/
> usr/doc/exempi-2.1.1/
> usr/doc/exempi-2.1.1/README
> usr/doc/exempi-2.1.1/COPYING
> usr/doc/exempi-2.1.1/AUTHORS
> usr/doc/exempi-2.1.1/ChangeLog
> usr/doc/exempi-2.1.1/exempi.SlackBuild
> usr/doc/exempi-2.1.1/NEWS
> usr/doc/exempi-2.1.1/INSTALL
> usr/include/
> usr/include/exempi-2.0/
> usr/include/exempi-2.0/exempi/
> usr/include/exempi-2.0/exempi/xmp.h
> usr/include/exempi-2.0/exempi/xmperrors.h
> usr/include/exempi-2.0/exempi/xmpconsts.h
>
>  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)
> 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.
> 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.
>  Many thanks for your attention
> Gilcio Amaral
>
>
>
>
> 2011/9/27 Thomas Ronayne <ronayne.thomas at gmail.com>
>
>> Check exempi.SlackBuild; you want it to look like this for a 64-bit build:
>>
>>   PRGNAM=exempi
>>   VERSION=${VERSION:-2.1.1}
>>   *ARCH=${ARCH:-x86_64}*
>>   BUILD=${BUILD:-1}
>>   TAG=${TAG:-_SBo}
>>
>> 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.
>>
>> 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).
>>
>> Then
>>
>>   exempi.SlackBuild
>>   wait a while
>>   mv /tmp/exempi-2.1.1-x86_64-1_SBo.tgz .
>>   installpkg exempi-2.1.1-x86_64-1_SBo.tgz
>>   cd <wherever the Tellico source is>
>>   tellico.SlackBuild
>>
>> and so on.
>>
>> 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.
>>
>> Hope this helps some.
>>
>> A riddle, wrapped in a mystery, inside an enigma but that's my story and
>> I'm stickin' to it.
>>
>> _______________________________________________
>> tellico-users mailing list
>> tellico-users at kde.org
>> https://mail.kde.org/mailman/listinfo/tellico-users
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/tellico-users/attachments/20110927/ba81a983/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tellico64-configure.log
Type: text/x-log
Size: 8761 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/tellico-users/attachments/20110927/ba81a983/attachment.log>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tellico32-configure.log
Type: text/x-log
Size: 8442 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/tellico-users/attachments/20110927/ba81a983/attachment-0001.log>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: slack64.info
Type: application/octet-stream
Size: 969 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/tellico-users/attachments/20110927/ba81a983/attachment.obj>

More information about the tellico-users mailing list