[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Ltib] Failure to build pkgconfig on LPC32xx Target
From: |
Stuart Hughes |
Subject: |
Re: [Ltib] Failure to build pkgconfig on LPC32xx Target |
Date: |
Mon, 26 Jul 2010 20:06:02 +0100 |
User-agent: |
Thunderbird 2.0.0.16 (X11/20080707) |
Hi Tim,
It's a bug in the package build rules, or at least it's incomplete. I'd
not tested this before except for building as a host tool. Clearly it
needs some TLC. Unfortunately I don't have time to do this right now.
Maybe you could try to fix it and submit back a patch. Often what is
needed in a case like this is to pre-supply the answer to configure with
the appropriate symbol (you need to look into configure). There
examples in other .spec files along the lines of:
ac_cv_xxx_xxx=y ./configure .....
Regards, Stuart
Tim Nelson wrote:
> As noted in an earlier post, I'm attempting to get LTIB working on a Phytec
> board with the LPC3205 SoC. The latest build was stopped with the relevant
> last lines of output below:
>
> ---BEGIN---
> checking for extra flags to get ANSI library prototypes... configure: error:
> cannot run test program while cross compiling
> See `config.log' for more details.
> configure: error: /bin/sh './configure' failed for glib-1.2.8
> error: Bad exit status from /usr/src/ltib/tmp/rpm-tmp.19931 (%build)
>
>
> RPM build errors:
> Bad exit status from /usr/src/ltib/tmp/rpm-tmp.19931 (%build)
> Build time for pkgconfig: 53 seconds
>
> Failed building pkgconfig
>
>
> f_buildrpms() returned an error, exiting
> traceback:
> main:567
>
>
> Started: Mon Jul 26 09:06:32 2010
> Ended: Mon Jul 26 09:09:31 2010
> Elapsed: 179 seconds
>
> VERSION : 10.1.1
> CVS_VERSION : $Revision: 1.68 $ (Savannah)
> PLATFORM : phy3250
> GNUTARCH : arm
> TOOLCHAIN : tc-fsl-x86lnx-armeabi-nptl-4.1.2-3.i386.rpm
> TOOLCHAIN_CFLAGS : -O2 -fsigned-char -mfloat-abi=softfp -mfpu=vfp
>
> These packages failed to build:
> pkgconfig
>
> Build Failed
>
> Exiting on error or interrupt
> ---END---
>
> Any thoughts?
>
> --Tim
>