Posts made by Daniel Janse Van Rensburg

The source for the packages of GDB need to be added to the package manager, then it installs fine.

I had the same issue, make sure you have at least 60GB of space available for the docker container to build the OS

Right, managed to fix this.
For the people coming here from Google, my issue was with HDD size, the build expands to almost 50GB. I ran the docker container on Fedora, giving it a ton of storage, and it completed. Takes forever in the VM though.

Thanks for the help ladies and gents

Created a fresh Ubuntu 18.04 VM, 4CPU, 8GB, 100GB, followed native build instructions, and ran make -j4 out of the box, build failed. I reran with make -j1 V=s, and here is the failing output:

make[6]: Entering directory '/home/jvr/onion/source/build_dir/host/e2fsprogs-1.43.3/e2fsck'
make[6]: Nothing to be done for 'all'.
make[6]: Leaving directory '/home/jvr/onion/source/build_dir/host/e2fsprogs-1.43.3/e2fsck'
making all in debugfs
make[6]: Entering directory '/home/jvr/onion/source/build_dir/host/e2fsprogs-1.43.3/debugfs'
CC create_inode.o
./../misc/create_inode.c: In function 'set_inode_xattr':
./../misc/create_inode.c:136:9: warning: implicit declaration of function 'llistxattr'; did you mean 'lstat64'? [-Wimplicit-function-declaration]
size = llistxattr(filename, NULL, 0);
^~~~~~~~~~
lstat64
./../misc/create_inode.c:172:16: warning: implicit declaration of function 'lgetxattr'; did you mean 'getdate_r'? [-Wimplicit-function-declaration]
value_size = lgetxattr(filename, name, NULL, 0);
^~~~~~~~~
getdate_r
./../misc/create_inode.c: At top level:
./../misc/create_inode.c:395:18: error: conflicting types for 'copy_file_range'
static errcode_t copy_file_range(ext2_filsys fs, int fd, ext2_file_t e2_file,
^~~~~~~~~~~~~~~
In file included from ./../misc/create_inode.c:19:0:
/usr/include/unistd.h:1110:9: note: previous declaration of 'copy_file_range' was here
ssize_t copy_file_range (int __infd, __off64_t *__pinoff,
^~~~~~~~~~~~~~~
Makefile:417: recipe for target 'create_inode.o' failed
make[6]: *** [create_inode.o] Error 1
make[6]: Leaving directory '/home/jvr/onion/source/build_dir/host/e2fsprogs-1.43.3/debugfs'
Makefile:404: recipe for target 'all-progs-recursive' failed
make[5]: *** [all-progs-recursive] Error 1
make[5]: Leaving directory '/home/jvr/onion/source/build_dir/host/e2fsprogs-1.43.3'
Makefile:339: recipe for target 'all' failed
make[4]: *** [all] Error 2
make[4]: Leaving directory '/home/jvr/onion/source/build_dir/host/e2fsprogs-1.43.3'
Makefile:49: recipe for target '/home/jvr/onion/source/build_dir/host/e2fsprogs-1.43.3/.built' failed
make[3]: *** [/home/jvr/onion/source/build_dir/host/e2fsprogs-1.43.3/.built] Error 2
make[3]: Leaving directory '/home/jvr/onion/source/tools/e2fsprogs'
tools/Makefile:147: recipe for target 'tools/e2fsprogs/compile' failed
make[2]: *** [tools/e2fsprogs/compile] Error 2
make[2]: Leaving directory '/home/jvr/onion/source'
tools/Makefile:145: recipe for target '/home/jvr/onion/source/staging_dir/target-mipsel_24kc_musl-1.1.16/stamp/.tools_install_yynyyyyynyyyyynyynnyyyynyyyyyyyyyyyyyyynyynynnyyynnny' failed
make[1]: *** [/home/jvr/onion/source/staging_dir/target-mipsel_24kc_musl-1.1.16/stamp/.tools_install_yynyyyyynyyyyynyynnyyyynyyyyyyyyyyyyyyynyynynnyyynnny] Error 2
make[1]: Leaving directory '/home/jvr/onion/source'
/home/jvr/onion/source/include/toplevel.mk:198: recipe for target 'world' failed
make: *** [world] Error 2

So I've been working at this for about two weeks now, I want to build the OS for my Omega2, in order to customize the installed libs; end goal being to cross compile for it.

I've followed the instructions at https://github.com/OnionIoT/source more times than I can count, I've tried Ubuntu 16.04 and 18.04, setting a clean VM up to build the OS natively, and it fails. Updating loads of things will get the build to continue further, but it never finishes.

I then tried doing the same on Fedora 29, also a clean VM, compilation fails here too (no surprises there).

Lastly I tried compiling using the docker image, on both versions of Ubuntu and on Fedora, and the builds fail.

I'm at my wits end, the docker image should be set up to just build whatever I want, as that is the whole point of using docker. So my question, has anyone had success using the latest docker image on either Ubuntu or Fedora as a fresh VM?

Its getting really demotivating having to start a build an then leave it for 4 or 5 hours only to come back to a failure.

In terms of the VM setup, it is set up with 2 CPU's (I've built using -j1 and -j2), 8GB of RAM and 100GB of storage.

Any pointers are welcome, or if someone has a dockerfile that I can use, even better, as I cant seem to find the Onion dockerfile online.

You can run docker inside the Linux Guest on VMWare, its what I've been doing.