search for: archicture

...t; --host=unknown checking for unknown-clang... icc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... yes checking for suffix of executables... configure: WARNING: Configuring LLVM for an unknown target archicture configure: WARNING: Configuring LLVM for an unknown host archicture checking for gcc... gcc configure: error: installation or configuration problem: compiler cannot create executables. Any ideas? Frank

...r unknown-clang... icc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... yes > checking for suffix of executables... > > configure: WARNING: Configuring LLVM for an unknown target archicture > configure: WARNING: Configuring LLVM for an unknown host archicture > checking for gcc... gcc > configure: error: installation or configuration problem: compiler > cannot create executables. > > > Any ideas? > > Frank > > > ____________________________________...

Greetings, I'm trying to add a virtual nic to an existing and active vm and I'm getting this error: error: internal error: No more available PCI slots the cmd I'm trying to run is: virsh -c qemu:///system attach-interface --domain router --type bridge --source virbr0 --model virtio --config --live the lspci output within the vm is this: # lspci 00:00.0 Host bridge: Intel Corporation

...vice [00ff]: Red Hat, Inc. Virtio memory balloon (rev 01) > 06:00.0 Ethernet controller: Red Hat, Inc. Virtio network device (rev 01) > 07:00.0 Unclassified device [0002]: Red Hat, Inc. Virtio filesystem (rev 01) ...and 7 PCIe devices, each taking up one of those root ports. On a PCIe-based archicture, you can only hotplug a device into a pcie-root-port (not into the root bus), but you can't hotplug the pcie-root-port itself. libvirt knows this, and since your guest is running and has no unused pcie-root-ports, it can't do the hotplug. If you do the attach-interface command with --confi...

...ed through *.mk and Makefile in the syslinux tree. This patch implements architecture-dependent code in memdisk to support for i386 and x86_64. The memcpy, memset and memmove routines originated from klibc. The assembler directive in memdump/code16.h is fixed for x86_64 build. Archicture-dependent get_cpuid in sysdump/cpuid is fixed. Console input initiated by com32 modules and sample programs hang on both i386 and x86_64. The issue is traced to the implementation of get_key() underlying firmware. For stdin file descriptor, the console read finally resolves to __rawco...

...ed through *.mk and Makefile in the syslinux tree. This patch implements architecture-dependent code in memdisk to support for i386 and x86_64. The memcpy, memset and memmove routines originated from klibc. The assembler directive in memdump/code16.h is fixed for x86_64 build. Archicture-dependent get_cpuid in sysdump/cpuid is fixed. Console input initiated by com32 modules and sample programs hang on both i386 and x86_64. The issue is traced to the implementation of get_key() underlying firmware. For stdin file descriptor, the console read finally resolves to __rawco...

Dear FreeBSD users and system administrators, While the FreeBSD Security Team has traditionally been very good at investigating and responding to security issues in FreeBSD, this only solves half of the security problem: Unless users and administrators of FreeBSD systems apply the security patches provided, the advisories issued accomplish little beyond alerting potential attackers to the