[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Backport to Woody: dpkg-shlibdeps failure



Le mar 07/10/2003 à 16:44, Chris Halls a écrit :
> On Tue, Oct 07, 2003 at 07:47:41AM +0200, Jérôme Warnier wrote:
> > dpkg-shlibdeps: warning: format of libstlport_gcc.so not recognized
> > /usr/bin/ldd: line 1: 24722 Segmentation fault     
> > LD_TRACE_LOADED_OBJECTS=1 LD_WARN= LD_BIND_NOW=
> > LD_LIBRARY_VERSION=$verify_out LD_VERBOSE= ${RTLD} "$file"
> > dpkg-shlibdeps: failure: ldd on
> > `debian/openoffice.org-bin/usr/lib/openoffice/program/filter/libicg645li.so' gave error exit status 1
> > dh_shlibdeps: command returned error code 2816
> 
> We seem to see random problems in dh_shlibs like this sometimes.  Try
> excluding this from the files that it looks at (-Xlibicg645li.so).
With this I finally got it to work by myself, I'm going to try to remove
the directory like you told me:
        dh_shlibdeps -l $(MAINPKGDIR)-bin/$(OPENOFFICEDIR)/program \
        $(SHLIBS_OVERRIDE)
-Xdebian/openoffice.org-bin/usr/lib/openoffice/program/filter/libicg645li.so \
       
-Xdebian/openoffice.org-bin/usr/lib/openoffice/program/libevoab1.so \
       
-Xdebian/openoffice.org-bin/usr/lib/openoffice/program/libflat645li.so

I'll try this instead at next build:
        dh_shlibdeps -l $(MAINPKGDIR)-bin/$(OPENOFFICEDIR)/program \
        $(SHLIBS_OVERRIDE) -Xlibicg645li.so -Xlibevoab1.so
-Xlibflat645li.so

> > BTW, it would be really great if it did not build Python 2.2 but used
> > the version already on the system.
> 
> Sure.  Finish the patch and we'll happily include it.  It's not trivial...
Rene told me that it was due to the fact that standard Python 2.2 would
not do it, it needed patches. Do you know at least if 2.2.1 (Woody's
version) would suffice?

> Chris
> P.S. I already started it a long time ago. It's called system-python.diff
I know, I know. You already do a great work, thanks.

-- 
Jérôme Warnier <jwarnier@beeznest.net>

Attachment: signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e=2E?=


Reply to: