Welcome to the forum. Your post is still flagged as "This post has NOT been
accepted by the mailing list yet", so nobody gets it unless they look.
You need to subscribe to the mailing list
http://forum.openscad.org/mailing_list/MailingListOptions.jtp?forum=1 ,
and CLICK THE LINK in the registration email.
I've quoted your post for the linux guru's to ponder...
tm_cad wrote
Hello.
Downloaded the nightly, several times, and re-ran the wiki manual
instructions for building on Linux (Debian). Re-built everything
including openscad_deps. No errors and the binary is produced but when
run it segfaults immediately showing libQtGui.so.4.8.6 as the likely
candidate for the problem. I see references to Qt5 in the compiling
output but I'm at a loss to find a way keep it all at v4 or 5. A search
on the error comes up in google but nothing helpful, so far. Here it is:
[404912.575116] openscad[3851]: segfault at 7fbb58f73550 ip
00007fbb569eecdc sp 00007ffc788d9e50 error 7 in
libQtGui.so.4.8.6[7fbb5683a000+aa3000]
Suggestions, please.
thanks,
tjm
Admin - PM me if you need anything, or if I've done something stupid...
Unless specifically shown otherwise above, my contribution is in the Public Domain; to the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. Obviously inclusion of works of previous authors is not included in the above.
View this message in context: http://forum.openscad.org/Starting-here-with-compile-problem-tp20613p20622.html
Sent from the OpenSCAD mailing list archive at Nabble.com.
Downloaded the nightly, several times, and re-ran the wiki manual
instructions for building on Linux (Debian). Re-built everything
including openscad_deps. No errors and the binary is produced but when
run it segfaults immediately showing libQtGui.so.4.8.6 as the likely
candidate for the problem. I see references to Qt5 in the compiling
output but I'm at a loss to find a way keep it all at v4 or 5. A search
on the error comes up in google but nothing helpful, so far. Here it is:
This sounds like the binary is linked against both Qt4 and Qt5.
That's always going to crash. You can verify this by running
ldd ../path/to/openscad
The main question is where this is coming from. One common case
we saw in the past was linking against the wrong libqscintilla
(e.g. building OpenSCAD against Qt5 but linking the Qt4 qscintilla)
CGAL also has some Qt extensions, so it could also come from
there, although I never had that on Debian.
ciao,
Torsten.