[OE-core] [PATCH 1/2] glibc-initial.inc: use relative path to run configure

[Trevor Woerner]

On 01/11/16 00:11, Robert Yang wrote:
> Avoid potential build path in output files.
>
> [YOCTO #8894]
>
> Signed-off-by: Robert Yang <liezhi.yang at windriver.com>
> ---
>  meta/recipes-core/glibc/glibc-initial.inc |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/glibc/glibc-initial.inc b/meta/recipes-core/glibc/glibc-initial.inc
> index 8e81f09..cb2f8dd 100644
> --- a/meta/recipes-core/glibc/glibc-initial.inc
> +++ b/meta/recipes-core/glibc/glibc-initial.inc
> @@ -11,7 +11,7 @@ TOOLCHAIN_OPTIONS = " --sysroot=${STAGING_DIR_TCBOOTSTRAP}"
>  do_configure () {
>  	(cd ${S} && gnu-configize) || die "failure in running gnu-configize"
>  	find ${S} -name "configure" | xargs touch
> -	${S}/configure --host=${TARGET_SYS} --build=${BUILD_SYS} \
> +	../git/configure --host=${TARGET_SYS} --build=${BUILD_SYS} \

Although I haven't tested it, this _looks_ like it might fail quite
readily. I'm sure there are some recipes that play tricks with ${S}, and
what about recipes that don't pull their sources from git?

Maybe something like: (cd ${S} && ./configure ...) would be better?

>  		--prefix=/usr \
>  		--without-cvs --disable-sanity-checks \
>  		--with-headers=${STAGING_DIR_TARGET}${includedir} \