Re: [Radiance-dev] specifying X11 location

[Randolph M. Fritz]

I see I didn't make clear that in these procedures ssh sets the DISPLAY
variable on the Amazon Linux instance, so that one need only connect and
ideally everything else just works.

-- 
Randolph M. Fritz || +1 206 659-8617 || rmfri...@gmail.com

On Sun, Apr 8, 2018 at 4:55 PM, Randolph M. Fritz 
wrote:

> As far as specifying X11 location; if this is a need – and I have found it
> sometimes useful – the usual way this is done is via an X server running on
> your desktop system and ssh. The specifics depend on the details of the
> desktop system. If it is a Windows system, the inexpensive solution is the
> Xming X server and the PuTTY application. This page gives a summary of the
> setup procedure: http://www.geo.mtu.edu/geoschem/docs/putty_install.html.
> On a Mac, one uses XQuartz and the usual Mac terminal application.
> Unix-like systems run X11 natively, and one can simply use ssh from a
> window. For all of these, you may have to turn X Windows ssh access on on
> your Amazon LInux instance.
>
> --
> Randolph M. Fritz || +1 206 659-8617 || rmfri...@gmail.com
>
> On Sun, Apr 8, 2018 at 11:47 AM, Lars O. Grobe  wrote:
>
>> Hi Philip,
>>
>> don't worry about the "healthy state" of the executables. Make sure that
>> you have oconv ("pre-sorting" your geometry), vwrays (generating rays for
>> given projections), rtrace (the fundamental ray-tracer), rpict (a
>> ray-tracer for images), rcalc (a calculator for tabular data), and the
>> various generators (especially gensky). As long as they build, they will
>> do, and you may simply ignore build errors as long as you get what you need.
>>
>> From the lib directory, you will at least need rayinit.cal. If you are
>> aiming at CBDM, you also need the directional basis definitions according
>> to Klems, Reinhart et al. These are somewhat scattered over directorys,
>> best is to check your particular commands and collect them from the source
>> tree in one central lib-directory which you would include in your RAYPATH.
>> The various .cal-files have descriptions of their intended use included as
>> comment lines, they are useful (e.g. for interpolation, mapping, color
>> conversions) and definitely worth browsing, but not critical for plain
>> ray-tracing.
>>
>> Cheers, Lars.
>>
>>> Do you just mean that we could have ignored the X11-related compilation
>>> errors? (we bothered to include X11 libraries at build time to get as
>>> clean
>>> a compilation as possible, to be sure that the binaries we get out of the
>>> build are in a healthy state). Or do you mean this implies certain
>>> auxiliary files can be excluded?
>>>
>>>
>> ___
>> 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] specifying X11 location

[Randolph M. Fritz]

As far as specifying X11 location; if this is a need – and I have found it
sometimes useful – the usual way this is done is via an X server running on
your desktop system and ssh. The specifics depend on the details of the
desktop system. If it is a Windows system, the inexpensive solution is the
Xming X server and the PuTTY application. This page gives a summary of the
setup procedure: http://www.geo.mtu.edu/geoschem/docs/putty_install.html.
On a Mac, one uses XQuartz and the usual Mac terminal application.
Unix-like systems run X11 natively, and one can simply use ssh from a
window. For all of these, you may have to turn X Windows ssh access on on
your Amazon LInux instance.

-- 
Randolph M. Fritz || +1 206 659-8617 || rmfri...@gmail.com

On Sun, Apr 8, 2018 at 11:47 AM, Lars O. Grobe  wrote:

> Hi Philip,
>
> don't worry about the "healthy state" of the executables. Make sure that
> you have oconv ("pre-sorting" your geometry), vwrays (generating rays for
> given projections), rtrace (the fundamental ray-tracer), rpict (a
> ray-tracer for images), rcalc (a calculator for tabular data), and the
> various generators (especially gensky). As long as they build, they will
> do, and you may simply ignore build errors as long as you get what you need.
>
> From the lib directory, you will at least need rayinit.cal. If you are
> aiming at CBDM, you also need the directional basis definitions according
> to Klems, Reinhart et al. These are somewhat scattered over directorys,
> best is to check your particular commands and collect them from the source
> tree in one central lib-directory which you would include in your RAYPATH.
> The various .cal-files have descriptions of their intended use included as
> comment lines, they are useful (e.g. for interpolation, mapping, color
> conversions) and definitely worth browsing, but not critical for plain
> ray-tracing.
>
> Cheers, Lars.
>
>> Do you just mean that we could have ignored the X11-related compilation
>> errors? (we bothered to include X11 libraries at build time to get as
>> clean
>> a compilation as possible, to be sure that the binaries we get out of the
>> build are in a healthy state). Or do you mean this implies certain
>> auxiliary files can be excluded?
>>
>>
> ___
> 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] specifying X11 location

