compiling radiance

Hi Bernd,

This seems like Debian-specific advice. Is there some way to roll it into your distribution other than putting it in the main one? Where would a person look for such advice at radiance-online?

-Greg

···

From: Bernd Zeimetz <[email protected]>
Date: December 28, 2008 5:20:11 AM PST

Hi,

as several people asked on how to build Radiance on older Debian variants
(like Ubuntu...) - would it make sense to add a howto like from the mail below
(the version number is not up-to-date there, but with some lines on how to
find the right file it's fine) somewhere on radiance-online, or include it
into a readme in the source?

Cheers,

Bernd

Bernd Zeimetz wrote:

Nick Doylend wrote:

Hi, I get the following error while compiling the latest Radiance on
Ubuntu 7.10

You could just make a backport of the radiance packages from Debian's
Lenny/testing or Hardy (or upgrade to Hardy):

(not tested, but I hope it works:)

############################
sudo apt-get install devscripts fakeroot build-essential
sudo apt-get install debhelper libtiff4-dev libx11-dev libglu1-mesa-dev \
                          libxext-dev quilt tcsh docbook-to-man ed tk8.4

dget -x \
http://ftp.debian.org/debian/pool/main/r/radiance/radiance_3R9+20080530-4.dsc

cd radiance-3R9+20080530
dpkg-buildpackage -uc -us -rfakeroot
cd ..
sudo dpkg -i radiance*.deb
#############################

Cheers,

Bernd

Hi Greg!

This seems like Debian-specific advice. Is there some way to roll it
into your distribution other than putting it in the main one? Where
would a person look for such advice at radiance-online?

People who are in the need of a backport usually don't have a distribution
with those informations available (otherwise they'd have at least an
out-of-date package). Also there are a lot of Debian derivates, Ubuntu is just
a more well known one. So imho it would make sense to describe a way to do it,
I'm just not sure what the best place for it is. The other option would be to
figure out how backports in Ubuntu work, as far as I know they have something
like Debian's backports.org - but as I'm not an Ubuntu guy and I don't have
the necessary chroot available, I think that somebody else would have to take
care of "official" Ubuntu backports.

Cheers,

Bernd

···

--
Bernd Zeimetz Debian GNU/Linux Developer
GPG Fingerprint: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79

Isn't a file INSTALL in the ray directory the right place to collect all this information? Having one section "old distributions" in such a file would allow to add information on sources such as backports, how to compile on old linux distributions and such. Here is also the place to collect hints on systems such as solaris, os x, the various windows ports - even if we have only urls to sites describing the procedure, that way users having problems to install could have a start. In the very beginning, the options

a) binaries from radiance-online.org and radsite
b) binaries coming with distributions
c) compiling from source (generic using makeall install) should be present,

than all the special work-arounds.

I have an ubuntu box running, is there need for an ubuntu maintainer? Be aware that I have no (aka zero aka nul) experience with package building except making my own ones, but I guess that building on top of Bernd's debian work, there are few changes to expect.

Lars.

Lars O. Grobe wrote:

Isn't a file INSTALL in the ray directory the right place to collect all
this information? Having one section "old distributions" in such a file
would allow to add information on sources such as backports, how to
compile on old linux distributions and such. Here is also the place to
collect hints on systems such as solaris, os x, the various windows
ports - even if we have only urls to sites describing the procedure,
that way users having problems to install could have a start. In the
very beginning, the options

a) binaries from radiance-online.org and radsite

Should we provide packages there, too - at least for older versions of Ubuntu?
For Debian I can upload a package to backports.org - using that should
probably described, too, as the package there is more uptodate than the
version which was part of the release.

b) binaries coming with distributions
c) compiling from source (generic using makeall install) should be present,

than all the special work-arounds.

I have an ubuntu box running, is there need for an ubuntu maintainer? Be
aware that I have no (aka zero aka nul) experience with package building
except making my own ones, but I guess that building on top of Bernd's
debian work, there are few changes to expect.

Providing ofiicial Ubuntu backports sounds like a lot of work:
https://help.ubuntu.com/community/UbuntuBackports

So I still think it's more easy to provide a way to build the packages,
especially since rebuilding them should work without any problems (at least
for all released which shipped with debhelper 5).

···

--
Bernd Zeimetz Debian GNU/Linux Developer
GPG Fingerprint: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79

Does anyone want to take the reins on writing an INSTALL for the top-level directory?

-Greg

···

From: "Lars O. Grobe" <[email protected]>
Date: December 30, 2008 12:22:03 AM PST

Isn't a file INSTALL in the ray directory the right place to collect all this information? Having one section "old distributions" in such a file would allow to add information on sources such as backports, how to compile on old linux distributions and such. Here is also the place to collect hints on systems such as solaris, os x, the various windows ports - even if we have only urls to sites describing the procedure, that way users having problems to install could have a start. In the very beginning, the options

a) binaries from radiance-online.org and radsite
b) binaries coming with distributions
c) compiling from source (generic using makeall install) should be present,

