Re: [Radiance-dev] how serious are these remaining 5 build errors?

[Randolph Fritz]

> Cannot find wish executable in current path -- trad not installed.
> https://gist.github.com/philipjss/bded331695eedfad0e76f48557b21427#file-build-1-console-output-txt-L802-L803
>  
> 
> 
> There were some errors.
> https://gist.github.com/philipjss/bded331695eedfad0e76f48557b21427#file-build-1-console-output-txt-L827
>  
> 
Wish is part of tk, which relies on tcl. Installing “tcl” and “tk” will 
probably resolve that build issue, but “trad” is in any event a GUI dependent 
program and – I think – not much used these days, so you may not need it.
-- 
Randolph


___
Radiance-dev mailing list
Radiance-dev@radiance-online.org
https://www.radiance-online.org/mailman/listinfo/radiance-dev

Re: [Radiance-dev] specifying X11 location

[Randolph Fritz]

> should I be concerned about the fact that installing libX11 and libX11-devel 
> seems to have been sufficient in order to eliminate the X11-related 
> compilation errors?

No. There’s probably a symlink that’s covering that.

> Also, our application uses Radiance in headless mode (no UI). 
> Am I right in thinking that whilst installing X11 is necessary in order to 
> get a clean build, many of the resulting binaries can be run without X11. 
> E.g. am I right in thinking that I can run oconv and rtrace without X11?
> 


That’s correct. If you want to use any of the X11 programs remotely, you can 
run an X server on the system you are accessing your Amazon system from. 

> Is there some resource that can be used to determine which Radiance binaries 
> rely on X11 and which don't?


Mmmm…”ldd” will probably tell you, if the build script uses shared libraries. 
But only the programs that have graphical interfaces use X11 anyway.

-- 
Randolph M. Fritz, Lighting Design and Simulation
+1 206 659-8617 || rmfri...@gmail.com 

> On Apr 5, 2018, at 12:19 PM, Philip Schwarz 
>  wrote:
> 
> Hello,
> 
> should I be concerned about the fact that installing libX11 and libX11-devel 
> seems to have been sufficient in order to eliminate the X11-related 
> compilation errors?
> 
> I expected to also have to  change the -L option to point to /usr/lib64 in 
> the following 
> 
> set mach="-Dlinux -D_FILE_OFFSET_BITS=64 -L/usr/X11R6/lib 
> -I/usr/include/X11 -DNOSTEREO"
> 
> That's because I don't have a /usr/X11R6/lib directory (but I have some X11 
> files in /usr/lib64 instead, due to having installed libX11).
> I didn't expect to have to edit the -I option because I do have a 
> /usr/include/X11 directory, due to having installed libX11-devel.
> 
> Thoughts?
> 
> Also, our application uses Radiance in headless mode (no UI). 
> Am I right in thinking that whilst installing X11 is necessary in order to 
> get a clean build, many of the resulting binaries can be run without X11. 
> 
> E.g. am I right in thinking that I can run oconv and rtrace without X11?
> 
> Is there some resource that can be used to determine which Radiance binaries 
> rely on X11 and which don't?
> 
> Thank you in advance for your help. 
> 
> Philip Schwarz
> 
> 
> ___
> Radiance-dev mailing list
> Radiance-dev@radiance-online.org
> https://www.radiance-online.org/mailman/listinfo/radiance-dev

___
Radiance-dev mailing list
Radiance-dev@radiance-online.org
https://www.radiance-online.org/mailman/listinfo/radiance-dev

Re: [Radiance-dev] src/rt/Version.c does not compile

[Philip Schwarz]

@Greg

>this is what your Version.c file should look like in the end

That works.

Great.

Thanks.

Philip

On 5 April 2018 at 16:46, Gregory J. Ward  wrote:

