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
i...@metux.net -- +49-151-27565287

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to 
ptxdist-requ...@pengutronix.de

Reply via email to