On Mon, Jun 17, 2019 at 05:25:56PM +0200, Matthias Schoepfer wrote:
Is there a smart, recommended way to deal with device specific data (i.e.
serial number, credentials for backend access, you name it), that is specific
for *one* device, and hence does not belong into the rootfs. I know, that t
Hi,
I can run following code in Ubuntu to print out the host address, but
I could not get host address (empty) in Yoctor imx6 build. That
function is POSIX compatible, what I could be missing?
struct sockaddr *addr; /* input */
socklen_t addrlen; /* input */
char hbuf[NI_MAXHOST];
if
Hi,
i was using some simple recipes for kernel modules since rocko branch
successfully with AUTOREV and a release branch in my local gitlab
instance (over ssh). I was upgrading to thud these days, and now I'm
triggering some FetchErrors in recipes which are using AUTOREV.
My recipe looks like this
Hi all.
I'm trying to compile kivy inside yocto for a 586 board.
The compilation fails because the i586-cc uses /usr/include and
/usr/local/include paths as INCLUDEDIR (togheter with others paths)
How can avoid this?
I need /usr/include o /usr/local/include for other apps, but I don't
lik
The problem is that kivy is ignoring all of the attempts at telling it
to build in a sysroot and *still* looking in /usr. This is a clear
cut bug in the kivy build system, so you'll have to look at that and
see how to fix it.
Ross
On Mon, 24 Jun 2019 at 18:32, Mauro Ziliani wrote:
>
> Hi all.
>
Hi,
I’m currently working to remove all GPLv3 packages included in my image.
I was using the license manifest file to list the remaining GPLv3 packages to
remove.
While I was trying to remove gdbm, I ecountered some native dependencies.
When I looked at the license.manifest file, gdbm was stil
All,
The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:
https://wiki.yoctoproject.org/wiki/Bug_Triage#N
The image manifest lists what is being *distributed* so doesn't
include native dependencies.
Ross
On Mon, 24 Jun 2019 at 19:50, wrote:
>
> Hi,
> I’m currently working to remove all GPLv3 packages included in my image.
> I was using the license manifest file to list the remaining GPLv3 packages t
I am using an upstream repo with a mix of line endings.
In my recipe, I'm applying a patch with normalized line endings, as our meta
layer repo has a .gitattributes with "text=auto" set.
The patch is failing due to "different line endings".
Can the git fetcher be configured to normalize line
On Sun, 2019-06-23 at 16:15 +0300, Adi Malca wrote:
> Hello,
>
> I'm looking for the current official OPKG spec with spelling and case
> sensitive.
> For example:
> Package:
> Version:
> Description:
> Section:
> Priority:
> Maintainer:
> License:
> Architecture:
> OE:
> Homepage:
> Depen
10 matches
Mail list logo
