public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Justin Chen <justinpopo6@gmail.com>
To: crossgcc@sourceware.org
Subject: Some Questions
Date: Mon, 20 Mar 2017 22:02:00 -0000	[thread overview]
Message-ID: <CAJx26kVUyZq0cDiNHEroyQx7T0_JeMrF4Dof=sKR+G-PFJMDJg@mail.gmail.com> (raw)

Hello all,

I have two questions, some input would be awesome. :)

1. Are there any plans to support LSB based builds?

2. I am building multiple cross-compilers and throwing them into the
same toolchain. I am doing this by running separate builds into the
same out dir. This works nicely, however, host components need to be
rebuilt for each configuration(which waste some time). Would you guys
be interested in a feature where you can pass multiple config files
and have crosstools-ng build all of them in one go? (I can put a patch
together, if you guys would be willing to accept such a feature)

Thanks,
Justin

             reply	other threads:[~2017-03-20 22:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20 22:02 Justin Chen [this message]
2017-03-21  5:37 ` Alexey Neyman
2017-03-21 17:30   ` Justin Chen

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='CAJx26kVUyZq0cDiNHEroyQx7T0_JeMrF4Dof=sKR+G-PFJMDJg@mail.gmail.com' \
    --to=justinpopo6@gmail.com \
    --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).