English

Compiling ends with Error 41

Under Debian 7 the required packages cannot be installed, because the are conflicts with very elementary packages.
But a schroot can be set up an be used for compiling.

schroot.conf:
[ubuntu64]
description=Ubuntu LTE 16 64-bit
type=directory
directory=/opt/ubuntu64
users=corngep
groups=corngep
root-users=corngep
root-groups=corngep
profile=ubuntu64
preserve-environment=true

copyfiles:
/etc/resolv.conf

fstab:
/proc /proc none rw,bind 0 0
/sys /sys none rw,bind 0 0
/dev /dev none rw,bind 0 0
/dev/pts /dev/pts none rw,bind 0 0
/home /home none rw,bind 0 0
/tmp /tmp none rw,bind 0 0

nssdatabases:
passwd
shadow
group
gshadow
services
protocols
networks
hosts

After definition of this schroot a basic system was installed. The latest version of ubuntu, that can be installed with debootstrap, is precise: debootstrap --variant=buildd --arch=amd64 --verbose precise /opt/ubuntu64

With “schroot -c ubuntu64” I am inside the schroot.

vi /etc/apt/sources.list
entries:
deb http://archive.ubuntu.com/ubuntu trusty main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu trusty-updates main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu trusty-backports main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu trusty-proposed main restricted universe multiverse

apt-get update
apt-get upgrade => 92 upgraded, 0 newly installed, 0 to remove and 41 not upgraded.

Now I have an unbuntu 14.04 64 Bit.

apt-get install phablet-tools => 12 upgraded, 394 newly installed, 0 to remove and 29 not upgraded

Errors were encountered while processing:
libpam-systemd:amd64
policykit-1
colord
click-apparmor
upstart-app-launch
upstart-app-launch-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

apt-get install openjdk-7-jdk bison g+±multilib
gcc-multilib git gperf libxml2-utils make
python-networkx zlib1g-dev:i386 zip
=>
The following packages have unmet dependencies:
g+±multilib : Depends: cpp (>= 4:4.8.2-1ubuntu6) but 4:4.6.3-1ubuntu5 is to be installed
Depends: g++ (>= 4:4.8.2-1ubuntu6) but 4:4.6.3-1ubuntu5 is to be installed
Depends: g+±4.8-multilib (>= 4.8.2-5~) but it is not going to be installed
gcc-multilib : Depends: cpp (>= 4:4.8.2-1ubuntu6) but 4:4.6.3-1ubuntu5 is to be installed
Depends: gcc (>= 4:4.8.2-1ubuntu6) but 4:4.6.3-1ubuntu5 is to be installed
Depends: gcc-4.8-multilib (>= 4.8.2-5~) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

apt-get remove gcc cpp g++

apt-get install openjdk-7-jdk bison g+±multilib gcc-multilib git gperf libxml2-utils make python-networkx zlib1g-dev:i386 zip cpp-4.8 gcc g+±4.8 gcc-4.8
=> 9 upgraded, 176 newly installed, 0 to remove and 17 not upgraded.

as normal user:

cd fairphone_os/
wget http://code.fairphone.com/downloads/FP2/blobs/fp2-sibon-16.06.0-blobs.tgz
sh fp2-sibon-16.06.0-blobs.sh
. build/envsetup.sh
choosecombo 1 FP2 2
make -j8

This ends:
make: *** [out/target/common/obj/APPS/FairphoneLauncher3_intermediates/classes-full-debug.jar] Error 41
make: *** Waiting for unfinished jobs…

I have found, that Error 41 means a stack overflow.

Do you have an idea to avoid this?
Is it a good idea to set up a 64-bit schroot? The “host” has 24GB RAM, 2 quad core processors.
Or must I set up a virtual machine with ubuntu? Should this be a 32 or a 64 bit installation?

Thank you for each hint,

Cornelius

I’m compiling android in LXC containers which are basically the same thing you do. Also, I have this Docker image in which compiling images for FP2 works. This is also more similar to your chroot than to a virtual machine.

Thus: I don’t see why you would need to set up a virtual machine.

That said, I don’t know what’s wrong with your setup.

I have installed the (small) docker package. But the usage seems to be different from your version of docker.
/opt/fairphone_os$ docker run -v $PATH_ON_HOST:/opt/fairphone_os/ jftr/fairphone2-build-env
says:
docker - version 1.4
Copyright 2003, Ben Jansens ben@orodu.net

Usage: docker [OPTIONS]

Options:
-help Show this help.
-display DISPLAY The X display to connect to.
-border The width of the border to put around the
system tray icons. Defaults to 1.
-vertical Line up the icons vertically. Defaults to
horizontally.
-wmaker WindowMaker mode. This makes docker a
fixed size (64x64) to appear nicely in
in WindowMaker.
Note: In this mode, you have a fixed
number of icons that docker can hold.
-iconsize SIZE The size (width and height) to display
icons as in the system tray. Defaults to
24.
-color COLOR The background color to use for the tray.
Defaults to whatever color the window
manager specifies.

“docker pull” or “docker run” is not a valid command.

In wich OS do you use docker?

lxc seems to work on my Debian. But I do not have any experience in using lxc. Can you so kind and send me the lines you use to create and configure the container? I would like no to copy the lots of source data, but I prefer to share these files with the host - if possible.

Thank you very much

Cornelius

Dear Franz,
nowI have seen, that the open OS 16.06 is available as a binary. The fastboot method works even with a self compiled build in the phone. Thua I have no need to compile the Os.

Have a great day

Cornelius

1 Like

Good to see that you’ve found a solution that works.

Only for the record: You’ve seemed to have installed the wrong docker. The Debian package docker is not the Docker we are talking about but some kind of desktop dock. I believe the installation under Debian should use sudo apt-get install docker.io (please double check).

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