From: Erwin Rol <mailinglists@erwinrol.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] ptxdist chrpath
Date: Wed, 17 Feb 2016 09:07:32 +0100 [thread overview]
Message-ID: <56C42A44.8030905@erwinrol.com> (raw)
Hey all,
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 ?
- Erwin
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2016-02-17 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 8:07 Erwin Rol [this message]
2016-02-18 8:18 ` Michael Olbrich
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=56C42A44.8030905@erwinrol.com \
--to=mailinglists@erwinrol.com \
--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