I was attempting to rebuild the Centos 5.4 freetype rpm freetype-2.2.1-21.el5_3.src.rpm and got the following error. What do I need to do to solve it?
ERROR 0001: file '/usr/bin/ftvalid' contains a standard rpath '/usr/lib64' in [/usr/lib64] ERROR 0001: file '/usr/bin/fttimer' contains a standard rpath '/usr/lib64' in [/usr/lib64:/usr/lib] ERROR 0001: file '/usr/bin/fttimer' contains a standard rpath '/usr/lib' in [/usr/lib64:/usr/lib] ERROR 0001: file '/usr/bin/ftbench' contains a standard rpath '/usr/lib64' in [/usr/lib64] ERROR 0001: file '/usr/bin/ftmulti' contains a standard rpath '/usr/lib64' in [/usr/lib64:/usr/lib] ERROR 0001: file '/usr/bin/ftmulti' contains a standard rpath '/usr/lib' in [/usr/lib64:/usr/lib] ERROR 0001: file '/usr/bin/ftdump' contains a standard rpath '/usr/lib64' in [/usr/lib64] ERROR 0001: file '/usr/bin/ftlint' contains a standard rpath '/usr/lib64' in [/usr/lib64] ERROR 0001: file'/usr/bin/ftchkwd' contains a standard rpath '/usr/lib64' in [/usr/lib64] ERROR 0001: file '/usr/bin/ftmemchk' contains a standard rpath '/usr/lib64' in [/usr/lib64] ERROR 0001: file '/usr/bin/ftview' contains a standard rpath '/usr/lib64' in [/usr/lib64:/usr/lib] ERROR 0001: file '/usr/bin/ftview' contains a standard rpath '/usr/lib' in [/usr/lib64:/usr/lib] ERROR 0001: file '/usr/bin/ftgamma' contains a standard rpath '/usr/lib64' in [/usr/lib64:/usr/lib] ERROR 0001: file '/usr/bin/ftgamma' contains a standard rpath '/usr/lib' in [/usr/lib64:/usr/lib] ERROR 0001: file '/usr/bin/ftstring' contains a standard rpath '/usr/lib64' in [/usr/lib64:/usr/lib] ERROR 0001: file '/usr/bin/ftstring' contains a standard rpath '/usr/lib' in [/usr/lib64:/usr/lib] error: Bad exit status from /var/tmp/rpm-tmp.4069 (%install)
On Fri, Nov 20, 2009 at 3:12 PM, Frank Cox theatre@sasktel.net wrote:
I was attempting to rebuild the Centos 5.4 freetype rpm freetype-2.2.1-21.el5_3.src.rpm and got the following error. What do I need to do to solve it?
ERROR 0001: file '/usr/bin/ftvalid' contains a standard rpath '/usr/lib64' in [/usr/lib64] ERROR 0001: file '/usr/bin/fttimer' contains a standard rpath '/usr/lib64' in [/usr/lib64:/usr/lib] ERROR 0001: file '/usr/bin/fttimer' contains a standard rpath '/usr/lib' in [/usr/lib64:/usr/lib]
Maybe this:
https://fedoraproject.org/wiki/Packaging/Guidelines#Beware_of_Rpath
On Fri, 20 Nov 2009 15:19:35 -0500 Kwan Lowe wrote:
Maybe this:
https://fedoraproject.org/wiki/Packaging/Guidelines#Beware_of_Rpath
I'm missing something.
In the freetype.spec file I made this line:
%configure --disable-static
look like this:
%configure --disable-static --disable-rpath
I got the same error as before when I tried to compile it.
I then added the following two lines immediately after the configure line, so it looks like this:
%configure --disable-static sed -i 's|^hardcode_libdir_flag_spec=.*|hardcode_libdir_flag_spec=""|g' libtool sed -i 's|^runpath_var=LD_RUN_PATH|runpath_var=DIE_RPATH_DIE|g' libtool
That didn't work either -- I got an error telling me that it can't find libtool, and that was it.
The frustrating part of this is that I have found some webpages that discuss how to recompile exactly this srpm and it apparently works for them.
Example here: http://n8wood.wordpress.com/2009/08/18/tight-anti-aliased-fonts-in-centosrhe...
I don't see what I am doing wrong, or why this isn't working for me.
On Fri, 20 Nov 2009 14:55:24 -0600 Frank Cox wrote:
I don't see what I am doing wrong, or why this isn't working for me.
I seem to have gone from a rebuild failure to an installation failure.
Looking at this spec file:
http://dl.atrpms.net/all/freetype-static-f11.spec
I copied what appeared to be the relevant lines out of that into the freetype.spec that I have in my rpmbuild/SPECS directory, so now the "Build Freetype 2" section looks like this:
# Build Freetype 2 { %configure --disable-static sed -i 's|^hardcode_libdir_flag_spec=.*|hardcode_libdir_flag_spec=""|g' builds/unix/libtool sed -i 's|^runpath_var=LD_RUN_PATH| runpath_var=DIE_RPATH_DIE|g' builds/unix/libtool
make X11_PATH=/usr %{?_smp_mflags} }
That actually worked and it built me this in my RPMS/x86_64 directory:
freetype-2.2.1-21.x86_64.rpm freetype-demos-2.2.1-21.x86_64.rpm freetype-debuginfo-2.2.1-21.x86_64.rpm freetype-devel-2.2.1-21.x86_64.rpm
Dandy, I thought. Since the ATI proprietary driver web page states that it requires the i386 stuff on an x86_64 machine, and since I appear to have both i386 and x86_64 versions of freetype installed, I did my build again using --arch-i386. And again, it worked:
freetype-2.2.1-21.i386.rpm freetype-demos-2.2.1-21.i386.rpm freetype-debuginfo-2.2.1-21.i386.rpm freetype-devel-2.2.1-21.i386.rpm
Interestingly enough, to install these I had to use the --oldpackage parameter in the rpm command, otherwise it told me that a newer package was already installed.
So:
rpm -U rpm -U --oldpackage i386/freetype-2.2.1-21.i386.rpm x86_64/freetype-2.2.1-21.x86_64.rpm
And all appeared to be well. I then logged out and the fun started. gdm crashed. Here is what it says in /var/log/messages:
Nov 20 16:42:38 mutt kernel: gdm-binary[32281]: segfault at 00000000f5d8bd84 rip 00002b883bd87ee6 rsp 00000000f5d8bd78 error 6
Lots and lots of lines that tell me that, over and over.
Logging in at a text console and running "yum update" brought me back to a working system again.
The only thing I'm trying to do is to enable the bytecode interpreter on this system. So far, it's a failed attempt.
-
Frank Cox -
Kwan Lowe