[
https://issues.apache.org/jira/browse/MYNEWT-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15433990#comment-15433990
]
Christopher Collins commented on MYNEWT-360:
--------------------------------------------
Thanks, Tim. Could you try using the updated newt script that I posted to
MYNEWT-361? I have a hunch that will fix this issue as well.
The updated script only allocates a tty for interactive commands which execute
gdb (debug and run). I don't think you would ever run these commands from an
IDE, so that might be sufficient.
Out of curiosity, which IDE are you running newt from?
> "the input device is not a TTY" when newt isn't run in terminal
> ---------------------------------------------------------------
>
> Key: MYNEWT-360
> URL: https://issues.apache.org/jira/browse/MYNEWT-360
> Project: Mynewt
> Issue Type: Bug
> Components: Newt
> Affects Versions: v0_9_0
> Environment: Ubuntu 14.10 using the Docker version of newt
> Reporter: Tim
> Assignee: Todd Mitton
>
> Basically, if I run newt (the Docker wrapper script) in an IDE rather than a
> terminal, it prints this:
> newt build bleprph -DLOG_LEVEL=LOG_LEVEL_INFO
> the input device is not a TTY
> I believe this is some craaaazy Docker issue, probably this one:
> https://github.com/docker/docker/issues/8755
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