> Incidentally, this is what your Version.c file should look like in the
> end.  If you create this in your src/rt directory, everything should
> compile from there.  Would like to get makeall working right, though:
>
> /*
>  * This file was created automatically during make.
>  */
>
> char VersionID[]="RADIANCE 5.2a lastmod Fri Feb 16 10:37:53 PST 2018 by
> gward on photon";
>
> 
> -G
>
> *From: *"Gregory J. Ward" 
>
> *Date: *April 5, 2018 8:44:39 AM PDT
>
>
> It seems like your Linux (and some others?) don't include the standard
> "ed" editor or any equivalent.  Can you install it?
>
> This script could probably be converted easily enough to 'sed' or Perl,
> but this is the first I've heard of the problem.
>
> Reporting errors on NREL's github is currently like telling your problems
> to a congressman, or a black hole.  We're looking to fix that, but no one
> gets notified of those posts at the moment.
>
> -Greg
>
> *From: *Philip Schwarz 
>
> *Date: *April 5, 2018 8:35:45 AM PDT
>
>
> by the way, someone has run into this problem in the past:
> https://github.com/NREL/Radiance/issues/17
>
> Philip
>
> On 5 April 2018 at 16:34, Philip Schwarz  googlemail.com> wrote:
>
>> Hello,
>>
>> when I run 'makeall install' against release 5.0 of Radiance (
>> https://github.com/NREL/Radiance/releases/tag/5.0),
>> file src/rt/Version.c is automatically generated, with the following
>> contents:
>>
>> RADIANCE 5.0
>>
>> Thu Apr  5 13:38:59 UTC 2018
>>
>> root
>>
>> 6f0749328ec2
>>
>>
>> Version.c does not compile. It causes the 3 very similar compilation
>> errors at the bottom of this email. The problem seems to be the dot in
>> '5.0'.
>>
>> Btw, there is a file called Verscrit.ed which seems to relate to the
>> content of Version.c, and which contains the following:
>>
>>
>> 1s/^/char VersionID[]="/
>>
>> 2s/^/ lastmod /
>>
>> 3s/^/ by /
>>
>> 4s/^/ on /
>>
>> 1,$j
>>
>> 1s/$/";/
>>
>> 1i
>>
>> /*
>>
>>  * This file was created automatically during make.
>>
>>  */
>>
>>
>> .
>>
>> w
>>
>> q
>>
>>
>> Is there something sort-term that I can do to prevent this from
>> happening?
>>
>> If not, is it the case that this is just a minor error that can be
>> ignored and doesn't prevent Radiance from being correctly installed and
>> ready for use?
>>
>> Thanks,
>>
>> Philip Schwarz
>>
>> === ERRORS ===
>>
>> gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
>> -L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO   -c -o pmaptype.o
>> pmaptype.c
>>
>> gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
>> -L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO   -c -o Version.o
>> Version.c
>>
>> *Version.c:1:10:* *error: *expected '*=*', '*,*', '*;*', '*asm*' or '
>> *__attribute__*' before numeric constant
>>
>>  RADIANCE 5.0
>>
>> *  ^*
>>
>> *Version.c:4:1:* *error: *invalid suffix "f0749328ec2" on integer
>> constant
>>
>>  6f0749328ec2
>>
>> * ^*
>>
>> make: *** [Version.o] Error 1
>>
>> gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
>> -L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO   -c -o rpmain.o rpmain.c
>>
>>
>> =
>>
>>
>> gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
>> -L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO
>> -DDEVPATH=\"/home/radiance/bin\"   -c -o viewbeams.o viewbeams.c
>>
>> cp ../rt/Version.c .
>>
>> gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
>> -L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO
>> -DDEVPATH=\"/home/radiance/bin\"   -c -o Version.o Version.c
>>
>> *Version.c:1:10:* *error: *expected '*=*', '*,*', '*;*', '*asm*' or '
>> *__attribute__*' before numeric constant
>>
>>  RADIANCE 5.0
>>
>> *  ^*
>>
>> *Version.c:4:1:* *error: *invalid suffix "f0749328ec2" on integer
>> constant
>>
>>  6f0749328ec2
>>
>> * ^*
>>
>> make: *** [Version.o] Error 1
>>
>>
>> =
>>
>>
>> gcc -I../common -I../rt -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
>> -L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO   -c -o rpiece.o rpiece.c
>>
>> cp ../rt/Version.c .
>>
>> gcc -I../common -I../rt -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
>> -L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO   -c -o Version.o
>> Version.c
>>
>> *Version.c:1:10:* *error: *expected '*=*', '*,*', '*;*', '*asm*' or '
>> *__attribute__*' before numeric constant
>>
>>  RADIANCE 5.0
>>
>> *  ^*
>>
>> *Version.c:4:1:* *error: *invalid suffix "f0749328ec2" on integer
>> constant
>>
>>  6f0749328ec2
>>
>> * ^*
>>
>> make: *** [Version.o] Error 1
>>
>> ===
>>
>>
> 

Re: [Radiance-dev] src/rt/Version.c does not compile

[Philip Schwarz]

by the way, someone has run into this problem in the past:
https://github.com/NREL/Radiance/issues/17

Philip

On 5 April 2018 at 16:34, Philip Schwarz <
philip.johann.schw...@googlemail.com> wrote:

> Hello,
>
> when I run 'makeall install' against release 5.0 of Radiance (
> https://github.com/NREL/Radiance/releases/tag/5.0), file src/rt/Version.c
> is automatically generated, with the following contents:
>
> RADIANCE 5.0
>
> Thu Apr  5 13:38:59 UTC 2018
>
> root
>
> 6f0749328ec2
>
>
> Version.c does not compile. It causes the 3 very similar compilation
> errors at the bottom of this email. The problem seems to be the dot in
> '5.0'.
>
> Btw, there is a file called Verscrit.ed which seems to relate to the
> content of Version.c, and which contains the following:
>
>
> 1s/^/char VersionID[]="/
>
> 2s/^/ lastmod /
>
> 3s/^/ by /
>
> 4s/^/ on /
>
> 1,$j
>
> 1s/$/";/
>
> 1i
>
> /*
>
>  * This file was created automatically during make.
>
>  */
>
>
> .
>
> w
>
> q
>
>
> Is there something sort-term that I can do to prevent this from happening?
>
> If not, is it the case that this is just a minor error that can be ignored
> and doesn't prevent Radiance from being correctly installed and ready for
> use?
>
> Thanks,
>
> Philip Schwarz
>
> === ERRORS ===
>
> gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
> -L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO   -c -o pmaptype.o
> pmaptype.c
>
> gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
> -L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO   -c -o Version.o Version.c
>
> *Version.c:1:10:* *error: *expected '*=*', '*,*', '*;*', '*asm*' or '
> *__attribute__*' before numeric constant
>
>  RADIANCE 5.0
>
> *  ^*
>
> *Version.c:4:1:* *error: *invalid suffix "f0749328ec2" on integer constant
>
>  6f0749328ec2
>
> * ^*
>
> make: *** [Version.o] Error 1
>
> gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
> -L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO   -c -o rpmain.o rpmain.c
>
>
> =
>
>
> gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
> -L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO 
> -DDEVPATH=\"/home/radiance/bin\"
>   -c -o viewbeams.o viewbeams.c
>
> cp ../rt/Version.c .
>
> gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
> -L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO 
> -DDEVPATH=\"/home/radiance/bin\"
>   -c -o Version.o Version.c
>
> *Version.c:1:10:* *error: *expected '*=*', '*,*', '*;*', '*asm*' or '
> *__attribute__*' before numeric constant
>
>  RADIANCE 5.0
>
> *  ^*
>
> *Version.c:4:1:* *error: *invalid suffix "f0749328ec2" on integer constant
>
>  6f0749328ec2
>
> * ^*
>
> make: *** [Version.o] Error 1
>
>
> =
>
>
> gcc -I../common -I../rt -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
> -L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO   -c -o rpiece.o rpiece.c
>
> cp ../rt/Version.c .
>
> gcc -I../common -I../rt -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
> -L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO   -c -o Version.o Version.c
>
> *Version.c:1:10:* *error: *expected '*=*', '*,*', '*;*', '*asm*' or '
> *__attribute__*' before numeric constant
>
>  RADIANCE 5.0
>
> *  ^*
>
> *Version.c:4:1:* *error: *invalid suffix "f0749328ec2" on integer constant
>
>  6f0749328ec2
>
> * ^*
>
> make: *** [Version.o] Error 1
>
> ===
>
>
___
Radiance-dev mailing list
Radiance-dev@radiance-online.org
https://www.radiance-online.org/mailman/listinfo/radiance-dev

Re: [Radiance-dev] src/rt/Version.c does not compile

[Gregory J. Ward]

It seems like your Linux (and some others?) don't include the standard "ed" 
editor or any equivalent.  Can you install it?

This script could probably be converted easily enough to 'sed' or Perl, but 
this is the first I've heard of the problem.

Reporting errors on NREL's github is currently like telling your problems to a 
congressman, or a black hole.  We're looking to fix that, but no one gets 
notified of those posts at the moment.

-Greg

> From: Philip Schwarz 
> Date: April 5, 2018 8:35:45 AM PDT
> 
> by the way, someone has run into this problem in the past: 
> https://github.com/NREL/Radiance/issues/17
> 
> Philip
> 
> On 5 April 2018 at 16:34, Philip Schwarz 
>  wrote:
> Hello,
> 
> when I run 'makeall install' against release 5.0 of Radiance 
> (https://github.com/NREL/Radiance/releases/tag/5.0), file src/rt/Version.c is 
> automatically generated, with the following contents:
> 
> RADIANCE 5.0
> Thu Apr  5 13:38:59 UTC 2018
> root
> 6f0749328ec2
> 
> Version.c does not compile. It causes the 3 very similar compilation errors 
> at the bottom of this email. The problem seems to be the dot in '5.0'.
> 
> Btw, there is a file called Verscrit.ed which seems to relate to the content 
> of Version.c, and which contains the following: 
> 
> 1s/^/char VersionID[]="/
> 2s/^/ lastmod /
> 3s/^/ by /
> 4s/^/ on /
> 1,$j
> 1s/$/";/
> 1i
> /*
>  * This file was created automatically during make.
>  */
> 
> .
> w
> q
> 
> Is there something sort-term that I can do to prevent this from happening? 
> 
> If not, is it the case that this is just a minor error that can be ignored 
> and doesn't prevent Radiance from being correctly installed and ready for use?
> 
> Thanks,
> 
> Philip Schwarz
> 
> === ERRORS ===
> 
> gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64 -L/usr/X11R6/lib 
> -I/usr/include/X11 -DNOSTEREO   -c -o pmaptype.o pmaptype.c
> gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64 -L/usr/X11R6/lib 
> -I/usr/include/X11 -DNOSTEREO   -c -o Version.o Version.c
> Version.c:1:10: error: expected '=', ',', ';', 'asm' or '__attribute__' 
> before numeric constant
>  RADIANCE 5.0
>   ^
> Version.c:4:1: error: invalid suffix "f0749328ec2" on integer constant
>  6f0749328ec2
>  ^
> make: *** [Version.o] Error 1
> gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64 -L/usr/X11R6/lib 
> -I/usr/include/X11 -DNOSTEREO   -c -o rpmain.o rpmain.c
> 
> =
> 
> gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64 -L/usr/X11R6/lib 
> -I/usr/include/X11 -DNOSTEREO -DDEVPATH=\"/home/radiance/bin\"   -c -o 
> viewbeams.o viewbeams.c
> cp ../rt/Version.c .
> gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64 -L/usr/X11R6/lib 
> -I/usr/include/X11 -DNOSTEREO -DDEVPATH=\"/home/radiance/bin\"   -c -o 
> Version.o Version.c
> Version.c:1:10: error: expected '=', ',', ';', 'asm' or '__attribute__' 
> before numeric constant
>  RADIANCE 5.0
>   ^
> Version.c:4:1: error: invalid suffix "f0749328ec2" on integer constant
>  6f0749328ec2
>  ^
> make: *** [Version.o] Error 1
> 
> =
> 
> gcc -I../common -I../rt -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64 
> -L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO   -c -o rpiece.o rpiece.c
> cp ../rt/Version.c .
> gcc -I../common -I../rt -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64 
> -L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO   -c -o Version.o Version.c
> Version.c:1:10: error: expected '=', ',', ';', 'asm' or '__attribute__' 
> before numeric constant
>  RADIANCE 5.0
>   ^
> Version.c:4:1: error: invalid suffix "f0749328ec2" on integer constant
>  6f0749328ec2
>  ^
> make: *** [Version.o] Error 1
> 
> ===
> 
> 
> ___
> Radiance-dev mailing list
> Radiance-dev@radiance-online.org
> https://www.radiance-online.org/mailman/listinfo/radiance-dev
___
Radiance-dev mailing list
Radiance-dev@radiance-online.org
https://www.radiance-online.org/mailman/listinfo/radiance-dev

[Radiance-dev] src/rt/Version.c does not compile

[Philip Schwarz]

Hello,

when I run 'makeall install' against release 5.0 of Radiance (
https://github.com/NREL/Radiance/releases/tag/5.0), file src/rt/Version.c
is automatically generated, with the following contents:

RADIANCE 5.0

Thu Apr  5 13:38:59 UTC 2018

root

6f0749328ec2


Version.c does not compile. It causes the 3 very similar compilation errors
at the bottom of this email. The problem seems to be the dot in '5.0'.

Btw, there is a file called Verscrit.ed which seems to relate to the
content of Version.c, and which contains the following:


1s/^/char VersionID[]="/

2s/^/ lastmod /

3s/^/ by /

4s/^/ on /

1,$j

1s/$/";/

1i

/*

 * This file was created automatically during make.

 */


.

w

q


Is there something sort-term that I can do to prevent this from happening?

If not, is it the case that this is just a minor error that can be ignored
and doesn't prevent Radiance from being correctly installed and ready for
use?

Thanks,

Philip Schwarz

=== ERRORS ===

gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
-L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO   -c -o pmaptype.o pmaptype.c

gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
-L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO   -c -o Version.o Version.c

*Version.c:1:10:* *error: *expected '*=*', '*,*', '*;*', '*asm*' or '
*__attribute__*' before numeric constant

 RADIANCE 5.0

*  ^*

*Version.c:4:1:* *error: *invalid suffix "f0749328ec2" on integer constant

 6f0749328ec2

* ^*

make: *** [Version.o] Error 1

gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
-L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO   -c -o rpmain.o rpmain.c


=


gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
-L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO
-DDEVPATH=\"/home/radiance/bin\"   -c -o viewbeams.o viewbeams.c

cp ../rt/Version.c .

gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
-L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO
-DDEVPATH=\"/home/radiance/bin\"   -c -o Version.o Version.c

*Version.c:1:10:* *error: *expected '*=*', '*,*', '*;*', '*asm*' or '
*__attribute__*' before numeric constant

 RADIANCE 5.0

*  ^*

*Version.c:4:1:* *error: *invalid suffix "f0749328ec2" on integer constant

 6f0749328ec2

* ^*

make: *** [Version.o] Error 1


=


gcc -I../common -I../rt -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
-L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO   -c -o rpiece.o rpiece.c

cp ../rt/Version.c .

gcc -I../common -I../rt -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
-L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO   -c -o Version.o Version.c

*Version.c:1:10:* *error: *expected '*=*', '*,*', '*;*', '*asm*' or '
*__attribute__*' before numeric constant

 RADIANCE 5.0

*  ^*

*Version.c:4:1:* *error: *invalid suffix "f0749328ec2" on integer constant

 6f0749328ec2

* ^*

make: *** [Version.o] Error 1

===
___
Radiance-dev mailing list
Radiance-dev@radiance-online.org
https://www.radiance-online.org/mailman/listinfo/radiance-dev

Re: [Radiance-dev] src/rt/Version.c does not compile

[Philip Schwarz]

Hello Greg,

Yes, about ed, I was getting the following error:

gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
-L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO   -c -o pmaptype.o pmaptype.c
( cat VERSION ; date ; whoami ; hostname ) > Version.c
ed - Version.c < verscript.ed
/bin/sh: ed: command not found
make: *** [Version.c] Error 127
gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
-L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO   -c -o rpmain.o rpmain.c


So I installed ed and that error got replaced by a third instance of the
following:

*Version.c:1:10:* *error: *expected '*=*', '*,*', '*;*', '*asm*' or '
*__attribute__*' before numeric constant

 RADIANCE 5.0

*  ^*

*Version.c:4:1:* *error: *invalid suffix "f0749328ec2" on integer constant

 6f0749328ec2

* ^*

make: *** [Version.o] Error 1


I had stopped posting to github, but I saw the same error I was
encountering, and I saw that it had been closed 3 days ago, so I thought it
could be useful to post anyway.

Thanks,

Philip


On 5 April 2018 at 16:44, Gregory J. Ward  wrote:

> It seems like your Linux (and some others?) don't include the standard
> "ed" editor or any equivalent.  Can you install it?
>
> This script could probably be converted easily enough to 'sed' or Perl,
> but this is the first I've heard of the problem.
>
> Reporting errors on NREL's github is currently like telling your problems
> to a congressman, or a black hole.  We're looking to fix that, but no one
> gets notified of those posts at the moment.
>
> -Greg
>
> *From: *Philip Schwarz 
>
> *Date: *April 5, 2018 8:35:45 AM PDT
>
>
> by the way, someone has run into this problem in the past:
> https://github.com/NREL/Radiance/issues/17
>
> Philip
>
> On 5 April 2018 at 16:34, Philip Schwarz  googlemail.com> wrote:
>
>> Hello,
>>
>> when I run 'makeall install' against release 5.0 of Radiance (
>> https://github.com/NREL/Radiance/releases/tag/5.0),
>> file src/rt/Version.c is automatically generated, with the following
>> contents:
>>
>> RADIANCE 5.0
>>
>> Thu Apr  5 13:38:59 UTC 2018
>>
>> root
>>
>> 6f0749328ec2
>>
>>
>> Version.c does not compile. It causes the 3 very similar compilation
>> errors at the bottom of this email. The problem seems to be the dot in
>> '5.0'.
>>
>> Btw, there is a file called Verscrit.ed which seems to relate to the
>> content of Version.c, and which contains the following:
>>
>>
>> 1s/^/char VersionID[]="/
>>
>> 2s/^/ lastmod /
>>
>> 3s/^/ by /
>>
>> 4s/^/ on /
>>
>> 1,$j
>>
>> 1s/$/";/
>>
>> 1i
>>
>> /*
>>
>>  * This file was created automatically during make.
>>
>>  */
>>
>>
>> .
>>
>> w
>>
>> q
>>
>>
>> Is there something sort-term that I can do to prevent this from
>> happening?
>>
>> If not, is it the case that this is just a minor error that can be
>> ignored and doesn't prevent Radiance from being correctly installed and
>> ready for use?
>>
>> Thanks,
>>
>> Philip Schwarz
>>
>> === ERRORS ===
>>
>> gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
>> -L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO   -c -o pmaptype.o
>> pmaptype.c
>>
>> gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
>> -L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO   -c -o Version.o
>> Version.c
>>
>> *Version.c:1:10:* *error: *expected '*=*', '*,*', '*;*', '*asm*' or '
>> *__attribute__*' before numeric constant
>>
>>  RADIANCE 5.0
>>
>> *  ^*
>>
>> *Version.c:4:1:* *error: *invalid suffix "f0749328ec2" on integer
>> constant
>>
>>  6f0749328ec2
>>
>> * ^*
>>
>> make: *** [Version.o] Error 1
>>
>> gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
>> -L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO   -c -o rpmain.o rpmain.c
>>
>>
>> =
>>
>>
>> gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
>> -L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO
>> -DDEVPATH=\"/home/radiance/bin\"   -c -o viewbeams.o viewbeams.c
>>
>> cp ../rt/Version.c .
>>
>> gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
>> -L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO
>> -DDEVPATH=\"/home/radiance/bin\"   -c -o Version.o Version.c
>>
>> *Version.c:1:10:* *error: *expected '*=*', '*,*', '*;*', '*asm*' or '
>> *__attribute__*' before numeric constant
>>
>>  RADIANCE 5.0
>>
>> *  ^*
>>
>> *Version.c:4:1:* *error: *invalid suffix "f0749328ec2" on integer
>> constant
>>
>>  6f0749328ec2
>>
>> * ^*
>>
>> make: *** [Version.o] Error 1
>>
>>
>> =
>>
>>
>> gcc -I../common -I../rt -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
>> -L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO   -c -o rpiece.o rpiece.c
>>
>> cp ../rt/Version.c .
>>
>> gcc -I../common -I../rt -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64
>> -L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO   

Re: [Radiance-dev] src/rt/Version.c does not compile

[Guglielmetti, Robert]

Yes, thanks for supplying the stdout. Greg is right, you need 'ed' as the 
script is written, easy to sub for some other stream editor. And I am starting 
to monitor the GitHub issues page more regularly, as people do seem to be using 
it, but as I and Greg have noted here and elsewhere Philip, it's not really the 
primary spot for posting these kinds of issues. 

- Rob

On 4/5/18, 9:44 AM, "Gregory J. Ward"  wrote:

It seems like your Linux (and some others?) don't include the standard "ed" 
editor or any equivalent.  Can you install it?


This script could probably be converted easily enough to 'sed' or Perl, but 
this is the first I've heard of the problem.


Reporting errors on NREL's github is currently like telling your problems 
to a congressman, or a black hole.  We're looking to fix that, but no one gets 
notified of those posts at the moment.


-Greg


From:
Philip Schwarz 
Date:
April 5, 2018 8:35:45 AM PDT





by the way, someone has run into this problem in the past: 
https://github.com/NREL/Radiance/issues/17 


Philip


On 5 April 2018 at 16:34, Philip Schwarz 
 wrote:

Hello,


when I run 'makeall install' against release 5.0 of Radiance 
(https://github.com/NREL/Radiance/releases/tag/5.0 
),
 file src/rt/Version.c is automatically generated, with the following 
contents:



RADIANCE 
5.0

Thu Apr  5 13:38:59
UTC 
2018

root

6f0749328ec2






Version.c does not compile. It causes the 3
 very similar compilation errors at the bottom of this email. The problem 
seems to be the dot in '5.0'.


Btw, there is a file called Verscrit.ed which seems to relate to the 
content of Version.c, and which contains the following: 



1s/^/char VersionID[]="/

2s/^/ lastmod /

3s/^/ by /

4s/^/ on /

1,$j

1s/$/";/

1i

/*

 * This file was created automatically during make.

 */




.

w

q





Is there something sort-term that I can do to prevent this from happening? 


If not, is it the case that this is just a minor error that can be ignored 
and doesn't prevent Radiance from being correctly installed and ready for use?


Thanks,


Philip Schwarz


=== ERRORS ===


gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64 
-L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO
  -c -o pmaptype.o pmaptype.c
gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64 
-L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO
  -c -o Version.o Version.c
Version.c:1:10: error: expected '=', ',', ';', 'asm' or '__attribute__' 
before numeric constant
 RADIANCE 5.0
  
^
Version.c:4:1: error: invalid suffix "f0749328ec2" on integer constant
 6f0749328ec2
 ^
make: *** [Version.o] Error 1
gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64 
-L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO
  -c -o rpmain.o rpmain.c


=


gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64 
-L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO -DDEVPATH=\"/home/radiance/bin\"
  -c -o viewbeams.o viewbeams.c
cp ../rt/Version.c .
gcc -I../common -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64 
-L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO -DDEVPATH=\"/home/radiance/bin\"
  -c -o Version.o Version.c
Version.c:1:10: error: expected '=', ',', ';', 'asm' or '__attribute__' 
before numeric constant
 RADIANCE 5.0
  
^
Version.c:4:1: error: invalid suffix "f0749328ec2" on integer constant
 6f0749328ec2
 ^
make: *** [Version.o] Error 1


=



gcc -I../common -I../rt -L../lib -O2 -Dlinux -D_FILE_OFFSET_BITS=64 
-L/usr/X11R6/lib -I/usr/include/X11 -DNOSTEREO
  -c -o rpiece.o 

[Radiance-dev] how serious are these remaining 5 build errors?

[Philip Schwarz]

Hello,


now that I no longer get X11-related compilation errors, I am down to the
following 5:


make clean error

https://gist.github.com/philipjss/bded331695eedfad0e76f48557b21427#file-build-1-console-output-txt-L121-L126


Lib tiff error

https://gist.github.com/philipjss/bded331695eedfad0e76f48557b21427#file-build-1-console-output-txt-L599-L610


make: Target `install' not remade because of errors.

https://gist.github.com/philipjss/bded331695eedfad0e76f48557b21427#file-build-1-console-output-txt-L672


Cannot find wish executable in current path -- trad not installed.

https://gist.github.com/philipjss/bded331695eedfad0e76f48557b21427#file-build-1-console-output-txt-L802-L803


There were some errors.

https://gist.github.com/philipjss/bded331695eedfad0e76f48557b21427#file-build-1-console-output-txt-L827

I would really appreciate it if you could have a quick look.

Is there a quick fix for them?

If not, how serious are they?

Thank you for your help.

Philip
___
Radiance-dev mailing list
Radiance-dev@radiance-online.org
https://www.radiance-online.org/mailman/listinfo/radiance-dev

Re: [Radiance-dev] how serious are these remaining 5 build errors?

[Lars O. Grobe]

Hi Philip, you may also want to install a current version of 
libtiff-dev. This is used for the tif image format conversion (ra_tiff 
and friends).


This would all better go to the Radiance discussion rather the 
development list - unless we aim at providing a list of external 
dependencies for coming distributions.


Cheers, Lars.


Am 05.04.18 um 18:19 schrieb Philip Schwarz:


Hello,


now that I no longer get X11-related compilation errors, I am down to 
the following 5:



make clean error

https://gist.github.com/philipjss/bded331695eedfad0e76f48557b21427#file-build-1-console-output-txt-L121-L126


Lib tiff error

https://gist.github.com/philipjss/bded331695eedfad0e76f48557b21427#file-build-1-console-output-txt-L599-L610


make: Target `install' not remade because of errors.

https://gist.github.com/philipjss/bded331695eedfad0e76f48557b21427#file-build-1-console-output-txt-L672


Cannot find wish executable in current path -- trad not installed.

https://gist.github.com/philipjss/bded331695eedfad0e76f48557b21427#file-build-1-console-output-txt-L802-L803


There were some errors.

https://gist.github.com/philipjss/bded331695eedfad0e76f48557b21427#file-build-1-console-output-txt-L827


I would really appreciate it if you could have a quick look.

Is there a quick fix for them?

If not, how serious are they?

Thank you for your help.

Philip


___
Radiance-dev mailing list
Radiance-dev@radiance-online.org
https://www.radiance-online.org/mailman/listinfo/radiance-dev


___
Radiance-dev mailing list
Radiance-dev@radiance-online.org
https://www.radiance-online.org/mailman/listinfo/radiance-dev

Re: [Radiance-dev] how serious are these remaining 5 build errors?

[Gregory J. Ward]

After installing "ed", you would need to remove the unedited Version.c file to 
recreate it with makeall.

Regarding your other errors, you need to install the Radiance overlay 
(Auxiliary files) that includes the src/px/tiff directory (I think).  The link 
was on the downloads page:


https://www.radiance-online.org/download-install/radiance-source-code/un-official-head-version

This is also responsible for the distclean error.  You can just ignore the 
errors related to libtiff and do without ra_tiff in your distro.

To run trad, you need to install wish.  If you don't have it, you can't use 
that program, so it doesn't bother installing.

-Greg

> From: Philip Schwarz 
> Date: April 5, 2018 9:19:57 AM PDT
> 
> Hello,
> 
> now that I no longer get X11-related compilation errors, I am down to the 
> following 5:
> 
> make clean error
> https://gist.github.com/philipjss/bded331695eedfad0e76f48557b21427#file-build-1-console-output-txt-L121-L126
> 
> Lib tiff error
> https://gist.github.com/philipjss/bded331695eedfad0e76f48557b21427#file-build-1-console-output-txt-L599-L610
> 
> make: Target `install' not remade because of errors.
> https://gist.github.com/philipjss/bded331695eedfad0e76f48557b21427#file-build-1-console-output-txt-L672
> 
> Cannot find wish executable in current path -- trad not installed.
> https://gist.github.com/philipjss/bded331695eedfad0e76f48557b21427#file-build-1-console-output-txt-L802-L803
> 
> There were some errors.
> https://gist.github.com/philipjss/bded331695eedfad0e76f48557b21427#file-build-1-console-output-txt-L827
> 
> I would really appreciate it if you could have a quick look.
> 
> Is there a quick fix for them?
> 
> If not, how serious are they?
> 
> Thank you for your help.
> 
> Philip
> ___
> Radiance-dev mailing list
> Radiance-dev@radiance-online.org
> https://www.radiance-online.org/mailman/listinfo/radiance-dev
___
Radiance-dev mailing list
Radiance-dev@radiance-online.org
https://www.radiance-online.org/mailman/listinfo/radiance-dev

Re: [Radiance-dev] how serious are these remaining 5 build errors?

[Philip Schwarz]

Hello Lars,

are we saying installing libtiff-dev should address the following?

cd ../libtiff ; make install
  /bin/sh: line 0: cd: tiff: No such file or directory
/bin/sh: ./configure: No such file or directory
/bin/sh: line 6: cd: port: No such file or directory
make[1]: Entering directory `/home/radiance/src/px'
make[1]: *** No rule to make target `all'.
make[1]: Leaving directory `/home/radiance/src/px'
/bin/sh: line 7: cd: ../libtiff: No such file or directory
make[1]: Entering directory `/home/radiance/src/px'
make[1]: *** No rule to make target `install'.
make[1]: Leaving directory `/home/radiance/src/px'
make: *** [../lib/libtiff.a] Error 2

I tried installing libtiff and was told I already have it.
I installed libtiff-dev and ran 'makeall install'  again but unfortunately
still got the same errors.

Thanks,

Philip

On 5 April 2018 at 17:26, Lars O. Grobe  wrote:

> Hi Philip, you may also want to install a current version of libtiff-dev.
> This is used for the tif image format conversion (ra_tiff and friends).
>
> This would all better go to the Radiance discussion rather the development
> list - unless we aim at providing a list of external dependencies for
> coming distributions.
>
> Cheers, Lars.
>
> Am 05.04.18 um 18:19 schrieb Philip Schwarz:
>
> Hello,
>
>
> now that I no longer get X11-related compilation errors, I am down to the
> following 5:
>
>
> make clean error
>
> https://gist.github.com/philipjss/bded331695eedfad0e76f48557b214
> 27#file-build-1-console-output-txt-L121-L126
>
>
> Lib tiff error
>
> https://gist.github.com/philipjss/bded331695eedfad0e76f48557b214
> 27#file-build-1-console-output-txt-L599-L610
>
>
> make: Target `install' not remade because of errors.
>
> https://gist.github.com/philipjss/bded331695eedfad0e76f48557b214
> 27#file-build-1-console-output-txt-L672
>
>
> Cannot find wish executable in current path -- trad not installed.
>
> https://gist.github.com/philipjss/bded331695eedfad0e76f48557b214
> 27#file-build-1-console-output-txt-L802-L803
>
>
> There were some errors.
>
> https://gist.github.com/philipjss/bded331695eedfad0e76f48557b214
> 27#file-build-1-console-output-txt-L827
>
> I would really appreciate it if you could have a quick look.
>
> Is there a quick fix for them?
>
> If not, how serious are they?
>
> Thank you for your help.
>
> Philip
>
>
> ___
> Radiance-dev mailing 
> listRadiance-dev@radiance-online.orghttps://www.radiance-online.org/mailman/listinfo/radiance-dev
>
>
>
> ___
> Radiance-dev mailing list
> Radiance-dev@radiance-online.org
> https://www.radiance-online.org/mailman/listinfo/radiance-dev
>
>
___
Radiance-dev mailing list
Radiance-dev@radiance-online.org
https://www.radiance-online.org/mailman/listinfo/radiance-dev

Re: [Radiance-dev] how serious are these remaining 5 build errors?

[Gregory J. Ward]

This is probably not worth talking about, but if you remove Version.c and run 
"rmake" in src/rt, you should see:

$ rmake Version.c
( cat VERSION ; date ; whoami ; hostname ) > Version.c
ed - Version.c < verscript.ed

Thus, if a bad version of Version.c exists, ed won't get run and you'll get the 
subsequent error, which is why I suggested removing Version.c and re-running 
makeall.  It doesn't matter what is in the Version string as far as running the 
program goes, but it's best if you have rmake create it if it's not an official 
Radiance release.

If the above command isn't being run or is generating an error after you 
installed 'ed', then I need to see the exact error.

It seems like you have a really stripped-down version of Linux.

-Greg

> From: Philip Schwarz 
> Date: April 5, 2018 10:32:20 AM PDT
> 
> >After installing "ed", you would need to remove the unedited Version.c file 
> >to recreate it with makeall.
> 
> Installing ed didn't solve the problem of Version.c being generated 
> incorrectly: it just resulted in one more instance being reported of the 
> compilation error due to the file's contents.
> 
> As you said, manually replacing the content of Version.c with the following, 
> results in the file compiling successfully: char VersionID[]="RADIANCE 5.2a 
> lastmod Fri Feb 16 10:37:53 PST 2018 by gward on photon";
> 
> At that point I thought I'd just put this doctored Version.c file under 
> version control and forget about it. Does the fact that the file already 
> exists cause the build a problem? At first sight, it doesn't seem so.
> 
> If instead of doing that I delete the file then makeall will continue to 
> generate the same problematic file leading to compilation errors, I believe.
> 
> Let me know if I need to do something else instead.
> 
> Sorry if I am belabouring this but I appreciate your time so I am hoping that 
> while I may well have repeated the obvious, it may spare you some effort in 
> replying.
> 
> Philip
> 
> 
> On 5 April 2018 at 18:01, Gregory J. Ward  wrote:
> After installing "ed", you would need to remove the unedited Version.c file 
> to recreate it with makeall.
> 
> Regarding your other errors, you need to install the Radiance overlay 
> (Auxiliary files) that includes the src/px/tiff directory (I think).  The 
> link was on the downloads page:
> 
>   
> https://www.radiance-online.org/download-install/radiance-source-code/un-official-head-version
> 
> This is also responsible for the distclean error.  You can just ignore the 
> errors related to libtiff and do without ra_tiff in your distro.
> 
> To run trad, you need to install wish.  If you don't have it, you can't use 
> that program, so it doesn't bother installing.
> 
> -Greg
> 
>> From: Philip Schwarz 
>> Date: April 5, 2018 9:19:57 AM PDT
>> 
>> Hello,
>> 
>> now that I no longer get X11-related compilation errors, I am down to the 
>> following 5:
>> 
>> make clean error
>> https://gist.github.com/philipjss/bded331695eedfad0e76f48557b21427#file-build-1-console-output-txt-L121-L126
>> 
>> Lib tiff error
>> https://gist.github.com/philipjss/bded331695eedfad0e76f48557b21427#file-build-1-console-output-txt-L599-L610
>> 
>> make: Target `install' not remade because of errors.
>> https://gist.github.com/philipjss/bded331695eedfad0e76f48557b21427#file-build-1-console-output-txt-L672
>> 
>> Cannot find wish executable in current path -- trad not installed.
>> https://gist.github.com/philipjss/bded331695eedfad0e76f48557b21427#file-build-1-console-output-txt-L802-L803
>> 
>> There were some errors.
>> https://gist.github.com/philipjss/bded331695eedfad0e76f48557b21427#file-build-1-console-output-txt-L827
>> 
>> I would really appreciate it if you could have a quick look.
>> 
>> Is there a quick fix for them?
>> 
>> If not, how serious are they?
>> 
>> Thank you for your help.
>> 
>> Philip
>> ___
>> Radiance-dev mailing list
>> Radiance-dev@radiance-online.org
>> https://www.radiance-online.org/mailman/listinfo/radiance-dev
> 
> ___
> Radiance-dev mailing list
> Radiance-dev@radiance-online.org
> https://www.radiance-online.org/mailman/listinfo/radiance-dev
> 
> 
> ___
> Radiance-dev mailing list
> Radiance-dev@radiance-online.org
> https://www.radiance-online.org/mailman/listinfo/radiance-dev
___
Radiance-dev mailing list
Radiance-dev@radiance-online.org
https://www.radiance-online.org/mailman/listinfo/radiance-dev

Re: [Radiance-dev] how serious are these remaining 5 build errors?

[Philip Schwarz]

@Greg

Yes, I can confirm that if I download the Radiance overlay (Auxiliary
files) and take the src/px/tiff directory, and add it to the radiance 5.0
codebase that I am trying to build, the following errors go away:

make clean error

https://gist.github.com/philipjss/bded331695eedfad0e76f48557b214
27#file-build-1-console-output-txt-L121-L126


Lib tiff error

https://gist.github.com/philipjss/bded331695eedfad0e76f48557b214
27#file-build-1-console-output-txt-L599-L610


make: Target `install' not remade because of errors.

https://gist.github.com/philipjss/bded331695eedfad0e76f48557b214
27#file-build-1-console-output-txt-L672


That leaves me with the following:

Cannot find wish executable in current path -- trad not installed.

https://gist.github.com/philipjss/bded331695eedfad0e76f48557b214
27#file-build-1-console-output-txt-L802-L803


There were some errors.

https://gist.github.com/philipjss/bded331695eedfad0e76f48557b214
27#file-build-1-console-output-txt-L827


You have explained why the first is happening, and the second is just a
message which would not appear if the first error wasn't there.

Thanks for that. Great.

The Radiance overlay (Auxiliary files) are 380MB (unzipped) - the src/px/tiff
directory within them is 8-9MB.

As you pointed out in another email, I am using a very stripped down
version of Linux. amazonlinux 2017.09 is 165MB.
We want it to be as small as possible to keep down the cost and time it
takes to create deploy and run our application in a docker container on AWS.

Right now, we are going to start off wanting to run just oconv and rtrace.
In time, we may run more commands.
On that basis, adding all of the Radiance overlay to our application seems
prohibitive.
Is there something that conveys how Radiance's various binaries rely on
which part of the Radiance overlay?
E.g. you said that if we can do without ra_tiff then we don't need src/px/tiff
- by the way, what is ra_tiff? I don't think I can see it among the
binaries created by the build.
Can oconv and rtrace run without ra_tiff?
Does the idea of running without the Radiance overlay make any sense, e.g.
if wanting to run just oconv and rtrace?
What is the set of binaries that can happily run without Radiance overlay?
Are oconv and rtrace among them? If not, what portions of the Radiance
overlay do they rely on?
Is it possible to pick and choose, within reason, which parts of the Radiance
overlay are needed based on the binaries one wishes to run?

Any help would be greatly appreciated.

Thanks,

Philip

On 5 April 2018 at 18:01, Gregory J. Ward  wrote:

> After installing "ed", you would need to remove the unedited Version.c
> file to recreate it with makeall.
>
> Regarding your other errors, you need to install the Radiance overlay
> (Auxiliary files) that includes the src/px/tiff directory (I think).  The
> link was on the downloads page:
>
> https://www.radiance-online.org/download-install/radiance-
> source-code/un-official-head-version
>
> This is also responsible for the distclean error.  You can just ignore the
> errors related to libtiff and do without ra_tiff in your distro.
>
> To run trad, you need to install wish.  If you don't have it, you can't
> use that program, so it doesn't bother installing.
>
> -Greg
>
> *From: *Philip Schwarz 
>
> *Date: *April 5, 2018 9:19:57 AM PDT
>
>
> Hello,
>
>
> now that I no longer get X11-related compilation errors, I am down to the
> following 5:
>
>
> make clean error
>
> https://gist.github.com/philipjss/bded331695eedfad0e76f48557b214
> 27#file-build-1-console-output-txt-L121-L126
>
>
> Lib tiff error
>
> https://gist.github.com/philipjss/bded331695eedfad0e76f48557b214
> 27#file-build-1-console-output-txt-L599-L610
>
>
> make: Target `install' not remade because of errors.
>
> https://gist.github.com/philipjss/bded331695eedfad0e76f48557b214
> 27#file-build-1-console-output-txt-L672
>
>
> Cannot find wish executable in current path -- trad not installed.
>
> https://gist.github.com/philipjss/bded331695eedfad0e76f48557b214
> 27#file-build-1-console-output-txt-L802-L803
>
>
> There were some errors.
>
> https://gist.github.com/philipjss/bded331695eedfad0e76f48557b214
> 27#file-build-1-console-output-txt-L827
>
> I would really appreciate it if you could have a quick look.
>
> Is there a quick fix for them?
>
> If not, how serious are they?
>
> Thank you for your help.
>
> Philip
> ___
> Radiance-dev mailing list
> Radiance-dev@radiance-online.org
> https://www.radiance-online.org/mailman/listinfo/radiance-dev
>
>
> ___
> Radiance-dev mailing list
> Radiance-dev@radiance-online.org
> https://www.radiance-online.org/mailman/listinfo/radiance-dev
>
>
___
Radiance-dev mailing list
Radiance-dev@radiance-online.org
https://www.radiance-online.org/mailman/listinfo/radiance-dev

[Radiance-dev] specifying X11 location

[Philip Schwarz]

Hello,

should I be concerned about the fact that installing libX11 and
libX11-devel seems to have been sufficient in order to eliminate the
X11-related compilation errors?

I expected to also have to  change the -L option to point to /usr/lib64 in
the following

set mach="-Dlinux -D_FILE_OFFSET_BITS=64 -L/usr/X11R6/lib
-I/usr/include/X11 -DNOSTEREO"

That's because I don't have a /usr/X11R6/lib directory (but I have some X11
files in /usr/lib64 instead, due to having installed libX11).
I didn't expect to have to edit the -I option because I do have a
/usr/include/X11
directory, due to having installed libX11-devel.

Thoughts?

Also, our application uses Radiance in headless mode (no UI).
Am I right in thinking that whilst installing X11 is necessary in order to
get a clean build, many of the resulting binaries can be run without X11.

E.g. am I right in thinking that I can run oconv and rtrace without X11?

Is there some resource that can be used to determine which Radiance
binaries rely on X11 and which don't?

Thank you in advance for your help.

Philip Schwarz
___
Radiance-dev mailing list
Radiance-dev@radiance-online.org
https://www.radiance-online.org/mailman/listinfo/radiance-dev