Thanks for the response. I was running it as root in an unprivileged container. I tried changing the ownership of a single file to the uid:gid in the error and got a similar error. It wasn't actually the build it was on the gclient sync.
I added the "o" flag to the extract line here: https://github.com/v8/v8/blob/5749d710bc73ef40f9b9e8b94ec290e0412d3f57/third_party/binutils/download.py#L91 and that worked, but then ran into another snag, similar to this one: https://bbs.archlinux.org/viewtopic.php?id=209871 I ended up bailing on the build from source and installing libv8 from this repo: https://launchpad.net/~pinepain/+archive/ubuntu/libv8-5.2 On Fri, May 27, 2016 at 1:28 PM, Florent Peterschmitt < [email protected]> wrote: > 27 mai 2016 20:33 "Caleb Everett" <[email protected]> a écrit: > > Hi, can anyone point me in the right direction to be able to build v8 in > a container? > > > > I'm getting the following errors when I try to run gclient sync: > > > > tar: ./lib/ldscripts/elf_k1om.xr: Cannot change ownership to uid 179961, > gid 5000: Invalid argument > > > > tar: ./lib/ldscripts/elf_i386.xw: Cannot change ownership to uid 179961, > gid 5000: Invalid argument > > > > tar: ./lib/ldscripts/elf_i386.xd: Cannot change ownership to uid 179961, > gid 5000: Invalid argument > > > > tar: ./lib/ldscripts/elf_l1om.xn: Cannot change ownership to uid 179961, > gid 5000: Invalid argument > > > > tar: ./lib/ldscripts/elf_i386.xr: Cannot change ownership to uid 179961, > gid 5000: Invalid argument > > tar: ./lib/ldscripts/elf_i386.xs: Cannot change ownership to uid 179961, > gid 5000: Invalid argument > > tar: ./lib/ldscripts/elf_k1om.xsw: Cannot change ownership to uid > 179961, gid 5000: Invalid > > argument > > tar: ./lib/ldscripts/elf_l1om.x: Cannot change ownership to uid 179961, > gid 5000: Invalid argument > > tar: ./lib/ldscripts/elf_x86_64.xu: Cannot change ownership to uid > 179961, gid 5000: Invalid > > argument > > > > I was thinking that I probably needed to find where the files were > extracted in the script and tell > > them not to use the existing ownership, but wondered whether there was a > way to get around this > > with lxc. > > > > Thank you, > > Is this behavior different on you host? > > This ownership change shouldn't prevent you from building anything. Do you > run this in another user than root? > > Florent Peterschmitt > _______________________________________________ > lxc-users mailing list > [email protected] > http://lists.linuxcontainers.org/listinfo/lxc-users
_______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
