<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small;color:rgb(7,55,99)">I'm not sure I explained what I've tried well enough for you to understand. While I normally use compile and install scripts that I wrote a long time ago (used with cvs and svn) I tried compiling from the official tar file for the recently released 5.0.2. It worked fine on both my older upgraded (F28 to F29) and on my new clean F29 install.</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small;color:rgb(7,55,99)"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small;color:rgb(7,55,99)">I think this means my systems are fine.</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small;color:rgb(7,55,99)"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small;color:rgb(7,55,99)">I just manually downloaded both the master and 5.0 branches from the KMM git web site. Both compile fine. When I run the git clone command that is in my script and then run cmake, it fails just like I mentioned in my original email. Except for how I download the source code, I'm running the exact same steps that I use for the manually downloaded zip versions of KMM (5.0.2 release, 5.0 branch & master branch) and they all succeed.</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small;color:rgb(7,55,99)"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small;color:rgb(7,55,99)">When I compare the size of the source code directories, all of the zip files result in about 21k of source files. The git downloaded folder is about 70k. I suspect git is the problem and it may not be related to F29 since I started having problems compiling from source several weeks before I upgraded to F29. There is a .git directory in the git clone directory that is about 49k so it's probably the difference.</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small;color:rgb(7,55,99)"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small;color:rgb(7,55,99)">The git command that worked until 4 to 6 weeks ago is:</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small;color:rgb(7,55,99)"><br></div><div class="gmail_default"><font color="#073763" face="monospace, monospace" size="1">git clone git://<a href="http://anongit.kde.org/kmymoney">anongit.kde.org/kmymoney</a> $BRANCH $KMMDIR</font><br></div><div class="gmail_default"><font color="#073763" face="monospace, monospace" size="1"><br></font></div><div class="gmail_default"><font color="#073763" face="monospace, monospace" size="1">Is this correct?</font></div><div><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><font color="#073763" face="monospace, monospace" size="1"><br></font></div><div dir="ltr"><font color="#073763" face="monospace, monospace" size="1">----<br>Brendan Coupe</font><br></div></div></div></div></div></div></div></div></div><br></div></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Sat, Nov 10, 2018 at 3:44 PM Jack <<a href="mailto:ostroffjh@users.sourceforge.net">ostroffjh@users.sourceforge.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 2018.11.10 13:35, Brendan Coupe wrote:<br>
> I downloaded the source for 5.0.2 and compiled it without any <br>
> problems. I<br>
> tried the 5.0 and master branches again and they failed on iCal again.<br>
> Seems that there is something off with the source on git???<br>
I doubt there is actually anything "wrong." I suspect some bad <br>
interaction caused by F29 using a newer version of some tool. Again - <br>
right after you get the failure, have you checked the files and <br>
directory I suggested? I'll also try compiling from git head with gcc <br>
8.<br>
<br>
> <br>
> ----<br>
> Brendan Coupe<br>
> <br>
> <br>
> On Thu, Nov 8, 2018 at 11:44 AM Jack <<a href="mailto:ostroffjh@users.sourceforge.net" target="_blank">ostroffjh@users.sourceforge.net</a>><br>
> wrote:<br>
> <br>
> > I am able to run cmake (3.11.4) with gcc 8.2.0, with either make or<br>
> > ninja, with no errors. In your build directory, is there anything<br>
> > useful in CMakeFiles/CMakeOutput.log or CMakeError.log? Also look <br>
> in<br>
> > CMakeTmp/<br>
> ><br>
> > Another possible approach: cmake --all-other-parameters<br>
> > --trace-source=/path/to/source/cmake/modules/FindLinical.cmake<br>
> > --debug-trycompile /path/to/source<br>
> > Then see if anything useful shows up in the above places.<br>
> ><br>
> > On 2018.11.07 20:29, Brendan Coupe wrote:<br>
> > > Fedora got 5.0.1 to compile so there must be some hope:-)<br>
> > ><br>
> > > I added the --debug-output option to cmake. The output from just <br>
> after<br>
> > > the weboob errors are copied below:<br>
> > ><br>
> > ><br>
> > <br>
> ===========================================================================<br>
> > ><br>
> > > CMake Warning (dev) at cmake/modules/FindLibical.cmake:59 <br>
> (try_run):<br>
> > > Policy CMP0066 is not set: Honor per-config flags in <br>
> try_compile()<br>
> > > source-file signature. Run "cmake --help-policy CMP0066" for <br>
> policy<br>
> > > details. Use the cmake_policy command to set the policy and<br>
> > > suppress this<br>
> > > warning.<br>
> > ><br>
> > > For compatibility with older versions of CMake, try_compile is <br>
> not<br>
> > > honoring<br>
> > > caller config-specific compiler flags (e.g. <br>
> CMAKE_C_FLAGS_DEBUG)<br>
> > > in the<br>
> > > test project.<br>
> > > Call Stack (most recent call first):<br>
> > > CMakeLists.txt:242 (find_package)<br>
> > > This warning is for project developers. Use -Wno-dev to suppress <br>
> it.<br>
> > ><br>
> > > Called from: [2]<br>
> > ><br>
> > <br>
> /usr/local/src/kmm/kmymoney-5.0-2018.11.07-18:23:12/cmake/modules/FindLibical.cmake<br>
> > > [1]<br>
> > > /usr/local/src/kmm/kmymoney-5.0-2018.11.07-18:23:12/CMakeLists.txt<br>
> > > CMake Warning (dev) at cmake/modules/FindLibical.cmake:59 <br>
> (try_run):<br>
> > > Policy CMP0056 is not set: Honor link flags in try_compile()<br>
> > > source-file<br>
> > > signature. Run "cmake --help-policy CMP0056" for policy <br>
> details.<br>
> > > Use the<br>
> > > cmake_policy command to set the policy and suppress this <br>
> warning.<br>
> > ><br>
> > > For compatibility with older versions of CMake, try_compile is <br>
> not<br>
> > > honoring<br>
> > > caller link flags (e.g. CMAKE_EXE_LINKER_FLAGS) in the test<br>
> > > project.<br>
> > > Call Stack (most recent call first):<br>
> > > CMakeLists.txt:242 (find_package)<br>
> > > This warning is for project developers. Use -Wno-dev to suppress <br>
> it.<br>
> > ><br>
> > > Called from: [2]<br>
> > ><br>
> > <br>
> /usr/local/src/kmm/kmymoney-5.0-2018.11.07-18:23:12/cmake/modules/FindLibical.cmake<br>
> > > [1]<br>
> > > /usr/local/src/kmm/kmymoney-5.0-2018.11.07-18:23:12/CMakeLists.txt<br>
> > > CMake Warning (dev) at cmake/modules/FindLibical.cmake:59 <br>
> (try_run):<br>
> > > Policy CMP0067 is not set: Honor language standard in <br>
> try_compile()<br>
> > > source-file signature. Run "cmake --help-policy CMP0067" for <br>
> policy<br>
> > > details. Use the cmake_policy command to set the policy and<br>
> > > suppress this<br>
> > > warning.<br>
> > ><br>
> > > For compatibility with older versions of CMake, try_compile is <br>
> not<br>
> > > honoring<br>
> > > language standard variables in the test project:<br>
> > ><br>
> > > CMAKE_CXX_STANDARD<br>
> > > CMAKE_CXX_STANDARD_REQUIRED<br>
> > > CMAKE_CXX_EXTENSIONS<br>
> > ><br>
> > > Call Stack (most recent call first):<br>
> > > CMakeLists.txt:242 (find_package)<br>
> > > This warning is for project developers. Use -Wno-dev to suppress <br>
> it.<br>
> > ><br>
> > > Called from: [2]<br>
> > ><br>
> > <br>
> /usr/local/src/kmm/kmymoney-5.0-2018.11.07-18:23:12/cmake/modules/FindLibical.cmake<br>
> > > [1]<br>
> > > /usr/local/src/kmm/kmymoney-5.0-2018.11.07-18:23:12/CMakeLists.txt<br>
> > > CMake Error at cmake/modules/FindLibical.cmake:75 (message):<br>
> > > Unable to compile or run the libical version detection program.<br>
> > > Call Stack (most recent call first):<br>
> > > CMakeLists.txt:242 (find_package)<br>
> > ><br>
> > ><br>
> > > Called from: [2]<br>
> > ><br>
> > <br>
> /usr/local/src/kmm/kmymoney-5.0-2018.11.07-18:23:12/cmake/modules/FindLibical.cmake<br>
> > > [1]<br>
> > > /usr/local/src/kmm/kmymoney-5.0-2018.11.07-18:23:12/CMakeLists.txt<br>
> > > -- Configuring incomplete, errors occurred!<br>
> > > See also<br>
> > ><br>
> > <br>
> "/usr/local/src/kmm/kmymoney-5.0-2018.11.07-18:23:12/build/CMakeFiles/CMakeOutput.log".<br>
> > > See also<br>
> > ><br>
> > <br>
> "/usr/local/src/kmm/kmymoney-5.0-2018.11.07-18:23:12/build/CMakeFiles/CMakeError.log".<br>
> > > make: *** No targets specified and no makefile found. Stop.<br>
> > ><br>
> > > =============================================================<br>
> > ><br>
> > > [1]<br>
> > > /usr/local/src/kmm/kmymoney-5.0-2018.11.07-18:23:12/CMakeLists.txt<br>
> > > -- Found PythonLibs: //lib64/<a href="http://libpython2.7.so" rel="noreferrer" target="_blank">libpython2.7.so</a> (found suitable <br>
> version<br>
> > > "2.7.15", minimum required is "2.7.15")<br>
> > > Called from: [4] <br>
> /usr/share/cmake/Modules/FindPackageMessage.cmake<br>
> > > [3]<br>
> > > /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake<br>
> > > [2] /usr/share/cmake/Modules/FindPythonLibs.cmake<br>
> > > [1]<br>
> > > /usr/local/src/kmm/kmymoney-5.0-2018.11.07-18:23:12/CMakeLists.txt<br>
> > > -- Could NOT find PY_weboob (missing: PY_WEBOOB)<br>
> > > Called from: [4]<br>
> > > /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake<br>
> > > [3]<br>
> > > /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake<br>
> > > [2]<br>
> > ><br>
> > <br>
> /usr/local/src/kmm/kmymoney-5.0-2018.11.07-18:23:12/cmake/modules/FindPythonModule.cmake<br>
> > > [1]<br>
> > > /usr/local/src/kmm/kmymoney-5.0-2018.11.07-18:23:12/CMakeLists.txt<br>
> > > -- Configuring incomplete, errors occurred!<br>
> > ><br>
> > ><br>
> > > ----<br>
> > > Brendan Coupe<br>
> > > On Wed, Nov 7, 2018 at 5:42 PM Jack <br>
> <<a href="mailto:ostroffjh@users.sourceforge.net" target="_blank">ostroffjh@users.sourceforge.net</a>><br>
> > > wrote:<br>
> > > ><br>
> > > > On 2018.11.07 19:22, Brendan Coupe wrote:<br>
> > > > > weboob errors seem to be unfixable in Fedora. I think they <br>
> have<br>
> > > been<br>
> > > > > around for a while, I found them in previous requests for <br>
> help. I<br>
> > > > > don' think they have anything to do with the compile failing. <br>
> not<br>
> > > > > sure if they cause any of the weird behavior I was seeing. I <br>
> will<br>
> > > try<br>
> > > > > to resurrect an old F28 system. I'm hoping the repos have <br>
> 5.0.2<br>
> > > soon<br>
> > > > > since I'm currently running 5.0.1 and dealing with old <br>
> problems<br>
> > > that<br>
> > > > > have been fixed.<br>
> > > > I agree weboob is not relevant here.<br>
> > > > ><br>
> > > > > Is this the detection program you are talking about:<br>
> > > > > cmake/modules/FindLibical.cmake<br>
> > > > No, the .cmake program tells cmake where to look for stuff, and <br>
> how<br>
> > > to<br>
> > > > set various variables used later in the cmake run. To actually<br>
> > > check,<br>
> > > > cmake creates a .c program (using hints and info from the .cmake<br>
> > > file,<br>
> > > > and then tries to compile and link it. (Some checks might be <br>
> done<br>
> > > with<br>
> > > > pkg_config) Normally that fails if libical isn't found, or <br>
> isn't a<br>
> > > > high enough version, for example. Your error says " Unable to<br>
> > > compile<br>
> > > > or run the libical version detection program." which seems like <br>
> a<br>
> > > > different sort of problem. I would look through the cmake <br>
> --help<br>
> > > > output to see what parameters might provide additional details <br>
> about<br>
> > > > what is actually failing.<br>
> > > > ><br>
> > > > > Line 75 is the source of the message.<br>
> > > > > gcc.x86_64 8.2.1-4.fc29<br>
> > > > > @updates<br>
> > > > > gcc-c++.x86_64 8.2.1-4.fc29<br>
> > > > > @updates<br>
> > > > > gcc-gdb-plugin.x86_64 8.2.1-4.fc29<br>
> > > > > @updates<br>
> > > > > libgcc.x86_64 8.2.1-4.fc29<br>
> > > > > @updates<br>
> > > > This, however, might be the issue. I'll have to try installing <br>
> gcc<br>
> > > 8<br>
> > > > and see how it works for me. As a temporary fix, you might try<br>
> > > using<br>
> > > > gcc 7.<br>
> > > ><br>
> > > > Jack<br>
> > > > ><br>
> > > > > ----<br>
> > > > > Brendan Coupe<br>
> > > > > On Wed, Nov 7, 2018 at 4:47 PM Jack<br>
> > > <<a href="mailto:ostroffjh@users.sourceforge.net" target="_blank">ostroffjh@users.sourceforge.net</a>><br>
> > > > > wrote:<br>
> > > > > ><br>
> > > > > > Hello Brendan,<br>
> > > > > ><br>
> > > > > > On 2018.11.07 18:17, Brendan Coupe wrote:<br>
> > > > > > > I have been compiling from source for 10+ years. I had <br>
> been<br>
> > > able<br>
> > > > > to<br>
> > > > > > > compile both the master branch and the 5.0 branch on my<br>
> > > Fedora 28<br>
> > > > > > > system until a month or so ago. I was having some weird<br>
> > > behavior<br>
> > > > > in<br>
> > > > > > > KMM5 that was not affecting a clean Fedora 28 test VM <br>
> running<br>
> > > KMM<br>
> > > > > > > from the repos so I decided to build a new clean Fedora 29<br>
> > > system.<br>
> > > > > > It may be worth checking the release notes for Fedora 29 to <br>
> see<br>
> > > what<br>
> > > > > > changed, and if anything looks possibly relevant.<br>
> > > > > ><br>
> > > > > > > I also upgraded the old system from Fedora 28 to 29. Both<br>
> > > systems<br>
> > > > > > > fail at the same point while compiling from the master <br>
> and 5.0<br>
> > > > > > > branches:<br>
> > > > > > It certainly sounds like some difference between 28 and 29 <br>
> is<br>
> > > behind<br>
> > > > > > the failure.<br>
> > > > > ><br>
> > > > > > > -- Found LibOfx:<br>
> > > > > > > -- Performing Test LIBOFX_HAVE_CLIENTUID<br>
> > > > > > > -- Performing Test LIBOFX_HAVE_CLIENTUID - Success<br>
> > > > > > > -- Found PythonInterp: /usr/bin/python2 (found suitable<br>
> > > version<br>
> > > > > > > "2.7.15", minimum required is "2.6")<br>
> > > > > > > -- Found PythonLibs: /usr/lib64/<a href="http://libpython2.7.so" rel="noreferrer" target="_blank">libpython2.7.so</a> (found<br>
> > > suitable<br>
> > > > > > > version "2.7.15", minimum required is "2.7.15")<br>
> > > > > > > -- Could NOT find PY_weboob (missing: PY_WEBOOB)<br>
> > > > > > I'm assuming this is not an issue for you.<br>
> > > > > > > CMake Error at cmake/modules/FindLibical.cmake:75 <br>
> (message):<br>
> > > > > > > Unable to compile or run the libical version detection<br>
> > > program.<br>
> > > > > > This does seem odd. It appears not even getting to the <br>
> point of<br>
> > > > > > actually checking for an installed libical.<br>
> > > > > > > Call Stack (most recent call first):<br>
> > > > > > > CMakeLists.txt:242 (find_package)<br>
> > > > > > At the point of failure, check in the build directory. <br>
> Often<br>
> > > you<br>
> > > > > can<br>
> > > > > > find the libical version detection program (I've forgotten<br>
> > > whether<br>
> > > > > it<br>
> > > > > > leaves the .c program around, and see if configure.log (or<br>
> > > something<br>
> > > > > > like it) might have a more detailed reason for the failure <br>
> to<br>
> > > > > compile<br>
> > > > > > that .c program.<br>
> > > > > ><br>
> > > > > > Not sure if it might be relevant, but what version of gcc <br>
> are<br>
> > > you<br>
> > > > > > using, both in F28 and in F29?<br>
> > > > > > ><br>
> > > > > > > -- Configuring incomplete, errors occurred!<br>
> > > > > > > ========================================<br>
> > > > > > ><br>
> > > > > > > libical appears to be installed:<br>
> > > > > > ><br>
> > > > > > ><br>
> > > > > > > dnf list installed | grep libical<br>
> > > > > > > libical.x86_64<br>
> > > > > 3.0.3-7.fc29<br>
> > > > > > > @fedora<br>
> > > > > > > libical-devel.x86_64<br>
> > > > > 3.0.3-7.fc29<br>
> > > > > > > @fedora<br>
> > > > > > ><br>
> > > > > > > Any ideas?<br>
> > > > > > ><br>
> > > > > > > Thanks,<br>
> > > > > > ><br>
> > > > > > > ----<br>
> > > > > > > Brendan Coupe<br>
> > > > > > Jack</blockquote></div>