https://bugzilla.redhat.com/show_bug.cgi?id=1403600



--- Comment #9 from Simone Caronni <[email protected]> ---
While building, I see lots of messages like this one:

-- Set runtime path of
"/builddir/build/BUILDROOT/YafaRay-3.2.0-0.2.20170212git.fc25.x86_64/usr/lib/libyafaray_v3_core.so"
to "$ORIGIN/:$ORIGIN/../:$ORIGIN/../lib/"

Runtime path is not allowed in Fedora, you might want to set one of these (I'm
looking at the CMake files):

CMAKE_SKIP_INSTALL_RPATH:BOOL=NO
CMAKE_SKIP_RPATH:BOOL=NO

And messages like this one:

extracting debug info from
/builddir/build/BUILDROOT/YafaRay-3.2.0-0.2.20170212git.fc25.x86_64/usr/bin/yafaray-xml
readelf: Error: the dynamic segment offset + size exceeds the size of the file

It seems there are problems when creating the debuginfo packages, maybe the
build is already doing something to the binaries.

- Stripping
- Using different build flags
- Not building with debug symbols

Maybe you should enable verbose building, see if the correct C/CXXFLAGS are
applied, and see if the debug symbols are being built. Then play with the CMake
options (I see some DEBUG flags in CMakeLists.txt).

Also, the build stops with the following:

+ /usr/lib/rpm/brp-python-bytecompile /usr/bin/python 1
Compiling
/builddir/build/BUILDROOT/YafaRay-3.2.0-0.2.20170212git.fc25.x86_64/usr/share/blender/2.78/scripts/addons/yafaray/ot/yafaray_presets.py
...
  File "/usr/share/blender/2.78/scripts/addons/yafaray/ot/yafaray_presets.py",
line 341
    class Yafaray_Menu(StructRNA, _GenericUI, metaclass=RNAMeta):  # Yafaray's
own Preset Menu drawing: search method for files changed
                                                       ^
SyntaxError: invalid syntax
RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.07Lyfo (%install)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to