than all the special work-arounds.

I have an ubuntu box running, is there need for an ubuntu maintainer? Be aware that I have no (aka zero aka nul) experience with package building except making my own ones, but I guess that building on top of Bernd's debian work, there are few changes to expect.

Lars.

Hi, I get the following error while compiling the latest Radiance on
Ubuntu 7.10

cd tiff ; ./configure -C -quiet -with-CC=gcc \
                "--libdir=`pwd`/../../lib"
                "--includedir=`pwd`/../../common" \
                --enable-static --disable-shared --disable-cxx \
                --enable-logluv --disable-jpeg \
                --disable-zlib --disable-pixarlog \
                "-with-ENVOPTS=-O2" ; \
        cd port ; make all ; \
        cd ../libtiff ; make install
appending configuration tag "CXX" to libtool
appending configuration tag "F77" to libtool
updating cache config.cache
config.status: error: cannot find input file: contrib/Makefile.in
make[1]: Entering directory
`/home/ndoylend/Radiance/ray/src/px/tiff/port'
make[1]: *** No rule to make target `all'.
make[1]: Leaving directory
`/home/ndoylend/Radiance/ray/src/px/tiff/port'
make[1]: Entering directory
`/home/ndoylend/Radiance/ray/src/px/tiff/libtiff'
make[1]: *** No rule to make target `install'.
make[1]: Leaving directory
`/home/ndoylend/Radiance/ray/src/px/tiff/libtiff'
make: *** [../lib/libtiff.a] Error 2

Any idea what's wrong? It looks like I'm missing a lot of the image
processing commands as a result.

Thanks,

Nick

Hi Nick,

I have not compiled Radiance in a while but if I remember right this kind of errors you see when you don't have the TIFF libraries installed. Just download rad3R8supp.tar.bz2 or whatever is the current version, unpack it in the buld directory (ray) and recompile. This should hopefully be sufficient to cure the problem.

Regards,
Erwin

···

-------- Original Message --------
Subject: [Radiance-general] compiling radiance (18-Sep-2008 14:18)
From: Nick Doylend <[email protected]>
To: [email protected]

Hi, I get the following error while compiling the latest Radiance on
Ubuntu 7.10

cd tiff ; ./configure -C -quiet -with-CC=gcc \
                "--libdir=`pwd`/../../lib"
                "--includedir=`pwd`/../../common" \
                --enable-static --disable-shared --disable-cxx \
                --enable-logluv --disable-jpeg \
                --disable-zlib --disable-pixarlog \
                "-with-ENVOPTS=-O2" ; \
        cd port ; make all ; \
        cd ../libtiff ; make install
appending configuration tag "CXX" to libtool
appending configuration tag "F77" to libtool
updating cache config.cache
config.status: error: cannot find input file: contrib/Makefile.in
make[1]: Entering directory
`/home/ndoylend/Radiance/ray/src/px/tiff/port'
make[1]: *** No rule to make target `all'.
make[1]: Leaving directory
`/home/ndoylend/Radiance/ray/src/px/tiff/port'
make[1]: Entering directory
`/home/ndoylend/Radiance/ray/src/px/tiff/libtiff'
make[1]: *** No rule to make target `install'.
make[1]: Leaving directory
`/home/ndoylend/Radiance/ray/src/px/tiff/libtiff'
make: *** [../lib/libtiff.a] Error 2

Any idea what's wrong? It looks like I'm missing a lot of the image
processing commands as a result.

Thanks,

Nick

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

Nick Doylend wrote:

Hi, I get the following error while compiling the latest Radiance on
Ubuntu 7.10

You could just make a backport of the radiance packages from Debian's
Lenny/testing or Hardy (or upgrade to Hardy):

(not tested, but I hope it works:)

···

############################
sudo apt-get install devscripts fakeroot build-essential
sudo apt-get install debhelper libtiff4-dev libx11-dev libglu1-mesa-dev \
                          libxext-dev quilt tcsh docbook-to-man ed tk8.4

dget -x \
http://ftp.debian.org/debian/pool/main/r/radiance/radiance_3R9+20080530-4.dsc

cd radiance-3R9+20080530
dpkg-buildpackage -uc -us -rfakeroot
cd ..
sudo dpkg -i radiance*.deb
#############################

Cheers,

Bernd

--
Bernd Zeimetz Debian GNU/Linux Developer
GPG Fingerprint: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79

Hi Nick,

The libtiff distribution I currently have in Radiance seems to have a broken build system, and is failing on a lot of platforms. I think I just need to remove it, and clear the related dependencies from px/Rmakefile. I'm pretty sure libtiff is included in most modern OS's, though I could use some verification on that point. I'm copying this discussion to the dev list, and we'll sort it out there.

Meanwhile, you should be able to get the px tools to compile by substituting the attached px/Rmakefile and running "rmake install" in the px directory.

Best,
-Greg

Rmakefile (5.22 KB)