David: > In the future, is openpkg.dev more appropriate for posts about build > problems? >
No, I think openpkg-users is appropriate for build-talk. > [root@shinji /root]# rpm -e tiff > [root@shinji /root]# find / -name "libtiff*" > /var/spool/pkg/SFWtiff/reloc/sfw/lib/libtiff.so.3 > /var/spool/pkg/SFWtiff/reloc/sfw/man/man3t/libtiff.3t > I kind of doubt that this is a RTFM problem, as Solaris is a pretty well supported platform. It has long been in production use without paying special attention to requirements (outside of a missing cc at bootstrap time - which you have already gotten around). I just hope that your machine did not meet with some unstandard hacks for some reason or was very strangely installed, but I doubt that too. I wouldn't worry about the stuff in /var/spool/pkg, but I assume that you did a pkgrm SFWtiff as well as rpm -r tiff. > Script started on Wed Oct 30 07:46:28 2002 > # rpm --rebuild > # ftp://ftp.openpkg.org/current/SRC/pdflib-4.0.3-20021030.src.rpm > Installing ftp://ftp.openpkg.org/current/SRC/pdflib-4.0.3-20021030.src.rpm > Executing(%prep): env -i /opt/openpkg/lib/openpkg/bash --norc --noprofile > --posix -e /opt/openpkg/RPM/TMP/rpm-tmp.24336 > + cd /opt/openpkg/RPM/TMP > + cd /opt/openpkg/RPM/TMP > + rm -rf pdflib-4.0.3 > + /opt/openpkg/lib/openpkg/gzip -dc > /opt/openpkg/RPM/SRC/pdflib/pdflib-4.0.3.tar.gz > + /opt/openpkg/lib/openpkg/tar -xf - > [...] > Otherwise as you see from your own script ScriptB, rpm unpacks into (1) /opt/openpkg/RPM/TMP/pdflib-4.0.3 on your machine (as it similarly does with all other OpenPKG packages). I think that in the next level of troubleshooting, you should build the package as usual: (2) # rpm --rebuild ftp://ftp.openpkg.org/[...]/pdflib-4.0.3-20021030.src.rpm and then do something like: (3) # cd /opt/openpkg/RPM/TMP/pdflib-4.0.3 (4) # cd tiff (5) # /opt/openpkg/bin/make This is what I would do if I had access to your machine, to find out just what is happening with the tiff library. Maybe it has nothing to do with the native tiff pieces - try checking this by doing the above in another subdirectory such as 'png', 'pdflib', or 'clients'. It looks like although you have ruled out bash or ksh as problem sources, you are building as the root user. Although this shouldn't be a problem, please try building (2) as a normal user. Also do '# which rpm' to make sure you are not using another rpm by accident. Because OpenPKG very cleanly controls the build environment (which isn't the case in (5)), I made another 'alternative' package to troubleshoot. You can try it, in which it tries to build png before tiff, and with no make flags: # rpm --rebuild ftp://ftp.europalab.com/opkgrepo/pdflib-4.0.3-alt2.src.rpm Also it might be raining too much there in Fremont, and so check for leaks in the roof just above your Sun E250 machine ;-) And hopefully all this should tell if (a) the packaging is flawed, (b) your environment is flawed, or (c) some other wierd thing is happening. Let me know what you find, and good luck. Regards, Michael -- [EMAIL PROTECTED] Development Team, Application Services Cable & Wireless Deutschland GmbH
msg00175/pgp00000.pgp
Description: PGP signature
