[CELT-dev] trouble building celt on Fedora

[Peter Robinson]

Hi Jean-Marc,

> Peter Robinson a écrit :
>> I'm looking to package up celt for inclusion in Fedora as the next
>> stable release of ekiga/opal will have support for it. I've run into
>> two issues in compiling it into a rpm. The first is a show stopper,
>> then second one not so much of an issue but thought I'd report it for
>> reference.
>
> Actually, recently Monty was working on packaging CELT for Fedora and
> (AFAIK) succeeded, so maybe you can use what he did.

My looking didn't find the package in Fedora Mainline nor a review
request for it so I packaged it up as the new ekiga 3.2 will support
it.

>> The first issue is due to the celtdec and celtenc explicitly define
>> rpath. I get the following errors when building the packages:
>> celt.x86_64: E: binary-or-shlib-defines-rpath /usr/bin/celtdec ['/usr/lib64']
>> celt.x86_64: E: binary-or-shlib-defines-rpath /usr/bin/celtenc ['/usr/lib64']
> ...
>> *******************************************************************************
>> ERROR   0001: file '/usr/bin/celtenc' contains a standard rpath
>> '/usr/lib64' in [/usr/lib64]
>> ERROR   0001: file '/usr/bin/celtdec' contains a standard rpath
>> '/usr/lib64' in [/usr/lib64]
>
> The thing is that the Makefile.am doesn't mention rpath at all. Any idea
> what's the problem? I don't remember Monty complaining about that one.

Weird, Fedora's RPM build system is pretty strict on all sorts of
things so it tends to find all sorts of bits.
I fixed it by running the following sed commands on the celtenc and
celtdec commands.

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

You can see the Fedora  details of it here.
 https://fedoraproject.org/wiki/Packaging/Guidelines#Beware_of_Rpath

>> The other issue I have (which I work around with the --disable-oggtest
>> configure option) is that the test app doesn't build.
>
> What app doesn't build? Do you have libogg-devel installed?

I have libogg-devel installed. I've just removed the option from
configure and its building OK now. Maybe it was caused by and env
variable I had set when I was trying to sort the other issue out. If
it happens again I'll be sure to actually save the output next time.

Cheers,
Peter