On Fri, Aug 27, 2010 at 2:19 AM, Nathan O <[email protected]> wrote:
> > > On Fri, Aug 27, 2010 at 1:27 AM, Nathan O <[email protected]> wrote: > >> >> >> On Fri, Aug 27, 2010 at 1:24 AM, Magnus Therning <[email protected]>wrote: >> >>> On 27/08/10 06:03, Nathan O wrote: >>> > I have encountered having the issues with software that uses cmake as >>> it's >>> > build system. Usually I get the warnings stating that there is an >>> Insecure >>> > RPATH and Package contains reference to $srcdir. I believe I figured >>> out how >>> > to fix the RPATH issue, because a previous package had Rpath issues and >>> I >>> > used sed to add a setting(can't remember what the setting is called at >>> this >>> > second). The issue I have now is the Reference to $srcdir, for the >>> current >>> > package and future reference, how do you fix it? >>> >>> The fix for the $srcdir issue depends on the nature of the issue. Not >>> very >>> helpful, I know. Have a look in the ml archives for a discussion of this >>> issue, it took place not so long ago and was started by me. There >>> you'll find >>> enough information to be able to do the same check that makepkg does so >>> you >>> can find *exactly* why it complains. >>> >>> If I find the time to take a closer look myself, is there a PKGBUILD >>> available >>> already that I can use? Where? >>> >>> /M >>> >>> -- >>> Magnus Therning (OpenPGP: 0xAB4DFBA4) >>> magnus＠therning．org Jabber: magnus＠therning．org >>> http://therning.org/magnus identi.ca|twitter: magthe >>> >>> If you would like to, http://aur.archlinux.org/packages.php?ID=22993 I >> will check out the archives. Thanks >> P.S. I searched Google last night and somebody stated to do something like >> "grep -R $srcdir $pkgdir" >> > > I used Google to search the ML with your email and name and subjects(not > all in one sentence) $srcdir, references, and cmake, though I couldn't find > it > Though I just found in another mailing-list about the issue. The ML stated to do grep -R "(pwd)/src" pkg/ in the directory where the PKGBUILD is at. I did that and grep returned nothing. So maybe my package is alright?
