Skip to content

Compile core against GLIBC < 2.18 #128

@naraesk

Description

@naraesk

I used this version on Arch Linux:
https://github.com/turtl/desktop/releases/download/v0.7.0-rc3/turtl-linux64.tar.bz2

$ sudo ./install.sh 
Copying Turtl to install directory (/opt/turtl)...
find: paths must precede expression: chmod
Usage: find [-H] [-L] [-P] [-Olevel] [-D help|tree|search|stat|rates|opt|exec] [path...] [expression]
find: paths must precede expression: chmod
Usage: find [-H] [-L] [-P] [-Olevel] [-D help|tree|search|stat|rates|opt|exec] [path...] [expression]
chmod: cannot access 'turtl-bin': No such file or directory
chmod: cannot access 'lib/*': No such file or directory
chmod: cannot access 'chromedriver': No such file or directory
chmod: cannot access 'nw': No such file or directory
chmod: cannot access 'payload': No such file or directory
chmod: cannot access 'nacl*': No such file or directory
chmod: cannot access 'pnacl/*nexe': No such file or directory
All done! Turtl has been installed in /opt/turtl/. To run:
  /opt/turtl/turtl

To uninstall, run:
  ./install.sh uninstall

Well, script says installation has been successful and /opt/turtl has been created and has files in it. But was it really successful? When running /opt/turtl/turtl I just get a white screen, the same as posted by Marrie on twitter: https://twitter.com/turtlapp/status/1025839719706284032

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions