public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Geert Stappers <stappers@stappers.nl>
To: crossgcc@sourceware.org
Subject: Re: Paid Support
Date: Sun, 23 Aug 2020 07:34:35 +0200	[thread overview]
Message-ID: <20200823053435.rofbk67k673vjbbd@gpm.stappers.nl> (raw)
In-Reply-To: <36e1a28a4152233355f19e40e4a5955b704de257.camel@silogroup.org>

On Sat, Aug 22, 2020 at 09:36:09PM -0400, Chris Punches via crossgcc wrote:
> Dear Crosstool-NG Community,
> 
> Please let me know if there is another venue to request this, but, I was
> wondering if anyone at the crosstool-ng project were willing to provide paid
> support to integrate crosstool-ng into the build process for a Linux
> distribution that compiles itself?
> 
> Basically, I want to use crosstool-ng to build a cross-toolchain for at least
> x86_64 targets in a docker container's /opt/xtools, and our automation would use
> that to cross-compile all the pieces of a chroot at /opt/chroot until we have
> enough to spit out a docker image and a bootable iso in a shared volume with the
> docker host.  It is a "distro from source in a box" concept.  Will use libc.
> 
> Before you type it -- buildroot does not meet my objectives.  Unfortunately.
> 
> This is after months of struggling with the documentation for both binutils and
> crosstool-ng.  The docs make this look pretty easy but I'm finding that the
> tutorials and docs are not resulting in successful builds with rather ambiguous
> blockers.
> 
> So, I figure it might be a good idea to see if this is something money can help
> with so that we can get someone more knowledgable than I am providing input on
> it.  Even if that paid support is paid training, fine, it's better than what
> we've been trying to do up to this point on that project.  I'm open to ideas. 
> 
> No one seems to know how this works outside of the gigantic brains that occupy
> this mailing list.  I know this because I've asked every person on the planet
> about it and can personally confirm. Every. Single. Person. :)
> 
> I am eager to move past this piece for a while so I can put more energy into the
> distro itself.  If there is a better place to ask or find this kind of support I
> am highly receptive to suggestions.

Idea:  Hire what you can hire, give  it a clear task/order/assigment.


At "what you can hire":  Establish a relation between those who work and
those who pay.  Yes, that is a two way relation.

At "it":  Company or single person

 
> Earnestly,
> 
> Chris Punches
> Owner
> SILO GROUP, LLC
> chris.punches@silogroup.org


Groeten
Geert Stappers
-- 
Silence is hard to parse

  reply	other threads:[~2020-08-23  5:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-23  1:36 Paid Support? Chris Punches
2020-08-23  5:34 ` Geert Stappers [this message]
2020-08-27 10:48 ` Thomas Petazzoni

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=20200823053435.rofbk67k673vjbbd@gpm.stappers.nl \
    --to=stappers@stappers.nl \
    --cc=crossgcc@sourceware.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).