I'm having problems compiling radiance from sources from radiance-online cvs. I downloaded the stable tarball and am able to compile most of the executables, but it errors in the src/px dir every time. It seems that the tiff directory is the cause of the problem. It appears that the configure script is borked in some way. I have run the script manually and end up with the same results:
It seems to fill the resulting Makefile with random spew
Warning, this file was automatically created by the TIFF configure script#Warning, this file was automatically created b
y the TIFF configure script Warning, this file was automatically created by the TIFF configure script@Warning, this file
was automatically created by the TIFF configure scriptWWarning, this file was automatically created by the TIFF configu
re scriptAWarning, this file was automatically created by the TIFF configure scriptRWarning, this file was automatically
created by the TIFF configure scriptNWarning, this file was automatically created by the TIFF configure scriptIWarning,
this file was automatically created by the TIFF configure scriptNWarning, this file was automatically created by the TI
FF configure scriptGWarning, this file was automatically created by the TIFF configure script@Warning, this file was aut
omatically created by the TIFF configure script
is all one line. This behaviour continues in the version, libdirs, machine type, and random(?) lines throughout the file. This causes make to bomb out with a missing separator error during the compile.
I'm wondering if this is a local toolchain problem, or if anyone else has experienced this behaviour. I'm compiling on a linux system (gentoo), which has been compiled from scratch using this same toolchain - gcc 3.2.1, glibc 2.3.1, and the gnu toolset. I have invoked the makeall script from a tcsh shell.
Hi Tom,
I've had the same problem compiling radiance on SuSE-Linux, Version 8.1.
The trouble was caused by sed version 3.02.xx(in conjunction with the
variable POSIXLY_CORRECT in the configure-script). As far as I know,
when
POSIXLY_CORRECT is set, the sed versions(I tried out version 3.02.51,
3.02.60
and 4.06) insert the replacement string before each character in the
matched
line, e.g. the command sed "/@VERSION@/s;;v3.4beta037;g" applied to
I handled this problem by reverting back to sed version 3.02.
Maybe you can remove/comment out the line
POSIXLY_CORRECT=1; export POSIXLY_CORRECT # disable GNU extensions
in ray/src/px/tiff/configure, but I don't know if this leads to any side
effects.
Augustinus
tom wrote:
···
Hi all,
I'm having problems compiling radiance from sources from
radiance-online cvs. I downloaded the stable tarball and am able to
compile most of the executables, but it errors in the src/px dir every
time. It seems that the tiff directory is the cause of the problem. It
appears that the configure script is borked in some way. I have run the
script manually and end up with the same results:
It seems to fill the resulting Makefile with random spew
Warning, this file was automatically created by the TIFF configure
script#Warning, this file was automatically created b
y the TIFF configure script Warning, this file was automatically created
by the TIFF configure script@Warning, this file
was automatically created by the TIFF configure scriptWWarning, this
file was automatically created by the TIFF configu
re scriptAWarning, this file was automatically created by the TIFF
configure scriptRWarning, this file was automatically
created by the TIFF configure scriptNWarning, this file was
automatically created by the TIFF configure scriptIWarning,
this file was automatically created by the TIFF configure
scriptNWarning, this file was automatically created by the TI
FF configure scriptGWarning, this file was automatically created by the
TIFF configure script@Warning, this file was aut
omatically created by the TIFF configure script
is all one line. This behaviour continues in the version, libdirs,
machine type, and random(?) lines throughout the file. This causes make
to bomb out with a missing separator error during the compile.
I'm wondering if this is a local toolchain problem, or if anyone else
has experienced this behaviour. I'm compiling on a linux system
(gentoo), which has been compiled from scratch using this same toolchain
- gcc 3.2.1, glibc 2.3.1, and the gnu toolset. I have invoked the
makeall script from a tcsh shell.
Hi Tom,
I've had the same problem compiling radiance on SuSE-Linux
<snip of very good analysis of problem>
I handled this problem by reverting back to sed version 3.02.
Maybe you can remove/comment out the line
POSIXLY_CORRECT=1; export POSIXLY_CORRECT # disable GNU extensions
in ray/src/px/tiff/configure, but I don't know if this leads to any side
effects.
Augustinus,
I am using sed 4.05. I commented out the line in the configure script and everything appeared to compile - including ra_tiff and friends. It appears that oconv and rpict and rview seem to work, but I'm still left with a nonworking ximage. Time to fiddle around a little more
Hi all,
I'm having problems compiling radiance from sources from
radiance-online cvs. I downloaded the stable tarball and a...
compile most of the executables, but it errors in the src/...
Too many errors encountered; the rest of the message is ignored:
time.
I am running Red Hat 9. I saw Tom had a similar problem back in April.
What I did not see is if he ever got it working and how.
I do have both files. The programs I am left without are ximage,xshowtrace and xyzimage. This is the error I am recieving:
cd libtiff ; make install
make[1]: Entering directory `/Working/Software/Radiance3.HEAD/ray/src/px/tiff/libtiff'
Makefile:31: *** missing separator. Stop.
In the followup post to mine in the archives, there is a workaround to this same problem. The last time I built the 'official' release (to use Roland's pmap addition), I just copied my system libtiff and headers into the Radiance source tree and built/linked against these. Everything built and seemed to function correctly. The included libtiff configure process doesn't seem to like newer versions of GNU sed - or vise versa
This sounds very familiar. My solution was to edit the RMakefile
in src/px to link to the existing system libraries. This was as
simple as:
186c186
< ra_tiff: ra_tiff.o ../lib/libtiff.a
···
On Sun, 18 Jan 2004, tom wrote:
etienne canard wrote:
> I do have both files. The programs I am left without are
> ximage,xshowtrace and xyzimage. This is the error I am recieving:
>
> cd libtiff ; make install
> make[1]: Entering directory
> `/Working/Software/Radiance3.HEAD/ray/src/px/tiff/libtiff'
> Makefile:31: *** missing separator. Stop.
In the followup post to mine in the archives, there is a workaround to
this same problem. The last time I built the 'official' release (to use
Roland's pmap addition), I just copied my system libtiff and headers
into the Radiance source tree and built/linked against these. Everything
built and seemed to function correctly. The included libtiff configure
process doesn't seem to like newer versions of GNU sed - or vise versa
I do have both files. The programs I am left without are ximage,xshowtrace and xyzimage. This is the error I am recieving:
cd libtiff ; make install
make[1]: Entering directory `/Working/Software/Radiance3.HEAD/ray/src/px/tiff/libtiff'
Makefile:31: *** missing separator. Stop.
In the followup post to mine in the archives, there is a workaround to this same problem. The last time I built the 'official' release (to use Roland's pmap addition), I just copied my system libtiff and headers into the Radiance source tree and built/linked against these. Everything built and seemed to function correctly. The included libtiff configure process doesn't seem to like newer versions of GNU sed - or vise versa
_________________________________________________________________
Rethink your business approach for the new year with the helpful tips here. http://special.msn.com/bcentral/prep04.armx
