POV-Ray : Newsgroups : povray.general : Input file size restrictions?? Server Time
1 Aug 2024 08:22:45 EDT (-0400)
  Input file size restrictions?? (Message 21 to 24 of 24)  
<<< Previous 10 Messages Goto Initial 10 Messages
From: Nicolas Calimet
Subject: Re: Input file size restrictions??
Date: 4 May 2006 19:19:08
Message: <445a8bec$1@news.povray.org>
> means. But ultimately, it reports an error internal to the compiler. Its
> using gcc and g++.

	For the sake of getting a better gcc (in case that matters on the
Itanium...) I'd suggest you follow the error message and file a bug report.

	In any case I recommand you to use the Intel C++ Compiler to build
anything on that platform.  It is available for free on Linux -- but I
never bothered downloading / testing the version for IA-64.  You can get
it at  https://premier.intel.com  which requires registration in order to
get an end-user license.  (Maybe your institution already has ICPC installed
though: check either "icc -V" or "icpc -V").
	Configuring and building POV should then just be a matter of doing:

./configure COMPILED_BY=you --disable-optimiz CXX=icpc CXXFLAGS="-O3 -ip"

	This is for a start.  In case of trouble I'd be glad to help you
further on.  Followup-To p.unix.

	- NC


Post a reply to this message

From: space cadet
Subject: Re: Input file size restrictions??
Date: 5 May 2006 15:00:00
Message: <web.445b9fcfbace7ee8339b0050@news.povray.org>
Nicolas Calimet <pov### [at] freefr> wrote:
> > means. But ultimately, it reports an error internal to the compiler. Its
> > using gcc and g++.
>
>  For the sake of getting a better gcc (in case that matters on the
> Itanium...) I'd suggest you follow the error message and file a bug report.
>
>  In any case I recommand you to use the Intel C++ Compiler to build
> anything on that platform.  It is available for free on Linux -- but I
> never bothered downloading / testing the version for IA-64.  You can get
> it at  https://premier.intel.com  which requires registration in order to
> get an end-user license.  (Maybe your institution already has ICPC installed
> though: check either "icc -V" or "icpc -V").
>  Configuring and building POV should then just be a matter of doing:
>
> ./configure COMPILED_BY=you --disable-optimiz CXX=icpc CXXFLAGS="-O3 -ip"
>
>  This is for a start.  In case of trouble I'd be glad to help you
> further on.  Followup-To p.unix.
>
>  - NC

Thanks NC.  icpc is not currently on our altix here.  I downloaded it. I
dont have root on that machine, so I looked into a local install, but that
introduces some issues, so I'm trying to get admin to install it system
wide (which should be done anyway).  So it might be a few days before that
gets done (I work at nasa->gov't environment->slower turning wheels), so
I'll resume the discussion at that time.

Other than that, you requested I attempt MegaPOV on that machine, and report
results.  I actually avoided the bz2 stuff, and just downloaded the tar
file. But trying to 'tar xvf' it on the altix, it reported "doesnt seem to
be a tar file".  So I dont know if there's already a platform
incompatibility at the file format level or what.  But I didnt wrestle with
it any further, since it was a long shot to begin with.

I'll let you know how things go with the home build (over on the p.unix
forum).

Thanks again.


Post a reply to this message

From: Nicolas Calimet
Subject: Re: Input file size restrictions??
Date: 6 May 2006 06:08:53
Message: <445c75b5$1@news.povray.org>
> Other than that, you requested I attempt MegaPOV on that machine, and report
> results.  I actually avoided the bz2 stuff, and just downloaded the tar
> file. But trying to 'tar xvf' it on the altix, it reported "doesnt seem to
> be a tar file".

	Tar archives are usually compressed with gzip (tar.gz) or bzip2 (tar.bz2).
Hence you should also pass the proper option to decompress the archive, e.g.
tar xvzf archive.tar.gz  (note the 'z' for the gzip'ed archive; for an archive
compressed with bzip2 you could use 'j' instead, but this option/decompressor
might not be supported by the tar utility installed on your machine).

	In any case, testing the AMD64 MegaPOV binary is no priority, as it will
normally fail on the Itanium as soon as the  megapov  command is ran.

	- NC


Post a reply to this message

From: space cadet
Subject: Re: Input file size restrictions??
Date: 6 May 2006 12:20:00
Message: <web.445ccc1bbace7eec052e9200@news.povray.org>
Nicolas Calimet <pov### [at] freefr> wrote:
> >
>  Tar archives are usually compressed with gzip (tar.gz) or bzip2 (tar.bz2).
> Hence you should also pass the proper option to decompress the archive, e.g.
> tar xvzf archive.tar.gz  (note the 'z' for the gzip'ed archive; for an archive
> compressed with bzip2 you could use 'j' instead, but this option/decompressor
> might not be supported by the tar utility installed on your machine).
>
>  In any case, testing the AMD64 MegaPOV binary is no priority, as it will
> normally fail on the Itanium as soon as the  megapov  command is ran.
>
>  - NC

Right, I believe I gunzipped the .gz to produce a .tar, and then tar xvf'd
that. I decompress tars and gzips all the time, that shouldnt have tripped
me up.  But perhaps I may have had a brain phart moment. It happens to the
best of us. :-)

No worries either way.


Post a reply to this message

<<< Previous 10 Messages Goto Initial 10 Messages

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.