octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #64447] Loads of load_path warnings when Octav


From: Markus Mützel
Subject: [Octave-bug-tracker] [bug #64447] Loads of load_path warnings when Octave install path contains umlaut
Date: Mon, 31 Jul 2023 05:05:51 -0400 (EDT)

Follow-up Comment #10, bug #64447 (project octave):

The GitHub runner only builds core Octave. There are no pre-built Octave
packages in that build artifact.

IIUC, it's not necessary to install any packages to reproduce this issue.

Did you follow the instructions from the Wiki page to which I referred in
comment #5? In case you did, *core* Octave should be working. And if you don't
see those `load_path` warnings on any command, the fix is probably doing what
it was meant to do.

If you'd like to install Octave packages to that test version of Octave, you'd
need to also install the (build) dependencies of those packages in MSYS2.
Judging from the error message, you don't have `make` installed. You'd
probably also need to install a compiler. The following command at the MINGW64
shell from MSYS2 might help with those two:

pacman -S --needed base-devel mingw-w64-ucrt-x86_64-gcc


I don't know if the image package has any more dependencies.

Additionally, there might be issues in the configure script and/or Makefile of
the respective package. There is probably little that Octave itself could do
to avoid those.
There might also be remaining issues in core Octave, e.g., when passing
environment variables with non-ASCII characters to bash. (But I couldn't
reproduce that in some simple tests. That part seems to be working here.)
If there are other issues, it would be better to track them separately in
dedicated bug reports.




    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?64447>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]