Jump to content


Photo

Compile Git for enigma2


  • Please log in to reply
13 replies to this topic

#1 Jagge

  • Member
  • 6 posts

0
Neutral

Posted 14 November 2019 - 14:04

Hi

I'm starting to develop python plugins on the actual hw itself (easier) and would like to install Git on the target machine (Vu+duo2). Since I didn't find git anywhere baked, I decided to bitbake it myself. There were some issues, like patch file no_read_restart_on_eagain.patch which didn't apply anymore. Removed that from the recipe and after that bitbake git worked fine. The package also installed on the machine fine but alas it does not work because of wrong dependency?

 

vuduo2: git

git: /usr/lib/libcrypto.so.1.0.2: version `OPENSSL_1.0.2d' not found (required by git)

 

This is confusing since opkg info git__2.11.1-r0_mips32el.ipk

returns

Package: git
Version: 2.11.1-r0
Depends: libc6 (>= 2.25), libcrypto1.0.2 (>= 1.0.2k), libcurl4 (>= 7.53.1), libexpat1 (>= 2.2.0), libssl1.0.2 (>= 1.0.2k), libz1 (>= 1.2.11)
Status: unknown ok not-installed
Section: console/utils
Architecture: mips32el
Maintainer: OE-Core Developers <openembedded-core@lists.openembedded.org>
Source: git_2.11.1.bb
Description: Distributed version control system
Distributed version control system.

 

On the other hand checking libssl version tells me this:
vuduo2:~$ grep OPENSSL /usr/lib/libssl.so.1.0.2
OPENSSL_cleanse
OPENSSL_DIR_read
OPENSSL_DIR_end
OPENSSL_1.0.0
OPENSSL_1.0.1
OPENSSL_1.0.1d
OPENSSL_1.0.2
OPENSSL_1.0.2g
OPENSSL_DIR_read(&ctx, '
OPENSSL_malloc Error

 

and on the other hand opgk info openssl10 tells me this:
Version: 1.0.2q-r0
Depends: libc6 (>= 2.28), libcrypto1.0.2 (>= 1.0.2q), libssl1.0.2 (>= 1.0.2q), openssl10-conf
Provides: openssl
Status: unknown ok not-installed
Section: libs/network
Architecture: vuduo2
Maintainer: OE-Core Developers <openembedded-core@lists.openembedded.org>
MD5Sum: be7fd6b8109817bf9a24e82d8e9f1491
Size: 151558
Filename: openssl10_1.0.2q-r0_vuduo2.ipk
Source: openssl10_1.0.2q.bb
Description: Secure Socket Layer

 

My question is what dependency now is wrong and where? I should have openssl 1.0.2q installed with same versioned libcrypto and git should need =>1.0.2k. So this should be covered but still when running the binary I get complain from git? that I should have openssl 1.0.2d installed? Grepping libcrypto shows that I have 1.0.2g available. How do I fix this?



Re: Compile Git for enigma2 #2 WanWizard

  • Forum Moderator
    PLi® Core member
  • 49,498 posts

+873
Excellent

Posted 14 November 2019 - 14:13

You could also do it the other way around: mount your development machine on /usr/lib/enigma2, and do everything on your development machine. That is what I do.


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: Compile Git for enigma2 #3 Jagge

  • Member
  • 6 posts

0
Neutral

Posted 14 November 2019 - 14:38

I don't have any compilers or such in the vu+duo2. It would have been easy to compile stuff on the target directly but since there are no tools for it in the current image...

 

Anyway this is also path to learning since I'm not very familiar with bitbake yet.


Edited by Jagge, 14 November 2019 - 14:39.


Re: Compile Git for enigma2 #4 WanWizard

  • Forum Moderator
    PLi® Core member
  • 49,498 posts

+873
Excellent

Posted 14 November 2019 - 14:43

For python you don't need to compile. For the C part, it's useless to try to compile on a box.

 

Our buildservers are Core i7-7700K's with fast SSD's, and they take about 90 minutes to build an image from scratch. Imagine the weak CPU in the box, even if you could get the toolchain installed and working...


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: Compile Git for enigma2 #5 Jagge

  • Member
  • 6 posts

0
Neutral

Posted 14 November 2019 - 14:53

Ah, you mean keep the python files on the pc and mount the pc on the target. I still wouldn't have git on the target tho and I want version control. I already lost many days worth of work because I didn't use version control :( Don't  want to repeat the mistake again.



Re: Compile Git for enigma2 #6 WanWizard

  • Forum Moderator
    PLi® Core member
  • 49,498 posts

+873
Excellent

Posted 14 November 2019 - 15:12

Correct. So you don't need git on the target, yoou need git on your PC, as that is where the source lives.


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: Compile Git for enigma2 #7 betacentauri

  • PLi® Core member
  • 5,597 posts

+254
Excellent

Posted 14 November 2019 - 16:35

Which OpenPLi version is on the box and which branch of the build environment did you use?
Such problems often occur when you use eg 6.1 image and 7.x build environment.
Xtrend ET-9200, ET-8000, ET-10000, OpenPliPC on Ubuntu 12.04

Re: Compile Git for enigma2 #8 Jagge

  • Member
  • 6 posts

0
Neutral

Posted 15 November 2019 - 08:36

I think I have 6. something, But I checked out development branch which probably is bleeding edge. None the less, these should be irrelevant now since all git requirements should be met. So either the requirement is wrong and git 2.11.1 requires exactly openssl 1.0.2d (and not >=1.0.2k as is in the packages) or openssl 1.0.2q is not in fact q version but g version (which is still greater than d). I'm not familiar what that grep /usr/lib/libssl.so.1.0.2 should return, currently it is returning OPENSSL_1.0.2g amongst others whereas opgk list-installed shows that openssl 1.0.2q is installed. I don't know if this is normal? Anyway, I also tried uninstalling openssl 1.0.2q package and installed openssl 1.0.2k (and all its requirements) from the develop branch, i.e. same branch I installed git from in hopes that those would satisfy the gits needs, but the error remains the same, git wants to find OPENSSL 1.0.2d and nothing else I guess.

I try to get understanding what is going on, by installing new packages I learn nothing, but if somebody can point me to right direction, then I'm one stop closer to becoming jedi master :)



Re: Compile Git for enigma2 #9 WanWizard

  • Forum Moderator
    PLi® Core member
  • 49,498 posts

+873
Excellent

Posted 15 November 2019 - 14:01

If you compile a binary that requires openssl, it will compile to whatever is present, if it wants OPENSSL_1.0.2d while you have a different version, you have a compile environment issue somewhere.

 

You'll have to root through the build logs to see what it builds against.


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: Compile Git for enigma2 #10 WanWizard

  • Forum Moderator
    PLi® Core member
  • 49,498 posts

+873
Excellent

Posted 15 November 2019 - 14:09

Current develop doesn't even build git:

ERROR: git-2.11.1-r0 do_patch: Command Error: 'quilt --quiltrc /data/openpli/oe/develop/build/tmp/work/armv7ahf-neon-oe-linux-gnueabi/git/2.11.1-r0/recipe-sysroot-native/etc/quiltrc push' exited with 0  Output:
Applying patch no_read_restart_on_eagain.patch
patching file wrapper.c
Hunk #1 FAILED at 150.
1 out of 1 hunk FAILED -- rejects in file wrapper.c
Patch no_read_restart_on_eagain.patch does not apply (enforce with -f)
ERROR: git-2.11.1-r0 do_patch: Function failed: patch_do_patch

Looks like the patches are out of date...


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: Compile Git for enigma2 #11 WanWizard

  • Forum Moderator
    PLi® Core member
  • 49,498 posts

+873
Excellent

Posted 15 November 2019 - 14:24

Fixed.

root@vuduo4k:~# opkg install git
Installing git (2.11.1) on root
Downloading http://wanwizard.local/feeds/openpli-develop/armv7ahf-neon/git_2.11.1-r0.0_armv7ahf-neon.ipk.
Configuring git.

root@vuduo4k:~# git --version
git version 2.11.1

root@vuduo4k:~# grep OPENSSL /usr/bin/git
OPENSSL_1.0.0

Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: Compile Git for enigma2 #12 Jagge

  • Member
  • 6 posts

0
Neutral

Posted 18 November 2019 - 10:54

Thank you,

 

All I need to do now is understand what you did. By checking the git logs it seems that you only updated openssl to a version 1.0.2r and fixed some dependencies inside and removed the obsolete patch from git recipe which I also had to remove when I built git. What I now don't understand is how this operation magically fixed the git when I rebuilt it? Was the previous openssl 1.0.2q version somehow broken or what? I sure would appreciate explanation please?



Re: Compile Git for enigma2 #13 WanWizard

  • Forum Moderator
    PLi® Core member
  • 49,498 posts

+873
Excellent

Posted 18 November 2019 - 13:50

It was removing the obsolete patch that fixed it. The rest isn't relevant.


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: Compile Git for enigma2 #14 Jagge

  • Member
  • 6 posts

0
Neutral

Posted 22 November 2019 - 06:09

But that's the thing, I did remove the obsolete patch like I mentioned in my first post. It did not help, the OpenSSL version issue surfaced. It was fixed by changing the openSSL version I should think.






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users