In my seeking a managable way to build libtiff, on the Asterfax forum I got the following recommendation (from another fax user that made the move to libtiff 3.8.2):
================================================================
Hi Robert,
I have compiled libtiff-3.8.2 from the source package for my Fedora Core 4 machine. I am not sure about CentOS, but I think you can try to do the same with rpmbuild and the source package for Fedora:
- Install the rpmbuild tools in CentOS; - Download the source package for Fedora: http://mirrors.ircam.fr/pub/atrpms/src/fc6-i386/redhat/SRPMS.updates/libtiff-3.8.2-2.src.rpmhttp://mirrors.ircam.fr/pub/atrpms/src/fc6-i386/redhat/SRPMS.updates/libtiff...
- Install the source package as a non-root user: rpm -ivh libtiff-3.8.2-2.src.rpm - Go to your rpmbuild folder: cd ~/rpmbuild - Rebuild the package: rpmbuild -ba SPECS/libtiff.spec
If everything goes well, you will find a brand new set of RPM packages in the ~/rpmbuild/RPMS/i386/ (replace i386 for your actual architecture if you're not building on i386), which you can install with the upgrade RPM command: rpm -Uvh libtiff-3.8.2*.rpm
================================================================
Does this 'look right' for Centos? If not what do I change?
And how do I get the rpmbuild tools? yum install rpmbuild ??
Finally, once I have built 3.8.2, how would I migrate it to other systems?
On Tue, 2006-06-06 at 08:49 -0400, Robert Moskowitz wrote:
In my seeking a managable way to build libtiff, on the Asterfax forum I got the following recommendation (from another fax user that made the move to libtiff 3.8.2):
================================================================
Hi Robert,
I have compiled libtiff-3.8.2 from the source package for my Fedora Core 4 machine. I am not sure about CentOS, but I think you can try to do the same with rpmbuild and the source package for Fedora:
- Install the rpmbuild tools in CentOS;
- Download the source package for Fedora:
http://mirrors.ircam.fr/pub/atrpms/src/fc6- i386/redhat/SRPMS.updates/libtiff-3.8.2-2.src.rpm
- Install the source package as a non-root user:
rpm -ivh libtiff-3.8.2-2.src.rpm
- Go to your rpmbuild folder: cd ~/rpmbuild
- Rebuild the package: rpmbuild -ba SPECS/libtiff.spec
If everything goes well, you will find a brand new set of RPM packages in the ~/rpmbuild/RPMS/i386/ (replace i386 for your actual architecture if you're not building on i386), which you can install with the upgrade RPM command: rpm -Uvh libtiff-3.8.2*.rpm
================================================================
Does this 'look right' for Centos? If not what do I change?
And how do I get the rpmbuild tools? yum install rpmbuild ??
Finally, once I have built 3.8.2, how would I migrate it to other systems?
Not totally ... I will example with a non-root user called "builder"
as root: yum groupinstall "Development Tools"
useradd builder
passwd builder
(give builder a password)
su - builder
as builder:
Edit a file called .rpmmacros as builder from builder's home directory and add the line:
%_topdir /home/builder/rpmbuild
then do:
mkdir ~/rpmbuild
Then start from above with: Download the source package for Fedora
(you would do everything else ... however you might need to install several xxxxx-devel packages on your system to meet the build or install requirements and get a good build or install.
I have built this just now on CentOS-4 and it seems to build and install. You are welcome to use it:
http://centos.hughesjr.com/testing/libtiff-3.8.2-2/
I don't plan to maintain these on updates, unless you ask me to rebuild them.
You should be able to install them on any machines as the root user (from a directory containing the the RPMS):
yum localinstall libtiff-3.8.2-2.i386.rpm
or
yum localinstall libtiff-3.8.2-2.i386.rpm libtiff-devel-3.8.2-2.i386.rpm
(if you need the devel package)
Thanks, Johnny Hughes
Johnny,
First thank you for all of your patience with me.
I am going with the rpms you built (already downloaded them) on my new trixbox build, but I am going to, again, try the build myself on my 'old' AAH 2.8 system. I tried it yesterday and did a lot wrong, I see. You show me what I need to do to run the build as non-root. I ended up going forward as root, as I could not figure out the directory permissions. Also I need the g++ compiler it seemed.
Anyway, I need to do this at least once and this guildline should help me do it right finally. Then I can put it into my freemind linux 'database'. (and I would like to see a newer, enhanced ver of freemind soon too!).
At 08:21 AM 6/7/2006, Johnny Hughes wrote:
On Tue, 2006-06-06 at 08:49 -0400, Robert Moskowitz wrote:
In my seeking a managable way to build libtiff, on the Asterfax forum I got the following recommendation (from another fax user that made the move to libtiff 3.8.2):
================================================================
Hi Robert,
I have compiled libtiff-3.8.2 from the source package for my Fedora Core 4 machine. I am not sure about CentOS, but I think you can try to do the same with rpmbuild and the source package for Fedora:
- Install the rpmbuild tools in CentOS;
- Download the source package for Fedora:
http://mirrors.ircam.fr/pub/atrpms/src/fc6- i386/redhat/SRPMS.updates/libtiff-3.8.2-2.src.rpm
- Install the source package as a non-root user:
rpm -ivh libtiff-3.8.2-2.src.rpm
- Go to your rpmbuild folder: cd ~/rpmbuild
- Rebuild the package: rpmbuild -ba SPECS/libtiff.spec
If everything goes well, you will find a brand new set of RPM packages in the ~/rpmbuild/RPMS/i386/ (replace i386 for your actual architecture if you're not building on i386), which you can install with the upgrade RPM command: rpm -Uvh libtiff-3.8.2*.rpm
================================================================
Does this 'look right' for Centos? If not what do I change?
And how do I get the rpmbuild tools? yum install rpmbuild ??
Finally, once I have built 3.8.2, how would I migrate it to other systems?
Not totally ... I will example with a non-root user called "builder"
as root: yum groupinstall "Development Tools"
useradd builder
passwd builder
(give builder a password)
su - builder
as builder:
Edit a file called .rpmmacros as builder from builder's home directory and add the line:
%_topdir /home/builder/rpmbuild
then do:
mkdir ~/rpmbuild
Then start from above with: Download the source package for Fedora
(you would do everything else ... however you might need to install several xxxxx-devel packages on your system to meet the build or install requirements and get a good build or install.
I have built this just now on CentOS-4 and it seems to build and install. You are welcome to use it:
http://centos.hughesjr.com/testing/libtiff-3.8.2-2/
I don't plan to maintain these on updates, unless you ask me to rebuild them.
You should be able to install them on any machines as the root user (from a directory containing the the RPMS):
yum localinstall libtiff-3.8.2-2.i386.rpm
or
yum localinstall libtiff-3.8.2-2.i386.rpm libtiff-devel-3.8.2-2.i386.rpm
(if you need the devel package)
Thanks, Johnny Hughes
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
At 08:21 AM 6/7/2006, Johnny Hughes wrote:
On Tue, 2006-06-06 at 08:49 -0400, Robert Moskowitz wrote:
In my seeking a managable way to build libtiff, on the Asterfax forum I got the following recommendation (from another fax user that made the move to libtiff 3.8.2):
Well one initerestng observation on installing these rpms.
I have built this just now on CentOS-4 and it seems to build and install. You are welcome to use it:
http://centos.hughesjr.com/testing/libtiff-3.8.2-2/
I don't plan to maintain these on updates, unless you ask me to rebuild them.
You should be able to install them on any machines as the root user (from a directory containing the the RPMS):
yum localinstall libtiff-3.8.2-2.i386.rpm
This failed with:
yum localinstall libtiff-3.8.2-2.i386.rpm Setting up Local Package Process Examining libtiff-3.8.2-2.i386.rpm: libtiff - 3.8.2-2.i386 Marking libtiff-3.8.2-2.i386.rpm as an update to libtiff - 3.6.1-10.i386 Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Package libtiff.i386 0:3.8.2-2 set to be updated --> Running transaction check Setting up repositories trixbox 100% |=========================| 951 B 00:00 update 100% |=========================| 951 B 00:00 base 100% |=========================| 1.1 kB 00:00 addons 100% |=========================| 951 B 00:00 extras 100% |=========================| 1.1 kB 00:00 Reading repository metadata in from local files primary.xml.gz 100% |=========================| 13 kB 00:00 trixbox : ################################################## 25/25 Added 8 new packages, deleted 5 old in 0.62 seconds primary.xml.gz 100% |=========================| 42 kB 00:00 update : ################################################## 111/111 Added 1 new packages, deleted 0 old in 0.99 seconds --> Processing Dependency: libtiff = 3.6.1 for package: libtiff-devel --> Finished Dependency Resolution Error: Missing Dependency: libtiff = 3.6.1 is needed by package libtiff-devel
yum localinstall libtiff-3.8.2-2.i386.rpm libtiff-devel-3.8.2-2.i386.rpm
Actually this did not seem to work either but the following did:
yum localinstall libtiff-devel-3.8.2-2.i386.rpm libtiff-3.8.2-2.i386.rpm
Interesting that order is important....
(if you need the devel package)
"Perfection is achieved not when there is nothing more to add, but rather, when there is nothing left to take away"
Antoine de Saint-Exupéry (1900-1944)
On Wed, 2006-06-07 at 09:21 -0400, Robert Moskowitz wrote:
At 08:21 AM 6/7/2006, Johnny Hughes wrote:
On Tue, 2006-06-06 at 08:49 -0400, Robert Moskowitz wrote:
In my seeking a managable way to build libtiff, on the Asterfax forum I got the following recommendation (from another fax user that made the move to libtiff 3.8.2):
Well one initerestng observation on installing these rpms.
I have built this just now on CentOS-4 and it seems to build and install. You are welcome to use it:
http://centos.hughesjr.com/testing/libtiff-3.8.2-2/
I don't plan to maintain these on updates, unless you ask me to rebuild them.
You should be able to install them on any machines as the root user (from a directory containing the the RPMS):
yum localinstall libtiff-3.8.2-2.i386.rpm
This failed with:
yum localinstall libtiff-3.8.2-2.i386.rpm Setting up Local Package Process Examining libtiff-3.8.2-2.i386.rpm: libtiff - 3.8.2-2.i386 Marking libtiff-3.8.2-2.i386.rpm as an update to libtiff - 3.6.1-10.i386 Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Package libtiff.i386 0:3.8.2-2 set to be updated --> Running transaction check Setting up repositories trixbox 100% |=========================| 951 B 00:00 update 100% |=========================| 951 B 00:00 base 100% |=========================| 1.1 kB 00:00 addons 100% |=========================| 951 B 00:00 extras 100% |=========================| 1.1 kB 00:00 Reading repository metadata in from local files primary.xml.gz 100% |=========================| 13 kB 00:00 trixbox : ################################################## 25/25 Added 8 new packages, deleted 5 old in 0.62 seconds primary.xml.gz 100% |=========================| 42 kB 00:00 update : ################################################## 111/111 Added 1 new packages, deleted 0 old in 0.99 seconds --> Processing Dependency: libtiff = 3.6.1 for package: libtiff-devel --> Finished Dependency Resolution Error: Missing Dependency: libtiff = 3.6.1 is needed by package libtiff-devel
yum localinstall libtiff-3.8.2-2.i386.rpm libtiff-devel-3.8.2-2.i386.rpm
Actually this did not seem to work either but the following did:
yum localinstall libtiff-devel-3.8.2-2.i386.rpm libtiff-3.8.2-2.i386.rpm
Interesting that order is important....
(if you need the devel package)
The order shouldn't make a difference ... though, I can see how it might (if the first (already installed) -devel file is used to meet the install requirement for something else).
Hopefully this will solve your problems.
At 08:21 AM 6/7/2006, Johnny Hughes wrote:
Not totally ... I will example with a non-root user called "builder"
as root: yum groupinstall "Development Tools"
useradd builder
passwd builder
(give builder a password)
su - builder
as builder:
Edit a file called .rpmmacros as builder from builder's home directory and add the line:
%_topdir /home/builder/rpmbuild
then do:
mkdir ~/rpmbuild
Then start from above with: Download the source package for Fedora
Now I get:
Checking for unpackaged file(s): /usr/lib/rpm/check-files /var/tmp/libtiff-3.8.2-2-root Wrote: /home/rgm/rpmbuild/SRPMS/libtiff-3.8.2-2.src.rpm error: cannot create /home/rgm/rpmbuild/RPMS/i386: No such file or directory error: Could not open /home/rgm/rpmbuild/RPMS/i386/libtiff-3.8.2-2.i386.rpm: No such file or directory
RPM build errors: cannot create /home/rgm/rpmbuild/RPMS/i386: No such file or directory Could not open /home/rgm/rpmbuild/RPMS/i386/libtiff-3.8.2-2.i386.rpm: No such file or directory
What do I need this time?
On Wed, 2006-06-07 at 14:05 -0400, Robert Moskowitz wrote:
At 08:21 AM 6/7/2006, Johnny Hughes wrote:
Not totally ... I will example with a non-root user called "builder"
as root: yum groupinstall "Development Tools"
useradd builder
passwd builder
(give builder a password)
su - builder
as builder:
Edit a file called .rpmmacros as builder from builder's home directory and add the line:
%_topdir /home/builder/rpmbuild
then do:
mkdir ~/rpmbuild
Then start from above with: Download the source package for Fedora
Now I get:
Checking for unpackaged file(s): /usr/lib/rpm/check-files /var/tmp/libtiff-3.8.2-2-root Wrote: /home/rgm/rpmbuild/SRPMS/libtiff-3.8.2-2.src.rpm error: cannot create /home/rgm/rpmbuild/RPMS/i386: No such file or directory error: Could not open /home/rgm/rpmbuild/RPMS/i386/libtiff-3.8.2-2.i386.rpm: No such file or directory
RPM build errors: cannot create /home/rgm/rpmbuild/RPMS/i386: No such file or directory Could not open /home/rgm/rpmbuild/RPMS/i386/libtiff-3.8.2-2.i386.rpm: No such file or directory
What do I need this time?
is there an RPMS dir under RPM that is owned by rgm?
also, go ahead and create an i386 dir under RPMS, also owned by rgm
those would be in /home/rgm/rpmbuild
and everything should be owned by rgm