From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Rouven Czerwinski <rouven@czerwinskis.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] rpath maxmimum length error
Date: Thu, 18 Apr 2019 16:23:48 +0200 [thread overview]
Message-ID: <20190418142348.nieysfh6np4g7own@pengutronix.de> (raw)
In-Reply-To: <877ebx6nxm.fsf@czerwinskis.de>
On Sun, Apr 14, 2019 at 09:33:41AM +0200, Rouven Czerwinski wrote:
> 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.
PTXdist should specify a long enough rpath at build-time. Please do a clean
build with '-v' and send the host-m4.compile section from the logfile.
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
prev parent reply other threads:[~2019-04-18 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-14 7:33 Rouven Czerwinski
2019-04-18 14:23 ` Michael Olbrich [this message]
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=20190418142348.nieysfh6np4g7own@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=rouven@czerwinskis.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