Startup error - no stackfile to run

Moderators: Klaus, FourthWorld, heatherlaine, kevinmiller, LCMark

slowmaker
Posts: 32
Joined: Fri Feb 08, 2019 1:53 pm

Startup error - no stackfile to run

Post by slowmaker » Sun Mar 01, 2020 4:35 pm

I'm running LXDE 16.04 (one of the many ubuntu derivatives), 64-bit.
Attempting to build the community version from source.

So, at the console, I do this:

Code: Select all

make config-linux
then I do this:

Code: Select all

make -k

then quite a lot of things happen for quite a long time, many orange warnings flash by, but the make appears to be happy in the end. At least, there is no 'ERROR!' message or anything that would lead me to believe something is genuinely awry.

So I cd into the linux-x86_64-bin folder generated by the above, and try this:

Code: Select all

standalone-community
And here's what I get:

Code: Select all

[7876] MCU_library_load libglib-2.0.so.0 -> libglib-2.0.so.0
[7876] MCU_library_load libglib-2.0.so.0 -> libglib-2.0.so.0
[7876] MCU_library_load libgobject-2.0.so.0 -> libgobject-2.0.so.0
[7876] MCU_library_load libpango-1.0.so.0 -> libpango-1.0.so.0
[7876] MCU_library_load libpangoft2-1.0.so.0 -> libpangoft2-1.0.so.0
[7876] MCU_library_load libX11.so.6 -> libX11.so.6
[7876] MCU_library_load libgobject-2.0.so.0 -> libgobject-2.0.so.0
[7876] MCU_library_load libgdk-x11-2.0.so.0 -> libgdk-x11-2.0.so.0
[7876] MCU_library_load libX11.so.6 -> libX11.so.6
[7876] MCU_library_load libgobject-2.0.so.0 -> libgobject-2.0.so.0
[7876] MCU_library_load libgdk-x11-2.0.so.0 -> libgdk-x11-2.0.so.0
[7876] MCU_library_load libgdk_pixbuf-2.0.so.0 -> libgdk_pixbuf-2.0.so.0
[7876] MCU_library_load libcairo.so.2 -> libcairo.so.2
[7876] MCU_library_load libgtk-x11-2.0.so.0 -> libgtk-x11-2.0.so.0
[7876] MCU_library_load libgtk-x11-2.0.so.0 -> libgtk-x11-2.0.so.0
[7876] MCU_library_load libgtk-x11-2.0.so.0 -> libgtk-x11-2.0.so.0
[7876] MCU_library_load libgtk-x11-2.0.so.0 -> libgtk-x11-2.0.so.0
[7876] MCU_library_load libgnomevfs-2.so.0 -> libgnomevfs-2.so.0
[7876] MCU_library_load libgnome-2.so.0 -> libgnome-2.so.0
Gtk-Message: Failed to load module "gail"
Gtk-Message: Failed to load module "atk-bridge"
[7876] MCU_library_load libpango-1.0.so.0 -> libpango-1.0.so.0
[7876] MCU_library_load libpangocairo-1.0.so.0 -> libpangocairo-1.0.so.0
[7876] MCU_library_load libpangoft2-1.0.so.0 -> libpangoft2-1.0.so.0
Startup error - no stackfile to run
I suspect I am blind-spotting some docs that would tell me what silly mistake I am making, but for the life of me I can't think of what it might be. I thought the stackfile for the ui was built in to the standalone; that may be wrong assumption number 1, not sure yet.

I'm currently going back and reading through mode_standalone.cpp - where the message appears to originate - to determine which assumption of mine is off base, but I'm hoping the above error will ring a bell for someone who can set me straight.

Any suggestions?
The important thing is not to stop questioning. Curiosity has its own reason for existence. - Albert Einstein (LIFE Magazine (1955 may 2), p64)

LCMark
Livecode Staff Member
Livecode Staff Member
Posts: 1094
Joined: Thu Apr 11, 2013 11:27 am

Re: Startup error - no stackfile to run

