search for: sysroots

Hi, this commit https://github.com/dovecot/core/commit/c9d76e2baf653fa5504d6849e5c1aae32eff3c53 added code which can not be compiled with uclibc-ng 1.0.26 using buildroot: make[3]: Entering directory '/home/bernd/buildroot/br4/output/build/dovecot-2.2.33.2/src/lib-test' /bin/bash ../../libtool --tag=CC --mode=compile

Hi Rich, On Wed, November 16, 2016 1:34 pm, Richard W.M. Jones wrote: > On Wed, Nov 16, 2016 at 11:31:40AM -0500, Derek Atkins wrote: >> > 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:

On Mon, Nov 13, 2017 at 20:07:00 +0100, Bernd Kuhls wrote: > Hi, > > this commit > https://github.com/dovecot/core/commit/c9d76e2baf653fa5504d6849e5c1aae32eff3c53 > > added code which can not be compiled with uclibc-ng 1.0.26 using buildroot: Hrm... ok. It'll be probably faster for you to try a test build instead of me setting up buildroot... What happens if in

Hi, On Wed, November 16, 2016 11:10 am, Richard W.M. Jones wrote: > >> It eventually did complete, after several hours. But I don't understand >> why this particular VM took so long when others (with similar disk >> sizes/usages/configurations) completed in only 1-2 minutes. Each VM is >> effectively exactly the same (it's a build slave), so it's just the

On Fri, Aug 04, 2017 at 04:40:44PM -0600, Jonathan Roelofs wrote: > Might be a helpful exercise for you to try building vanilla clang with > runtimes for the host, before worrying about how to build everything for > your baremetal case: > http://llvm.org/docs/GettingStarted.html#getting-started-quickly-a-summary So I did. :o) It was fun realizing how much Release type reduces LD

Hi! I am trying to use virt-customize to add packages to an image. However it seems that there is a problem where a resolv.conf is not being installed and thus package installation fails. The command is: virt-customize -v -x -a trusty-server-cloudimg-amd64-disk1.img --run-command "host openstack.org" I am having a hard time gathering complete output as the command seems to

Hi, I am recovering a CentOS 5.4 system. I've copied 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

Hi! I'm trying to convert some Xen guests running Centos 5.8 to KVM on Centos 6.3. Hopefully this is the right place to ask this question, if not, let me know and I'll go there instead! :) My setup: Centos 5.8 Host running Xen with a Centos 5.8 guest, and I want to transfer this guest to a different Centos 6.3 host running KVM. I am able to tweak the target server all I want, but the

On 2020-05-14, Rui Ueyama via llvm-dev wrote: >On Thu, May 14, 2020 at 11:04 AM Ivan Medoedov via llvm-dev < >llvm-dev at lists.llvm.org> wrote: > >> 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 >> >>

...<libc++-install-prefix>/lib This is even when the C++ library for your target is part of your Clang toolchain so the driver arguably should know how to find it without you having to duplicate the driver logic. > What's currently missing is a standardized naming for a) where the > sysroots live, and b) what they're named. Host libraries should continue > to live in $prefix/{include, lib, lib32, lib64} as appropriate, whereas > target libraries should live in something like: > $prefix/clang-runtimes/$triple/$multilib/{usr/include, usr/lib, etc.} > I don't care too...

Sadly, there are elements (hello "gentoo"!) that, during the cleanup.d phase, wipe out almost everything in the /tmp of the guest, including the /tmp/aux where virt-dib mounts the auxiliary data. Since that removal excludes things starting with "in_target" (mostly to avoid wiping the "in_target.d" that disk-image-create itself sets up, then rename our "aux"

Thank You for your reply. >What was the output of the 'virt-rescue --suggest -d XYZ'? Inspecting the virtual machine or disk image ... 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:

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

Hello, Richard. > -----Original Message----- > From: Richard W.M. Jones [mailto:rjones@redhat.com] > Sent: Monday, March 5, 2018 8:42 PM > To: Зиновик Игорь Анатольевич <ZinovikIA@nspk.ru> > Cc: libguestfs@redhat.com > Subject: Re: [Libguestfs] virt-v2v 1.38 fails to convert .vmx VM: setfiles ... > Multiple same specifications for /.*. > > On Mon, Mar 05, 2018 at

> On 7 Nov 2016, at 22:16, Derek Atkins <derek@ihtfp.com> wrote: > > Hi, > > My last VM imported in 2 minutes. This one has been sitting for three > hours. I think this is a bug. well, some time it does take a long time. Are you sure it was hung? No I/O going on? adding libguestfs list Thanks, michal > > Just in case it helps, here's a larger piece of

Since /dev and other directories contain sub-mounts, suggest using --rbind instead of --bind. This also allows us to remove the /dev/pts line. --- rescue/rescue.c | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/rescue/rescue.c b/rescue/rescue.c index 53afdae..9a7c988 100644 --- a/rescue/rescue.c +++ b/rescue/rescue.c @@ -453,10 +453,9 @@ do_suggestion (struct drv

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\" ];

I've just tried putting usr in a subvol. Installation proceeds normally, no errors, but I'm dropped to a dracut prompt which indicates mount of /usr failed. dmesg follows: [ 14.025215] systemd[1]: Starting dracut initqueue hook... [ 14.077890] Btrfs loaded [ 14.129987] device label fedora_f18v devid 1 transid 31 /dev/sda1 [ 14.313607] device label fedora_f18v devid 1 transid 31

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 \

...n. > This is even when the C++ library for your target is part of your Clang > toolchain so the driver arguably should know how to find it without you > having to duplicate the driver logic. > > >> What's currently missing is a standardized naming for a) where the >> sysroots live, and b) what they're named. Host libraries should continue >> to live in $prefix/{include, lib, lib32, lib64} as appropriate, whereas >> target libraries should live in something like: >> $prefix/clang-runtimes/$triple/$multilib/{usr/include, usr/lib, etc.} >> >...