From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Bian, Naimeng" <biannm@cn.fujitsu.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: [Question]Remove $BUILDDIR from gcc -v
Date: Tue, 16 Sep 2014 08:21:22 +0100 [thread overview]
Message-ID: <1410852082.14624.54.camel@ted> (raw)
In-Reply-To: <30DC4EDFD798C94083F3E083754532CCCA4509@G08CNEXMBPEKD02.g08.fujitsu.local>
On Tue, 2014-09-16 at 02:44 +0000, Bian, Naimeng wrote:
> Any suggestion to remove the "$BUILDDIR" from "gcc -v".
> Maybe the building option such as --with-libtool-sysroot is unnecessary
> for toolchain. Thanks a million!
>
> --------------------------------------------------------------------------------
> #i586-poky-linux-gcc -v
> Using built-in specs.
> COLLECT_GCC=/opt/poky-lsb/1.4.2/sysroots/x86_64-pokysdk-linux/usr/bin/
> i586-poky-linux/i586-poky-linux-gcc
> COLLECT_LTO_WRAPPER=/opt/poky-lsb/1.4.2/...
> Target: i586-poky-linux
> Configured with: $BUILDDIR/tmp/work-shared/gcc-4.7.2-r20/gcc-4.7.2/configure \
> --build=x86_64-linux --host=x86_64-pokysdk-linux --target=i586-poky-linux \
> --prefix=/opt/poky-lsb/1.4.x/... \
> --bindir=/opt/poky-lsb/1.4.x/... \
>
> ... ...
>
> --with-libtool-sysroot=$BUILDDIR/tmp/sysroots/x86_64-nativesdk-pokysdk-linux \
> --with-build-sysroot=$BUILDDIR tmp/sysroots/ubinux-qemux86 \
> --with-mpfr=$BUILDDIR/tmp/sysroots/x86_64-nativesdk-pokysdk-linux \
> --with-mpc=$BUILDDIR/tmp/sysroots/x86_64-nativesdk-pokysdk-linux \
> ... ...
> --------------------------------------------------------------------------------
These options are required. Why do you want to remove them?
Cheers,
Richard
next prev parent reply other threads:[~2014-09-16 7:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 2:44 [Question]Remove $BUILDDIR from gcc -v Bian, Naimeng
2014-09-16 7:21 ` Richard Purdie [this message]
2014-09-17 1:04 ` Bian, Naimeng
2014-09-18 7:32 ` Khem Raj
2014-09-18 9:46 ` Bian, Naimeng
2014-09-26 3:29 ` Khem Raj
2014-09-26 11:06 ` Richard Purdie
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=1410852082.14624.54.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=biannm@cn.fujitsu.com \
--cc=poky@yoctoproject.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 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.