public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Michael Hope <michael.hope@linaro.org>
To: tpflima <thiagolima@gmail.com>
Cc: crossgcc@sourceware.org
Subject: Re: problems installing my arm-linux crosscompiler using ct-ng - Build failed in step 'Installing static core C compiler'
Date: Mon, 23 Apr 2012 03:07:00 -0000	[thread overview]
Message-ID: <CANLjY-nMLq1JqtaPBWEa+HpJ_t981tAw3p1sPO_DGb1agSSjOQ@mail.gmail.com> (raw)
In-Reply-To: <33730502.post@talk.nabble.com>

On 23 April 2012 14:04, tpflima <thiagolima@gmail.com> wrote:
>
> Hello, how are you?
>
> I am having problems installing my arm-linux crosscompiler using ct-ng
>
> I downloaded the crosstoll-ng 1.9.3 last week.
> - I changed the prefixed directory for /usr/local/xtools/${CT_TARGET}
> - I changed the number of parallel jobs, 8
> - I changed the «Tuple's alias» to arm-­linux.
> - I Enabled strace on debug facilities (gdb and ltrace could not be enabled
> because the tarball could not be retrieved from their online locals)
>
> I also used the following configurations:
>
> Target OS Linux
> Operating System, linux kernel version - 2.6.36
> Binary Utilities - binutils version 2.20.1
> C Compiler - gcc version 4.4.5
> C-library - egLibc version 2_10
> Companion libraries - GMP Version 4.3.2
> MPFR version 3.0.0
> PPL Version0.10.2
> Cloog/ppl version 0.15.10
> libelf version 0.8.13
> (*) Build shared companion libraries
>
> The output was:
>
> =====================
>
>
> [INFO ]  Performing some trivial sanity checks
> [INFO ]  Build started 20120422.223549
> [INFO ]  Building environment variables
> [INFO ]  =================================================================
> [INFO ]  Retrieving needed toolchain components' tarballs
> [INFO ]  Retrieving needed toolchain components' tarballs: done in 0.05s (at
> 00:02)
> [INFO ]  =================================================================
> [INFO ]  Extracting and patching toolchain components
> [INFO ]  Extracting and patching toolchain components: done in 2.45s (at
> 00:04)
> [INFO ]  =================================================================
> [INFO ]  Installing kernel headers
> [INFO ]  Installing kernel headers: done in 4.96s (at 00:09)
> [INFO ]  =================================================================
> [INFO ]  Installing GMP
> [INFO ]  Installing GMP: done in 54.65s (at 01:04)
> [INFO ]  =================================================================
> [INFO ]  Installing MPFR
> [INFO ]  Installing MPFR: done in 15.13s (at 01:19)
> [INFO ]  =================================================================
> [INFO ]  Installing PPL
> [INFO ]  Installing PPL: done in 132.39s (at 03:31)
> [INFO ]  =================================================================
> [INFO ]  Installing CLooG/ppl
> [INFO ]  Installing CLooG/ppl: done in 6.76s (at 03:38)
> [INFO ]  =================================================================
> [INFO ]  Installing binutils
> [INFO ]  Installing binutils: done in 35.86s (at 04:14)
> [INFO ]  =================================================================
> [INFO ]  Installing static core C compiler
> [ERROR]    make[1]: *** [configure-gcc] Error 1
> [ERROR]    Build failed in step 'Installing static core C compiler'
> [ERROR]    Error happened in
> '/home/thiago/Documents/linux_labs/crosstool-ng-1.9.3/scripts/functions' in
> function 'CT_DoExecLog' (line unknown, sorry)
> [ERROR]          called from
> '/home/thiago/Documents/linux_labs/crosstool-ng-1.9.3/scripts/build/cc/gcc.sh'
> at line # 289 in function 'do_cc_core'
> [ERROR]          called from
> '/home/thiago/Documents/linux_labs/crosstool-ng-1.9.3/scripts/build/cc/gcc.sh'
> at line # 52 in function 'do_cc_core_pass_1'
> [ERROR]          called from
> '/home/thiago/Documents/linux_labs/crosstool-ng-1.9.3/scripts/crosstool-NG.sh'
> at line # 597 in function 'main'
> [ERROR]    Look at '/usr/local/xtools/arm-unknown-linux-gnueabi/build.log'
> for more info on this error.
> [ERROR]  (elapsed: 4:37.67)
> [04:38] / make: *** [build] Error 2
>
> I dont know what I'm doing wrong. :(
> Could anyone give me a hint.
>
> Thanks a lot and congrats for this excellent forum.
>
> Thiago - tpfslima

Hi Thiago.  I imagine it's a permissions problem.  /usr/local is
normally only writeable as root and you're probably running the script
as a normal user.

Does a plain 'mkdir -p /usr/local/xtools' work?  If not, try something like
 sudo mkdir /usr/local/xtools
 chown tpfslima:tpfslima /usr/local/xtools (or whatever your username is)

and test it by running
 touch /usr/local/xtools/itworked

-- Michael

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

  reply	other threads:[~2012-04-23  3:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-23  2:05 tpflima
2012-04-23  3:07 ` Michael Hope [this message]
2012-04-23 16:32 ` Yann E. MORIN
2012-04-23 22:53   ` Thiago Lima

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=CANLjY-nMLq1JqtaPBWEa+HpJ_t981tAw3p1sPO_DGb1agSSjOQ@mail.gmail.com \
    --to=michael.hope@linaro.org \
    --cc=crossgcc@sourceware.org \
    --cc=thiagolima@gmail.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).