> On Feb 12, 2017, at 12:14 PM, Carsten Rinke wrote:
>
> Hi Frank,
>
> thanks for the hint - that did the trick.
>
> The change was introduced with
> commit f54fc2ff11d4fe8a1b415081fb45f39fd73ba703
> Author: Robert Fewell <14ubo...@gmail.com>
> Date: Mon Aug 1 12:45:35
Hi Carsten,
Am 12.02.2017 um 21:14 schrieb Carsten Rinke:
> Hi Frank,
>
> thanks for the hint - that did the trick.
>
> The change was introduced with
> commit f54fc2ff11d4fe8a1b415081fb45f39fd73ba703
> Author: Robert Fewell <14ubo...@gmail.com>
> Date: Mon Aug 1 12:45:35 2016 +0100
> Commit:
Hi Frank,
thanks for the hint - that did the trick.
The change was introduced with
commit f54fc2ff11d4fe8a1b415081fb45f39fd73ba703
Author: Robert Fewell <14ubo...@gmail.com>
Date: Mon Aug 1 12:45:35 2016 +0100
Commit: Geert Janssens (Di 13 Sep 2016
20:57:14 CEST)
Hi Carsten,
It seems to link against an old library (2.6.13), in which
`gnc_recn_cell_set_read_only' did not exist.
As I am no linker expert, I would suggest to search for outdated gnc
libraries, either from a previous build or provided by your distribution.
So first clean your install dirs. If
Update:
I made a new clone from git hub -> no success, same error message
I checked out 2.6.14 -> no success, same error message
I checked out 2.6.13 -> success
What is so surprising about it: 2.6.14 once worked, I have a build done
on 20th Sep 2016 based on 2.6.14
Kind regards,
Carsten