public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Alexandr Zatevalov <sitesv@narod.ru>
To: crossgcc@sourceware.org
Subject: Re: Build Error
Date: Fri, 03 Feb 2012 20:07:00 -0000	[thread overview]
Message-ID: <CFC31E91-0D44-42F9-A906-5F415773261C@narod.ru> (raw)
In-Reply-To: <66DE0D7C-501D-4AB0-B4C8-769C72722AAD@narod.ru>

Guys, i don't understand what is this error: 
[ERROR]  Missing: 'i686-pc-linux-gnu-gcj' or 'i686-pc-linux-gnu-gcj' or 'gcj' : either needed!
What are these files and why are they missed?

This situation didn't happen In Windows-7 (Cygwin).

On 03.02.2012, at 16:17, Alexandr Zatevalov wrote:

> Good day!
> Trying to use Crosstool-NG under Debian.
> After command 
> ct-ng build
> 
> i see this some of log file:
> 
> [DEBUG]  ==> Executing: 'ln' '-sf' 'lib' '/root/x-tools/x86_64-unknown-linux-gnu/lib64'
> [DEBUG]  ==> Executing: 'ln' '-sf' 'lib' '/root/x-tools/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/sysroot/lib32'
> [DEBUG]  ==> Executing: 'ln' '-sf' 'lib' '/root/x-tools/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/sysroot/lib64'
> [DEBUG]  ==> Executing: 'ln' '-sf' 'lib' '/root/x-tools/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/sysroot/usr/lib32'
> [DEBUG]  ==> Executing: 'ln' '-sf' 'lib' '/root/x-tools/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/sysroot/usr/lib64'
> [DEBUG]  ==> Executing: 'ln' '-sf' 'lib' '/root/x-tools/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/lib32'
> [DEBUG]  ==> Executing: 'ln' '-sf' 'lib' '/root/x-tools/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/lib64'
> [DEBUG]  Making build system tools available
> [DEBUG]    'i686-build_pc-linux-gnu-ar' -> '/usr/bin/ar'
> [DEBUG]  ==> Executing: 'chmod' '700' '/home/sitesv/7800/toolchain-build/.build/x86_64-unknown-linux-gnu/buildtools/bin/i686-build_pc-linux-gnu-ar'
> [DEBUG]    'i686-build_pc-linux-gnu-as' -> '/usr/bin/as'
> [DEBUG]  ==> Executing: 'chmod' '700' '/home/sitesv/7800/toolchain-build/.build/x86_64-unknown-linux-gnu/buildtools/bin/i686-build_pc-linux-gnu-as'
> [DEBUG]    Missing: 'i686-pc-linux-gnu-dlltool' or 'i686-pc-linux-gnu-dlltool' or 'dlltool' : not required.
> [DEBUG]    'i686-build_pc-linux-gnu-gcc' -> '/usr/bin/gcc'
> [DEBUG]  ==> Executing: 'chmod' '700' '/home/sitesv/7800/toolchain-build/.build/x86_64-unknown-linux-gnu/buildtools/bin/i686-build_pc-linux-gnu-gcc'
> [DEBUG]    'i686-build_pc-linux-gnu-g++' -> '/usr/bin/g++'
> [DEBUG]  ==> Executing: 'chmod' '700' '/home/sitesv/7800/toolchain-build/.build/x86_64-unknown-linux-gnu/buildtools/bin/i686-build_pc-linux-gnu-g++'
> [DEBUG]  Testing '! ( y = y )'
> [ERROR]  Missing: 'i686-pc-linux-gnu-gcj' or 'i686-pc-linux-gnu-gcj' or 'gcj' : either needed!
> 
> What is wrong?
> Thanx! 
> 
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
> 


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

  reply	other threads:[~2012-02-03 20:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03 12:17 Alexandr Zatevalov
2012-02-03 20:07 ` Alexandr Zatevalov [this message]
2012-02-03 20:11   ` Bryan Hundven
2021-10-06  9:17 build error muhammad hatami
2021-10-06 16:54 ` Reinoud Koornstra

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=CFC31E91-0D44-42F9-A906-5F415773261C@narod.ru \
    --to=sitesv@narod.ru \
    --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).