[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #55266] [octave forge] (image) compiler warnin
From: |
Hartmut |
Subject: |
[Octave-bug-tracker] [bug #55266] [octave forge] (image) compiler warnings when building image-2.10.0 with Octave 5.0.1 |
Date: |
Sat, 22 Dec 2018 14:25:59 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:64.0) Gecko/20100101 Firefox/64.0 |
URL:
<https://savannah.gnu.org/bugs/?55266>
Summary: [octave forge] (image) compiler warnings when
building image-2.10.0 with Octave 5.0.1
Project: GNU Octave
Submitted by: hardy
Submitted on: Sat 22 Dec 2018 07:25:57 PM UTC
Category: Octave Forge Package
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Other
Status: None
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: 5.0.0
Operating System: GNU/Linux
_______________________________________________________
Details:
I see a couple of compiler warnings, when building the upcomeing image-2.10.0
with the upcomeing Octave 5.0.1.
Here is my setup:
* using Ubuntu 18.04
* using a self-compiled Octave 5.0.1 (hg-id 9644c0b7efd8)
* using the stable branch from the current image repo (hg-id dcac3df7936e),
intended to be image-2.10.0
* doing "make release" for the image package
The compiling all succeeds. But I see some ugly compiler warnings during the
build process:
g++ -I/opt/octave-5.0/include/octave-5.0.1/octave/..
-I/opt/octave-5.0/include/octave-5.0.1/octave -I/opt/octave-5.0/include
-pthread -fopenmp -g -O2 -g -shared -Wl,-Bsymbolic -Wall -O2 -o
nonmax_supress.oct /tmp/oct-f7pDCj.o -L/opt/octave-5.0/lib
In file included from strel.cc:27:0:
/opt/octave-5.0/include/octave-5.0.1/octave/../octave/parse.h: In function
‘octave_value_list eval_string(const string&, bool, int&, int)’:
/opt/octave-5.0/include/octave-5.0.1/octave/../octave/parse.h:673:65: warning:
‘octave_value_list octave::eval_string(const string&, bool, int&, int)’ is
deprecated: [5]: use 'octave::interpreter::eval_string' instead
[-Wdeprecated-declarations]
return octave::eval_string (str, silent, parse_status, nargout);
^
/opt/octave-5.0/include/octave-5.0.1/octave/../octave/parse.h:585:3: note:
declared here
eval_string (const std::string&, bool silent, int& parse_status, int
nargout);
^~~~~~~~~~~
/opt/octave-5.0/include/octave-5.0.1/octave/../octave/parse.h: In function
‘octave_value eval_string(const string&, bool, int&)’:
/opt/octave-5.0/include/octave-5.0.1/octave/../octave/parse.h:680:56: warning:
‘octave_value octave::eval_string(const string&, bool, int&)’ is
deprecated: [5]: use 'octave::interpreter::eval_string' instead
[-Wdeprecated-declarations]
return octave::eval_string (str, silent, parse_status);
^
/opt/octave-5.0/include/octave-5.0.1/octave/../octave/parse.h:589:3: note:
declared here
eval_string (const std::string&, bool silent, int& parse_status);
^~~~~~~~~~~
/opt/octave-5.0/bin/mkoctfile-5.0.1 --verbose -Wall -g -O2 conndef.cc
connectivity.o
/opt/octave-5.0/bin/mkoctfile-5.0.1 --verbose -Wall -g -O2 bwlabeln.cc
connectivity.o
/opt/octave-5.0/bin/mkoctfile-5.0.1 --verbose -Wall -g -O2 imreconstruct.cc
connectivity.o
g++ -c -fPIC -I/opt/octave-5.0/include/octave-5.0.1/octave/..
-I/opt/octave-5.0/include/octave-5.0.1/octave -I/opt/octave-5.0/include
-pthread -fopenmp -g -O2 -g -Wall -O2 bwlabeln.cc -o /tmp/oct-AAqeZl.o
conndef.cc: In function ‘octave_value_list Fiptcheckconn(const
octave_value_list&, int)’:
conndef.cc:251:59: warning: format ‘%i’ expects argument of type
‘int’, but argument 4 has type ‘octave_idx_type {aka long int}’
[-Wformat=]
func.c_str (), var.c_str (), pos, e.what ());
^
/opt/octave-5.0/bin/mkoctfile-5.0.1 --verbose -Wall -g -O2 bwconncomp.cc
connectivity.o
g++ -c -fPIC -I/opt/octave-5.0/include/octave-5.0.1/octave/..
-I/opt/octave-5.0/include/octave-5.0.1/octave -I/opt/octave-5.0/include
-pthread -fopenmp -g -O2 -g -Wall -O2 imerode.cc -o /tmp/oct-zQBn9d.o
In file included from watershed.cc:20:0:
/opt/octave-5.0/include/octave-5.0.1/octave/../octave/parse.h: In function
‘octave_value_list eval_string(const string&, bool, int&, int)’:
/opt/octave-5.0/include/octave-5.0.1/octave/../octave/parse.h:673:65: warning:
‘octave_value_list octave::eval_string(const string&, bool, int&, int)’ is
deprecated: [5]: use 'octave::interpreter::eval_string' instead
[-Wdeprecated-declarations]
return octave::eval_string (str, silent, parse_status, nargout);
^
/opt/octave-5.0/include/octave-5.0.1/octave/../octave/parse.h:585:3: note:
declared here
eval_string (const std::string&, bool silent, int& parse_status, int
nargout);
^~~~~~~~~~~
/opt/octave-5.0/include/octave-5.0.1/octave/../octave/parse.h: In function
‘octave_value eval_string(const string&, bool, int&)’:
/opt/octave-5.0/include/octave-5.0.1/octave/../octave/parse.h:680:56: warning:
‘octave_value octave::eval_string(const string&, bool, int&)’ is
deprecated: [5]: use 'octave::interpreter::eval_string' instead
[-Wdeprecated-declarations]
return octave::eval_string (str, silent, parse_status);
^
/opt/octave-5.0/include/octave-5.0.1/octave/../octave/parse.h:589:3: note:
declared here
eval_string (const std::string&, bool silent, int& parse_status);
^~~~~~~~~~~
@Avinoam @Carne: Do you have an idea how to remove those compiler warnings for
Octave 5.0 (and still keep the functionality for Octave 4.2 I hope) ? I don't
want all the users to see those warnings when doing "pkg install -forge image"
from inside Octave 5.0.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?55266>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #55266] [octave forge] (image) compiler warnings when building image-2.10.0 with Octave 5.0.1,
Hartmut <=
- [Octave-bug-tracker] [bug #55266] [octave forge] (image) compiler warnings when building image-2.10.0 with Octave 5.0.1, Mike Miller, 2018/12/22
- [Octave-bug-tracker] [bug #55266] [octave forge] (image) compiler warnings when building image-2.10.0 with Octave 5.0.1, Carnë Draug, 2018/12/23
- [Octave-bug-tracker] [bug #55266] [octave forge] (image) compiler warnings when building image-2.10.0 with Octave 5.0.1, Mike Miller, 2018/12/24
- [Octave-bug-tracker] [bug #55266] warns about eval_string just for including parser.h, Carnë Draug, 2018/12/24
- [Octave-bug-tracker] [bug #55266] deprecation warning about octave::eval_string just for including parse.h, Mike Miller, 2018/12/28
- [Octave-bug-tracker] [bug #55266] deprecation warning about octave::eval_string just for including parse.h, Mike Miller, 2018/12/28
- [Octave-bug-tracker] [bug #55266] deprecation warning about octave::eval_string just for including parse.h, Rik, 2018/12/30
- [Octave-bug-tracker] [bug #55266] deprecation warning about octave::eval_string just for including parse.h, Mike Miller, 2018/12/30
- [Octave-bug-tracker] [bug #55266] deprecation warning about octave::eval_string just for including parse.h, Mike Miller, 2018/12/30
- [Octave-bug-tracker] [bug #55266] deprecation warning about octave::eval_string just for including parse.h, Mike Miller, 2018/12/31