Le dim. 23 juil. 2023 à 17:05, Ralf Hemmecke <r...@hemmecke.org> a écrit : > > On 23.07.23 12:44, Grégory Vanuxem wrote: > > Hi Ralf, *, > > > > This is just a shortcut to call Julia[1] directly. > > )julia print(Base.VERSION) > > Aha. > > Did you know that within jfricas you can easily call python stuff via > > )python 1+1 > > ?
Not at all. Thanks for the info :) > > Well, to implement this was too easy since fricaskernel.py runs on > python anyway. > > But you seem to be starting a julia process and then connect to it, right? No, I use the library interface. As Waldek did for GMP, the library, here libjulia.so, is loaded by the underlying LISP, and I just need to initialize it. Two threads (I have two cores on this machine) are started. This is configurable though. So a 'top -H' shows three FRICASsys process instead of one. I don't know what is going on behind the scenes. The exported routines available are in julia.h: https://github.com/JuliaLang/julia/blob/master/src/julia.h > I browsed a bit through your julia-addition-patches. > It seems that they need cleaning up. Webspad shouldn't be in there. Right, it can now be removed, it was there as an eventual utility, and to keep it in the tree. In fact I deleted jfricas 2.0.0 built from source and installed it with pip. > Before I can test your stuff, I need to install Juila. Unfortunately, > Ubuntu 22.04 does not (yet) seem to have a julia.deb package. I would say, forget that. Debian package maintainers tried but I presume they abandoned it. It was a real mess. The Debian policy is to, first separate binaries, libraries, and development stuff (-dev) and, importantly, there mustn't be redundancy between packages. Nor conflicts, files or library versions of course. I am sure you know that. The pain happens for example with llvm package maintainers and julia package maintainers, they were not synchro and tons of issues emerged. In fact, the Julia policy is diametrically opposed. All is included in Julia and even if you build it from scratch the build process will download their dependencies and build them with the modifiers -Wl, -rpath, (runtime library search path). If you want I can give a link to a simple julia-1.9.2.deb binary package or you can use 'dpkg-deb --build' in a prepared tree. You just have to put a DEBIAN/control in it (attached for example). So, something like: $mkdir julia-1.9.2 $mkdir julia-1.9.2/DEBIAN copy control in the DEBIAN directory $mkdir julia-1.9.2/usr eventually mkdir julia-1.9.2/usr/local ... /usr/local/bin etc. etc, i.e. tree of your binary app and your app in it $dpkg-deb --build julia-1.9.2.deb This is not the correct way of course, it allows just to install a binary tarball that can be easily deleted. __ Greg > > Ralf > > -- > You received this message because you are subscribed to the Google Groups "FriCAS - computer algebra system" group. > To unsubscribe from this group and stop receiving emails from it, send an email to fricas-devel+unsubscr...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/msgid/fricas-devel/53e046d8-b53e-3662-ba97-7d3de9321288%40hemmecke.org . __ Greg -- You received this message because you are subscribed to the Google Groups "FriCAS - computer algebra system" group. To unsubscribe from this group and stop receiving emails from it, send an email to fricas-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/fricas-devel/CAHnU2daSBUc5h%2B0jy_t6WeReC58zn5s7mNh7ZRo4cYadC3eV%2Bw%40mail.gmail.com.
control
Description: Binary data
