comp.lang.idl-pvwave archive: archive

Home » Public Forums » archive » linux 64

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: linux 64 [message #45699 is a reply to message #45655]

Sun, 02 October 2005 01:34

Robert Barnett
Messages: 70
Registered: May 2004

Member

Hello,

Most Linux applications are compiled from source, thus you will find
that most Linux distributions have everything compiled as 64 bit
binaries. If you want to run 32-bit binaries then you have to install
the 32-bit compatbility packages. Under fedora, you can install the
32-bit and 64-bit packages in parallel. However, this makes for a very
messy system. I don't think that fedora/redhat has really sorted out
how to effectively maintain 32bit and 64bit packages correctly. There
are quite a few entries in fedora's bugzilla on this issue.

If you really require 32-bit then I would recommend asking RSI for a
list of all dependant rpm packages so you can install just the required
32 bit dependancies. You will need to tinker with yum or redhat-update
to install from both the i386 and x86_64 repositories.

If it's just for testing and debugging, then an idea might be to
install 32 bit linux on another partition as a 'failsafe' sandbox. Or
maybe you could run 32-bit linux from CD and then mount and su in as
yourself. For both solutions you need to mount /home on the original
partition.

On another note about IDL on Fedora Core 4. Has anyone found that
object graphics do not work using hardware rendering? Xorg is supposed
emulate 3d graphics even if the 3d graphics driver is not
active/installed.

Cheers,
Robbie

Reimar Bauer wrote:
> Dear all
>
> that's more a system diagnostics question. Probably someone else has
> solved the same and could give hints.
>
>
> We have a bunch of AMD 64 bit linux machines and in 64 bit idl they all
> work .
>
> One of the machine shows a memory fault if the 32 bit version with idl
> -32 is called. There are some hints that it could depend on something
> missing in glibc because if on this machine many times netCDF files are
> readed we got a Bus error message or
> *** glibc detected *** malloc(): memory corruption: 0x0000000000b39180
> *** too.
> I thinks it's a problem on the machine and not an idl one. But where to
> start?
>
>
>
> cheers
> Reimar
>
>
> --
> Reimar Bauer
>
> Institut fuer Stratosphaerische Chemie (ICG-I)
> Forschungszentrum Juelich
> email: R.Bauer@fz-juelich.de
> ------------------------------------------------------------ -------
> a IDL library at ForschungsZentrum Juelich
> http://www.fz-juelich.de/icg/icg-i/idl_icglib/idl_lib_intro. html
> ============================================================ =======

Report message to a moderator

[Message index]

		linux 64 By: R.Bauer on Mon, 26 September 2005 23:51
		Re: linux 64 By: Robert Barnett on Sun, 02 October 2005 01:34
		Re: linux 64 By: Karl[1] on Mon, 03 October 2005 21:08
		Re: linux 64 By: Karl Schultz on Wed, 05 October 2005 10:35
		Re: linux 64 By: Rick Towler on Mon, 03 October 2005 14:54

Previous Topic:	McIDAS Area to hdf
Next Topic:	Five days mean values

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Oct 11 09:23:15 PDT 2025

Total time taken to generate the page: 1.92010 seconds