|
From: | anonymous |
Subject: | [Octave-bug-tracker] [bug #45509] communications-1.2.1 fails during package install in octave-4.0.0 |
Date: | Thu, 30 Jul 2015 14:28:33 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.125 Safari/537.36 |
Follow-up Comment #16, bug #45509 (project octave): Thanks so much for that tip on how to get the config log. That was the key to unraveling a bit what's going on. That escape sequence seems to be related to what terminal I'm using (gnome-terminal, default installed) when running Octave. If I ssh into my system (ssh address@hidden) and re-run the octave-cli, I can install the communications package (config.log loses that escape sequence it pulled from the HDF5_LDFLAGS, etc.). So chalking this up to a local environment problem is certainly a true statement, but surely it can be overcome by a less...hackish way to handle the terminal. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?45509> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |