Hi Albert,
The shell script in the attached zip file builds a working 64 bit libglob.dll under MSYS2 (just ignore the warnings).
I tried to build 64 bit Pure under MSYS2 several times. It builds
successfully, but some tests are still failing. I use it, because
I need 64 bit ODBC drivers, but I cannot use some features.
Jiri
--
You received this message because you are subscribed to the Google Groups "pure-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pure-lang+...@googlegroups.com.
To post to this group, send email to pure...@googlegroups.com.
Visit this group at https://groups.google.com/group/pure-lang.
For more options, visit https://groups.google.com/d/optout.
The shell script in the attached zip file builds a working 64 bit libglob.dll under MSYS2 (just ignore the warnings).
I tried to build 64 bit Pure under MSYS2 several times. It builds successfully, but some tests are still failing. I use it, because I need 64 bit ODBC drivers, but I cannot use some features.
Dne 22.2.2018 v 23:42 Albert Graef napsal(a):
AlbertCheers,The only remaining issue with 64 bit on Windows is that pesky libglob library. I currently only have a 32 bit version of that (pilfered from my old build system). Still need to find a stand-alone version, preferably one that compiles cleanly with both mingw32 and mingw64 so that I can just add it to the Pure source. (Gnulib is not an option as it pulls in most of Gnulib if I just want to build that one little library.) If anyone more in the know on Windows has an idea on this, I'd like to hear about it!BTW, this is still a 32 bit build, but now that I have everything in msys2 there shouldn't be any major roadblocks preventing compilation with mingw64.I know that most of you guys on Windows 10 are probably developing using the Linux subsystem now, but I think that there's still some value in a Windows-native port of Pure. In any case I also needed this for my students so that they can run pd-pure and pd-faust in Pd, so there it is now. As usual, bug reports are appreciated. :)Hi everybody,Spring cleaning comes a bit early this year. :) My old virtual winxp build system was getting a bit long in the tooth (ancient msys+mingw, 32 bit only), so I now set up a new one based on Windows 10 and msys2 (http://www.msys2.org/), and created a new one-click msi installer which now installs into an existing msys2/mingw32 environment. More information is on this new wiki page here: https://github.com/agraef/pure-lang/wiki/PureOnWindows
--
Dr. Albert Gr"af
Computer Music Research Group, JGU Mainz, Germany
Email: agg...@gmail.com
WWW: https://plus.google.com/+AlbertGraef
--
You received this message because you are subscribed to the Google Groups "pure-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pure-lang+unsubscribe@googlegroups.com.
To post to this group, send email to pure...@googlegroups.com.
Visit this group at https://groups.google.com/group/pure-lang.
For more options, visit https://groups.google.com/d/optout.
Hi everybody,
Win10's Linux subsystems supports only command line programs (no Xserver, no daemons at all). Some programs can use Xserver installed on Windows (e. g. Xming) - it depends on set of features supported by the Linux subsystem. The programs are real Linux binaries. They can access Windows filesystem, can access the network, but otherwise they cannot share anything with Windows. Pure compiles and runs without any glitches and can use addons, provided that they are compiled under the Linux subsystem.
On Fri, Feb 23, 2018 at 12:58 PM, Albert Graef <agg...@gmail.com> wrote:
Yeah, I remember that now, it's this old issue here: https://bitbucket.org/purelang/pure-lang/issues/10. I've now opened a new ticket at GH over here: https://github.com/agraef/pure-lang/issues/16, so that I can have another go at it during the semester holidays. We're so close -- there just ought to be a way to make it work in mingw64.
Should be fixed with rev. 088b875. Passes all tests for me now (even the notorious test020 which fails in 32 bit because of apparent msvcrt IEEE 754 incompatibilities), and the minimal test witness [1,2]!5
now properly reports an exception.
Jiri, could you please give it whirl?
Albert
Yes, works fine. I used the (trick) configure below to provoke a fallback to 3.5
/ static. BTW it works with the native Tm as well when wrapping into a CMD file.
Hi Albert,
Three test fail for me :-(. Diffs are attached. Are the log files
up to date? I installed a fresh MSYS2 bundle and cloned a fresh
pure-lang tree. Exceptions work well - no crashes.
Jiri
The failures are random with that setting. Test 042 failed for
the first time , succeeded for the second. So I tried "make check"
again. All tests passed in the firs run. Tests 011 and 021 failed
in the repeated run.
No improvement :-(. I removed locales for "cs", reconfigured & recompiled and get still random fails. I even removed locales at all with almost the same result.
Repeated pure test011.pure in the "test" subdir gives randomly
either
$ pure test011.pure
or
test011.pure, line 2: unhandled exception 'scanf_error ()' while evaluating 'sscanf "this" "%d"'
test011.pure, line 3: unhandled exception 'scanf_error ()' while evaluating 'sscanf "this" "%g"'
test011.pure, line 5: unhandled exception 'scanf_error ()' while evaluating 'sscanf "this" "%p"'
test011.pure, line 7: unhandled exception 'scanf_error ()' while evaluating 'sscanf "this" "that"'
nothing for Pure compiled with all locales and removed cs locales and Segmentation fault for Pure compiled without any locales.
It seems, it has stil something to do with exception handling.
Jiri
Dne 24.2.2018 v 14:36 Albert Graef napsal(a):
Next up on my list is VTK, which is the best choice for doing 3D scientific visualizations in Pure via pure-tk. Unfortunately, the current version in msys2 is 8.x, but AFAICT VTK 6.3 or earlier is required to get proper Tcl packages, so I'm currently trying to build that using an earlier revision of the corresponding MINGW PKGBUILD.
Thanks Albert. I will give it a whirl at lunch.
On Fri, Feb 23, 2018 at 11:18 PM, Albert Graef <agg...@gmail.com> wrote:
Ok, thanks for the heads up. So it does make sense to have another look at that some time.
FWIW, as promised I took another look at texmacs, works fine over here, see screenie below. The plugin runs without a hitch, using the Pure from the new installer and the plugin from the git source (pure/texmacs). Just two little edits in the init.pure.scm did the trick:
diff --git a/pure/texmacs/plugins/pure/progs/init-pure.scm b/pure/texmacs/plugins/pure/progs/init-pure.scm
index 6442190d..3ce8adea 100644
--- a/pure/texmacs/plugins/pure/progs/init-pure.scm
+++ b/pure/texmacs/plugins/pure/progs/init-pure.scm
@@ -67,7 +67,7 @@
;; if the auto-detection doesn't work for you then you'll have to set this
;; variable to the path where your Pure library scripts are to be found.
(if (not (defined? 'pure-default-lib-path))
-(define pure-default-lib-path "/usr/local/lib"))
+(define pure-default-lib-path "c:/msys64/mingw32/lib"))
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
@@ -94,11 +94,7 @@
;; Detect the Pure library path (this needs pkg-config).
(use-modules (ice-9 popen))
-(define pure-lib-path
- (let* ((port (open-input-pipe "pkg-config pure --variable libdir"))
- (str (read-line port)))
- (close-pipe port)
- (if (string? str) str pure-default-lib-path)))
+(define pure-lib-path pure-default-lib-path)
;; Check if the given script exists on the library path or in one of the
;; texmacs-specific paths. Return the full script name if present, ""
Screenie (running Pure-Math):
That doesn't really help with TeXmacs' frequent crashes (which is why, alas, I pretty much stopped using it), but there you have it. :)
Albert
FWIW, as promised I took another look at texmacs, works fine over here, see screenie below. The plugin runs without a hitch, using the Pure from the new installer and the plugin from the git source (pure/texmacs). Just two little edits in the init.pure.scm did the trick:
That doesn't really help with TeXmacs' frequent crashes (which is why, alas, I pretty much stopped using it), but there you have it. :)