Hi,
Check your /usr/lib/libc.so in SDK’s target rootfs.
Last time I experienced this problem /usr/lib/libc.so script contained absolute
paths to ld-linux-armhf.so and real libc.so.
Changing these paths to relative fixes the problem. Unfortunately, I do not
have the common fix for this.
Regards,
Hi all,
I'm trying to build a distribution that has multiple partitions. The
desiderata is something like:
- rootfs.ubifs mounted on /
- data.ubifs mounted on /data
- opt.ubifs mounted on /opt
I was wondering if there is a standard way to achieve the goal. I see that
there is a tool called wic,
All,
The triage team meets weekly and does its best to handle the bugs reported
into the Bugzilla. The number of people attending that meeting has fallen,
as have the number of people available to help fix bugs. One of the things
we hear users report is they don't know how to help. We (the tria
All,
Just a reminder we will hold the monthly Yocto Project Technical Meeting at
8am PST tomorrow. (3/5)
Yocto Project Technical Team Meeting: We encourage people attending the
meeting to logon and announce themselves on the Yocto Project IRC chancel
during the meeting (optional):
Yocto
Hi,
I have an systemd recipe to start an application as a service, i have
included an service file.
Now I am looking for an solution to be able to set settings in the service
file from Yocto variables, i have found recipes that use python to build
files during build.
What is best practice for thi
On 03/05/2019 05:46 AM, Jonas Andersson wrote:
Hi,
I have an systemd recipe to start an application as a service, i have
included an service file.
Now I am looking for an solution to be able to set settings in the
service file from Yocto variables, i have found recipes that use
python to buil
Thanks for the tip, it is a bit sleeker than pulling in an python script.
Den tis 5 mars 2019 kl 02:05 skrev ChenQi :
> On 03/05/2019 05:46 AM, Jonas Andersson wrote:
>
> Hi,
>
> I have an systemd recipe to start an application as a service, i have
> included an service file.
> Now I am looking f
Hi All,
Recently I'm dealing with issue from which some discussion raises.
I'd like to ask why update-alternatives from opkg-utils chooses /usr/lib
to hold its alternatives database?
I looked into debian, its update-alternatives chooses /var/lib by default.
Is there some design consideration? O