Alexander Khryukin escreveu:
> Now i porting OMV to AARCH64 architecture and i got a strange thing
>
> Command to build:
> 1. clone pcre package
> 2. rpm -ba --nodeps --target aarch64-mandriva-linux-gnu --without check
> --with bootstrap --with crosscompile --without dietlibc --without diet
> --without minizip --without uclibc --define "_sourcedir `pwd`" --define
> "_builddir `pwd`/BUILD" --define "_rpmdir `pwd`/RPMS" --define "_srpmdir
> `pwd`/SRPMS" *.spec
>
> in output i see
>
> Wrote:
> /home/fff/crossbuild/packages/gamin/pcre/RPMS/aarch64/pcre-8.33-1-omv2014.0.aarch64.rpm
> Wrote:
> /home/fff/crossbuild/packages/gamin/pcre/RPMS/aarch64/lib64pcre1-8.33-1-omv2014.0.aarch64.rpm
> Wrote:
> /home/fff/crossbuild/packages/gamin/pcre/RPMS/aarch64/lib64pcre16_0-8.33-1-omv2014.0.aarch64.rpm
> Wrote:
> /home/fff/crossbuild/packages/gamin/pcre/RPMS/aarch64/lib64pcrecpp0-8.33-1-omv2014.0.aarch64.rpm
> Wrote:
> /home/fff/crossbuild/packages/gamin/pcre/RPMS/aarch64/lib64pcreposix1-8.33-1-omv2014.0.aarch64.rpm
> Wrote:
> /home/fff/crossbuild/packages/gamin/pcre/RPMS/aarch64/lib64pcreposix0-8.33-1-omv2014.0.aarch64.rpm
> Wrote:
> /home/fff/crossbuild/packages/gamin/pcre/RPMS/aarch64/lib64pcre-devel-8.33-1-omv2014.0.aarch64.rpm
> Wrote:
> /home/fff/crossbuild/packages/gamin/pcre/RPMS/aarch64/pcre-debuginfo-8.33-1-omv2014.0.aarch64.rpm
>
>
> Looks like a good ouput, but..
>
> rpm -qlp
> /home/fff/crossbuild/packages/gamin/pcre/RPMS/aarch64/lib64pcre1-8.33-1-omv2014.0.aarch64.rpm
>
> /lib64/libpcre.so.1.2.1
>
> Only ONE lib!
>
> let's see what's contains same package on x86 arch
>
> rpm -qlp /home/fff/pcre/RPMS/x86_64/lib64pcre1-8.33-1-omv2013.0.x86_64.rpm
> /lib64/libpcre.so.1
> /lib64/libpcre.so.1.2.1
>
> Two libs where libpcre.so.1 is a SYMLINK
>
> Yesterday i got the same thing with bzip2 package
> see my patch
> https://abf.rosalinux.ru/openmandriva/bzip2/blob/master/build_good-so-lib.patch
>
> But maybe it is a RPM BUG?

  Probably the tarball was generated with an auto* and/or libtool that does
not know about aarch64.

  libtoolize and autoreconf are supposed to "fix" these cases...

> Ideas?

Paulo


Reply via email to