[Lars O. Grobe]

Hi Philip,

don't worry about the "healthy state" of the executables. Make sure that 
you have oconv ("pre-sorting" your geometry), vwrays (generating rays 
for given projections), rtrace (the fundamental ray-tracer), rpict (a 
ray-tracer for images), rcalc (a calculator for tabular data), and the 
various generators (especially gensky). As long as they build, they will 
do, and you may simply ignore build errors as long as you get what you need.


From the lib directory, you will at least need rayinit.cal. If you are 
aiming at CBDM, you also need the directional basis definitions 
according to Klems, Reinhart et al. These are somewhat scattered over 
directorys, best is to check your particular commands and collect them 
from the source tree in one central lib-directory which you would 
include in your RAYPATH. The various .cal-files have descriptions of 
their intended use included as comment lines, they are useful (e.g. for 
interpolation, mapping, color conversions) and definitely worth 
browsing, but not critical for plain ray-tracing.


Cheers, Lars.

Do you just mean that we could have ignored the X11-related compilation
errors? (we bothered to include X11 libraries at build time to get as clean
a compilation as possible, to be sure that the binaries we get out of the
build are in a healthy state). Or do you mean this implies certain
auxiliary files can be excluded?



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

Re: [Radiance-dev] specifying X11 location

[Philip Schwarz]

Hello Rob,

what about the lib directory? Are you in a position to elaborate on Lars'
following suggestion: "You may also remove all the example files from the
lib directory"

>if you're really only using oconv and rtrace, not only do you not need
libtiff,
Yes, initially at least, we plan to use just oconv and rtrace. We probably
want to use additional binaries in future.

>you don't even need X11 at all.
Do you just mean that we could have ignored the X11-related compilation
errors? (we bothered to include X11 libraries at build time to get as clean
a compilation as possible, to be sure that the binaries we get out of the
build are in a healthy state). Or do you mean this implies certain
auxiliary files can be excluded?

>And the obj directory can be ignored as well, those are all sample scenes
and stuff.
good to know

Thanks for your help,

Philip



On 6 April 2018 at 15:50, Rob Guglielmetti 
wrote:

> Hang on, if you're really only using oconv and rtrace, not only do you not
> need libtiff, you don't even need X11 at all. And the obj directory can be
> ignored as well, those are all sample scenes and stuff.
>
> On Fri, Apr 6, 2018 at 8:41 AM, Philip Schwarz  googlemail.com> wrote:
>
>> Thanks Lars,
>>
>> If I look at the contents of rad5R1supp.tar.gz
>> 
>>  (I
>> would look at the equivalent for 5.0, the version I am targeting, but it
>> doesn't seem to exist - it looks like core and auxiliary files are bundled
>> together in
>>
>> rad5R0all.tar.gz
>> ),
>> I see the following:
>>
>>
>> doc 102KB
>>
>> lib 371 MB
>>
>> obj 2.6MB
>>
>> src 9.3 MB
>>
>>
>> src just contains px/tiff, which you explained I can exclude
>>
>>
>> doc is just documentation so can be excluded
>>
>>
>> lib is the large one - what do you mean when you say "You may also
>> remove all the example files from the lib directory" - can the whole
>> directory be excluded?
>>
>>
>> what about the obj directory? You didn't mention it: can all of it be
>> excluded? It contains the following subdirectories:
>>
>> alpha
>>
>> cabin
>>
>> misc
>>
>> office
>>
>> texture
>>
>> virtual
>>
>>
>> Also, in a context in which I am only running binaries oconv and rtrace,
>> is it the case that none of the auxiliary files are needed? If not, which
>> ones are needed?
>>
>>
>> Your help with the above would be greatly appreciated.
>>
>>
>> Thanks,
>>
>>
>> Philip
>>
>>
>>
>> On 6 April 2018 at 12:43, Lars O. Grobe  wrote:
>>
>>> Hi Philip,
>>>
>>> as far as I understand you, the aim is to get a minimalistic Radiance
>>> rendering node. For that, I would propose to exclude all the X11, tcl-tk
>>> and tiff stuff. You will probably not work interactively on the node but
>>> get the results transferred to a local work-station, where you could do all
>>> file conversion and display work. You may also remove all the example files
>>> from the lib directory. The question is how to best implement all this in a
>>> makefile, so that you do not get all the errors. I have to admit that the
>>> many build systems around in Radiance are confusing... Maybe editing the
>>> rmakefiles, and setting up a new target such as "minimal-install" would be
>>> a good start.
>>>
>>> Cheers, Lars.
>>>
>>> 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 
>>> listRadiance-dev@radiance-online.orghttps://www.radiance-online.org/mailman/listinfo/radiance-dev
>>>
>>>
>>>
>>> ___
>>> Radiance-dev mailing list
>>> 

