failure in docker

[meta-rust]

failure in docker

[cardoe]

We use this in a docker container always. Docker isn't the issue here. What's the distro that your container is based on? @derekstraka have we seen something like this? I vaguely remember something like that.

[tekjar]

@cardoe I tried both ubuntu 14.04 & 15.10 containers. (but it works properly outside container on my ubuntu 15.10 machine)

[derekstraka]

@cardoe - we did see an error similar to this. I don't recall if we just removed our SSTATE_DIR and it built or if I added a fix in our fork.

@rt - Any chance you could try https://github.com/starlab-io/meta-rust/ to see if it builds? If it does, that will give us an idea of what may be the underlying issue.

[tekjar]

@derekstraka @cardoe Oh yeah. libterm undefined symbol error is gone with starlab-io/meta-rust (jethro branch). But unfortunately, I'm facing the below error which I previously reported (this was a problem in fido but not jethro)

cargo: /home/build/buildbot/slave-jeth/jeth/main/build/tmp/sysroots/x86_64-linux/usr/bin/cargo
| rustc: /home/build/buildbot/slave-jeth/jeth/main/build/tmp/sysroots/x86_64-linux/usr/bin/arm-poky-linux-gnueabi/rustc
| NOTE: cargo build -v --target arm-poky-linux-gnueabi --release
|     Updating git repository `https://github.com/kteza1/asystemd.rs`
| Unable to update https://github.com/kteza1/asystemd.rs#6c594f2d
| 
| Caused by:
|   failed to clone into: /home/build/buildbot/slave-jeth/jeth/main/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/vcu-cloud-connect/1.0-r0/cargo_home/git/db/asystemd.rs-7b371576c8b86303
| 
| Caused by:
|   [12/-1] Unsupported URL protocol
| WARNING: exit code 101 from a shell command.

[derekstraka]

@kteza1 - Is it safe to assume you are building krogoth or master for your poky version? Or are you using jethro?

[tekjar]

@derekstraka I'm on jethro (2.0.2)

[derekstraka]

@kteza1 - Ok. I've seen the issue before on krogoth, but we haven't yet moved to use that internally.

[tekjar]

@derekstraka Ok. Is it openssl? I'm seeing openssl 1.0.2h being built with starlab-io/meta-rust where as with meta-rust/meta-rust it is 1.0.2b. Maybe I can validate this if I know what is causing libterm issue by using meta-rust/meta-rust just with libterm issue fix

[derekstraka]

@kteza1 - If I had to guess, I would say that there is a race condition on when libgit2-native is getting built causing things to not get built with SSL support. To humor me, you could try a bitbake -c cleansstate libgit2-native cargo-native; and then do the rust build again to see if that fixes it?

[tekjar]

@derekstraka 😸 😈 I think you are right. It worked. I was stuck with this error for quite some time

[derekstraka]

@kteza1 Cool. I can look at adding a bbappend for the DEPENDS as a temp fix, but I'll need to get that solved upstream.

[tekjar]

@derekstraka Awesome. Thanks a lot. What might be the reason for libterm symbol lookup error?

[cardoe]

The libterm issue is still an unknown to me.

[cardoe]

@kteza1 Do you want to try #63 and confirm it resolves the issue for you?

[tekjar]

I'll confirm by tomorrow @cardoe

[tekjar]

@cardoe Seems to be fixed 👍 . I think you've done a lot of clean up. May I know what the problem was?

[cardoe]

@kteza1 It was actually @derekstraka that did the work. I believe it was 7c494d9 that fixed the issue however.