All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Trapanese <marcotrapanese@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Few questions external toolchain
Date: Wed, 26 Feb 2014 20:53:17 +0100	[thread overview]
Message-ID: <530E462D.50600@gmail.com> (raw)
In-Reply-To: <CAAXf6LUYGTL2BQJY07JMu5WmLb7qxf+Mb6AQvi-EWYvYxi3EXA@mail.gmail.com>

Hi Thomas,

Il 26/02/2014 20:42, Thomas De Schampheleire ha scritto:

> Can you run following command: 
> /home/marco/dev/buildroot/output/host/usr/bin/arm-fsl-linux-gnueabi-gcc -print-file-name=crt1.o 
> and verify that the reported file exists? What is the output? 

The output is:

crt1.o

Furthermore:

find -name crt1.o
./output/host/usr/arm-buildroot-linux-gnueabi/sysroot/usr/lib/crt1.o


> Normally you shouldn't give any special environment flags. You could 
> also try to compile a simple hello world program with that compiler in 
> output/host/usr/bin, to see if that works correctly or not.

Compiling an hello world program with the (symbolic link) in 
output/host/usr/bin/arm-fsl-linux-gnueabi-gcc leads to the same linker 
errors described in the previous post.

But the original compiler 
(/home/marco/dev/fsl-linaro-toolchain/bin/arm-fsl-linux-gnueabi-gcc) 
works fine with the same hello world.

Thanks again!
Marco

  reply	other threads:[~2014-02-26 19:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-24 18:18 [Buildroot] Few questions external toolchain Marco Trapanese
2014-02-25 10:17 ` Marco Trapanese
2014-02-25 13:10   ` Thomas De Schampheleire
2014-02-25 13:34     ` Marco Trapanese
2014-02-25 14:11   ` Thomas De Schampheleire
2014-02-26 16:53     ` Marco Trapanese
2014-02-26 19:42       ` Thomas De Schampheleire
2014-02-26 19:53         ` Marco Trapanese [this message]
2014-02-26 21:47       ` Arnout Vandecappelle
2014-02-26 22:46         ` Marco Trapanese
2014-03-17 14:59           ` Thomas De Schampheleire

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=530E462D.50600@gmail.com \
    --to=marcotrapanese@gmail.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.