>
> 1) on the i586 builds for Fedora 21, OpenSUSE 13.1, openSUSE 13.2, we got
> these:
> -- Installing:
> /home/abuild/rpmbuild/BUILDROOT/oorexx-5.0.svn-52.1.i386/usr/INSTALL_LIB_DIR-NOTFOUND/librxmath.so.5.0.0
> Apparently CMake got confused on which is the correct library directory.
>
Until someone figures out, why Cmake's find_path will return
"INSTALL_LIB_DIR-NOTFOUND" on Ubuntu and other platforms, I've committed a
fallback fix to set INSTALL_LIB_DIR=lib in such a case
Erico, would you wnat to tests this fix on Fedora 21 etc. ?
Erich
On Tue, Jun 21, 2016 at 4:40 PM, Erico Mendonca <[email protected]>
wrote:
> Hello all,
>
> I placed ooRexx 5.0 (from the code-0 branch) up into SUSE's Open Build
> Service, and the report is back.
>
> Please bear with me, as there are quite a few errors/warnings. I don't
> have solutions for them all, and sure would like to hear from all of you. I
> have suggestions that worked for us while packaging ooRexx 4.2.0 that could
> be adopted upstream, but it's your call.
>
> First, check out the project at OBS:
> https://build.opensuse.org/package/show/home:emendonca/oorexx5
>
> Every distro I'm trying to compile ooRexx on (along with its architecture)
> is listed on the right. OBS starts a "clean" VM for each one and tries to
> build the package. Click on each architecture to get the build log, the
> rpmlint report is in the bottom.
>
> Problems worth noting so far:
>
> 1) on the i586 builds for Fedora 21, OpenSUSE 13.1, openSUSE 13.2, we got
> these:
>
> -- Installing:
> /home/abuild/rpmbuild/BUILDROOT/oorexx-5.0.svn-52.1.i386/usr/INSTALL_LIB_DIR-NOTFOUND/librxmath.so.5.0.0
>
> Apparently CMake got confused on which is the correct library directory.
>
> 2) On CentOS 6 and SLE11SP4 for both i586 and x86_64, we got this:
>
> [ 235s] [ 83%] Building CXX object
> CMakeFiles/rexx_exe.dir/utilities/rexx/platform/unix/rexx.cpp.o
> [ 235s] Linking CXX executable bin/rexx
> [ 235s] bin/librexx.so.5.0.0: undefined reference to `RexxString::ch_PLUS'
> [ 235s] bin/librexx.so.5.0.0: undefined reference to
> `MemorySegmentSet::LargeSegmentDeadSpace'
> [ 235s] bin/librexx.so.5.0.0: undefined reference to
> `RexxString::ch_MINUS'
> [ 235s] bin/librexx.so.5.0.0: undefined reference to
> `MemorySegmentSet::SegmentDeadSpace'
> [ 235s] bin/librexx.so.5.0.0: undefined reference to
> `Numerics::FORM_ENGINEERING'
> [ 235s] bin/librexx.so.5.0.0: undefined reference to
> `Numerics::FORM_SCIENTIFIC'
> [ 235s] collect2: ld returned 1 exit status
> [ 235s] make[2]: *** [bin/rexx] Error 1
> [ 235s] make[1]: *** [CMakeFiles/rexx_exe.dir/all] Error 2
> [ 235s] make: *** [all] Error 2
>
> It looks like the make rules got confused and "forgot" to link a couple of
> object files on these distros. Have to dig further for details.
>
> 3) On RHEL 5, RHEL 6, SLE11SP1, SLE11SP2, SLE11SP3, for both i586 and
> x86_64, we got an error related to the CMake version. Can we lower the
> requisite?
>
> CMake Error at CMakeLists.txt:42 (cmake_minimum_required):
> [ 44s] CMake 2.8 or higher is required. You are running version 2.6.4
>
> Check the corresponding logs, each one has a different version of CMake
> available.
>
> 4) On OpenSUSE Factory and openSUSE Factory ARM, there are quite a few
> errors caused by GCC 6.0.
>
> 5) There are no proper systemd files (they weren't there in 4.x either).
> Check our patch in the original ooRexx 4.2.0 package:
> https://build.opensuse.org/package/show/devel:languages:misc/ooRexx
>
> 6) There are files that historically are placed under /usr/bin and
> /usr/share that aren't supposed to be there. See the "oorexx-rpmlintrc"
> file for details on some of these. Some of them are excusable (as you can
> see in my reasons on the comments in this file), some are not.
>
> 7) There are other simple fixable errors, like wrong linefeeds in a few
> .CLS files. We used to do a dos2unix on them, but this could be corrected
> upstream. See the logs, they are marked as warnings only.
>
> 8) There is the problem of placing classes in the binary path. We solved
> this with a patch in 4.2.0 that changes the "class path" (see above). In
> our experience, we have a few thousand machines running it with no issues.
>
>
> This is work in progress, feel free to send suggestions.
>
>
> ------------------------------------------------------------------------------
> Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
> Francisco, CA to explore cutting-edge tech and listen to tech luminaries
> present their vision of the future. This family event has something for
> everyone, including kids. Get more information and register today.
> http://sdm.link/attshape
> _______________________________________________
> Oorexx-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
