[Radiance-general] rad3R5 from latest stable cvs doesn't compile

[Augustinus Topor]

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

# VERSION:      @VERSION@"

will result in

v3.4beta037#v3.4beta037
v3.4beta037Vv3.4beta037Ev3.4beta037Rv3.4beta037Sv3.4beta037Iv3.4beta037Ov3.4beta037Nv3.4beta037:v3.4beta037    
v3.4beta037@v3.4beta037Vv3.4beta037Ev3.4beta037Rv3.4beta037Sv3.4beta037Iv3.4beta037Ov3.4beta037Nv3.4beta037@v3.4beta037

whereas sed 3.02 generates

# VERSION:      v3.4beta037


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.
> 
> any ideas?
> 
> tom
> 
> _______________________________________________
> Radiance-general mailing list
> Radiance-general@radiance-online.org
> http://www.radiance-online.org/mailman/listinfo/radiance-general