Post by LCMark » Sun Mar 01, 2020 4:48 pm

@slowmaker: The `standalone-community` executable requires to either have had a stackfile embedded, or a command-line argument passed which is a stackfile to run (as it is what the IDE uses to make a standalone). If you are wanting to run the ide then its the `LiveCode-Community` executable you want to run (or similar - I'm not in front a Linux box right now to be able to check the exact name!).

bogs
Posts: 4790
Joined: Sat Feb 25, 2017 10:45 pm

Re: Startup error - no stackfile to run

Post by bogs » Sun Mar 01, 2020 7:16 pm

This one...
aPic_LcExe.png
A community builds a home...
Image

slowmaker
Posts: 32
Joined: Fri Feb 08, 2019 1:53 pm

Re: Startup error - no stackfile to run

Post by slowmaker » Sun Mar 01, 2020 8:50 pm

Thanks, guys; the exact name that builds on mine is 'LiveCode-Community'.

Running that moved the ball a bit further along; now it produces the following output, which ends with 'Segmentation fault (core dumped)', right after the MCU_library_load attempt on dbsqlite.

Code: Select all

[4868] MCU_library_load libglib-2.0.so.0 -> libglib-2.0.so.0
[4868] MCU_library_load libglib-2.0.so.0 -> libglib-2.0.so.0
[4868] MCU_library_load libgobject-2.0.so.0 -> libgobject-2.0.so.0
[4868] MCU_library_load libpango-1.0.so.0 -> libpango-1.0.so.0
[4868] MCU_library_load libpangoft2-1.0.so.0 -> libpangoft2-1.0.so.0
[4868] MCU_library_load libX11.so.6 -> libX11.so.6
[4868] MCU_library_load libgobject-2.0.so.0 -> libgobject-2.0.so.0
[4868] MCU_library_load libgdk-x11-2.0.so.0 -> libgdk-x11-2.0.so.0
[4868] MCU_library_load libX11.so.6 -> libX11.so.6
[4868] MCU_library_load libgobject-2.0.so.0 -> libgobject-2.0.so.0
[4868] MCU_library_load libgdk-x11-2.0.so.0 -> libgdk-x11-2.0.so.0
[4868] MCU_library_load libgdk_pixbuf-2.0.so.0 -> libgdk_pixbuf-2.0.so.0
[4868] MCU_library_load libcairo.so.2 -> libcairo.so.2
[4868] MCU_library_load libgtk-x11-2.0.so.0 -> libgtk-x11-2.0.so.0
[4868] MCU_library_load libgtk-x11-2.0.so.0 -> libgtk-x11-2.0.so.0
[4868] MCU_library_load libgtk-x11-2.0.so.0 -> libgtk-x11-2.0.so.0
[4868] MCU_library_load libgtk-x11-2.0.so.0 -> libgtk-x11-2.0.so.0
[4868] MCU_library_load libgnomevfs-2.so.0 -> libgnomevfs-2.so.0
[4868] MCU_library_load libgnome-2.so.0 -> libgnome-2.so.0
Gtk-Message: Failed to load module "gail"
Gtk-Message: Failed to load module "atk-bridge"
[4868] MCU_library_load libpango-1.0.so.0 -> libpango-1.0.so.0
[4868] MCU_library_load libpangocairo-1.0.so.0 -> libpangocairo-1.0.so.0
[4868] MCU_library_load libpangoft2-1.0.so.0 -> libpangoft2-1.0.so.0
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-revxml.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-revxml.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revbrowser.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revbrowser.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revsecurity.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revsecurity.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbsqlite.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbsqlite.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/dbsqlite.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/dbsqlite.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revandroid.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revandroid.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revxml.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revxml.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-revdb.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-revdb.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-revzip.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-revzip.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbpostgresql.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbpostgresql.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/dbodbc.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/dbodbc.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revpdfprinter.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revpdfprinter.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revzip.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revzip.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbodbc.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbodbc.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/dbmysql.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/dbmysql.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbmysql.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbmysql.so
[4868] dlopen failed /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbmysql.so: undefined symbol: SSL_connect
[4868] MCU_library_load failed for /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbmysql.so
[4868] MCU_library_load .//home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbmysql.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbmysql.so
[4868] dlopen failed /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbmysql.so: cannot open shared object file: No such file or directory
[4868] MCU_library_load failed for /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbmysql.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revdb.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revdb.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/dbpostgresql.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/dbpostgresql.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-revxml.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-revxml.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revbrowser.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revbrowser.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revsecurity.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revsecurity.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbsqlite.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbsqlite.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/dbsqlite.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/dbsqlite.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revandroid.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revandroid.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revxml.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revxml.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-revdb.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-revdb.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-revzip.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-revzip.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbpostgresql.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbpostgresql.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/dbodbc.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/dbodbc.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revpdfprinter.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revpdfprinter.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revzip.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revzip.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbodbc.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbodbc.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/dbmysql.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/dbmysql.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbmysql.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbmysql.so
[4868] dlopen failed /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbmysql.so: undefined symbol: SSL_connect
[4868] MCU_library_load failed for /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbmysql.so
[4868] MCU_library_load .//home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbmysql.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbmysql.so
[4868] dlopen failed /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbmysql.so: cannot open shared object file: No such file or directory
[4868] MCU_library_load failed for /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/server-dbmysql.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revdb.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/revdb.so
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/dbpostgresql.so -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/dbpostgresql.so
[4868] MCU_library_load libpango-1.0.so.0 -> libpango-1.0.so.0
[4868] MCU_library_load libpangocairo-1.0.so.0 -> libpangocairo-1.0.so.0
[4868] MCU_library_load libpangoft2-1.0.so.0 -> libpangoft2-1.0.so.0
[4868] MCU_library_load libpango-1.0.so.0 -> libpango-1.0.so.0
[4868] MCU_library_load libpangocairo-1.0.so.0 -> libpangocairo-1.0.so.0
[4868] MCU_library_load libpangoft2-1.0.so.0 -> libpangoft2-1.0.so.0
[4868] MCU_library_load libpango-1.0.so.0 -> libpango-1.0.so.0
[4868] MCU_library_load libpangocairo-1.0.so.0 -> libpangocairo-1.0.so.0
[4868] MCU_library_load libpangoft2-1.0.so.0 -> libpangoft2-1.0.so.0
[4868] MCU_library_load libpango-1.0.so.0 -> libpango-1.0.so.0
[4868] MCU_library_load libpangocairo-1.0.so.0 -> libpangocairo-1.0.so.0
[4868] MCU_library_load libpangoft2-1.0.so.0 -> libpangoft2-1.0.so.0
[4868] MCU_library_load libpango-1.0.so.0 -> libpango-1.0.so.0
[4868] MCU_library_load libpangocairo-1.0.so.0 -> libpangocairo-1.0.so.0
[4868] MCU_library_load libpangoft2-1.0.so.0 -> libpangoft2-1.0.so.0
[4868] MCU_library_load libpango-1.0.so.0 -> libpango-1.0.so.0
[4868] MCU_library_load libpangocairo-1.0.so.0 -> libpangocairo-1.0.so.0
[4868] MCU_library_load libpangoft2-1.0.so.0 -> libpangoft2-1.0.so.0
[4868] MCU_library_load libpango-1.0.so.0 -> libpango-1.0.so.0
[4868] MCU_library_load libpangocairo-1.0.so.0 -> libpangocairo-1.0.so.0
[4868] MCU_library_load libpangoft2-1.0.so.0 -> libpangoft2-1.0.so.0
[4868] MCU_library_load libpango-1.0.so.0 -> libpango-1.0.so.0
[4868] MCU_library_load libpangocairo-1.0.so.0 -> libpangocairo-1.0.so.0
[4868] MCU_library_load libpangoft2-1.0.so.0 -> libpangoft2-1.0.so.0
[4868] MCU_library_load libpango-1.0.so.0 -> libpango-1.0.so.0
[4868] MCU_library_load libpangocairo-1.0.so.0 -> libpangocairo-1.0.so.0
[4868] MCU_library_load libpangoft2-1.0.so.0 -> libpangoft2-1.0.so.0
[4868] MCU_library_load libpango-1.0.so.0 -> libpango-1.0.so.0
[4868] MCU_library_load libpangocairo-1.0.so.0 -> libpangocairo-1.0.so.0
[4868] MCU_library_load libpangoft2-1.0.so.0 -> libpangoft2-1.0.so.0
[4868] MCU_library_load libpango-1.0.so.0 -> libpango-1.0.so.0
[4868] MCU_library_load libpangocairo-1.0.so.0 -> libpangocairo-1.0.so.0
[4868] MCU_library_load libpangoft2-1.0.so.0 -> libpangoft2-1.0.so.0
[4868] MCU_library_load libpango-1.0.so.0 -> libpango-1.0.so.0
[4868] MCU_library_load libpangocairo-1.0.so.0 -> libpangocairo-1.0.so.0
[4868] MCU_library_load libpangoft2-1.0.so.0 -> libpangoft2-1.0.so.0
[4868] MCU_library_load libpango-1.0.so.0 -> libpango-1.0.so.0
[4868] MCU_library_load libpangocairo-1.0.so.0 -> libpangocairo-1.0.so.0
[4868] MCU_library_load libpangoft2-1.0.so.0 -> libpangoft2-1.0.so.0
[4868] MCU_library_load libpango-1.0.so.0 -> libpango-1.0.so.0
[4868] MCU_library_load libpangocairo-1.0.so.0 -> libpangocairo-1.0.so.0
[4868] MCU_library_load libpangoft2-1.0.so.0 -> libpangoft2-1.0.so.0
[4868] MCU_library_load libpango-1.0.so.0 -> libpango-1.0.so.0
[4868] MCU_library_load libpangocairo-1.0.so.0 -> libpangocairo-1.0.so.0
[4868] MCU_library_load libpangoft2-1.0.so.0 -> libpangoft2-1.0.so.0
[4868] MCU_library_load libpango-1.0.so.0 -> libpango-1.0.so.0
[4868] MCU_library_load libpangocairo-1.0.so.0 -> libpangocairo-1.0.so.0
[4868] MCU_library_load libpangoft2-1.0.so.0 -> libpangoft2-1.0.so.0
Use of deprecated SAXv1 function setDocumentLocator
[4868] MCU_library_load /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/dbsqlite -> /home/slowmaker/src/livecode/openSourceLC/clone/livecode/linux-x86_64-bin/dbsqlite
Segmentation fault (core dumped)
That path it references doesn't actually exist; there is a dbsqlite.so, but no file just named dbsqlite without extension.

running dmesg right after shows a tad more detail on the fault:

Code: Select all

[ 2931.275546] LiveCode-Commun[4954]: segfault at 41 ip 00007f98b1164d44 sp 00007ffeffab1e20 error 4 in libpthread-2.23.so[7f98b115b000+18000]
I'm going to try this over in a clean vm running lubuntu or some such; I'm not sure this part isn't some oddball issue with my distros installed libraries or some such thing.
The important thing is not to stop questioning. Curiosity has its own reason for existence. - Albert Einstein (LIFE Magazine (1955 may 2), p64)

mwieder
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 3122
Joined: Mon Jan 22, 2007 7:36 am
Location: Berkeley, CA, US
Contact:

Re: Startup error - no stackfile to run

Post by mwieder » Mon Mar 09, 2020 2:56 am

This is the result of the gyp files being based on the obsolete linux distro the team uses.
Here's the pull request to fix that to develop on current distros: https://github.com/livecode/livecode/pull/7127
As I understand things, the pull request won't get merged into the develop branch until the team updates to a current linux distro, and that won't happen until the CEF browser incompatibility gets resolved.

So create a new branch for this patch
Merge the patch branch into your current develop branch
Build locally
Reset the develop branch head afterwards to maintain parity with the github repo

FourthWorld
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 7930
Joined: Sat Apr 08, 2006 7:05 am
Location: Los Angeles
Contact:

Re: Startup error - no stackfile to run

Post by FourthWorld » Mon Mar 09, 2020 4:40 am

mwieder wrote:
Mon Mar 09, 2020 2:56 am
This is the result of the gyp files being based on the obsolete linux distro the team uses.
...
As I understand things, the pull request won't get merged into the develop branch until the team updates to a current linux distro, and that won't happen until the CEF browser incompatibility gets resolved.
To my ignorant ear that sounds incongruous. And to my watchful eye the LC Linux engine hasn't had a working browser widget in years.

Help me understand the connection, please.
Richard Gaskin
Community volunteer LiveCode Community Liaison

LiveCode development, training, and consulting services: Fourth World Systems: http://FourthWorld.com
LiveCode User Group on Facebook : http://FaceBook.com/groups/LiveCodeUsers/

mwieder
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 3122
Joined: Mon Jan 22, 2007 7:36 am
Location: Berkeley, CA, US
Contact:

Re: Startup error - no stackfile to run

Post by mwieder » Mon Mar 09, 2020 5:14 am

Someone from the mothership may step in and correct me, but the way I remember this is:

The currently supported ubuntu linux system is 14.04. That's what the team builds on.
They don't want yet to say they support ubunbu 16 because of the CEF issue and so they're not switching their build machines to anything newer than 14.
Ubuntu 14.04 uses an older version of gcc that has different defaults and the sqlite libraries are built to a different standard. See my PR comment
From my limited understanding of this, it would appear that the team's build server is using a gcc version pre-5.1? I'm currently on 7.4.0. And that this patch instructs the compiler that the dbsqlite libraries are in C++03 ABI rather than C++11?
So upgrading the build server to a newer distro with a newer gcc could mean maintainability problems for the officially supported Ubuntu 14.04.

FourthWorld
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 7930
Joined: Sat Apr 08, 2006 7:05 am
Location: Los Angeles
Contact:

Re: Startup error - no stackfile to run

Post by FourthWorld » Mon Mar 09, 2020 6:32 am

Ubuntu 14.04 reached EOL last year. Please tell me nothing in their build system touches the Internet.
Richard Gaskin
Community volunteer LiveCode Community Liaison

LiveCode development, training, and consulting services: Fourth World Systems: http://FourthWorld.com
LiveCode User Group on Facebook : http://FaceBook.com/groups/LiveCodeUsers/

LCMark
Livecode Staff Member
Livecode Staff Member
Posts: 1094
Joined: Thu Apr 11, 2013 11:27 am

Re: Startup error - no stackfile to run

Post by LCMark » Mon Mar 09, 2020 8:34 am

We don't build on Ubuntu - we build using Debian - the current builders use Debian 8 which has LTS until June of this year (2020). [ There is also a freely available Extended LTS offering - where interested parties contribute to extend this window, with the results freely available to all ].

What we build on has nothing to do with CEF (or Ubuntu for that matter) - the problem is that building executables on newer versions of Linux distributions tends to render them inoperable on older ones at the dyld (dynamic linker) level, and less frequently (because at least it is actually versioned reasonably well) glibc.

bogs
Posts: 4790
Joined: Sat Feb 25, 2017 10:45 pm

Re: Startup error - no stackfile to run

Post by bogs » Mon Mar 09, 2020 9:40 am

LCMark,

I wonder if you can tell me why, if your using Debian 8 as the build base (which I think is a great choice, btw), that Debian isn't the supported platform instead of 'buntu?

This is a question I've asked often and, I thought clearly enough, many times, but have never gotten a coherrent answer on.

If you don't mind, and it isn't a state secret, I'd really love to know. Thanks :D
Image

LCMark
Livecode Staff Member
Livecode Staff Member
Posts: 1094
Joined: Thu Apr 11, 2013 11:27 am

Re: Startup error - no stackfile to run

Post by LCMark » Mon Mar 09, 2020 11:19 am

@bogs: Ubuntu is based on the Debian distribution, but provides a 'single' choice of Desktop (in terms of the collection of things it guarantees to use - i.e. Gnome, GTK etc.). The base debian distribution contains multiple choices of such things (which is why there are various flavors of Ubuntu e.g. Xubuntu / Kubuntu).

Thus we support Debian as a server distribution, but Ubuntu as a desktop distribution (and by extension, Debian as a desktop distribution, assuming you are using the desktop components which Ubuntu uses).

FourthWorld
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 7930
Joined: Sat Apr 08, 2006 7:05 am
Location: Los Angeles
Contact:

Re: Startup error - no stackfile to run

Post by FourthWorld » Mon Mar 09, 2020 5:08 pm

LCMark wrote:
Mon Mar 09, 2020 8:34 am
We don't build on Ubuntu - we build using Debian - the current builders use Debian 8 which has LTS until June of this year (2020). [ There is also a freely available Extended LTS offering - where interested parties contribute to extend this window, with the results freely available to all ].

What we build on has nothing to do with CEF (or Ubuntu for that matter) - the problem is that building executables on newer versions of Linux distributions tends to render them inoperable on older ones at the dyld (dynamic linker) level, and less frequently (because at least it is actually versioned reasonably well) glibc.
Thanks for that background, Mark.

Given the number of years LC/Linux has had no browser widget, if a quicker fix is available for newer distros could we move forward with that? For me it would be handy, better to have a simpler solution that supports newer distros than a more comprehensive fix that's been too expensive to undertake.
Richard Gaskin
Community volunteer LiveCode Community Liaison

LiveCode development, training, and consulting services: Fourth World Systems: http://FourthWorld.com
LiveCode User Group on Facebook : http://FaceBook.com/groups/LiveCodeUsers/

bogs
Posts: 4790
Joined: Sat Feb 25, 2017 10:45 pm

Re: Startup error - no stackfile to run

Post by bogs » Mon Mar 09, 2020 10:42 pm

Thank you for the answer LCMark, I loved gnome 2, but despise 3 -> and eschew it for XFCE, so I guess no gumdrops for me heh.
Image

mwieder
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 3122
Joined: Mon Jan 22, 2007 7:36 am
Location: Berkeley, CA, US
Contact:

Re: Startup error - no stackfile to run

Post by mwieder » Tue Mar 10, 2020 3:16 am

@LCMark- thanks for the correction. So in June are we going to switch to a more recent version of the base distro with an updated gcc and incorporate either my pull request or Ian's version that accomplishes something similar so I can stop having to patch the build system locally? Note that the current stable and recommended version of Debian is 10 ("buster").

<rant1>
Where is the list of supported linux distros? I can't find it on the web site any more nor on github.
</rant1>

<rant2>
The docs for building from source say
It should be possible to build and run LiveCode on any modern Linux desktop distribution.

The x86-64 and x86 Linux build environments used for compiling LiveCode are based on Debian Wheezy.
</rant2>

FourthWorld
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 7930
Joined: Sat Apr 08, 2006 7:05 am
Location: Los Angeles
Contact:

Re: Startup error - no stackfile to run

Post by FourthWorld » Tue Mar 10, 2020 7:01 am

mwieder wrote:
Tue Mar 10, 2020 3:16 am
<rant1>
Where is the list of supported linux distros? I can't find it on the web site any more nor on github.
</rant1>
Isn't that near the top of each of the Release Notes accompanying each version?
Richard Gaskin
Community volunteer LiveCode Community Liaison

LiveCode development, training, and consulting services: Fourth World Systems: http://FourthWorld.com
LiveCode User Group on Facebook : http://FaceBook.com/groups/LiveCodeUsers/

Post Reply

Return to “Engine Contributors”