From: ludo@gnu.org (Ludovic Courtès)
To: "Raphaël Mélotte" <raphael.melotte@gmail.com>
Cc: 32624@debbugs.gnu.org
Subject: [bug#32624] [PATCH] gnu: perl: Add support for cross-compilation
Date: Wed, 05 Sep 2018 11:57:44 +0200 [thread overview]
Message-ID: <87tvn46zc7.fsf@gnu.org> (raw)
In-Reply-To: <87bm9d8tah.fsf@gmail.com> ("Raphaël Mélotte"'s message of "Tue, 04 Sep 2018 12:13:10 +0200")
Hi Raphaël,
Raphaël Mélotte <raphael.melotte@gmail.com> skribis:
> 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 ?
I would prefer to rely on Perl’s build system, assuming it supports cross-compilation.
Now, I see that Buildroot uses perl-cross, so maybe it’s a sign that
it’s unavoidable:
https://git.busybox.net/buildroot/tree/package/perl/perl.mk
Besides I personally don’t consider cross-compilation of Perl a
priority, so unless you have a need for it, you can choose a different
task to work on. ;-)
> Yes you mentioned it a few month ago, and that helped me a lot back
> then :-)
Great. :-)
> 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).
It is! It’s usually a lot easier with packages that use the GNU build
system than with packages that use custom build tools such as Perl.
Let me know if you want to pursue the Perl cross-compilation endeavor
and if not, we can close this issue.
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-09-05 9:58 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
2018-09-05 9:57 ` Ludovic Courtès [this message]
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=87tvn46zc7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=32624@debbugs.gnu.org \
--cc=raphael.melotte@gmail.com \
/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.