Comment 23 for bug 1485199

Vladimir Zhbanov schreef op wo 07-10-2015 om 11:56 [+0000]:
> Hi Richard,
> Have you actually installed gschem before running? That is, have
> you done 'sudo make install && sudo ldconfig' after 'make'? (See
> bug #1492599). In the case if you don't want to clutter your
> working installation just use the '--prefix' option.

I did 'make install', but not 'ldconfig' -- that last one is new for me.
But shouldn't the compiled executable in de geda-gaf/gschem/src behave
exactly like a fully installed version? Because that executable did
start properly, without the guile error messages.

Here goes once more:

        ~> git pull -> OK
        ~> sudo apt-get remove geda-gschem -> OK
        ~> ./configure --prefix=/tmp/gEDA --without-libstroke
        ...
        configure: error: python headers not found
        configure: error: ./configure failed for xorn

Interesting, I can't remember having seen this one before. But OK:

        ~> sudo apt-get install python2.7-dev
        ~> ./configure --prefix=/tmp/gEDA --without-libstroke -> OK now
        ~> make -> OK
        ~> sudo make install -> OK
        ~> sudo ldconfig -> OK
        ~> /tmp/gEDA/bin/gschem -> gschem starts without error messages

But no, nothing has changed. There is still the window
resizing/redrawing bug, the extreme CPU usage, and the weird PDF export
behaviour. And as usual, all these issues go away by closing either the
status window, the sidebar, or both.

But tonight, I get a chance to install yet another machine with Mint 17.
I'll select the English language from the onset, and see what that
brings. If gschem doesn't misbehave there, I'll do a full machine
reinstall with Dutch, and try again. I'll let you know how this works
out.

Best regards,

Richard Rasker