Can't you get a 32-bit source file and rebuild it for 64?


On Fri, Mar 27, 2009 at 2:36 PM, George Oakman <[email protected]> wrote:

>  Thank you all for great comments, what I need to so is starting to be
> clearer.
>
> I just can't find a X86_64 lapack RPM for RHEL4, but I'll keep looking.
> If one of you knows where I could find it that'd be great.
>
> George.
>
> > From: [email protected]
> > To: [email protected]
> > Date: Fri, 27 Mar 2009 15:46:10 -0400
> > CC: [email protected]
> > Subject: Re: [Rdkit-discuss] Compiling on Red Hat linux
> >
> >
> > > How about now?
> > > http://code.google.com/p/rdkit/wiki/BuildingOnLinux
> > > or
> > > http://code.google.com/p/rdkit/wiki/NewLinuxBuild
> > >
> > Ah, this is much better! Would it be possible to add a bullet point with
> > options for python-less build?
> >
> > > > even (?!) the default?
> > >
> > > That's definitely possible, but I wonder how advisable it is.
> > > What fraction of active linux boxes are running 64bit?
> >
> > I switched all of the linux computers I control to 64 bit for a couple
> > of years now. Out of 60+ systems I think I have 32-bit installed on 2,
> > one being my old home PC...
> > There is simply no good reason to run 32-bit linux on 64-bit hardware.
> > All of the old 32-bit programs work fine for me, and there is a bonus
> > that I don't have the ancient 2/4 Gb filesize/RAM limits.
> >
> > Igor
> >
> >
> >
> ------------------------------------------------------------------------------
> > _______________________________________________
> > Rdkit-discuss mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/rdkit-discuss
>
> ------------------------------
> Windows Live Messenger just got better. Find out 
> more!<http://clk.atdmt.com/UKM/go/134665230/direct/01/>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Rdkit-discuss mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/rdkit-discuss
>
>

Reply via email to