From: "Raphaël Mélotte" <raphael.melotte@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 32624@debbugs.gnu.org
Subject: [bug#32624] [PATCH] gnu: perl: Add support for cross-compilation
Date: Tue, 04 Sep 2018 12:13:10 +0200 [thread overview]
Message-ID: <87bm9d8tah.fsf@gmail.com> (raw)
In-Reply-To: <878t4iuuaf.fsf@gnu.org>
Ludovic Courtès writes:
> I tested a variant of this patch with --target=arm-linux-gnueabihf.
> During the ‘configure’ phase, I see:
>
> --8<---------------cut here---------------start------------->8---
> Checking for cross-compile
> No targethost for running compiler tests against defined, running locally
> --8<---------------cut here---------------end--------------->8---
>
> Then the build completes but the result is a set of x86_64 (native)
> binaries.
>
> So I suppose some more work in needed to really cross-compile. Maybe we
> need to pass specific configure flags?
Ok, thanks for checking.
After some web searching and according to the following page, cross-compiling perl isn't an easy
task:
https://arsv.github.io/perl-cross/index.html
Do you think it would be a good idea to package perl-cross and use it
when cross-compiling ?
The other option (giving -Dtargethost to the configure script) seems to require
a target host to be available with an ssh
server running.
> (BTW, I think I already wrote this but you don’t need to cross-compile
> if all you want is 32-bit binaries. Simply use “-s i686-linux” for
> that.)
Yes you mentioned it a few month ago, and that helped me a lot back
then :-)
I wanted to come back to trying to cross-compile some packages because
I find it interesting (the idea of remotely building packages for other architectures
is so cool).
Thanks,
Raphaël.
next prev parent reply other threads:[~2018-09-04 10:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 14:10 [bug#32624] [PATCH] gnu: perl: Add support for cross-compilation Raphaël Mélotte
2018-09-03 21:48 ` Ludovic Courtès
2018-09-04 10:13 ` Raphaël Mélotte [this message]
2018-09-05 9:57 ` Ludovic Courtès
2018-09-07 12:58 ` Raphaël Mélotte
2018-09-07 14:17 ` bug#32624: " Raphaël Mélotte
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=87bm9d8tah.fsf@gmail.com \
--to=raphael.melotte@gmail.com \
--cc=32624@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.