[Top][All Lists]

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

[Octave-bug-tracker] [bug #41924] build_packages - probelms with path

From: anonymous
Subject: [Octave-bug-tracker] [bug #41924] build_packages - probelms with path
Date: Fri, 21 Mar 2014 16:04:41 +0000
User-agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0)


                 Summary: build_packages - probelms with path
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Fr 21 Mär 2014 16:04:40 UTC
                Category: Libraries
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
             Assigned to: None
         Originator Name: Martin Hepperle
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 3.8.1
        Operating System: Microsoft Windows



I tried to install Octave 3.8.1 on my Windows 7 machine.

After copying the files I tried to run "build_packages.m" in the src
It failed with a sh syntax error complaining about ')' at line 0 etc. 

The install directory was "D:\Program Files (x86)\Octave\octave-3.8.1" and I
learned that this problem was already reported and followed back to spaces in
the path name. 

Ok, so I moved Octave to a path like

This failed also and after a while I figured it might have to do the the

Ok, so I moved Octave to a path like "D:/Programme/Octave/octave-3.8.1/src".
No spaces, no parentheses.

The next try failed also with another sh error. I noted that teh sh that was
executed, was taken from the installation of another sh which was found
earlier in the search path.

So my conclusions are:
- Octave should make sure that it only uses the tools (like sh) from its
binary directory and not from what it finds in the search path.
- Octave should be able to handle spaces, parentheses, Umlauts etc. as one
would expect today in the 21st centrury where some people are already beyond
the ASCII character set. For example the GUI prototype does not show Umlaits
and special characters properly. Maybe another font would be needed?
I know all this is difficult, but I would encourage all testers to use path
names with special characters and also try to use quotes in path names in
scripts whenever possible.

Sorry for bashing a bit around, but in general Octave is great but for many
first time useres these things are big hurdles.


Reply to this item at:


  Nachricht gesendet von/durch Savannah

reply via email to

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