On 8/14/20 1:37 PM, Richard Shaw wrote:
On Fri, Aug 14, 2020 at 7:12 AM Rich Mattes <richmattes@xxxxxxxxx
<mailto:richmattes@xxxxxxxxx>> wrote:
On Fri, Aug 14, 2020, 7:37 AM Richard Shaw <hobbes1069@xxxxxxxxx
<mailto:hobbes1069@xxxxxxxxx>> wrote:
I'm getting consistent differences across at least two versions
of zipios and the offending arches seem to always be s390x and
ppc64le.
BuildError: The following noarch package built differently on
different architectures: zipios-doc-2.2.1.0-5.fc33.noarch.rpm
rpmdiff output was:
removed
/usr/share/doc/zipios/html/dir_0f7abfb91da657dcb27dff31b827312f.html
removed
/usr/share/doc/zipios/html/dir_32504400af4b8c553a85c61a7ef01dea.html
added
/usr/share/doc/zipios/html/dir_8f6b9ad7431774f92e3ec3efe35ac7da.html
added
/usr/share/doc/zipios/html/dir_dd208edd458824e9eaf902c6da16200d.html
zipios 2.2.5.0
https://koji.fedoraproject.org/koji/taskinfo?taskID=49057750
zipios 2.2.1.0
https://koji.fedoraproject.org/koji/taskinfo?taskID=48597282
Is this likely a big vs little endian thing?
Is it a CMake package? The vpath_builddir that is now used for out
of source builds is different for each architecture. If that
directory is included in the doxygen processing paths you'll get
this error.
Yes, but why is doxygen using that to generate a directory name? Bah...
I worked around this in a few of my packages by adding the cmake
build directory to the EXCLUDE list in the doxyfile.
I added a patch to the doxy.in <http://doxy.in> file and it seemed to
get rid of one of the directory problems, but not both...
https://koji.fedoraproject.org/koji/taskinfo?taskID=49250574
Patch:
$ cat zipios-doxygen.patch
Index: doc/zipios.doxy.in <http://zipios.doxy.in>
===================================================================
--- Zipios/doc.orig/zipios.doxy.in <http://zipios.doxy.in>
+++ Zipios/doc/zipios.doxy.in <http://zipios.doxy.in>
@@ -152,7 +152,7 @@ FULL_PATH_NAMES = YES
# will be relative from the directory where doxygen is started.
# This tag requires that the tag FULL_PATH_NAMES is set to YES.
-STRIP_FROM_PATH = @CMAKE_CURRENT_SOURCE_DIR@
+STRIP_FROM_PATH = @CMAKE_CURRENT_BINARY_DIR@
# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part
of the
# path mentioned in the documentation of a class, which tells the
reader which
I downloaded the i686-generated doc package,
dir_dd208edd458824e9eaf902c6da16200d.html is the directory that contains
zipios-config.h. That file is generated from a template by CMake, and
is located in the root of the build folder (which is now
%{_vpath_builddir}. So it's going to be different on every arch. I'm
also seeing the file path to zipios-config.h that includes the
%{_vpath_builddir} folder in the some of the images generated for the
dependency graphs.
Your above patch is filtering out CMAKE_CURRENT_BINARY_DIR, which I
think points the doc/ subdirectory of the build tree, since the doxyfile
is configured in the doc/CMakeLists.txt, not the root CMakeLists.txt.
Perhaps try using @PROJECT_BINARY_DIR@ instead.
Is it possible to override %{_vpath_builddir} to just be "build" on all
architectures (e.g. "%global _vpath_builddir build" at the top of a spec?)
Rich
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