Re: [Radiance-dev] specifying X11 location

[Rob Guglielmetti]

Hang on, if you're really only using oconv and rtrace, not only do you not
need libtiff, you don't even need X11 at all. And the obj directory can be
ignored as well, those are all sample scenes and stuff.

On Fri, Apr 6, 2018 at 8:41 AM, Philip Schwarz <
philip.johann.schw...@googlemail.com> wrote:

> Thanks Lars,
>
> If I look at the contents of rad5R1supp.tar.gz
> 
>  (I
> would look at the equivalent for 5.0, the version I am targeting, but it
> doesn't seem to exist - it looks like core and auxiliary files are bundled
> together in
>
> rad5R0all.tar.gz
> ),
> I see the following:
>
>
> doc 102KB
>
> lib 371 MB
>
> obj 2.6MB
>
> src 9.3 MB
>
>
> src just contains px/tiff, which you explained I can exclude
>
>
> doc is just documentation so can be excluded
>
>
> lib is the large one - what do you mean when you say "You may also remove
> all the example files from the lib directory" - can the whole directory be
> excluded?
>
>
> what about the obj directory? You didn't mention it: can all of it be
> excluded? It contains the following subdirectories:
>
> alpha
>
> cabin
>
> misc
>
> office
>
> texture
>
> virtual
>
>
> Also, in a context in which I am only running binaries oconv and rtrace,
> is it the case that none of the auxiliary files are needed? If not, which
> ones are needed?
>
>
> Your help with the above would be greatly appreciated.
>
>
> Thanks,
>
>
> Philip
>
>
>
> On 6 April 2018 at 12:43, Lars O. Grobe  wrote:
>
>> Hi Philip,
>>
>> as far as I understand you, the aim is to get a minimalistic Radiance
>> rendering node. For that, I would propose to exclude all the X11, tcl-tk
>> and tiff stuff. You will probably not work interactively on the node but
>> get the results transferred to a local work-station, where you could do all
>> file conversion and display work. You may also remove all the example files
>> from the lib directory. The question is how to best implement all this in a
>> makefile, so that you do not get all the errors. I have to admit that the
>> many build systems around in Radiance are confusing... Maybe editing the
>> rmakefiles, and setting up a new target such as "minimal-install" would be
>> a good start.
>>
>> Cheers, Lars.
>>
>> 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 
>> 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
>
>
___
Radiance-dev mailing list
Radiance-dev@radiance-online.org
https://www.radiance-online.org/mailman/listinfo/radiance-dev

Re: [Radiance-dev] specifying X11 location

[Lars O. Grobe]

Hi Philip,

as far as I understand you, the aim is to get a minimalistic Radiance 
rendering node. For that, I would propose to exclude all the X11, tcl-tk 
and tiff stuff. You will probably not work interactively on the node but 
get the results transferred to a local work-station, where you could do 
all file conversion and display work. You may also remove all the 
example files from the lib directory. The question is how to best 
implement all this in a makefile, so that you do not get all the errors. 
I have to admit that the many build systems around in Radiance are 
confusing... Maybe editing the rmakefiles, and setting up a new target 
such as "minimal-install" would be a good start.


