We have moved to a new Sailfish OS Forum. Please start new discussions there.
0

Dependency libc.so.6 [answered]

asked 2015-10-02 12:10:05 +0300

Daeto gravatar image

updated 2015-10-03 12:08:29 +0300

What I did not compile everything does not run on Jolla libc.so.6 (GLIBC_2.0) needed for sailfish-utilities-0.0.0-1.arv7hl ibc.so.6 (GLIBC_2.1.3) needed for sailfish-utilities-0.0.0-1.arv7hl I compile the program in the latest version MerSDK included in SDK 1509 What am i doing wrong?

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by JSEHV
close date 2016-02-01 19:19:19.396066

Comments

The problem remains in the new version SDK 15.10

Daeto ( 2015-10-10 19:50:36 +0300 )edit

@Deato And in version 15.11?

JSEHV ( 2016-02-01 18:14:55 +0300 )edit

@JSE Fixed :3

Daeto ( 2016-02-01 19:00:48 +0300 )edit

2 Answers

Sort by » oldest newest most voted
0

answered 2015-10-02 18:18:07 +0300

x86 binary by accident? clean source tree

edit flag offensive delete publish link more

Comments

Excuse me, what do you suggest?

Daeto ( 2015-10-03 00:38:58 +0300 )edit

Clean and build again.

tortoisedoc ( 2015-10-10 20:12:09 +0300 )edit

Please give me a terminal command. It dont know it.

Daeto ( 2015-10-10 20:13:35 +0300 )edit

If what you want to do is to connect to the mer virtual machine and compile by hand, then do:

  • ssh to the mer virtual machine ssh -p 2222 -i /opt/SailfishOS/vmshare/ssh/private_keys/engine/mersdk mersdk@localhost (depend where you've installed the SDK);
  • then you can see your disk in ~/share/ ;
  • copy your sources somewhere, like in /home/deploy ;
  • (cross-) compile with mb2 -t SailfishOS-armv7hl -s yourfile.spec build.
Damien Caliste ( 2015-10-10 22:16:29 +0300 )edit

mb2 -t SailfishOS-armv7hl -s rpm/sailfish-office.spec usage: mb2 [-t <target>] [-s <specfile>] [-d <device>] [-p <projectdir>] [-f <folder>] [-i] [-P] [-x] build [-d] [-j <n>] [<args>] | qmake [<args>] | make [<args>] | ssh <args> install [<args>] | installdeps <args> | rpm [<args>] | deploy <args> run <args> mb2 --version mb2 --help</args></args></args></args></args></args></args></args></args></n></folder></projectdir></device></specfile></target>

Are you sure?

Daeto ( 2015-10-11 01:01:53 +0300 )edit
0

answered 2015-10-16 17:39:29 +0300

Daeto gravatar image

I kind of found a solution:

Building projects with mb2 leaves temporary makefiles and object files across the project directory. Currently recommended whey to do a clean build is call "git clean -fx", but that will also a lot unrelated files. Support for cleaning the builds ("mb2 -t target clean" like "mb2 -t target build") _and_ for doing shadow builds is needed.

Clean builds are especially important for multi-device development, building for Jolla 1 armv7hl and Jolla Tablet i486. Without clean environment the builds with different architecture fail due to processor specific Makefile and object file declarations.

https://bugs.merproject.org/show_bug.cgi?id=1373

edit flag offensive delete publish link more

Question tools

Follow
2 followers

Stats

Asked: 2015-10-02 12:10:05 +0300

Seen: 760 times

Last updated: Oct 16 '15