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

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

[Octave-bug-tracker] [bug #62554] [octave forge] (nan) nan 3.7.0 errors


From: Nicholas Jankowski
Subject: [Octave-bug-tracker] [bug #62554] [octave forge] (nan) nan 3.7.0 errors and warnings on install
Date: Wed, 1 Jun 2022 14:00:35 -0400 (EDT)

Update of bug #62554 (project octave):

                 Release:                   7.1.0 => other                  
                 Summary: [octave forge] (nan) pkg update with nan 3.7.0
produces long series of warnings => [octave forge] (nan) nan 3.7.0 errors and
warnings on install

    _______________________________________________________

Follow-up Comment #1:

updating - re ran a 'pkg install -forge nan' on another 6.4.0 install that had
not yet been updated from nan 3.6.0. Most of the same shadowing warnings
messages appeared, but I also got ./configure and readlink messages I hadn't
gotten before:


octave:2> pkg install -forge -global nan
./configure: line 3811: which: command not found
readlink: missing operand
Try 'readlink --help' for more information.
ls: cannot access './bin/mexext': No such file or directory
svm.cpp: In constructor 'Cache::Cache(int, long int)':
svm.cpp:135:7: warning: conversion from 'long long unsigned int' to 'long int'
may change value [-Wconversion]
  135 |  size /= sizeof(Qfloat);
      |  ~~~~~^~~~~~~~~~~~~~~~~
svm.cpp:136:7: warning: conversion from 'long long unsigned int' to 'long int'
may change value [-Wconversion]
  136 |  size -= l * sizeof(head_t) / sizeof(Qfloat);
      |  ~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
warning: function
C:\devtools\Octave\octave-6.4.0-w64\mingw64\share\octave\packages\nan-3.7.0\center.m
shadows a core library function
warning: called from
    doc_cache_create>gen_doc_cache_in_dir at line 146 column 5
    doc_cache_create at line 62 column 12
    install>generate_lookfor_cache at line 823 column 5
    install at line 235 column 7
    pkg at line 568 column 9

...


updating report header accordingly


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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