Am Samstag, 18. März 2017 um 00:23:10, schrieb Scott Kostyshak 
<skost...@lyx.org>
> On Wed, Mar 15, 2017 at 03:47:31PM +0100, Kornel Benko wrote:
> > Am Samstag, 11. März 2017 um 22:29:58, schrieb Kornel Benko <kor...@lyx.org>
> > > Am Samstag, 11. März 2017 um 14:47:37, schrieb Scott Kostyshak 
> > > <skost...@lyx.org>
> > > > On Mon, Mar 06, 2017 at 07:09:16PM -0500, Scott Kostyshak wrote:
> > > > > On Mon, Mar 06, 2017 at 12:19:48PM +0100, Kornel Benko wrote:
> > > > > 
> > > > > > Looks like nobody seems to to be interested.
> > > > > 
> > > > > I'm interested and will test in a week when I'm home and have access 
> > > > > to
> > > > > the computer where I have Qt 5.8 installed.
> > > > 
> > > > I can't reproduce with Qt 5.8.1dev (compiled a few weeks ago).
> > > > 
> > > > Scott
> > > 
> > > I tried to compile Qt 5.9.0-alpha, but unfortunately I was unable to do 
> > > it.
> > > Did not even come trough the configuration phase
> > > (You cannot configure qt separately within a top-level build)
> > > 
> > > Should probably try with Qt 5.8.
> > > 
> > >   Kornel
> > 
> > Next try was to compile QT5.8 from source. Now lyx does not crash.
> > 
> > Scott, could you try to check if the binary-provided qt5.8 crashes on your 
> > system?
> 
> Yes I will try this when I'm back to my testing computer (I'm currently
> traveling). I will have to make sure that my custom compiled Qt does not
> interfere. Do I just need to edit
> 
>   /etc/ld.so.conf.d/qt5.conf
> 
> and run
> 
>   sudo ldconfig
> 
> ?
> 
> Scott

Yes, this is sufficient.
If you want to switch more often, you should create a script.
I have a symbolic link, /usr/BUILD/BuildQt, pointing to the correct QT.
And in /etc/ld.so.conf.d/qt5.conf the first line reads
        /usr/BUILD/BuildQtRoot/lib

Also the env PATH contains /usr/BUILD/BuildQtRoot/bin.

In case of using built-in qt, /usr/BUILD/BuildQtRoot is removed.

But to be sure, I always also use 'sudo ldconfig' too.

        Kornel

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

Reply via email to