All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Daniel Dragomir <daniel.dragomir@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] gcc-runtime: Remove libgfortran data from receipe
Date: Thu, 15 Jan 2015 16:40:29 +0000	[thread overview]
Message-ID: <1421340029.18703.0.camel@linuxfoundation.org> (raw)
In-Reply-To: <1421339471-11486-1-git-send-email-daniel.dragomir@windriver.com>

On Thu, 2015-01-15 at 18:31 +0200, Daniel Dragomir wrote:
> Remove libgfortran packages from PACKAGES list and skip them at compiling
> and installing as long as libgfortran has separate receipe since commit
> 
> 5bde5d9b39ea67f19a1a6aedd0c08c6cfedcbe5f
> gcc: Allow fortran to build successfully in 4.8
> 
> Otherwise, when fortran support will be enabled in the compiler, both
> lingfortran and gcc-runtime receipes will create the same files and will
> try to install them. This will cause errors:
> 
> ERROR: The recipe libgfortran is trying to install files into a shared
> area when those files already exist. Those files and their manifest
> location are: ...
> Please verify which recipe should provide the above files.
> 
> Signed-off-by: Daniel Dragomir <daniel.dragomir@windriver.com>
> ---
>  meta/recipes-devtools/gcc/gcc-runtime.inc | 41 ++++++++++++-------------------
>  1 file changed, 16 insertions(+), 25 deletions(-)
> 
> diff --git a/meta/recipes-devtools/gcc/gcc-runtime.inc b/meta/recipes-devtools/gcc/gcc-runtime.inc
> index 167869e..c3b4a46 100644
> --- a/meta/recipes-devtools/gcc/gcc-runtime.inc
> +++ b/meta/recipes-devtools/gcc/gcc-runtime.inc
> @@ -22,28 +22,34 @@ do_configure () {
>  	target=`echo ${TARGET_SYS} | sed -e s#-${SDKPKGSUFFIX}##`
>  	hardlinkdir ${STAGING_INCDIR_NATIVE}/gcc-build-internal-$mtarget ${B}
>  	for d in libgcc ${RUNTIMETARGET}; do
> -		echo "Configuring $d"
> -		rm -rf ${B}/$target/$d/
> -		mkdir -p ${B}/$target/$d/
> -		cd ${B}/$target/$d/
> -		chmod a+x ${S}/$d/configure
> -		${S}/$d/configure ${CONFIGUREOPTS} ${EXTRA_OECONF}
> +		if [ "$d" != "libgfortran" ]; then

Why would libgfortran be in RUNTIMETARGET? Surely it would be better
just to ensure it isn't rather than ignore it?

Cheers,

Richard

> +			echo "Configuring $d"
> +			rm -rf ${B}/$target/$d/
> +			mkdir -p ${B}/$target/$d/
> +			cd ${B}/$target/$d/
> +			chmod a+x ${S}/$d/configure
> +			${S}/$d/configure ${CONFIGUREOPTS} ${EXTRA_OECONF}
> +		fi
>  	done
>  }
>  
>  do_compile () {
>  	target=`echo ${TARGET_SYS} | sed -e s#-${SDKPKGSUFFIX}##`
>  	for d in libgcc ${RUNTIMETARGET}; do
> -		cd ${B}/$target/$d/
> -		oe_runmake MULTIBUILDTOP=${B}/$target/$d/
> +		if [ "$d" != "libgfortran" ]; then
> +			cd ${B}/$target/$d/
> +			oe_runmake MULTIBUILDTOP=${B}/$target/$d/
> +		fi
>  	done
>  }
>  
>  do_install () {
>  	target=`echo ${TARGET_SYS} | sed -e s#-${SDKPKGSUFFIX}##`
>  	for d in ${RUNTIMETARGET}; do
> -		cd ${B}/$target/$d/
> -		oe_runmake 'DESTDIR=${D}' MULTIBUILDTOP=${B}/$target/$d/ install
> +		if [ "$d" != "libgfortran" ]; then
> +			cd ${B}/$target/$d/
> +			oe_runmake 'DESTDIR=${D}' MULTIBUILDTOP=${B}/$target/$d/ install
> +		fi
>  	done
>  	rm -rf ${D}${infodir}/libgomp.info ${D}${infodir}/dir
>  	rm -rf ${D}${infodir}/libquadmath.info ${D}${infodir}/dir
> @@ -76,9 +82,6 @@ PACKAGES = "\
>      libssp \
>      libssp-dev \
>      libssp-staticdev \
> -    libgfortran \
> -    libgfortran-dev \
> -    libgfortran-staticdev \
>      libmudflap \
>      libmudflap-dev \
>      libmudflap-staticdev \
> @@ -131,18 +134,6 @@ FILES_libssp-dev = "\
>  "
>  FILES_libssp-staticdev = "${libdir}/libssp*.a"
>  
> -FILES_libgfortran = "${libdir}/libgfortran.so.*"
> -FILES_libgfortran-dev = "\
> -    ${libdir}/libgfortran*.so \
> -    ${libdir}/libgfortran.spec \
> -    ${libdir}/libgfortran.la \
> -    ${libdir}/gcc/${TARGET_SYS}/${BINV}/libgfortranbegin.* \
> -    ${libdir}/gcc/${TARGET_SYS}/${BINV}/libcaf_single* \
> -"
> -FILES_libgfortran-staticdev = "${libdir}/libgfortran.a"
> -
> -INSANE_SKIP_${MLPREFIX}libgfortran-dev = "staticdev"
> -
>  FILES_libquadmath = "${libdir}/libquadmath*.so.*"
>  FILES_libquadmath-dev = "\
>      ${libdir}/gcc/${TARGET_SYS}/${BINV}/include/quadmath* \
> -- 
> 1.8.1.4
> 




  reply	other threads:[~2015-01-15 16:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-15 16:31 [PATCH] gcc-runtime: Remove libgfortran data from receipe Daniel Dragomir
2015-01-15 16:40 ` Richard Purdie [this message]
2015-01-16 18:31   ` Dragomir, Daniel
2015-01-16 23:32     ` Richard Purdie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1421340029.18703.0.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=daniel.dragomir@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.