From: Rouven Czerwinski <rouven@czerwinskis.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] rpath maxmimum length error
Date: Sun, 14 Apr 2019 09:33:41 +0200 [thread overview]
Message-ID: <877ebx6nxm.fsf@czerwinskis.de> (raw)
Hello,
I'm currently hitting the following error while trying to build
toolchains for Arch Linux:
----------------------------
target: host-m4.install.pack
----------------------------
new rpath '${ORIGIN}/../lib' too large; maximum length 4
ptxdist: error: Failed to adjust rpath for '/home/phoenix/build/tc-build/src/OSELAS.Toolchain-2018.12.0/platform-arm-v7a-linux-gnueabihf-gcc-8.2.1-glibc-2.28-binutils-2.31.1-kernel-4.19-sanitized/packages/host-m4-1.4.18/bin/m4'
make: *** [/opt/lib/ptxdist-2018.12.0/rules/post/ptxd_make_world_install.make:60: /home/phoenix/build/tc-build/src/OSELAS.Toolchain-2018.12.0/platform-arm-v7a-linux-gnueabihf-gcc-8.2.1-glibc-2.28-binutils-2.31.1-kernel-4.19-sanitized/state/host-m4.install.pack] Error 1
Because chrpath can not dynamically allocate more space for the new
rpath. I found a bug report for oe-core which ran into the same issue
under [1].
Their suggested solution is to switch to patchelf [2]. Is there an interest
for this switch in ptxdist as well? If so I'll gladly send-patches.
[1] Link: https://patchwork.openembedded.org/patch/34653/
[2] Link: https://nixos.org/patchelf.html
Regards,
Rouven
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2019-04-14 7:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-14 7:33 Rouven Czerwinski [this message]
2019-04-18 14:23 ` Michael Olbrich
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=877ebx6nxm.fsf@czerwinskis.de \
--to=rouven@czerwinskis.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