[Pkg-scicomp-devel] building paraview-3.2.3, QT_X11_Xext_LIBRARY not set properly

Ondrej Certik ondrej at certik.cz
Fri Aug 1 16:26:35 UTC 2008

On Fri, Aug 1, 2008 at 5:47 PM, Gero Putzar <gero.putzar at bam.de> wrote:
> Hi Ondrej,
>> This is exactly the right place to ask. Doesn't the paraview package
>> in testing work for you?
> I did not try this, because it was not there by the time when I
> installed paraview from your repos. Now I installed the newer Version
> 3.2.3 from source with the skripts from the pkg-scicomp svn-repository
> (just checked: I've got the latest version). I would rather stay with
> this version, only if you say you desperately need testers for the
> version in the testing-repository, I could downgrade to this version
> again.
>> So try to compile it in pbuilder, it works for me. If it doesn't
>> though, please prepare a patch to our svn repo and we can apply it.
>> (Last time I tried to compile paraview, it worked though).
> What I did was roughly this (just the key points):
> svn co svn://svn.debian.org/pkg-scicomp/paraview/trunk package
> cp ..../paraview-3.2.3.tar.gz tarballs/paraview_3.2.3.orig.tar.gz
> svn-buildpackage -us -uc -rfakeroot
> Is that what you mean with "compile it in pbuilder"? If yes, I can say
> that it doesn't work right out of the box with my computer and this
> configuration. Now you ask for a patch, hmm.
> ... Yes. I think I found something which might help. The debian package
> libxext-dev creates a symlink /usr/lib/libXext.so -> libXext.so.6.4.0.
> But libxext-dev is not in the build dependecies of the paraview pkg,
> yet. I think it should.
> Attached is a patch for the debian/control file, I don't want to
> uninstall everything just to test if that's the right place and
> svn-buildpackage now complains about unmet dependencies. Is that ok for
> you? If the new dependency has to be mentioned somewhere else, I guess
> you know and can fix it with only little effort, right?

The way to work is to create a source package:

svn-buildpackage -rfakeroot --svn-ignore-new -S  -uc -us

if it complain of missing dependencies, use "-d" flag.

then prepare pbuilder, e.g. "man pbuilder", e.g. "sudo pbuilder
--create", "sudo pbuilder --update" and

sudo pbuilder --build paraview_...dsc

This will build it. All uploads to unstable should be checked and
built using this, otherwise it compiles on your own system, which may
not be setup correctly.

I just checked paraview before your patch and it builds just fine in
pbuilder... I think Christophe didn't check that it fails, right? :)

Anyway, if it makes it work for you, then it probably doesn't hurt.
But in unstable this patch is not needed.

And as to installing the package -- you can easily install it from
unstable as well.


More information about the Pkg-scicomp-devel mailing list