Re: Strange rpath issue with F-16 and F-17
Kevin, On Sat, 2011-09-10 at 02:19 +0200, Kevin Kofler wrote: > Tadej Janež wrote: > > What has changed between F-15 and F-16 so that "-rpath,/usr/lib64" gets > > appended to g++ options? > > Looks like a regression somewhere, probably in sip (which also contains some > build-system-type stuff). Something needs fixing for multilib. thanks for the tip! > > What is the best way to fix this? > > I'd start by filing a bug against sip in Fedora Bugzilla. I'll do that. Regards, Tadej -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Strange rpath issue with F-16 and F-17
Tadej Janež wrote: > What has changed between F-15 and F-16 so that "-rpath,/usr/lib64" gets > appended to g++ options? Looks like a regression somewhere, probably in sip (which also contains some build-system-type stuff). Something needs fixing for multilib. > What is the best way to fix this? I'd start by filing a bug against sip in Fedora Bugzilla. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Strange rpath issue with F-16 and F-17
Hi, I just noticed a strange rpath issue with my PyQwt package. Building the latest git version on F-16 and F-17 results in "-rpath,/usr/lib64" being appended to the g++ compiler options. Build logs of scratch builds are here: https://koji.fedoraproject.org/koji/getfile?taskID=3332309&name=build.log https://koji.fedoraproject.org/koji/getfile?taskID=3332685&name=build.log However, building the latest git version on F-15 doesn't exhibit this problem. See build log: https://koji.fedoraproject.org/koji/getfile?taskID=3332430&name=build.log What has changed between F-15 and F-16 so that "-rpath,/usr/lib64" gets appended to g++ options? What is the best way to fix this? Regards, Tadej -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
