[Angstrom-devel] a clean build of angstrom fails: gcc-cross-initial_4.5.bb, attached logfile

[Denys Dmytriyenko]

On Fri, Mar 23, 2012 at 05:02:57PM -0700, Khem Raj wrote:
> On Fri, Mar 23, 2012 at 3:10 PM, Norman Schleicher
> <normanschleicher at gmx.de> wrote:
> > On 03/23/2012 10:47 PM, Khem Raj wrote:
> >>
> >> On Fri, Mar 23, 2012 at 2:15 PM, Norman Schleicher
> >> <normanschleicher at gmx.de>  wrote:
> >>>
> >>> Hello,
> >>>
> >>> a complete rebuild of angstrom does not work even if retried several
> >>> times
> >>> so please check previous logs too.
> >>>
> >>> Summary: 1 task failed:
> >>>
> >>>  /var/lib/jenkins/jobs/pandaboard-angstrom/workspace/setup-scripts/sources/meta-openembedded/meta-oe/recipes-devtools/gcc/gcc-cross-initial_4.5.bb,
> >>> do_compile
> >>>
> >>>
> >>>
> >>> http://norman-schleicher.de/jenkins/job/pandaboard-angstrom/103/console
> >>>
> >>
> >> /workspace/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/gcc-cross-initial-4.5-r47+svnr184907/gcc-4_5-branch/build.x86_64-linux.arm-angstrom-linux-gnueabi/arm-angstrom-linux-gnueabi/libgcc':
> >> | configure: error: cannot compute suffix of object files: cannot compile
> >> | See `config.log' for more details.
> >> | make[1]: *** [configure-target-libgcc] Error 1
> >>
> >>
> >> can you post that config.log which should be in that libgcc builddir
> >
> > Yes i attached the file and the whole workspace is browsable too if you need
> > any further information. So ill not start a new build to give you reasonable
> > links/results.
> >
> > http://norman-schleicher.de/jenkins/job/pandaboard-angstrom/ws/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/gcc-cross-initial-4.5-r47+svnr184907/gcc-4_5-branch/build.x86_64-linux.arm-angstrom-linux-gnueabi/arm-angstrom-linux-gnueabi/libgcc/config.log
> >
> > Cheers Norman (nschle85)
> >
> > PS: please give me a hint that i can restart the build.
> >
> 
> version `GLIBC_2.14' not found this means the compiler was compiled on
> a newer host than the one you are running on it looks like a shared
> state problem
> 
> do bitbake -ccleansstate gcc-cross-intermediate gcc-cross-intitial gcc-cross
> 
> and rerun your build for image that might help here

I've been seeing the same problem, had to clean sstate for all the toolchain 
components one by one - gcc-cross-*, binutils, eglibc etc.

It doesn't seem to happen in distro-less configuration, so might be something 
specific to Angstrom sstate seetings...

-- 
Denys