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

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

[Octave-bug-tracker] [bug #41636] mkoctfile doesn't accept -std=c++11 op


From: Falk Tannhäuser
Subject: [Octave-bug-tracker] [bug #41636] mkoctfile doesn't accept -std=c++11 option
Date: Wed, 19 Feb 2014 00:14:15 +0000
User-agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0

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

                 Summary: mkoctfile doesn't accept -std=c++11 option
                 Project: GNU Octave
            Submitted by: fata
            Submitted on: Mi 19 Feb 2014 00:14:14 GMT
                Category: Configuration and Build System
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Feature Request
                  Status: None
             Assigned to: None
         Originator Name: Falk Tannhäuser
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 3.8.0
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

Platform: MS Windows 8.1, Cygwin64, g++ (GCC) 4.8.2
I would like to use the great new C++ 2011 features for generating .oct files.
Unfortunately, there doesn't seem to be a straightforward way to pass the
option "-std=c++11" or "-std=c++0x" to g++ through mkoctfile.
I found the possibility

$ mkoctfile -v -Wall -Wextra -W\ -std=c++11 foo.cpp
g++ -c   -I/usr/include/octave-3.8.0/octave/..
-I/usr/include/octave-3.8.0/octave  -ggdb -O2 -pipe   -Wall -Wextra -W
-std=c++11   foo.cpp -o foo.o
g++ -shared -Wl,--export-all-symbols -Wl,--enable-auto-import
-Wl,--enable-runtime-pseudo-reloc  -Wall -Wextra -W -std=c++11 -o foo.oct 
foo.o   -L/usr/lib/octave/3.8.0 -loctinterp -loctave

but it looks weird and leaves a stray "-W" (an obsolete synonym for "-Wall"
which is probably harmless) on the g++ command line.




    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Nachricht gesendet von/durch Savannah
  http://savannah.gnu.org/




reply via email to

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