[oi-dev] Something is wrong with the physfs build

[Andreas Wacknitz]

Hi all,

I have problems publishing the physfs package. The 64 Bits build seem to
have problem.
I have created a sample-manifest that reveals the problem:

diff sample-manifest.p5m sample-manifest.p5m.orig
13c13
< # Copyright 2018 <contributor>
---
> # Copyright 2016 <contributor>
28,30c28,30
< link path=usr/lib/$(MACH64)/amd64/libphysfs.so target=libphysfs.so.1
< file path=usr/lib/$(MACH64)/amd64/libphysfs.so.$(COMPONENT_VERSION)
< link path=usr/lib/$(MACH64)/amd64/libphysfs.so.1 \
---
> link path=usr/lib/$(MACH64)/libphysfs.so target=libphysfs.so.1
> file path=usr/lib/$(MACH64)/libphysfs.so.$(COMPONENT_VERSION)
> link path=usr/lib/$(MACH64)/libphysfs.so.1 \


So, there is an extra "amd64" in the path. And if I check my installed
versions of libphysfs.so.2.0.3 in
/usr/lib and /usr/lib/amd64 the time stamps differ:
ll /usr/lib/libphysfs.so.2.0.3
-r-xr-xr-x   1 root     bin         618K May 27 07:49
/usr/lib/libphysfs.so.2.0.3
ll /usr/lib/amd64/libphysfs.so.2.0.3
-r-xr-xr-x   1 root     bin         804K Feb 12 17:15
/usr/lib/amd64/libphysfs.so.2.0.3


IMO the time stamps should be equal and thus for me this is an
indication that the package contains amd64 files
from a previous build of the library.
Alas, I don't know how to fix the build.

Regards,
Andreas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20180803/322af40a/attachment-0004.html>