Installing trouble on Linux

Software
1

Hi everyone

I’m trying to install KiCad on my Linux laptop, a Librem 13 running PureOS (a Debian derivative).

First I tried using the system default “Software” GUI application to install KiCad. The installer ran successfully but when I tried to launch pcbnew, KiCad crashed because of this bug: https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1596403.html

I then tried to build KiCad 5 RC2 from sources, but that failed with ‘Unknown CMake command “_CHECK_SYMBOL_EXISTS”.’, which is discussed here: https://www.mail-archive.com/kicad-developers@lists.launchpad.net/msg29830.html

Responses to both issues suggest that a workaround would be to downgrade some software, but that’s a rabbit hole I’d rather avoid going down. I’m afraid messing with the libraries will break something else…

I just need to design a PCB. What would be the easiest way to get (any version of) KiCad working on my machine? Thanks.

2

You can try Flatpak or Snappy package (from the download page). They both will install some extra infrastructure, probably hundreds of megabytes.

3

2 cents of opinion upon distros…

Currently there are a plethora of magical “ultimate” “modern”
"best build system " for compilation and installation and whatever…

They have been piling up from the latest 10 years… just for record:

  • CMAKE
  • SCONS
  • WAF
  • MESON
  • NINJA
  • ANT
    … the list goes on…

They do a weird mess on any sane system.

GTK3 is latest target while somebody decided that
a “MESON” “NINJA” thing would replace the 30y+ GNU
more than competent and reliable suite.

PERIOD. Nut cranks.
By changing GTK3 WILL CHANGE WxGTK and various others bindings

Just GO SANE - download a fresh GIT/CVS/SUBVERSION/MERCURIAL
whatever the thing…

and RECOMPILE using the LATEST MAGICAL “BUILD thing”
should work … some say that is the BEST…

GNU +30y autoconf MUST BE wrong.

2 cents.

4

Recent Debian and it derivatives have big problems with KiCad because of wxPython and Gtk3

5

Not only DEBIAN and not DEBIAN’s fault.

Since that MESON NINJA thing started A LOT of things just went crazy…
that “MESON” thing relies on Python3 ONLY.

It means that BEFORE anything the whole Python3 MUST BE working
Completely in reverse from that of automake which requires ONLY
GLIBC and standard system base tools.

Someone decided that MESON is “MODERN” ULTIMATE best…
and should be written in Python3.

Results will just got worst and bad things will happen
Much like the non-sense “systemd” thing replacing init.

Some kid thinks that 30/40 years of reliable results are BAD
modern must be better

Paul

6

@PKTKS
You are not adding to finding a solution. (You might even confuse some of the readers) Please do not rant in a thread by others.

2 Likes
7

Not at all. Solution is in the first comment.

SOLUTION: RECOMPILE a fresh version to match YOUR system base.

As the GTK3 bundle got mixed up with some parts done by automake
and some others done by MESON results will vary a lot.

The only way you can match YOUR SYSTEM is recompiling.

** THE PROPER WAY** will be…
hope… that someone with proper vision rollback
GTK3 build system as it was … via GNU automake.

GNU automake covers a WIDE RANGE of *NIX systems.

The cause is more or less ovbious…
There is no way a 3 month or 3 year developed build system
match the 30 years 3000 minds GNU automake.

Happens that now parts of GTK are being built via MESON
while others (like core GLIB) been built via automake.

Things will be messed, “SOLUTION” by recompiling will not
revert things back to proper automake macros

My system is recompiled and works… so far.
Yours should too… as mine.

There is no “receipt” to magically solve this complex issue.
But it is done. Some parts of GTK3 now are ONLY built by MESON.

Paul

8

… and as one more detail …

“MY SOLUTION” when I have found these problems of
incompatible build of parts of GTK3 was radical…

I DOWNGRADED ALL PARTS that moved from automake to MESON
and ditched MESON … parts are built ONLY via automake on all GTK3 core.

ALL PROBLEMS VANISHED.

For how long I will avoid upgrading that parts… I can’t answer.

But I prefer a RELIABLE, ZERO FAULT system than…
a problematic and prone to crash one.

Got it? SOLUTION: (mine) dowgraded ALL MESON based parts
to previous automake ones. RECOMPILED those parts.

and done. Problems vanished.
“the rant part…” the result of almost 15 days lost with that crap. :slight_smile:

Paul

9

I thought that we had fixed that issue but if you are still seeing it, can you please report it over at the bug tracker? https://bugs.launchpad.net/kicad

10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.