Cheers, Lars.


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 becauseI don't have a/usr/X11R6/lib directory (but I have some 
X11 files in /usr/lib64 instead, due to having installedlibX11).
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] 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

[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

Re: [Radiance-dev] specifying X11 location

[Randolph Fritz]

I think you need at least the "xorg-x11-proto-devel-7.7” package, or whatever 
the current version is. That has at least some of the headers. You may need 
some other packages, but that’s a place to start.

Might want to try asking on Amazon’s developer forums or Amazon technical 
support directly, if Amazon offers any.

-- 
Randolph M. Fritz || rmfri...@gmail.com 


> On Apr 4, 2018, at 12:27 PM, Axel Jacobs  wrote:
> 
> If you're compiling Radiance yourself, you not only need the X11 libs, but 
> also the X11-development libs, as well as a few other build dependencies.  Is 
> there something like libX11-dev for Amazon LINUX?
> 
> A
> 
> On 04/04/18 18:54, Philip Schwarz wrote:
>> Hello,
>> In https://github.com/NREL/Radiance/blob/master/noX11.help I see the 
>> following:
>>If you have X11 installed but in a non-standard location, you only need 
>> to edit the rmake script to add the needed -I and -L options.
>> I think that by 'add the needed -I and -L options." it really means modify 
>> the existing -I and -L options to reflect the location of X11.
>> Is that right?
>> In https://github.com/NREL/Radiance/blob/master/makeall#L113 I see
>> set mach="-Dlinux -D_FILE_OFFSET_BITS=64 -L/usr/X11R6/lib -I/usr/include/X11 
>> -DNOSTEREO"
>> Am I right in thinking that I just need to replace /usr/X11R6/lib and/or 
>> /usr/include/X11with alternative absolute paths, and the build should work?
>> My X11 installation consists of the following four files:
>> /usr/lib64/libX11-xcb.so.1
>> /usr/lib64/libX11-xcb.so.1.0.0
>> /usr/lib64/libX11.so.6
>> /usr/lib64/libX11.so.6.3.0
>> How should I change the -L and -I options. Do I need to have both -L and -I 
>> or just one of them?
>> Is this what I need?:
>> set mach="-Dlinux -D_FILE_OFFSET_BITS=64 -L/usr/lib64 -I/usr/lib64 
>> -DNOSTEREO"
>> When I run makeall install, I am given the opportunity to change the line 
>> interactively. Is that all I need to do, or should I make the change myself 
>> directly to the makeall file?
>> Thank you in advance for your help.
>> Philip Schwarz
>> P.S. If the solution involves setting up symbolic links (preferably not), 
>> can you please go into details? Thanks.
>> On 4 April 2018 at 16:05, Philip Schwarz 
>> > > wrote:
>>Hello,
>>I am trying to install radiance on Linux 64 (in a docker container
>>based onhttps://hub.docker.com/_/amazonlinux/
>>)
>>When I run ‘makeall install’ I get 10 errors of the following
>>type:*fatal error:*X11/Xlib.h: No such file or directory
>>I believe this is because I don’t have X11 installed. I have
>>a/usr/lib64/X11 directory but it is empty.
>>There is a library for amazonlinux called libX11
>>(https://aws.amazon.com/amazon-linux-ami/2017.09-packages/
>>), so I
>>installed it: yum install libX11-1.6.0.
>>I can ask what was installed:
>>sh-4.2# repoquery --list libX11
>>/usr/lib/libX11-xcb.so.1
>>/usr/lib/libX11-xcb.so.1.0.0
>>/usr/lib/libX11.so.6
>>/usr/lib/libX11.so.6.3.0
>>/usr/lib64/libX11-xcb.so.1
>>/usr/lib64/libX11-xcb.so.1.0.0
>>/usr/lib64/libX11.so.6
>>/usr/lib64/libX11.so.6.3.0
>>sh-4.2#
>>How do I now change the -L option of the rmake command to reflect my
>>environment?
>>The current value is‘-L/usr/X11R6/lib’
>>I tried changing it to ‘-L/usr/lib64’but I still get the X11-related
>>fatal errors.
>>I also tried copying the libX11 files from /usr/lib/ to
>>/usr/lib64/X11 and setting -L to '-L/usr/lib64/X11' but I get the
>>same errors.
>>Have you come across this problem before?
>>Any suggestions as to how to address the problem?
>>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

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

Re: [Radiance-dev] specifying X11 location

[Philip Schwarz]

btw, I received an email confirming that I have joined the mailing list,
but when I send an email to the list I am told the message is awaiting
moderation because I am not a member.

Philip

On 4 April 2018 at 18:54, Philip Schwarz <
philip.johann.schw...@googlemail.com> wrote:

> Hello,
>
> In https://github.com/NREL/Radiance/blob/master/noX11.help I see the
> following:
>
>If you have X11 installed but in a non-standard location, you only need
> to edit the rmake script to add the needed -I and -L options.
>
> I think that by 'add the needed -I and -L options." it really means
> modify the existing -I and -L options to reflect the location of X11.
> Is that right?
>
> In https://github.com/NREL/Radiance/blob/master/makeall#L113 I see
>
> set mach="-Dlinux -D_FILE_OFFSET_BITS=64 -L/usr/X11R6/lib
> -I/usr/include/X11 -DNOSTEREO"
>
> Am I right in thinking that I just need to replace /usr/X11R6/lib  and/or
> /usr/include/X11 with alternative absolute paths, and the build should
> work?
>
> My X11 installation consists of the following four files:
>
> /usr/lib64/libX11-xcb.so.1
>
> /usr/lib64/libX11-xcb.so.1.0.0
>
> /usr/lib64/libX11.so.6
>
> /usr/lib64/libX11.so.6.3.0
>
> How should I change the -L and -I options. Do I need to have both -L and
> -I or just one of them?
>
> Is this what I need?:
>
> set mach="-Dlinux -D_FILE_OFFSET_BITS=64 -L/usr/lib64 -I/usr/lib64
> -DNOSTEREO"
>
> When I run makeall install, I am given the opportunity to change the line
> interactively. Is that all I need to do, or should I make the change myself
> directly to the makeall file?
>
> Thank you in advance for your help.
>
> Philip Schwarz
>
> P.S. If the solution involves setting up symbolic links (preferably not),
> can you please go into details? Thanks.
>
>
>
>
> On 4 April 2018 at 16:05, Philip Schwarz  googlemail.com> wrote:
>
>> Hello,
>>
>>
>> I am trying to install radiance on Linux 64 (in a docker container based
>> on https://hub.docker.com/_/amazonlinux/)
>>
>>
>> When I run ‘makeall install’ I get 10 errors of the following type: *fatal
>> error: *X11/Xlib.h: No such file or directory
>>
>>
>> I believe this is because I don’t have X11 installed. I have a /usr/lib64/X11
>> directory but it is empty.
>>
>>
>> There is a library for amazonlinux called libX11 (
>> https://aws.amazon.com/amazon-linux-ami/2017.09-packages/), so I
>> installed it: yum install libX11-1.6.0.
>>
>>
>> I can ask what was installed:
>>
>>
>> sh-4.2# repoquery --list libX11
>>
>> /usr/lib/libX11-xcb.so.1
>>
>> /usr/lib/libX11-xcb.so.1.0.0
>>
>> /usr/lib/libX11.so.6
>>
>> /usr/lib/libX11.so.6.3.0
>>
>> /usr/lib64/libX11-xcb.so.1
>>
>> /usr/lib64/libX11-xcb.so.1.0.0
>>
>> /usr/lib64/libX11.so.6
>>
>> /usr/lib64/libX11.so.6.3.0
>>
>> sh-4.2#
>>
>>
>> How do I now change the -L option of the rmake command to reflect my
>> environment?
>>
>>
>> The current value is  ‘-L/usr/X11R6/lib’
>>
>>
>> I tried changing it to ‘-L/usr/lib64’  but I still get the X11-related
>> fatal errors.
>>
>>
>> I also tried copying the libX11 files from /usr/lib/ to /usr/lib64/X11
>> and setting -L to '-L/usr/lib64/X11' but I get the same errors.
>>
>>
>> Have you come across this problem before?
>>
>>
>> Any suggestions as to how to address the problem?
>>
>>
>> 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