Re: pkg/50039: erroneous dependency of print/xpdf on libXp

[Jörn Clausen <joern.clausen%uni-bielefeld.de@localhost>]

>   Can you check, e.g. with 'make show-buildlink3', where libXp is pulled in?

$ bmake show-buildlink3
freetype2
    bzip2
    zlib
libXpm
    x11-links
    xproto
x11-links

(with unmodified Makefile!)

>   >  After commenting out
>   >
>   >  MAKE_ENV+=             SED=${SED:Q} ECHO=${ECHO:Q}
>   >
>   >  from the Makefile, the package is built without requiring libXp.
>
>   It doesn't make sense to me that this change should change anything.

Something mangling the dependencies hits a bug/feature in Solaris sed 
(or is it pkgsrc's gsed? or echo/gecho?) that shortens libXpm to libXp? 
And this piece of code seems to be used only in the toolchain wrapper 
phase, but not when the actual dependencies are resolved or recorded 
while installing the package. Here is more context from the build:

=> Tool dependency nbpatch-[0-9]*: found nbpatch-20100124
=> Build dependency kbproto>=1.0.2: found kbproto-1.0.7
=> Build dependency xproto>=7.0.9: found xproto-7.0.28
=> Build dependency xcb-proto>=1.4: found xcb-proto-1.11
=> Build dependency xextproto>=7.0: found xextproto-7.3.0
=> Build dependency inputproto>=1.4: found inputproto-2.3.1
=> Build dependency printproto>=1.0.3: found printproto-1.0.5
=> Build dependency renderproto>=0.9.3nb1: found renderproto-0.11.1
=> Full dependency urw-fonts-[0-9]*: found urw-fonts-1.0.7pre44
=> Full dependency poppler-utils-[0-9]*: found poppler-utils-0.32.0
=> Full dependency freetype2>=2.4.11: found freetype2-2.5.5
=> Full dependency libXpm>=3.5.4.2: found libXpm-3.5.11
=> Full dependency lesstif>=0.95.2nb4: found lesstif-0.95.2nb5
===> Overriding tools for xpdf-3.04nb1
===> Extracting for xpdf-3.04nb1
===> Patching for xpdf-3.04nb1
=> Applying pkgsrc patches for xpdf-3.04nb1
=> Substituting "paths" in doc/sample-xpdfrc doc/xpdf.1 doc/xpdfrc.5
===> Creating toolchain wrappers for xpdf-3.04nb1
ERROR: libXp>=1.0.0 is not installed; can't buildlink files.
*** Error code 1

OTOH: trussing the build process shows, that in both cases (i.e. with 
the line in Makefile intact and commented out) only /usr/gnu/bin/sed is 
ever executed, no other sed is used. And this happens way before the 
build process fails. And "echo" is never executed before the build 
breaks. Okay, now I am puzzled...

--
Jörn Clausen
Plattformen & Serverdienste
Hochschulrechenzentrum

Universität Bielefeld
Universitätsstraße 25
33615 Bielefeld
Telefon: +49 521 106-12601
E-Mail: joern.clausen%uni-bielefeld.de@localhost

http://www.uni-bielefeld.de/hrz