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

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

[Octave-bug-tracker] [bug #47559] pkg install of nan package on octave f


From: Tatsuro MATSUOKA
Subject: [Octave-bug-tracker] [bug #47559] pkg install of nan package on octave for windows
Date: Tue, 29 Mar 2016 02:48:10 +0000
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36

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

                 Summary: pkg install of nan package on octave for windows
                 Project: GNU Octave
            Submitted by: tmacchant
            Submitted on: 2016年03月29日 02時48分09秒
                Category: Octave Forge Package
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Build Failure
                  Status: None
             Assigned to: None
         Originator Name: Tatsuro MATSUOKA
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.0.1
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

pkg install of nan package on octave for windows.

>From the below install command

>> pkg install -verbose nan-3.0.1.tar.gz


I got an error message:


cc -fopenmp -Wall -Wextra -Wconversion -O2  -fopenmp  -c svm.cpp
make: cc: Command not found
make: *** [svm.o] Error 127
make: Leaving directory `/tmp/oct-lMjN0h/NaN/src'


This is of course, cc.exe does not exist in bin directory of octave for
windows. Workaround is to copy gcc.exe to cc.exe.

However, other places g++ command is found. Then I wonder why cc is used
instead of gcc.




    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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