public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: crossgcc@sourceware.org
Cc: Blair Burtan <info@northernlightstactical.com>,
	per-arnold.blaasmo@atmel.com
Subject: Re: Build failed in step 'Dumping user-supplied crosstool-NG configuration'
Date: Wed, 26 Sep 2012 16:56:00 -0000	[thread overview]
Message-ID: <201209261856.25534.yann.morin.1998@free.fr> (raw)
In-Reply-To: <CC886D94.256A7%info@northernlightstactical.com>

Blair, All,

[Please, do not top-post]

On Wednesday 26 September 2012 17:30:12 Blair Burtan wrote:
> That was the problem but not quite the complete solution.  I had to modify
> the grep path to point to the MacPorts verison when I built ct-ng.  I also
> had to use ginstall instead of the OSX install.

./configure --help
[--SNIP--]
Optional Packages:
  --with-PACKAGE[=ARG]    use PACKAGE [ARG=yes]
  --without-PACKAGE       do not use PACKAGE (same as --with-PACKAGE=no)
  --with-install=PATH     Specify the full PATH to a BSD-compatible install
  --with-sed=PATH         Specify the full PATH to GNU sed
  --with-objcopy=PATH     Specify the full PATH to GNU objcopy
  --with-objdump=PATH     Specify the full PATH to GNU objdump
  --with-ranlib=PATH      Specify the full PATH to GNU ranlib
  --with-readelf=PATH     Specify the full PATH to GNU readelf
  --with-bash=PATH        Specify the full PATH to GNU bash >= 3.1
  --with-awk=PATH         Specify the full PATH to GNU awk
  --with-make=PATH        Specify the full PATH to GNU make >= 3.80
  --with-libtool=PATH     Specify the full PATH to GNU libtool >= 1.5.26
  --with-libtoolize=PATH  Specify the full PATH to GNU libtoolize >= 1.5.26
  --with-automake=PATH    Specify the full PATH to GNU automake >= 1.10
[--SNIP--]

That's how you tell crosstool-NG what tools to use if the default ones are
not the GNU ones.

Alternatively, that's also explained at length in the documentation:
    docs/C - Misc. tutorials.txt

And there is also a table of contents for the documentation:
    docs/0 - Table of content.txt

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

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

  reply	other threads:[~2012-09-26 16:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-26  3:46 Blair Burtan
2012-09-26  6:54 ` Per Arnold Blaasmo
2012-09-26 15:30   ` Blair Burtan
2012-09-26 16:56     ` Yann E. MORIN [this message]
2014-08-06  2:27       ` [PATCH] Added support for AC_ARG_WITH([grep]...) and sed substitution fixes Fabian Freyer
2014-08-06  2:40         ` Fabian Freyer
2014-08-26 22:26         ` Yann E. MORIN
2014-08-26 22:43           ` Fabian Freyer
2014-08-26 22:47             ` Yann E. MORIN
2014-08-26 22:51         ` Yann E. MORIN

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=201209261856.25534.yann.morin.1998@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=crossgcc@sourceware.org \
    --cc=info@northernlightstactical.com \
    --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).