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

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

[Octave-bug-tracker] [bug #60169] error: call of overloaded pow is ambig


From: Michele
Subject: [Octave-bug-tracker] [bug #60169] error: call of overloaded pow is ambiguous
Date: Thu, 4 Mar 2021 11:09:56 -0500 (EST)
User-agent: Mozilla/5.0 (X11; SunOS sun4v; rv:52.0) Gecko/20100101 Firefox/52.0

URL:
  <https://savannah.gnu.org/bugs/?60169>

                 Summary: error: call of overloaded pow is ambiguous
                 Project: GNU Octave
            Submitted by: michele31415
            Submitted on: Thu 04 Mar 2021 04:09:54 PM UTC
                Category: Configuration and Build System
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Build Failure
                  Status: None
             Assigned to: None
         Originator Name: Michele
        Originator Email: 
             Open/Closed: Open
                 Release: 6.2.0
         Discussion Lock: Any
        Operating System: Solaris/SunOS

    _______________________________________________________

Details:

Building 6.2.0 on Solaris 10 SPARC, gmake stops with:

libgui/graphics/Table.cc:88:76: error: call of overloaded 'pow(int, int)' is
ambiguous
         else if (d <= pow (10, precision - 1) && d > pow (10, 1 - precision))
\                                                                           
^
libgui/graphics/Table.cc:104:33: error: call of overloaded 'pow(int, int)' is
ambiguous
         d *= pow (10, -exponent);
                                ^                                             
                    

This is the same problem as in bug #54217: "Build fails with error: call of
overloaded ‘pow(int, int)’ is ambiguous" from two years ago building
4.4.0, though in a different file.  Back then the suggested fix was

-      static const float tiny = pow (2, -50);
+      static const float tiny = octave::math::exp2 (-50.0f);

but it is not clear to me how to proceed in this case.




    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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