|
From: | Nicholas Jankowski |
Subject: | [Octave-bug-tracker] [bug #55646] image package 2.10.0 install fails on Windows (octave v4.4.1 and later) |
Date: | Tue, 5 Feb 2019 18:01:32 -0500 (EST) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Edge/16.16299 |
Follow-up Comment #11, bug #55646 (project octave): windows command shell has no idea what to do with a ./configure command. outside octave I opened a bash shell to /src and .configure yelled at me for 'checking for octave... no'. I think generally it was assumed that the windows install wouldn't look outside of the octave system for a compiler, because most users probably don't have one. is there another way for me to call this within octave? _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?55646> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |