[meta-freescale] : Re: glibc configure fails with e5500 / t1040 on master

[Beaman, Thomas]

> -----Original Message-----
> From: meta-freescale-bounces at yoctoproject.org [mailto:meta-freescale-
> bounces at yoctoproject.org] On Behalf Of meta-freescale-
> request at yoctoproject.org
> Sent: Saturday, January 19, 2019 3:00 PM
> To: meta-freescale at yoctoproject.org
> Subject: meta-freescale Digest, Vol 75, Issue 14
> 
> Message: 1
> Date: Fri, 18 Jan 2019 21:43:07 +0000
> From: "Lautenschlager (US), David C"
> 	<David.C.Lautenschlager at boeing.com>
> To: "C.r. Guo" <chunrong.guo at nxp.com>, Bob Cochran
> 	<yocto at mindchasers.com>,	"meta-freescale at yoctoproject.org"
> 	<meta-freescale at yoctoproject.org>
> Subject: Re: [meta-freescale] glibc configure fails with e5500 /	t1040
> 	on	master...
> Message-ID: <16e134ccf5d14cb1bb7e29169e1ecddb at boeing.com>
> Content-Type: text/plain; charset="utf-8"
> 

David,  I had this same problem and was able to successfully apply the patch using a glibc_2.28.bbappend file in my custom layer.

The glibc_2.28.bbappend file just needs this in it.
cat glibc_2.28.bbappend

FILESEXTRAPATHS_prepend := "${THISDIR}/glibc:"

SRC_URI += "file://0001-glibc-support-e5500-and-e6500.patch \
"

And the patch file goes in a glibc directory at the same level
ls *
glibc_2.28.bbappend

glibc:
0001-glibc-support-e5500-and-e6500.patch

Tom 

> I found a patch file from each of your links, however I am still trying to figure
> out how to use the patch file to patch my build. I know how to use the patch
> command, but I don't know when/where to run it on a poky-thud set of files
> to produce a successful build.
> 
> David
> 
> -----Original Message-----
> From: C.r. Guo [mailto:chunrong.guo at nxp.com]
> Sent: Thursday, January 17, 2019 8:23 PM
> To: Lautenschlager (US), David C <David.C.Lautenschlager at boeing.com>;
> Bob Cochran <yocto at mindchasers.com>; meta-freescale at yoctoproject.org
> Subject: RE: [meta-freescale] glibc configure fails with e5500 / t1040 on
> master...
> 
> Please see
> https://patchwork.openembedded.org/patch/157986/
> 
> Thanks
> Chunrong
>