search for: sysroot

...-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Os -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I/home/bernd/buildroot/br4/output/host/i586-buildroot-linux-uclibc/sysroot/usr/include -c -o test-common.lo test-common.c libtool: compile: /home/bernd/buildroot/br4/output/host/bin/i586-buildroot-linux-uclibc-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-charset -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -std=gnu99 -D_LARGEFILE...

...ving the output will give you a >> > good idea of what precisely it was doing for those hours. >> >> Well, as I said in my original email, it was hanging at running >> setfiles: >> >> commandrvf: stdout=n stderr=y flags=0x0 >> commandrvf: setfiles -F -e /sysroot/dev -e /sysroot/proc -e >> /sysroot/selinux -e /sysroot/sys -r /sysroot -q >> /sysroot/etc/selinux/targeted/contexts/files/file_contexts /sysroot/ >> Can't stat exclude path "/sysroot/selinux", No such file or directory >> - ignoring. > > OK that's in...

...-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Os -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I/home/bernd/buildroot/br4/output/host/i586-buildroot-linux-uclibc/sysroot/usr/include -c -o test-common.lo test-common.c > libtool: compile: /home/bernd/buildroot/br4/output/host/bin/i586-buildroot-linux-uclibc-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-charset -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -std=gnu99 -D_LARG...

...disk usage). > Running `virt-v2v -v -x ...' and observing the output will give you a > good idea of what precisely it was doing for those hours. Well, as I said in my original email, it was hanging at running setfiles: commandrvf: stdout=n stderr=y flags=0x0 commandrvf: setfiles -F -e /sysroot/dev -e /sysroot/proc -e /sysroot/selinux -e /sysroot/sys -r /sysroot -q /sysroot/etc/selinux/targeted/contexts/files/file_contexts /sysroot/ Can't stat exclude path "/sysroot/selinux", No such file or directory - ignoring. There's no timestamp in the output or logs so it's ha...

...repos checkout under llvm - clang-6.0 compiles "Hello World" - make check-all fails (not sure I'm not causing it) - make install creates everything under PREFIX # cmake -G 'Unix Makefiles' -DCMAKE_BUILD_TYPE=Release -DLLVM_TARGETS_TO_BUILD=X86 -DCMAKE_INSTALL_PREFIX=/tmp/x86-sysroot ../../source/llvm # make -j4 # make install It was fun learning how to manualy compile compiler for the first time. Now how to cross compile for bare? Given that I have musl-1.1.16 directory and that I'm preseeding sysroot with: # rm -rf /tmp/barearm-sysroot # mkdir -p /tmp/barearm-sysroot #...

...3.0] Running: host openstack.org running command: exec >>'/tmp/builder.log' 2>&1 host openstack.org libguestfs: trace: sh "exec >>'/tmp/builder.log' 2>&1\n\n\nhost openstack.org\n" guestfsd: main_loop: new request, len 0x60 mount --bind /dev /sysroot/dev mount --bind /dev/pts /sysroot/dev/pts mount: mount point /sysroot/dev/pts does not exist mount --bind /proc /sysroot/proc mount --bind /sys/fs/selinux /sysroot/selinux mount: mount point /sysroot/selinux does not exist mount --bind /sys /sysroot/sys mount --bind /sys/fs/selinux /sysroot/sys/fs...

...ied all partitions into the recovery system. I've installed grub boot loader. However, the original system is using /dev/sdb1 for root (/), while the recovery system is using LVM (/dev/vg0/lv1) for root (/). When recovery system boots, I got the panic error: * Mounting /dev/sdb1 on /sysroot * Mount: mounting /dev/sdb1 on /sysroot failed: No such file or directory * Mount: mounting /dev on /sysroot/dev failed: No such file or directory * * switching / to /sysroot * Switch_root: bad newroot /sysroot * Kernel panic - not syncing: Attempted to...

....pm line 178. Use of qw(...) as parentheses is deprecated at /usr/share/perl5/vendor_perl/Sys/VirtConvert/Converter/RedHat.pm line 230. Use of qw(...) as parentheses is deprecated at /usr/share/perl5/vendor_perl/Sys/VirtConvert/Converter/RedHat.pm line 252. umount: umount: /transfer4b5GFf: umount: /sysroot/transfer4b5GFf: not mounted at /usr/share/perl5/vendor_perl/Sys/VirtConvert/GuestfsHandle.pm line 193. at /usr/share/perl5/vendor_perl/Sys/VirtConvert/Config.pm line 262 I re-ran the command setting LIBGUESTFS_TRACE=1 and LIBGUESTFS_DEBUG=1, and there is about 144K of output I that looks like an...

...t; >> Hello, >> >> I'm trying to compile a Linux hello world executable on macOS. >> >> The first step is simple: >> >> clang -c -target x86_64-linux-gnu -c -o hello.o hello.c >> >> But linking results in an error: >> >> ld.lld --sysroot=/linuxroot/ -o hello -m elf_x86_64 \ >> -dynamic-linker /lib64/ld-linux-x86-64.so.2 \ >> /lib/crt1.o \ >> /usr/lib/x86_64-linux-gnu/crti.o ../hello.o \ >> /usr/lib/x86_64-linux-gnu/libc.so \ >> /usr/lib/x86_64-linux-gnu/crtn.o >> >> ld.lld: error:...

...bi, libunwind: > > headers: $prefix/include/c++/v1 > > libraries: $prefix/lib/$name.$ext > > > > The scheme used by libc++, libc++abi, libunwind doesn't support targets > > other than the host which is a problem when cross-compiling. > > Yes, it does: --sysroot= > What if my sysroot doesn't contains C++ library, or even if it does I may still want to use libc++ shipped with the toolchain e.g. because the one that's part of the sysroot doesn't support C++17? I don't like the "build libc++ separately and then put it inside your sys...

...dib/dib.ml | 62 +++++++++++++++++++++++++++++++------------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/dib/dib.ml b/dib/dib.ml index bcb81c0..5713bc6 100644 --- a/dib/dib.ml +++ b/dib/dib.ml @@ -176,8 +176,8 @@ shift %s # system variables -export HOME=$mysysroot/tmp/aux/perm/home -export PATH=$mysysroot/tmp/aux/hooks/bin:$PATH +export HOME=$mysysroot/tmp/in_target.aux/perm/home +export PATH=$mysysroot/tmp/in_target.aux/hooks/bin:$PATH export TMP=$mysysroot/tmp export TMPDIR=$TMP export TMP_DIR=$TMP @@ -190,12 +190,12 @@ export IMAGE_NAME=\"%s\&quot...

.... This disk contains one or more operating systems. You can use these mount commands in virt-rescue (at the ><rescue> prompt) to mount the filesystems. # /dev/sda1 is the root of a linux operating system # type: linux, distro: ubuntu, version: 12.4 # Ubuntu 12.04.3 LTS mount /dev/sda1 /sysroot/ mount --bind /dev /sysroot/dev mount --bind /dev/pts /sysroot/dev/pts mount --bind /proc /sysroot/proc mount --bind /sys /sysroot/sys >And did you run _all_ those commands? yes I run all those commands in this sequence: virt-rescue --network -d XYZ mount /dev/sda1 /sysroot/ chroot /sysroot upd...

On Fri, Aug 04, 2017 at 04:03:35PM -0600, Jonathan Roelofs wrote: > > > 1) Pick a directory as your sysroot > > ~/arm-sysroot > > > > > 2) Install the libc headers there (without having built it) > > What I did was mv musl-*/include ~/arm-sysroot/usr/include. > > I think you need to copy them, not move them. On a new directories and fresh untar of musl, I don't think...

...> > On Mon, Mar 05, 2018 at 02:03:17PM +0000, Зиновик Игорь Анатольевич > wrote: > > Hello. > > > > I'm trying to convert VMware based virtual machines (CentOS 7.2) and output > them into oVirt. > > virt-v2v fails with following error: > > setfiles: /sysroot/etc/selinux/targeted/contexts/files/file_contexts: Multiple > same specifications for /.*. > > > > File `file_contexts' looks same like in recent CentOS 7.4. My > > conversion server is Fedora 28 (Rawhide), since it contains virt-v2v 1.38. > > This has got to be a bug...

...= 0 >> libguestfs: trace: v2v: selinux_relabel >> "/etc/selinux/targeted/contexts/files/file_contexts" "/" "force:true" >> guestfsd: main_loop: new request, len 0x6c >> commandrvf: stdout=n stderr=y flags=0x0 >> commandrvf: setfiles -F -e /sysroot/dev -e /sysroot/proc -e >> /sysroot/selinux -e /sysroot/sys -r /sysroot -q >> /sysroot/etc/selinux/targeted/contexts/files/file_contexts /sysroot/ >> Can't stat exclude path "/sysroot/selinux", No such file or directory - >> ignoring. >> ^C >> >...

.../rescue/rescue.c index 53afdae..9a7c988 100644 --- a/rescue/rescue.c +++ b/rescue/rescue.c @@ -453,10 +453,9 @@ do_suggestion (struct drv *drvs) /* If it's Linux, print the bind-mounts. */ if (type && STREQ (type, "linux")) { - printf ("mount --bind /dev /sysroot/dev\n"); - printf ("mount --bind /dev/pts /sysroot/dev/pts\n"); - printf ("mount --bind /proc /sysroot/proc\n"); - printf ("mount --bind /sys /sysroot/sys\n"); + printf ("mount --rbind /dev /sysroot/dev\n"); + printf ("mount...

The real sudo does it as well, and leaving them when preserving the environment (-E) maybe breaks the applications, as e.g. chroot will have a TMPDIR path pointing outside of it. --- dib/dib.ml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/dib/dib.ml b/dib/dib.ml index df83ba1..d15cd19 100644 --- a/dib/dib.ml +++ b/dib/dib.ml @@ -301,6 +301,11 @@ if [ -z \"$preserve_env\" ];

...9] systemd[1]: Started dracut initqueue hook. [ 15.574280] systemd[1]: Starting dracut pre-pivot and cleanup hook... [ 15.735181] device label fedora_f18v devid 1 transid 31 /dev/sda1 [ 15.876950] btrfs: 'root' is not a valid subvolume dracut-pre-pivot[228]: Warning: Mounting /usr to /sysroot/usr failed dracut-pre-pivot[228]: Warning: *** Dropping you to a shell; the system will continue dracut-pre-pivot[228]: Warning: *** when you leave the shell. dracut-pre-pivot[228]: Warning: [[1;32m OK ] Started Show Plymouth Boot Screen. [[1;32m OK ] Reached target Basic System. dracut-pre-piv...

Hello, I'm trying to compile a Linux hello world executable on macOS. The first step is simple: clang -c -target x86_64-linux-gnu -c -o hello.o hello.c But linking results in an error: ld.lld --sysroot=/linuxroot/ -o hello -m elf_x86_64 \ -dynamic-linker /lib64/ld-linux-x86-64.so.2 \ /lib/crt1.o \ /usr/lib/x86_64-linux-gnu/crti.o ../hello.o \ /usr/lib/x86_64-linux-gnu/libc.so \ /usr/lib/x86_64-linux-gnu/crtn.o ld.lld: error: cannot open /lib/crt1.o: No such file or directory ld.lld: er...

...headers: $prefix/include/c++/v1 >> > libraries: $prefix/lib/$name.$ext >> > >> > The scheme used by libc++, libc++abi, libunwind doesn't support targets >> > other than the host which is a problem when cross-compiling. >> >> Yes, it does: --sysroot= >> > > What if my sysroot doesn't contains C++ library, or even if it does I may > still want to use libc++ shipped with the toolchain e.g. because the one > that's part of the sysroot doesn't support C++17? > > I don't like the "build libc++ separately...