From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: ptxdist@pengutronix.de
Subject: [ptxdist] adding golang support
Date: Fri, 16 Apr 2021 14:00:08 +0200 [thread overview]
Message-ID: <b7566cfb-eb6e-edd4-247a-068c3ac92e14@metux.net> (raw)
Hi folks,
I'm currently in process of adding some golang-based packages (eg. runc)
to ptxdist/distrokit-based projects.
For now, I'm just doing it quick+dirty, but a bunch of things IMHO
should be done on a more central point, eg:
* golang toolchain settings
* golang doesn't understand the standard GNU target identifiers, so
some mapping is required (eg. "x86_64" must be translated to
"amd64")
* $GOARCH must be set explicitly
* $CC must be set explicitly (to point to the cross compiler)
* currently expecting a recent-enough golang toolchain on the host
(eg. have to use an extra backports repo on Debian)
* in some cases, extra golang packages need to be installed on the host
Certainly, this doesn't fit the spirit of ptxdist, so a bunch of things
need to be done for a clean solution:
* build our own (recent) golang crosscompiler with some arbitrary old
golang from the host
* automatically setup the correct pathes / envs to use our own toolchain
(w/o having to redo that in each single packages), like we already
have for C/C++.
* add some extra host tools (eg. manpage generator, ...)
Anybody here already working on that ?
--mtx
--
---
Hinweis: unverschlüsselte E-Mails können leicht abgehört und manipuliert
werden ! Für eine vertrauliche Kommunikation senden Sie bitte ihren
GPG/PGP-Schlüssel zu.
---
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next reply other threads:[~2021-04-16 12:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 12:00 Enrico Weigelt, metux IT consult [this message]
2021-04-23 6:49 ` 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=b7566cfb-eb6e-edd4-247a-068c3ac92e14@metux.net \
--to=lkml@metux.net \
--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