public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Zhenqiang Chen <zhenqiang.chen@linaro.org>
To: Danny Gale <Daniel.Gale@coloradoengineeringinc.com>
Cc: "crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: Re: Build error: link tests are not allowed after GCC_NO_EXECUTABLES
Date: Tue, 07 Jan 2014 01:28:00 -0000	[thread overview]
Message-ID: <CACgzC7CwrNuvhAWNZF5jDu79xi1ZxZ1-gGFPbyLMGbbotD9bdg@mail.gmail.com> (raw)
In-Reply-To: <52CB2A7D.9050902@coloradoengineeringinc.com>

On 7 January 2014 06:13, Danny Gale
<Daniel.Gale@coloradoengineeringinc.com> wrote:
> Hi all,
>
> I've duplicated the 64-bit powerpc build listed on the website,
> powerpc64-unknown-linux-gnu. I'm now trying to build specifically for a
> Freescale processor using the e6500 core, powerpc64-e6500-linux-gnu. Their
> SDK was built using Yocto and bitbake -- the powers that be have decided it
> needs to be converted to a Crosstool-NG based build for our use. I'm running
> into some trouble.
>
> The Freescale SDK in question is here
> (http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=SDKLINUX&fpsp=1&tab=Design_Tools_Tab)
> . I've been working with v1.4, though I see now they've released v1.5. I've
> brought over their patches from the Yocto build tree and Crosstool-NG is
> configured to use the same versions of the various packages that Freescale
> used. While building pass-1 gcc with Crosstool-NG, the build fails with:
> configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES .

Please try to install multib-gcc and multilib-g++ in your host machine.
Or configure your gcc with "--with-system-zlib"

> I found and tried a couple of fixes for this, but none of them have resolved
> the problem: removing optimization for size on the libraries, not compiling
> for c++ support, not statically linking libstdc++. What else can cause this
> and how can it be resolved?
>
> I've attached both my config file and the tail of the log file in case that
> will help in diagnosis. Note that multilib is enabled because Freescale says
> it's required for building u-boot
>
> Thanks for your help,
> Danny
>
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq

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

  reply	other threads:[~2014-01-07  1:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-06 22:13 Danny Gale
2014-01-07  1:28 ` Zhenqiang Chen [this message]
2014-01-08  2:26   ` Danny Gale
  -- strict thread matches above, loose matches on Subject: below --
2013-04-10 19:14 Build error: Link " Gustav van der Merwe

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=CACgzC7CwrNuvhAWNZF5jDu79xi1ZxZ1-gGFPbyLMGbbotD9bdg@mail.gmail.com \
    --to=zhenqiang.chen@linaro.org \
    --cc=Daniel.Gale@coloradoengineeringinc.com \
    --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).