yade-dev team mailing list archive

[Anton Gladky <640401@xxxxxxxxxxxxxxxxxx>]

Jerome, try to install yade-bzr package form our ppa
https://launchpad.net/~yade-users/+archive/ppa
But not "yade-bzr1951", just "yade-bzr".

It is also packaged with qt4. Try to start packaged version to check,
whether the problem is in compiling or...

Anton


On Mon, Sep 27, 2010 at 4:23 PM, jduriez <jerome.duriez@grenoble-
inp.fr>wrote:

> - Anton : I followed
> https://yade-dem.org/wiki/Installation_of_yade_on_debian_or_kubuntu, and
> in fact, compared to
> https://www.yade-dem.org/sphinx/installation.html#prerequisities, the
> installation of binutils-gold was missing. Because of that, I put a
> warning on the wiki, advicing to go to sphinx.
> But now it's done, the problem is still not solved.
>
> - Vaclav :
> jduriez@c1solimara-l:~/yade$ scons clean
> scons: Reading SConscript files ...
> @@@ Using profile default (scons.profile-default) @@@
> Yade version is `trunk' (bzr2447), installed files will be suffixed with
> `-trunk'.
> All intermediary files will be in `/home/3S-LAB/jduriez/build-trunk'.
> Cleaning: /home/3S-LAB/jduriez/build-trunk.
> jduriez@c1solimara-l:~/yade$ scons brief=0 2>&1 > build.log
>
> And here is the corresponding log. I do not know exactly what to look
> for in it but it does not seem to contain "qt3" or "libqt-mt-3" characters.
> Concerning your question, no normally I did not fiddle anything, I even
> would not know how to do this... (in this field, I only had to do some
> compilations by defining by hand libstdcxx scons options, but I do not
> think it is linked)
>
> Thanks
>
>
> ** Attachment added: "build.log"
>
> https://bugs.launchpad.net/bugs/640401/+attachment/1643975/+files/build.log
>
> --
> Yade-qt4 does not launch
> https://bugs.launchpad.net/bugs/640401
> You received this bug notification because you are subscribed to Yade.
>
> Status in Yet Another Dynamic Engine: Incomplete
>
> Bug description:
> Since updates executed on 15/09/10, (from a long-time non updated state), I
> can not launch yade with qt4.
>
> If I compile with
>
> PREFIX = '/home/3S-LAB/jduriez/YADE'
> exclude = 'none'
> features = 'gts,log4cxx,opengl,openmp,qt4,vtk'
> version = 'trunk'
> CXXFLAGS = []
> SHCCFLAGS = ['-fPIC']
>
> I get a segmentation fault at the launch :
> jduriez@c1solimara-l:~/YADE/bin$ ./yade-trunk
> Welcome to Yade bzr2438
> Erreur de segmentation
>
> Whereas, if I compile with :
>
> PREFIX = '/home/3S-LAB/jduriez/YADE'
> exclude = 'none'
> features = 'gts,log4cxx,opengl,openmp,vtk'
> version = 'trunk'
> CXXFLAGS = []
> SHCCFLAGS = ['-fPIC']
>
> I have no problem:
> jduriez@c1solimara-l:~/YADE/bin$ ./yade-trunk-ssqt4
> Welcome to Yade bzr2438
> TCP python prompt on localhost:9000, auth cookie `aukesy'
> XMLRPC info provider on http://localhost:21000
> [[ ^L clears screen, ^U kills line. F8 plot. ]]
> Yade [1]:
>
> I'll try to compile on debug mode to have more information (not sure it is
> possible on my PC)
>
>
>

-- 
Yade-qt4 does not launch
https://bugs.launchpad.net/bugs/640401
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.

Status in Yet Another Dynamic Engine: Incomplete

Bug description:
Since updates executed on 15/09/10, (from a long-time non updated state), I can not launch yade with qt4.

If I compile with 

PREFIX = '/home/3S-LAB/jduriez/YADE'
exclude = 'none'
features = 'gts,log4cxx,opengl,openmp,qt4,vtk'
version = 'trunk'
CXXFLAGS = []
SHCCFLAGS = ['-fPIC']

I get a segmentation fault at the launch : 
jduriez@c1solimara-l:~/YADE/bin$ ./yade-trunk
Welcome to Yade bzr2438
Erreur de segmentation

Whereas, if I compile with :

PREFIX = '/home/3S-LAB/jduriez/YADE'
exclude = 'none'
features = 'gts,log4cxx,opengl,openmp,vtk'
version = 'trunk'
CXXFLAGS = []
SHCCFLAGS = ['-fPIC']

I have no problem:
jduriez@c1solimara-l:~/YADE/bin$ ./yade-trunk-ssqt4
Welcome to Yade bzr2438
TCP python prompt on localhost:9000, auth cookie `aukesy'
XMLRPC info provider on http://localhost:21000
[[ ^L clears screen, ^U kills line. F8 plot. ]]
Yade [1]:

I'll try to compile on debug mode to have more information (not sure it is possible on my PC)