Whats the easy way to get 'develop' in the docker?
On Fri, Jan 20, 2017 at 9:34 AM, Christopher Collins
wrote:
> On Fri, Jan 20, 2017 at 11:55:59PM +0800, Li-Chun Ko wrote:
> > As an update, the Docker Container works well with the "./newt test all"
> > commend.
>
> Great
On Fri, Jan 20, 2017 at 11:55:59PM +0800, Li-Chun Ko wrote:
> As an update, the Docker Container works well with the "./newt test all"
> commend.
Great to hear. Thanks for following up!
Chris
Hi folks,
As an update, the Docker Container works well with the "./newt test all"
commend.
Br,
Lichun
2017-01-20 9:40 GMT+08:00 Li-Chun Ko :
> Hi Chris,
>
> I switched to Linux by installing Ubuntu on the same virtual box and am
> not using the Docker Container any more.
Hi Chris,
I switched to Linux by installing Ubuntu on the same virtual box and am not
using the Docker Container any more. I could try it again today and get
back to you later.
Previously the problem I encountered seemed to be I was compiling a
tutorial package that doesn't exist (as pointed out
Hi Li-Chun,
I'm glad you got it working, but now I'm confused. The docker container
should already use the correct version of gcc (multilib). Furthermore,
as I understand it, installing a different compiler on your machine
should not have any effect on the docker container. Are you still using
Hi Fabio,
After I install gcc-multilib all problems solved!
I guess it is worthwhile to add a note for this in the tutorial.
Thank you very much.
BTW, I am using Ubuntu 16.04.1 64 bit version.
Br,
Lichun
2017-01-19 22:44 GMT+08:00 Li-Chun Ko :
> Hi all,
>
> I tried
On Thu, Jan 19, 2017, at 12:44 PM, Li-Chun Ko wrote:
> Hi all,
>
> 2. Error message when executing $newt test all:
>
> lcko@lcko-VirtualBox:~/dev/go/myproj$ cd repos
> lcko@lcko-VirtualBox:~/dev/go/myproj/repos$ $newt test all
> Testing package @apache-mynewt-core/boot/boot_serial/test
>
Hi all,
I tried "$newt test @repos/apache-mynewt-core/kernel/os" in Linux but it
still doesn't work.
I also attached the error message of executing "$newt test all" below.
It seems some files are missing.
Br,
Lichun
1. Error message when executing $newt test
@repos/apache-mynewt-core/kernel/os:
On Thu, Jan 19, 2017, at 06:55 AM, Li-Chun Ko wrote:
>
> In addition, I also found the conmend:
>
> newt test all
>
> did not work in Linux and resulted in compiling errors and somehow I feel
> there is some issues with the newt install commend.
Hi, could you copy the error here?
And could you also make sure you are running the latest docker container?
docker pull mynewt/newt:latest
thanks,
aditi
> On Jan 18, 2017, at 10:42 AM, aditi hilbert wrote:
>
> Lichun,
>
> That particular package path actually does not exist - so the documentation
> is
Lichun,
That particular package path actually does not exist - so the documentation is
incorrect. I can fix that.
Try testing with the package with a valid path e.g.
newt test @apache-mynewt-core/kernel/os
thanks,
aditi
> On Jan 18, 2017, at 3:59 AM, Li-Chun Ko
This appears not to be a docker-specific problem.
I am running natively on MacOS Sierra and see the same problem. It seems to be
a Go problem
newt test @repos/apache-mynewt-core/libs/os
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation
Hi all,
I am a noob here and I am trying to build Mynewt applications with the
Docker Container (using the Docker Quickstart Terminal).
I followed the instructions I found here:
http://mynewt.apache.org/os/get_started/project_create/ and encountered a
problem in the step when executing this
13 matches
Mail list logo