All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch-fe.de>
To: openembedded-devel <openembedded-devel@lists.openembedded.org>,
	Martin Jansa <martin.jansa@gmail.com>,
	Otavio Salvador <otavio@ossystems.com.br>
Subject: [meta-qt5] install problem for qtbase
Date: Fri, 4 Sep 2015 18:14:55 +0200	[thread overview]
Message-ID: <55E9C37F.4010509@dresearch-fe.de> (raw)
In-Reply-To: <55E9C13C.9070308@zone42.org>

We've a big problem building qtbase (from fido branch) for two machines with the same SoC in one workspace.

It seems that the do_install of the run for the second machine (which fails) destroys the image subdirectory totally. :(

Here's what we see after a clean build:

-------------------------------------------------------------------------------------
MACHINE=firstmachine bitbake qtbase

# tree -d -L 3 tmp-glibc/work/cortexa9t2hf-vfp-neon-mx6qdl-angstrom-linux-gnueabi/qtbase/5.4.2+gitAUTOINC+2cb17c1fb9-r0/image/
tmp-glibc/work/cortexa9t2hf-vfp-neon-mx6qdl-angstrom-linux-gnueabi/qtbase/5.4.2+gitAUTOINC+2cb17c1fb9-r0/image/
└── usr
    ├── bin
    │   └── qt5
    ├── include
    │   └── qt5
    ├── lib
    │   ├── cmake
    │   ├── fonts
    │   ├── pkgconfig
    │   └── qt5
    └── share
        ├── doc
        └── qt5

13 directories
# tree -d -L 3 tmp-glibc/work/x86_64-linux/qtbase-native/5.4.2+gitAUTOINC+2cb17c1fb9-r0/image/
tmp-glibc/work/x86_64-linux/qtbase-native/5.4.2+gitAUTOINC+2cb17c1fb9-r0/image/
└── home
    └── sledz
        └── work

3 directories

-------------------------------------------------------------------------------------
MACHINE=secondmachine bitbake qtbase

# tree -d -L 3 tmp-glibc/work/cortexa9t2hf-vfp-neon-mx6qdl-angstrom-linux-gnueabi/qtbase/5.4.2+gitAUTOINC+2cb17c1fb9-r0/image/
tmp-glibc/work/cortexa9t2hf-vfp-neon-mx6qdl-angstrom-linux-gnueabi/qtbase/5.4.2+gitAUTOINC+2cb17c1fb9-r0/image/
├── home
│   └── sledz
│       └── work
└── usr
    ├── bin
    │   └── qt5
    └── lib

7 directories
# tree -d -L 3 tmp-glibc/work/x86_64-linux/qtbase-native/5.4.2+gitAUTOINC+2cb17c1fb9-r0/image/
tmp-glibc/work/x86_64-linux/qtbase-native/5.4.2+gitAUTOINC+2cb17c1fb9-r0/image/
└── home
    └── sledz
        └── work

3 directories

-------------------------------------------------------------------------------------

Additionally after the second run some files are in the wrong subdirectories, e.g. the font files are located in image/usr/lib/ instead of image/usr/lib/fonts.

-- 
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058


       reply	other threads:[~2015-09-04 16:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <55E9C13C.9070308@zone42.org>
2015-09-04 16:14 ` Steffen Sledz [this message]
2015-09-04 17:43 ` [meta-qt5] install problem for qtbase Martin Jansa
2015-09-05  6:49   ` Steffen Sledz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55E9C37F.4010509@dresearch-fe.de \
    --to=sledz@dresearch-fe.de \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.