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

Bug#457075: Salomé packaging



Hi André,

Apologies for the long delay in replying since your message arrived.
I've been very busy, and just yesterday finally compiled Salomé.

On Wed, 2010-04-07 at 12:06 +0200, Andre Espaze wrote:
> Hi Adam,
> 
> > 
> > > Concerning the 5.1.3-5, I can not start Salomé from debian/tmp/usr. The
> > > funny point is that I can run Salomé when compiling it by hand in a
> > > dedicated directory. An identified problem was the line:
> > > 
> > >     chmod -x $(CURDIR)/debian/tmp/usr/lib/python2.5/*-packages/salome/*
> > > 
> > > however I still get the 'Study server is not found' error at startup. I
> > > have reached a point where I am comparing the configuration steps,
> > > I hope to identify the problem soon.
> > 
> > Thanks for your work on this.  Between the two of us, I hope we can find
> > out what's breaking this soon...
> I made the KERNEL and GUI modules work this morning on the 5.1.3-5
> release. I have enclose the patch 'kernel-gui-building.patch' that
> should be applied on the revision:
> 
>     862cebe157a4ce50984d6fc15758da7d3ca96e2a
>     Thu Mar 4 20:29:30 2010
>     Remove troublesome /usr/bin subdirectory from HXX2SALOME.
> 
> by:
> 
>     patch -p1 < kernel-gui-building.patch
> 
> The steps for running the resulting Salome are provided inside the patch.
> 
> For me, the main problem was that I did not install the shared 
> librairies stored in the package libsalome-dev. It explains why
> I could run Salome by ajusting environment variables to debian/tmp/usr 
> but never once installed on the system.

Indeed, you found the problem!  The shared libraries themselves are not
in the -dev package, only the symlinks are, but for some reason the -dev
package is required to run Salomé.  We'll have to investigate why...

> By the way, it is correct 
> to have the line:
>     usr/lib/*.so
> inside 'debian/libsalome-dev.files'? 

That's fine: the shared library package gets the real shared libraries
*.so.0.0.0 , and -dev gets the symlinks *.so .  If the library loading
code needs the .so files, then that's something to fix.

> I guess that it is not relevant to run the 5.1.3-4 build again 
> if this version works for you. I am now starting a complete build
> with all modules.

I've built -5 with everything but VISU and NETGENPLUGIN (which don't
build), they're at http://lyre.mit.edu/~powell/salome/ .

There's lots more to do, but having a version which runs seems like a
big milestone.  If you could test it, that would be great.  This may
even be worth uploading, so it gets started in the NEW queue, and if all
goes well we can start using the Debian bug reporting system.

By the way, have you had any luck with asking upstream to adopt some of
these patches?  Let me know if you need more information about any of
them.

-Adam
-- 
GPG fingerprint: D54D 1AEE B11C CE9B A02B  C5DD 526F 01E8 564E E4B6

Engineering consulting with open source tools
http://www.opennovation.com/

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: