meta-fsl-arm build failure

meta-fsl-arm build failure

[Richard Purdie]

amd-gpu-x11-bin/amd-gpu-mx51.inc contains:

# FIXME: All binaries lack GNU_HASH in elf binary but as we don't have
# the source we cannot fix it. Disable the insane check for now.
python populate_packages_prepend() {
    for p in d.getVar('PACKAGES', True).split():
        d.setVar("INSANE_SKIP_%s" % p, "ldflags")
}

and with the recent change that merged to make package QA a separate
task, this no longer works. I'd suggest you change this to:

python {
    for p in d.getVar('PACKAGES', True).split():
        d.setVar("INSANE_SKIP_%s" % p, "ldflags")
}

which should fix the issue. Doing that as a populate_packages prepend
wasn't the nicest of things to be doing in the first place.

Cheers,

Richard

Re: meta-fsl-arm build failure

[Otavio Salvador]

On Fri, Jul 11, 2014 at 5:06 AM, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> amd-gpu-x11-bin/amd-gpu-mx51.inc contains:
>
> # FIXME: All binaries lack GNU_HASH in elf binary but as we don't have
> # the source we cannot fix it. Disable the insane check for now.
> python populate_packages_prepend() {
>     for p in d.getVar('PACKAGES', True).split():
>         d.setVar("INSANE_SKIP_%s" % p, "ldflags")
> }
>
> and with the recent change that merged to make package QA a separate
> task, this no longer works. I'd suggest you change this to:
>
> python {
>     for p in d.getVar('PACKAGES', True).split():
>         d.setVar("INSANE_SKIP_%s" % p, "ldflags")
> }
>
> which should fix the issue. Doing that as a populate_packages prepend
> wasn't the nicest of things to be doing in the first place.

Ok; I will change those to anonymous.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

meta-fsl-arm build failure

[Richard Purdie]

I've been running tests on the autobuilder for B != S and there are some
issues in the meta-fsl-arm layer:

http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm/builds/91

Specifically:

nightly-fsl-arm/build/meta-fsl-arm/recipes-bsp/mxsldr/mxsldr_git.bb
nightly-fsl-arm/build/meta-fsl-arm/recipes-graphics/xorg-driver/xf86-video-imxfb-vivante_3.10.17-1.0.0.bb

both probably need to inherit autotools-brokensep instead of autotools
as an untested guess.

Cheers,

Richard

Re: meta-fsl-arm build failure

[Otavio Salvador]

[-- Attachment #1: Type: text/plain, Size: 819 bytes --]

On Mon, Mar 17, 2014 at 6:30 AM, Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:
> I've been running tests on the autobuilder for B != S and there are some
> issues in the meta-fsl-arm layer:
>
>
http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm/builds/91
>
> Specifically:
>
> nightly-fsl-arm/build/meta-fsl-arm/recipes-bsp/mxsldr/mxsldr_git.bb
> nightly-fsl-arm/build/meta-fsl-arm/recipes-graphics/xorg-driver/
xf86-video-imxfb-vivante_3.10.17-1.0.0.bb
>
> both probably need to inherit autotools-brokensep instead of autotools
> as an untested guess.

Your guesses were right; I did both and I should push them tomorrow.

-- 
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750

[-- Attachment #2: Type: text/html, Size: 1315 bytes --]

Re: meta-fsl-arm build failure

[Richard Purdie]

On Mon, 2014-03-17 at 20:14 -0300, Otavio Salvador wrote:
> On Mon, Mar 17, 2014 at 6:30 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > I've been running tests on the autobuilder for B != S and there are
> some
> > issues in the meta-fsl-arm layer:
> >
> >
> http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm/builds/91
> >
> > Specifically:
> >
> > nightly-fsl-arm/build/meta-fsl-arm/recipes-bsp/mxsldr/mxsldr_git.bb
> >
> nightly-fsl-arm/build/meta-fsl-arm/recipes-graphics/xorg-driver/xf86-video-imxfb-vivante_3.10.17-1.0.0.bb
> >
> > both probably need to inherit autotools-brokensep instead of
> autotools
> > as an untested guess.
> 
> Your guesses were right; I did both and I should push them tomorrow.

Thanks :)

Cheers,

Richard