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

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

[Octave-bug-tracker] [bug #48710] changed "configured for" string makes


From: Hartmut
Subject: [Octave-bug-tracker] [bug #48710] changed "configured for" string makes installed packages unusable
Date: Fri, 5 Aug 2016 18:56:51 +0000 (UTC)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:47.0) Gecko/20100101 Firefox/47.0

URL:
  <http://savannah.gnu.org/bugs/?48710>

                 Summary: changed "configured for" string makes installed
packages unusable
                 Project: GNU Octave
            Submitted by: hardy
            Submitted on: Fri 05 Aug 2016 06:56:49 PM GMT
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.0.3
        Operating System: GNU/Linux

    _______________________________________________________

Details:

Forge packages that where installed under Octave 4.0.1 aren't fully functional
under Octave 4.0.3. The reason seems to be a change in the "configured for"
string between those two Octave version. (In my case this was
"x86_64-unknown-linux-gnu-api-v50+" and changed to
"x86_64-pc-linux-gnu-api-v50+".)

This was observed on a Ubuntu 14.04 linux system, both Octave versions are
self compiled from the official release tar-balls.

Here is how to reproduce the behavior, with the example of the image package:
In Octave 4.0.1 do:

pkg uninstall image
pkg install image -forge
pkg load image
path

This will show the two paths of the image package:
* ~/octave/image-2.4.1
* ~/octave/image-2.4.1/x86_64-unknown-linux-gnu-api-v50+

Then in Octave 4.0.3 do:

pkg uninstall image
path

* This will only show one of the necessary paths for the image package, the
subfolder with the compiled oct-files is missing:
* ~/octave/image-2.4.1

The reason for this becomes obvious when you continue in Octave 4.0.3:

pkg uninstall image
pkg install image -forge
pkg load image
path

This will again show the two necessary paths:
* ~/octave/image-2.4.1
* ~/octave/image-2.4.1/x86_64-pc-linux-gnu-api-v50+

Note that the name of the oct-file subfolder is now DIFFERENT, it is
"pc-linux" instead of "unknown-linux". This seems to be the reason for
packages to not work properly under Octave 4.0.3 if they have been installed
under Octave 4.0.1 (or earlier).

(Prior to this bug report, this was nailed down during bug #48601.)

This change in this "configured for" string might be an intended change and
well known change during the development from Octave 4.0.3 to 4.0.1. But it
does have the explained side effects.

I am fully aware of the possibility to "work around" this behavior, by simply
re-installing all packages. But this might not be obvious for the other Octave
users.




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?48710>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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