Yocto build fails to fetch sources for libtalloc, how to fix that? - meta-raspberrypi

I'm trying to build Yocto for Raspberrypi2, with qt5-image, and it gives me some build errors, most I have been able to resolve with:
bitbake -c cleansstate libname
bitbake libnam
but it failts in:
WARNING: libtalloc-2.1.8-r0 do_fetch: Failed........
......
code 4, output:
--2017-02-04 01:09:20-- http://samba.org/ftp/talloc/talloc-2.1.8.tar.gz
Resolving samba.org (samba.org)... 144.76.82.156, 2a01:4f8:192:486::443:2
Connecting to samba.org (samba.org)|144.76.82.156|:80... failed: Connection refused.
Connecting to samba.org (samba.org)|2a01:4f8:192:486::443:2|:80... failed: Network is unreachable.
How can i fix that?
I am new in Building custom image using Yocto for raspberrypi. Any your suggest is important form me.
Thank you in advance

Related

How to fix "vagrant up" errors when trying to set up Trellis?

I've been trying to set up a Trellis local WordPress dev environment from the Roots stack. I did all the steps from the docs, have the recommended folder structure, downloaded all the dependencies, but I still get a few errors.
First I get some errors and warnings when I use "yarn" in my theme folder, as suggested here. They say to use the CLI from my host instead of Vagrant box, that's just the MacBook's terminal right? Or do I need a CLI from VirtualBox?
The second error happens when trying to call "vagrant up", and this is one that I can paste here as it's a bit more concise.
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["hostonlyif", "create"]
Stderr: 0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to create the host-only adapter
VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage: error: Context: "RTEXITCODE handleCreate(HandlerArg *)" at line 95 of file VBoxManageHostonly.cpp
After Googling this I got a lot of outdated suggestions to check my PATH and restart the VirtualBox, but these I tried and didn't help. I hope someone can help me set this up, thanks. :)

Corda 4.3 compilation issues

Trying to compile Corda from scratch. I cloned version 4.3 from Github. Details and error codes below.I am using Oracle java version 1.8. I have asked this question on slack as well but didn't find anyone who has faced this issue before.
Task :node-api-tests:test
net.corda.nodeapitests.internal.crypto.X509UtilitiesTest > create valid server certificate chain FAILED
java.security.cert.CertificateException at X509UtilitiesTest.kt:166
net.corda.nodeapitests.internal.crypto.X509UtilitiesTest > create valid self-signed CA certificate FAILED
java.security.cert.CertificateException at X509UtilitiesTest.kt:131
46 tests completed, 2 failed
Task :node-api-tests:test FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ‘:node-api-tests:test’.
So it looks like you're trying to build Corda's source code. Most of the time you really won't need to do this. I'd recommend instead just taking a look at the Corda samples as they use gradle which will download the jars and compile the samples for you.
Here's a link to some of those sample repo's so you can try building off of them.
https://github.com/corda/samples-kotlin
https://github.com/corda/samples-java
All of them compile and run the same way so it shouldn't be too difficult to get running.
./gradlew deployNodes
and then
./build/nodes/runnodes

Facing issue while building Corda Version 1

I am getting below error while building Corda Version 1 (branch name - release-V1)
Task :core:test
net.corda.core.flows.ContractUpgradeFlowTest > 2 parties contract upgrade using RPC FAILED
java.util.concurrent.TimeoutException at ContractUpgradeFlowTest.kt:123
329 tests completed, 1 failed
FAILURE: Build failed with an exception.
Please help...
You can build the project without running the tests by using the command ./gradlew build -x test or gradlew.bat build -x test.
The integration tests can occasionally time-out, so I wouldn't be concerned by this issue. We are working to fix this.
In general, you shouldn't need to build Corda itself. The binaries for release-V1 are published to Maven, so will be downloaded automatically. You should probably work from the templates:
https://github.com/corda/cordapp-template-java
https://github.com/corda/cordapp-template-kotlin

basic_client which is built with Makefile BusAttachment::Connect failed

I just built standard core 15.09a on linux and run sample apps basic_client.
This one built by scons.
bin/samples/basic_client works fine.
However, I built cpp/samples/basic/basic_client with Makefile.
It does not work. It shows an error
"0.232 ****** ERROR ALLJOYN external ...e/src/BusAttachment.cc:560 | BusAttachment::Connect failed: ER_OS_ERROR
BusAttachment::Connect('') failed.".
So, I launched the bin/allhoyn-daemon, then no error occurred.
What is difference between scon and Makefile version?
Additionally, where can I get the information of application under the bin directory?
I searched the web-site of AllSeen and couldn't find any info.
As i know, the error that you got when build with Makefile happens because basic_client hasn't alljoyn router inside, with scons it runs fine because it compiles with BR=on and some flags:
-lajrouter -lBundledRouter.o -lssl -lcrypto
For more infomation, visit: here

New Static Library has build error "libtool exited with code 1"

I created a new static library in my iOS project and now I'm getting the build error
Command /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/libtool failed with exit code 1
How do I go about debugging this?
To see the actual output and not just the error message, try building your target or scheme with xcodebuild from command line.
I had a problem with the same error message. In my case, I couldn't build for the simulator, but it worked find when building for the device. The output from xcodebuild confirmed that Xcode could not set the proper architecture to build for the simulator.
Long story short, it turned out that one build setting was corrupted. The Mach-O Type setting in the Linking category was set to Relocatable Object File for some reason. I switched it back to Static Library and the error disappeared.

Resources