Gaby,

This problem had me scratching my head for a long time.  Tonight I
happened to find this:

wspage@suse:~> ls -l
/usr/local/lib64/open-axiom/x86_64-unknown-linux-gnu/1.5.0-2016-02-07/bin/*

-rwxr-xr-x 1 wspage users   127544 Feb 18 21:57
/usr/local/lib64/open-axiom/x86_64-unknown-linux-gnu/1.5.0-2016-02-07/bin/asq
-rwxr-xr-x 1 wspage users  1152088 Feb 18 22:50
/usr/local/lib64/open-axiom/x86_64-unknown-linux-gnu/1.5.0-2016-02-07/bin/AXIOMsys
-rwxr-xr-x 1 wspage users 50921520 Feb 18 21:41
/usr/local/lib64/open-axiom/x86_64-unknown-linux-gnu/1.5.0-2016-02-07/bin/bootsys
-rwxr-xr-x 1 wspage users   194448 Feb 18 21:57
/usr/local/lib64/open-axiom/x86_64-unknown-linux-gnu/1.5.0-2016-02-07/bin/clef
-rwxr-xr-x 1 wspage users 49184816 Feb 18 21:41
/usr/local/lib64/open-axiom/x86_64-unknown-linux-gnu/1.5.0-2016-02-07/bin/lisp
lrwxrwxrwx 1 root   root         8 Feb  9 08:08
/usr/local/lib64/open-axiom/x86_64-unknown-linux-gnu/1.5.0-2016-02-07/bin/open-axiom
-> AXIOMsys
-rwxr-xr-x 1 wspage users   255296 Feb 18 21:57
/usr/local/lib64/open-axiom/x86_64-unknown-linux-gnu/1.5.0-2016-02-07/bin/sman
-rwxr-xr-x 1 wspage users   134560 Feb 18 21:58
/usr/local/lib64/open-axiom/x86_64-unknown-linux-gnu/1.5.0-2016-02-07/bin/viewAlone

wspage@suse:~/open-axiom>

Notice the link with a different date and different owner. I am not
sure exactly when this link was created - presumably some time before
I decided to experiment with building OpenAxiom with the QT4 gui.
After I completely blew away '/usr/local/lib64/open-axiom' and re-ran
the 'make install' it now all works as you describe.  My guess is that
first building OpenAxiom without QT installed, then installing QT and
re-building OpenAxiom without first uninstalling it was a bad idea.

Anyway, I am happy again.


On 18 February 2016 at 02:46, Gabriel Dos Reis
<g...@integrable-solutions.net> wrote:
>
> On Mon, Feb 15, 2016 at 6:26 AM, Bill Page <bill.p...@newsynthesis.org>
> wrote:
>> ...
>> Yes a QT interface would be nice but (re-)implementing HyperDoc and
>> Graphics in QT seems to me like a lot of effort. The current fashion
>> trend however seems to be browser-based interfaces like Jupyter.
>
>
> Yes, the QT front-end should not be seen as excluding a Jupiter front-end,
> and I would welcome contributions implementing the Jupiter front-end.
>

Do you think it is worthwhile first porting Kurt's Jupyter FriCAS
kernel to OpenAxiom? I think it is/was his intention that it should be
Axiom-agnostic and run on any flavor.  But as I said it is based
rather centrally on Lisp and QuickLisp.  As far as I know it has only
been fully tested on FriCAS built with SBCL.

>>
>> Probably QT5 is a reasonable target.
>
>
> Great!
>

Have you tried a QT5 build yet? Are there any known challenges in the
difference between QT4 and QT5?

>>
>>
>> > My personal development environment these days is OS X El Capitan, I can
>> > have access to OpenSUSE Tumbleweed but only sporadically.  I would have
>> > to rely on you for OpenSUSE Leap -- I am not familiar with its
>> > characteristics.
>> >
>>
>> I can try.
>>

I can now report success with OpenSUSE Leap and QT4.

>>
>> At this point I have *both* QT4.8 and QT5 installed.  Maybe that is a
>> problem?
>
> That might be the issue.
>

No, that turns out not to be a problem.

> ...
> Yes, unfortunately, I cannot reproduce this on the opens use tumbleweed I
> have access to.
>

Thank you very much for checking and letting me know.

I think I will try a build with QT5 and see how far I get.

Bill.

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
open-axiom-devel mailing list
open-axiom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open-axiom-devel

Reply via email to