Chitlesh GOORAH wrote: > On 11/28/06, Rex Dieter < hidden > wrote: >> dunno, will need to see the exact failure, if you could post the tail end >> of the failed build log... > > Here you go, the build log for kdebase4 which failed with rpath=true: > http://tux.u-strasbg.fr/~chit/kdebase4_build.log It was as I suspected: ... + /usr/lib/rpm/check-rpaths /usr/lib/rpm/check-buildroot ******************************************************************************* * * WARNING: 'check-rpaths' detected a broken RPATH and will cause 'rpmbuild' * to fail. To ignore these errors, you can set the '$QA_RPATHS' * environment variable which is a bitmask allowing the values * below. The current value of QA_RPATHS is 0x0000. * * 0x0001 ... standard RPATHs (e.g. /usr/lib); such RPATHs are a minor * issue but are introducing redundant searchpaths without * providing a benefit. They can also cause errors in multilib * environments. * 0x0002 ... invalid RPATHs; these are RPATHs which are neither absolute * nor relative filenames and can therefore be a SECURITY risk ... but that's not specific to mock, it's part of rpmdevtools(?). Anyway, quick-n-dirty fix is to set QA_RPATHS=0x0003; export QA_RPATHS and try again. -- Rex -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
