public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Nikita Orlov <nikitos1550@yandex.ru>
To: Bryan Hundven <bryanhundven@gmail.com>,
	"per-arnold.blaasmo@atmel.com" <per-arnold.blaasmo@atmel.com>
Cc: crossgcc maillist <crossgcc@sourceware.org>
Subject: Re: Announcing `autocrossgen'
Date: Thu, 23 Oct 2014 08:18:00 -0000	[thread overview]
Message-ID: <6111901414052286@web28m.yandex.ru> (raw)
In-Reply-To: 2420000004601229105

Hi!

Is it possible to build toolchain for arm, that runs on same arm, but build toolchain on x86?

23.10.2014, 11:41, "Bryan Hundven" <bryanhundven@gmail.com>:
> Per, List,
>
> To get context correct "more friendly to developers". So say you are
> working on binutils, gcc, glibc, musl-libc, etc...
>
> If you are using crosstool-ng, you have to save steps if you want to
> not build the prereqs for building gcc (say you are working on gcc
> specifically) over and over again. autocrossgen's build system uses
> GNU/Make rather then Bash. So you can just delete the build/gcc*, type
> make and the build will leave off at configuring and building gcc
> instead of starting the whole build process over from scratch.
>
> -Bryan
>
> On Thu, Oct 23, 2014 at 12:35 AM, Per Arnold Blaasmo
> <per-arnold.blaasmo@atmel.com> wrote:
>
>> б On 23. okt. 2014 04:58, Bryan Hundven wrote:
>>> б Hello list,
>>>
>>> б Out of necessity for a tool to build a cross-compiler that is more
>>> б friendly to developers, I started this project. I've posted it to
>>> б github so that it is easy for others to contribute to:
>>>
>>> б https://github.com/bhundven/autocrossgen
>>>
>>> б If you'd like to contribute, check out the issues and milestones:
>>> б https://github.com/bhundven/autocrossgen/issues
>>> б https://github.com/bhundven/autocrossgen/milestones
>>>
>>> б Just fork the code, make changes to your tree, and open a pull request.
>>>
>>> б Enjoy!
>>>
>>> б -Bryan
>>>
>>> б --
>>> б For unsubscribe information see http://sourceware.org/lists.html#faq
>> б Hi Bryan,
>>
>> б "more friendly" is not a very concrete term, can you be more specific
>> б and maybe make a comparison with i.e. crosstool-ng.
>>
>> б I appreciate the initiative, but what to know more :-)
>>
>> б Regards
>> б Per A.
>>
>> б --
>> б For unsubscribe information see http://sourceware.org/lists.html#faq
>
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq

--б 
Nikita Orlov
Skype: nik_stet
QQ: 2717846083

--
For unsubscribe information see http://sourceware.org/lists.html#faq

  parent reply	other threads:[~2014-10-23  8:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-23  2:58 Bryan Hundven
2014-10-23  7:36 ` Per Arnold Blaasmo
2014-10-23  7:41   ` Bryan Hundven
2014-10-23  7:58     ` Bryan Hundven
2014-10-23  8:18     ` Nikita Orlov [this message]
2014-10-23  8:27       ` Bryan Hundven
2014-10-23  9:07         ` Nikita Orlov
2014-10-23 17:40           ` ANDY KENNEDY
2014-10-23  9:18       ` Bryan Hundven
2014-10-23 18:49     ` Thomas Petazzoni
2014-10-23 19:50       ` Bryan Hundven
2014-11-10  2:10 ` Bryan Hundven

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=6111901414052286@web28m.yandex.ru \
    --to=nikitos1550@yandex.ru \
    --cc=bryanhundven@gmail.com \
    --cc=crossgcc@sourceware.org \
    --cc=per-arnold.blaasmo@atmel.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.
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).