From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] Wrong compiler path when compiling zlib
Date: Thu, 2 Jan 2014 06:47:04 +0200 [thread overview]
Message-ID: <20140102044704.GF6589@tarshish> (raw)
In-Reply-To: <CA+hj=MoNYEZchBs1_34cS4eA=UYfU+2QNdbNBDOqt=u2YFsJPw@mail.gmail.com>
Hi Ivan,
On Wed, Jan 01, 2014 at 11:46:27PM +0100, Ivan Wagner wrote:
> I noticed that the compiler base directory is actually wrong when
> attempting to compiler the zlib library.
>
> I've configured CodeSourcery as an external pre-installed toolchain with
> path under /opt but this is the error log I get when trying to compile zlib:
>
> --------------------
> ./configure --shared --prefix=/usr
> Wed Jan 1 23:37:01 CET 2014
> === ztest6146.c ===
> extern int getchar();
> int hello() {return getchar();}
> ===
> /home/ivan/projects/buildroot/output/host/usr/bin/arm-none-linux-gnueabi-gcc
> -c ztest6146.c
> ./configure: line 165:
> /home/ivan/projects/buildroot/output/host/usr/bin/arm-none-linux-gnueabi-gcc:
> No such file or directory
> ... using
> /home/ivan/projects/buildroot/output/host/usr/bin/arm-none-linux-gnueabi-gcc
>
> Checking for obsessive-compulsive compiler options...
> === ztest6146.c ===
> int foo() { return 0; }
> ===
> /home/ivan/projects/buildroot/output/host/usr/bin/arm-none-linux-gnueabi-gcc
> -c -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -pipe
> -Os -fPIC ztest6146.c
> ./configure: line 343:
> /home/ivan/projects/buildroot/output/host/usr/bin/arm-none-linux-gnueabi-gcc:
> No such file or directory
> (exit code 127)
> Compiler error reporting is too harsh for ./configure (perhaps remove
> -Werror).
> ** ./configure aborting.
> --------------------
>
> I don't know where it gets the
> /home/ivan/projects/buildroot/output/host/usr/bin/arm-none-linux-gnueabi-gcc
> path from...
This should be a symlink to the external toolchain wrapper. See the comment in
toolchain/toolchain-external/toolchain-external.mk for some more information
on this wrapper. I guess that a 'make clean' would solve your problem.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2014-01-02 4:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-01 22:46 [Buildroot] Wrong compiler path when compiling zlib Ivan Wagner
2014-01-02 4:47 ` Baruch Siach [this message]
2014-01-02 9:06 ` Ivan Wagner
2014-01-02 9:19 ` Baruch Siach
2014-01-02 10:08 ` Ivan Wagner
2014-01-02 10:34 ` Baruch Siach
2014-01-02 10:37 ` Ivan Wagner
2014-01-02 11:06 ` Baruch Siach
2014-01-02 11:09 ` Ivan Wagner
2014-01-02 11:17 ` Baruch Siach
2014-01-02 11:35 ` Ivan Wagner
2014-01-02 12:21 ` Thomas Petazzoni
2014-01-02 12:33 ` Ivan Wagner
2014-01-02 12:20 ` Thomas Petazzoni
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=20140102044704.GF6589@tarshish \
--to=baruch@tkos.co.il \
--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.