On 2018.11.07 19:22, Brendan Coupe wrote:
weboob errors seem to be unfixable in Fedora. I think they have been
around for a while, I found them in previous requests for help. I
don' think they have anything to do with the compile failing. not
sure if they cause any of the weird behavior I was seeing. I will try
to resurrect an old F28 system. I'm hoping the repos have 5.0.2 soon
since I'm currently running 5.0.1 and dealing with old problems that
have been fixed.
I agree weboob is not relevant here.
Is this the detection program you are talking about:
cmake/modules/FindLibical.cmake
No, the .cmake program tells cmake where to look for stuff, and how to
set various variables used later in the cmake run. To actually check,
cmake creates a .c program (using hints and info from the .cmake file,
and then tries to compile and link it. (Some checks might be done with
pkg_config) Normally that fails if libical isn't found, or isn't a
high enough version, for example. Your error says " Unable to compile
or run the libical version detection program." which seems like a
different sort of problem. I would look through the cmake --help
output to see what parameters might provide additional details about
what is actually failing.
Line 75 is the source of the message.
gcc.x86_64 8.2.1-4.fc29
@updates
gcc-c++.x86_64 8.2.1-4.fc29
@updates
gcc-gdb-plugin.x86_64 8.2.1-4.fc29
@updates
libgcc.x86_64 8.2.1-4.fc29
@updates
This, however, might be the issue. I'll have to try installing gcc 8
and see how it works for me. As a temporary fix, you might try using
gcc 7.
Jack
----
Brendan Coupe
On Wed, Nov 7, 2018 at 4:47 PM Jack <ostrof...@users.sourceforge.net>
wrote:
>
> Hello Brendan,
>
> On 2018.11.07 18:17, Brendan Coupe wrote:
> > I have been compiling from source for 10+ years. I had been able
to
> > compile both the master branch and the 5.0 branch on my Fedora 28
> > system until a month or so ago. I was having some weird behavior
in
> > KMM5 that was not affecting a clean Fedora 28 test VM running KMM
> > from the repos so I decided to build a new clean Fedora 29 system.
> It may be worth checking the release notes for Fedora 29 to see what
> changed, and if anything looks possibly relevant.
>
> > I also upgraded the old system from Fedora 28 to 29. Both systems
> > fail at the same point while compiling from the master and 5.0
> > branches:
> It certainly sounds like some difference between 28 and 29 is behind
> the failure.
>
> > -- Found LibOfx:
> > -- Performing Test LIBOFX_HAVE_CLIENTUID
> > -- Performing Test LIBOFX_HAVE_CLIENTUID - Success
> > -- Found PythonInterp: /usr/bin/python2 (found suitable version
> > "2.7.15", minimum required is "2.6")
> > -- Found PythonLibs: /usr/lib64/libpython2.7.so (found suitable
> > version "2.7.15", minimum required is "2.7.15")
> > -- Could NOT find PY_weboob (missing: PY_WEBOOB)
> I'm assuming this is not an issue for you.
> > CMake Error at cmake/modules/FindLibical.cmake:75 (message):
> > Unable to compile or run the libical version detection program.
> This does seem odd. It appears not even getting to the point of
> actually checking for an installed libical.
> > Call Stack (most recent call first):
> > CMakeLists.txt:242 (find_package)
> At the point of failure, check in the build directory. Often you
can
> find the libical version detection program (I've forgotten whether
it
> leaves the .c program around, and see if configure.log (or something
> like it) might have a more detailed reason for the failure to
compile
> that .c program.
>
> Not sure if it might be relevant, but what version of gcc are you
> using, both in F28 and in F29?
> >
> > -- Configuring incomplete, errors occurred!
> > ========================================
> >
> > libical appears to be installed:
> >
> >
> > dnf list installed | grep libical
> > libical.x86_64
3.0.3-7.fc29
> > @fedora
> > libical-devel.x86_64
3.0.3-7.fc29
> > @fedora
> >
> > Any ideas?
> >
> > Thanks,
> >
> > ----
> > Brendan Coupe
> Jack
