search for: x386

Hi all, I am trying to build a cross compiler for Sparc on x386 host. I tried to run configure with configure --enable-targets=sparc or with configure --target=sparc but in both cases I got llvm compiler for x86 target. Is there a way to build a cross compiler for Sparc (or ARM)? Thanks. -- Fima Rabin -------------- next part -------...

...M] /tmp/vmware-config0/vmnet-only/userif.o CC [M] /tmp/vmware-config0/vmnet-only/netif.o CC [M] /tmp/vmware-config0/vmnet-only/bridge.o CC [M] /tmp/vmware-config0/vmnet-only/procfs.o CC [M] /tmp/vmware-config0/vmnet-only/smac_compat.o SHIPPED /tmp/vmware-config0/vmnet-only/smac_linux.x386.o LD [M] /tmp/vmware-config0/vmnet-only/vmnet.o Building modules, stage 2. MODPOST WARNING: could not find /tmp/vmware-config0/vmnet-only/.smac_linux.x386.o.cmd for /tmp/vmware-config0/vmnet-only/smac_linux.x386.o CC /tmp/vmware-config0/vmnet-only/vmnet.mod.o LD [M] /tmp/vmware-con...

...1-fonts-100dpi is needed by R-base-2.4.1-2.1 xorg-x11-fonts-75dpi is needed by R-base-2.4.1-2.1 xorg-x11-libs is needed by R-base-2.4.1-2.1 blas is needed by R-base-2.4.1-2.1 libreadline.so.5 is needed by R-base-2.4.1-2.1 euler src/R-base-2.4.1# I also tried the x386 version with the same results. The documentation lists some prerequisite items to install such as blas, but I have searched and I can't see to locate that software. Is it public domain or a commercial product? I also see that my server already has x11 fonts installed, so I don't know...

I believe I know the answer, but I'd like to be certain, since I keep seeing references to things like smbmount and smbfs... Is it possible to mount an NT (4.0sp3) share onto a Solaris 2.6/Sparc? I just grabbed Samba 2.0.6. I suspect not (I don't see any smbmount or smbfs in my samba/bin directory). Will this ever be a possibility? If so, when? And, are there any other options for

...edos-linux/sys-freedos-linux.zip --- it auto-detects the FAT type in your image file and puts in the appropriate boot sector. You'll also need to go to fdos.org and obtain the correct kernel.sys (there's one for FAT{12,16}, and a different one for FAT32, and each flavor comes in x86 and x386 versions). If you told the Perl script to put in an LBA version of a boot sector, and you're going to boot the image with MEMDISK, be sure to also pass "edd" to MEMDISK so that it will respond to the LBA-based INT13 calls. 8) If you don't want to use the Perl script from the p...

.../>>/ Just wondering if people had started using i386 Xen DomU's on a x86_64 />>/ dom0 machine with 5.1 as yet ? And just wondering what their experiences />>/ have been. /I thought I would chime in here with my experience. I am running a Cent5.1 x86_64 Dom0 with a Cent 5.1 x386 domU (both fully updated). Everything works well including installation and subsequent "xm create" boots. A gotcha that I have not been able to work around has to do with the automatic save/restore with the xendomains script. When I mimic Dom0 shutdown behavior (i.e., xendomains stop)...

Hi, Is there a command that will give the total size of an R object in bytes? thanks Nicholas -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or "[un]subscribe" (in the "body", not the subject !) To: r-help-request at

...os-linux.zip > --- it auto-detects the FAT type in your image file and puts in the > appropriate boot sector. You'll also need to go to fdos.org and obtain > the correct kernel.sys (there's one for FAT{12,16}, and a different one > for FAT32, and each flavor comes in x86 and x386 versions). If you told > the Perl script to put in an LBA version of a boot sector, and you're > going to boot the image with MEMDISK, be sure to also pass "edd" to > MEMDISK so that it will respond to the LBA-based INT13 calls. > > 8) If you don't want to use t...

On Tue, 08 Jul 2014 15:54, H. Peter Anvin wrote: > >On 07/08/2014 11:26 AM, Ady wrote: >> >> It's interesting that you ask this, because every document related to >> newmkfloppyimg.sh specifically recommends adding: >> floppy c=$CYLINDERS s=$SECTORS h=$HEADS >> to the MEMDISK arguments. >> > >It would be important for floppies to know

In http://www.freebsd.org/releases/7.0R/announce.html says Updating Existing Systems > An upgrade of any existing system to FreeBSD 7.0-RELEASE constitutes > a major version upgrade, so no matter which method you use to update > an older system you should reinstall any ports you have installed on > the machine. This will avoid binaries becoming linked to inconsistent > sets