From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] ptxdist chrpath
Date: Thu, 18 Feb 2016 09:18:00 +0100 [thread overview]
Message-ID: <20160218081800.GG4567@pengutronix.de> (raw)
In-Reply-To: <56C42A44.8030905@erwinrol.com>
On Wed, Feb 17, 2016 at 09:07:32AM +0100, Erwin Rol wrote:
> qt5 (not just my 5.5.1 version, but also the one in ptxdist master) use
> chrpath in the qt5.make file;
>
> @chrpath -d $(QT5_PKGDIR)/usr/lib/qt5/libexec/QtWebProcess
>
> Is that really supposed to work ? I get the following error (shortened
> the paths for readability);
>
> [erwin@eir rootfs]$ chrpath -d
> ..../platform-Seco_T30/packages/qt-everywhere-opensource-src-5.5.1/usr/lib/qt5/libexec/QtWebProcess
>
>
> `.../platform-Seco_T30/packages/qt-everywhere-opensource-src-5.5.1/usr/lib/qt5/libexec/QtWebProcess'
> probably isn't a 64-bit LSB-first ELF file.
> elf_open: Exec format error
>
> The ptxdist verion platform-Seco_T30/sysroot-host/bin/chrpath gives the
> same error.
>
> Not so strange because the QtWebProcess is an ARM binary and not a x64
> binary like the host.
>
> Shouldn't there be a cross-chrpath version of chrpath ?
The latest version of host-chrpath should be able to handle different
architectures. I think "select HOST_CHRPATH" is missing in qt5.in. Can you
check if that helps?
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-02-18 8:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 8:07 Erwin Rol
2016-02-18 8:18 ` Michael Olbrich [this message]
2016-02-18 9:39 ` Erwin Rol
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=20160218081800.GG4567@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox