similar to: 32-bit compat-gcc on 64-bit CentOS?

hi, i have been using a 64 bit desktop machine to process a whole lot of data which i have then subsequently used save() to store. i am now wanting to use this data on my laptop machine, which is a 32 bit install. i suppose that i should not be surprised that the 64 bit data files do not open on my 32 bit machine! does anyone have a smart idea as to how these data can be reformatted for 32 bits?

Rers: I installed R 2.9.0 from the Debian package manager on our amd64 system that currently has 6GB of RAM -- my first question is whether this installation is a true 64-bit installation (should R have access to > 4GB of RAM?) I suspect so, because I was running an rqss() (package quantreg, installed via install.packages() -- I noticed it required a compilation of the source) and

I owe you a gala dinner at your favorite restaurant. Really. A few questions: Why did you 'git pull --rebase' when the branch was up-to-date? Is this just a safety habit? I don't understand the pushing upstream. Since we use Phabricator, isn't that the job of the person who commits the patch? Does git keep all my branches up-to-date with the origin? Say I come in tomorrow and

Hi everyone, I tried finding this using Google, but no joy. I have a massive (6GB uncompressed, 2.9GB compressed) file I'm attempting to transfer using SCP or SFTP. I get a random length into the transfer, and then it aborts with "Disconnecting: Corrupted MAC on input." Both hosts are Solaris 8, using OpenSSH4.4p1 compiled 64-bit by the Sun Forte C compiler. I've tried

Having finally found some free time, I was going to use it to update a bunch of R packages from 2.15 to 3.0. I am running Windows 7, 64-bit professional. This is on a brand-new laptop using vanilla settings when installing the operating system. Problem 1: I installed R3.0 to the default location (C:\Program FIles\R\R-3.0.0). The first thing I tried to do was install BioConductor. This

Hi List, Early in dec I was forced to upgrade one of my server systems - initially built in 2004 on an intel server mb it finally failed. Under some time pressure, I replaced the mb etc with a 64 bit asus system and did a repair of the linux system upon reboot with a 64 bit DVD. As one can imagine there were some headaches as the kernel was now 64 bit, but yum and friends were still 32 bit. I

Hi there, I wish to read a 9.6GB .DAT file into R (64-bit R on 64-bit Windows machine) - to then delete a substantial number of rows & then convert to a .csv file. Upon the first attempt the computer crashed (at some point last night). I'm rerunning this now & am closely monitoring Processor/CPU/Memory. Apart from this crash being a computer issue alone (possibly), is R equipped to

I was asked this question today and frankly, I didn't know the answer. So I thought I'd post it here.... If you don't need to access greater than 4GB RAM, is there any benefit to running the 64-bit version of CentOS vs the 32-bit one? That's assuming, of course, that the target machine utilizes a 64-bit capable processor. I hadn't seen any noticeable difference, but I

Hello, I'm hitting a problem with heartbeat which might be related to the use of x86_64. My test system is CentOS 5 Xen DomU x86_64 under CentOS 5 Dom0. Can I run i386 CentOS 5 DomU under x86_64 Dom0? Thanks, --Amos -------------- next part -------------- An HTML attachment was scrubbed... URL:

I'm trying to install a custom greeter into a newly installed 64-bit Centos 5 system. I originally tried to modify Xsession to include xpop /path/to/text_to_dispay as the first executable line, but that didn't work. Then I read about gdmconfig which led to gdmsetup which led to custom.conf. Nothing, so far, is producing a custom banner prior to login. Is this an issue with CentOS

On 7/2/07, Scott Ehrlich <scott at mit.edu> wrote: > Now, onto PAM - /etc/pam.d/blah.conf claims in the header comments that > the file is autogenerated and any edits will be lost. So what is the > proper way to make changes that WILL stick? What changes are you looking to make? Most times the pam.d/foo files are not where you want to set things. > > I'm new to the

ocfs2_getattr() uses generic_fillattr() to set inode number(and other attributes). generic_fillattr() inturn fills inode number with inode->i_ino which is a 32-bit(unsigned long) value. if the ocfs2 partition is huge enough, that may become an incorrect value. the fix is filling it again after generic_fillattr() with ip_blkno(u64). Signed-off-by: Wengang Wang <wen.gang.wang at

Our research group is thinking of buying a 64-bit windows workstation with an intel core2 duo processor, and I am going to use R on it. I have a couple of questions. Is it possible to run 32-bit build of R on a 64-bit computer without problems?(For windows) Would there be problems with contrib packages? >From what I've read in the mailing lists, there is eventually going to be a 64-bit

Hi all, it is possible create a 32 bits xen guest in a 64 bits xen server? I need get guest running with DirectAdmin (32 bits) and the problem is: if i use a 64 bits kernel for the guest, the Directadmin instalation fails because the 64 bits arch , if i create the guest with a 32 kernel it fails on boot: XENBUS: Device with no driver: device/vkbd/0 XENBUS: Device with no driver:

>>However, in case (2) the i386 guest kernel unconditionally goes for >>sysenter, and the hypervisor will accept this because CPUID has advertised >>SEP. *But* AMD CPUs do not support sysenter except in legacy mode! The >>correct thing to do is to use syscall. The hypervisor 32-on-64 compat code >>would accept CALLBACKTYPE_syscall, but the Linux i386 code here

2 questions- projected date on 64 bit support? and... can you run a 32-bit app on a 64-bit OS ? I just a read a great article on the Opteron vs. Xeon argument at: http://www.samag.com/documents/sam0411b/ Thanks, Dave

I''ve currently got a system with a 32-bit PAE hypervisor, dom0 and domUs I''ve now decided that I have a need for 64-bit domUs and from what I understand that this would be possible by having a 64-bit hypervisor. What I''m trying to establish is whether it''s wise to change my hypervisor to 64-bit with the existing dom0 and domUs in place?

Are 32-bit precompiled packages supposed to work on 32-bit R installed on 64-bit Windows? I *think* the Windows R FAQ (2.28 Should I run 32-bit or 64-bit R?) implies that they will work, but I am having trouble getting certain packages to work. Before I spend more time on it or start asking questions about specific packages, I would like to know I'm not trying to do something impossible.

I'm using the latest R on Windows XP: > R.version _ platform i386-pc-mingw32 arch i386 os mingw32 system i386, mingw32 status major 2 minor 5.0 year 2007 month 04 day 23 svn rev 41293 language R version.string R version 2.5.0 (2007-04-23) I understand this: >

Dear Rxperts,.. I am using R 3.0 in both 32- and 64-bit Windows 7 environment and have trouble using SASxport. They seem to work fine under R.2.15.3. ....The error/warning messages are provided below... Following are the messages obtained when trying to read s SAS transport file (.xpt) library(SASxport) Warning message: package ‘SASxport’ was built under R version 3.0.1 read.xport(fname)