I'm not sure, but would suspect some change to the cmake input files.
I know I've seen both of those formats over time, but I admit I've
never paid attention to what might cause seeing one format or the
other. However, it looks to me like the longer (non tabular) version
has more detaile
It failed when I ran cmake. I never ran make after the failure when I was
compiling manually.
During all of this testing I compiled from the 5.0.1 and the 5.0.2 tar
files. cmake gives a nice summary table when it's done (Configure results
(user options):) and 5.0.2 does not. See the end of the out
The build option that is not supported is doing the build right in the
top source dir, called an "in source" build. Having the build dir
below that or outside that are both OK as far as I can tell. Both are
called "out of source builds" or something like that. If you build
from tar or cl
I was just reconciling my investment account (confirming number of
shares held) and my statement shows a number of shares of a stock which
did not appear in the investments list for that account. I went back
to the ledger, and found the buy shares transaction, which shows a
balance of the
I agree, something appears to have changed in the most recent version of
cmake.
My build directory has always been added to the source directory. I think
you've questioned that before but Thomas is the one that told me to do it
that way and he came to the rescue and said it's fine and I think it's
On 2018.11.12 16:27, Jack wrote:
OK, I've now been able to duplicate it - it does NOT happen if the
build directory is not under the source directory. It does happen if
the build directory is under the source directory. I still haven't
figured out exactly what is failing, but I finally do
OK, I've now been able to duplicate it - it does NOT happen if the
build directory is not under the source directory. It does happen if
the build directory is under the source directory. I still haven't
figured out exactly what is failing, but I finally do see the relevant
files left unde
I figured it out. After trying many manual and script based builds I
started to see a pattern. It only failed to build when it was in the
directory that my script created with a date/time stamp. I've been using
this script for 10+ years without a problem. The download directory names
looked like th
https://bugs.kde.org/show_bug.cgi?id=398957
Bug Janitor Service changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=384062
Bug Janitor Service changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=397180
Bug Janitor Service changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=395965
Bug Janitor Service changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=344625
Bug Janitor Service changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINF
https://bugs.kde.org/show_bug.cgi?id=370227
Bug Janitor Service changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
14 matches
Mail list logo
