[Top][All Lists]

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

[Octave-bug-tracker] [bug #55672] [octave forge] (control) undefined sym

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #55672] [octave forge] (control) undefined symbol: _Z11warning_msgPKcllPS0_l (development branch)
Date: Thu, 7 Feb 2019 20:08:29 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.81 Safari/537.36


                 Summary: [octave forge] (control) undefined symbol:
_Z11warning_msgPKcllPS0_l (development branch)
                 Project: GNU Octave
            Submitted by: mtmiller
            Submitted on: Thu 07 Feb 2019 05:08:27 PM PST
                Category: Octave Forge Package
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Unexpected Error
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux



If a snapshot of the current development branch of the control package is
installed in Octave (any version), the following error comes out when calling
certain functions

>> norm (tf (1, [1, 1]))
error: __proper_tf2ss__: /path/to/__control_slicot_functions__.oct: failed to
load: /path/to/__control_slicot_functions__.oct: undefined symbol:
error: called from
    __sys2ss__>__proper_tf2ss__ at line 121 column 16
    __sys2ss__ at line 69 column 18
    ss at line 181 column 18
    ssdata at line 53 column 9
    norm>h2norm at line 68 column 18
    norm at line 55 column 12

This works in control 3.1.0, the error happens because some parameter types
have been changed in the control repository. I suspect these should be changed
back to octave_idx_type, but I'm not sure that these changes were correct in
the first place.

Doug - did you intend to change these parameter types from octave_idx_type to
int? This change doesn't seem safe if Octave is built with 64-bit Fortran
integers. If you agree that the parameters types should be reverted from int
to octave_idx_type, do you need help fixing whatever warnings you were trying
to fix with these changes?


Reply to this item at:


  Message sent via Savannah

reply via email to

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