Poky Project Discussions
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Poky Project <poky@yoctoproject.org>
Subject: Re: GCC 4.6.0?
Date: Thu, 28 Apr 2011 07:13:14 -0600	[thread overview]
Message-ID: <4DB967EA.4030705@mlbassoc.com> (raw)
In-Reply-To: <4DB95316.1090001@mlbassoc.com>

On 04/28/2011 05:44 AM, Gary Thomas wrote:
> I see that the Poky master (3279737cdf164962b0121bd850634cb05a616f15)
> now has recipes for GCC 4.6.0, so I thought I'd try it on my OMAP/3530
>
> Sadly, it failed:
> | checking if ccache arm-poky-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -fno-tree-vectorize
> --sysroot=/home/local/p60_poky/tmp/sysroots/cobra3530p60 supports -fno-rtti -fno-exceptions... no
> | checking for ccache arm-poky-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -fno-tree-vectorize
> --sysroot=/home/local/p60_poky/tmp/sysroots/cobra3530p60 option to produce PIC... -fPIC -DPIC
> | checking if ccache arm-poky-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -fno-tree-vectorize
> --sysroot=/home/local/p60_poky/tmp/sysroots/cobra3530p60 PIC flag -fPIC -DPIC works... yes
> | checking if ccache arm-poky-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -fno-tree-vectorize
> --sysroot=/home/local/p60_poky/tmp/sysroots/cobra3530p60 static flag -static works... no
> | checking if ccache arm-poky-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -fno-tree-vectorize
> --sysroot=/home/local/p60_poky/tmp/sysroots/cobra3530p60 supports -c -o file.o... yes
> | checking if ccache arm-poky-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -fno-tree-vectorize
> --sysroot=/home/local/p60_poky/tmp/sysroots/cobra3530p60 supports -c -o file.o... (cached) yes
> | checking whether the ccache arm-poky-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -fno-tree-vectorize
> --sysroot=/home/local/p60_poky/tmp/sysroots/cobra3530p60 linker (arm-poky-linux-gnueabi-ld --sysroot=/home/local/p60_poky/tmp/sysroots/cobra3530p60) supports shared libraries... yes
> | checking whether -lc should be explicitly linked in... no
> | checking dynamic linker characteristics... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.
> | ERROR: Function 'do_configure' failed (see /home/local/p60_poky/tmp/work/armv7a-poky-linux-gnueabi/gcc-runtime-4.6.0-r0/temp/log.do_configure.6331 for further information)
> NOTE: package gcc-runtime-4.6.0-r0: task do_configure: Failed
> ERROR: Task 458 (/home/local/poky-amltd/meta/recipes-devtools/gcc/gcc-runtime_4.6.0.bb, do_configure) failed with exit code '1'
>
> Should this work? Has it been tested on ARM targets?
> Maybe I missed something else?
>

Note: this was in an extant build.  I just tried it in a fresh
tree and it seems to be working better now.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


      reply	other threads:[~2011-04-28 13:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-28 11:44 GCC 4.6.0? Gary Thomas
2011-04-28 13:13 ` Gary Thomas [this message]

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=4DB967EA.4030705@mlbassoc.com \
    --to=gary@mlbassoc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox