On Tue, Mar 06, 2007 at 05:42:34PM +0100, Trond Danielsen wrote: > 2007/3/6, Eric Blossom <[EMAIL PROTECTED]>: > >On Tue, Mar 06, 2007 at 01:38:51PM +0100, Trond Danielsen wrote: > >> Hi, > >> > >> I creating a spec file for GNU Radio, and I discovered some minor issues: > >> > >> 1. Standard library paths are hardcoded into some of the libraries. I > >> use this command in the spec file to fix libtool before building: > >> 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 > > > >Just out of curiosity, how does _everybody_ else handle this problem? > >I suspect that they're not editing libtool source. > > > >Please take a look at the .spec files for other applications built > >with autotools. > > I am aware of that this solution looks a bit dirty, but it is actually > taken from the packaging guidelines on the fedoraproject wiki: > http://fedoraproject.org/wiki/Packaging/Guidelines#head-a1dfb5f46bf4098841e31a75d833e6e1b3e72544
Very good. I guess they don't care for --rpath ;) > The message reported by rpmbuild is not an error; it is possible to > ignore it, but I wanted to do the right thing. Thats why I am asking. Thanks for you efforts on this. It'll be great to have an rpm. > Trond Danielsen Eric _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
