[csw-maintainers] gar, checkpkg and subversion ... bratislava?

Ben Walton bwalton at opencsw.org
Sun Apr 22 18:05:58 CEST 2012


Excerpts from rupert THURNER's message of Wed Apr 11 16:36:53 -0400 2012:

Hi Rupert,

> tried to build svn-1.7.4 ... and the result were a lot of checkpkg
> errors which looked correct ... but i am unsure where they came from,
> see here: http://sourceforge.net/apps/trac/gar/changeset/17593/csw

I dug into this a bit last night and some more this morning.  It looks
like the DESTDIR setting for the python swig binding installation was
$(DESTDIR)/lib/python.  This was causing the extra /lib/python path to
be prepended to the otherwise sane file layout.

I'm down to the following list of checkpkg issues:

CHECKPKG_OVERRIDES_CSWjavasvn += bad-rpath-entry|/lib|/tmp/pkg_Vsw_QH/CSWjavasvn/root/opt/csw/lib/svn/libsvnjavahl-1.so.0.0.0
CHECKPKG_OVERRIDES_CSWjavasvn += bad-rpath-entry|/opt/SUNWspro/lib|/tmp/pkg_Vsw_QH/CSWjavasvn/root/opt/csw/lib/svn/libsvnjavahl-1.so.0.0.0
CHECKPKG_OVERRIDES_CSWjavasvn += bad-rpath-entry|/opt/SUNWspro/lib/rw7|/tmp/pkg_Vsw_QH/CSWjavasvn/root/opt/csw/lib/svn/libsvnjavahl-1.so.0.0.0

These need attention but I think they're not the same problems you
were facing.

One thought I just had is that the build may work for me and not for
you (or others that looked) due environmental differences.  The
primary steps that GAR runs are done in a mostly sanitized environment
using 'env -i' where only things we explicitly want to push there are
set.  The python and other language bindings for subversion are built
in custom stages and are not subjected to this clean environment.

I just the build with the following (now committed) patch applied and
get the same results:

Index: Makefile
===================================================================
--- Makefile    (revision 17811)
+++ Makefile    (working copy)
@@ -351,8 +351,8 @@
        touch \
                $(WORKSRC)/subversion/bindings/swig/python/*.c \
                $(WORKSRC)/subversion/bindings/swig/python/*.py
-       @$(BUILD_ENV)   gmake -C $(WORKSRC) swig-py
-       @$(INSTALL_ENV) gmake -C $(WORKSRC) install-swig-py
DESTDIR=$(DESTDIR)
+       @/usr/bin/env -i $(BUILD_ENV) /opt/csw/bin/gmake -C $(WORKSRC)
swig-py
+       @/usr/bin/env -i $(INSTALL_ENV) /opt/csw/bin/gmake -C
$(WORKSRC) install-swig-py DESTDIR=$(DESTDIR)
        #@$(TEST_ENV)    gmake -C $(WORKSRC) check-swig-py
        @$(MAKECOOKIE)

I think this change should likely be applied to the others as well
once they're verified.

Can someone try the recipe now and see if it works for anyone other
than me?

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302



More information about the maintainers mailing list