From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC] Fix libgcc nativesdk to install libgcc.a in good location for tools
Date: Fri, 28 Oct 2011 10:03:41 +0100 [thread overview]
Message-ID: <1319792621.22423.7.camel@ted> (raw)
In-Reply-To: <1319684838-24527-1-git-send-email-msm@freescale.com>
On Wed, 2011-10-26 at 22:07 -0500, Matthew McClintock wrote:
> This fixes an issue where we cannot find -lgcc when linking. We
> update the path to libgcc.a so the library can be installed
> correctly
>
> Signed-off-by: Matthew McClintock <msm@freescale.com>
> ---
> I really doubt this is the correct fix and I'm no expert but it's
> here for comments. This fixes a real u-boot cross compile build
> issue
This patch looks very very confused to me. Firstly your subject summary
talks about libgcc-nativesdk. This is the compiler used to generate
binaries for SDKMACHINE so I seriously doubt you're using nativesdk to
build uboot.
> The previous mv command was failing as the files did not exist
> and I also rejiggered the packages since I was not sure if
> gdb-cross-canadian-powerpc-dev was included in my tarball of
> the toolchain
>
> meta/recipes-devtools/gcc/libgcc_4.6.bb | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/meta/recipes-devtools/gcc/libgcc_4.6.bb b/meta/recipes-devtools/gcc/libgcc_4.6.bb
> index 63a46ec..7f3ac55 100644
> --- a/meta/recipes-devtools/gcc/libgcc_4.6.bb
> +++ b/meta/recipes-devtools/gcc/libgcc_4.6.bb
> @@ -8,9 +8,8 @@ PACKAGES = "\
> ${PN}-dev \
> "
>
> -FILES_${PN} = "${base_libdir}/libgcc*.so.*"
> +FILES_${PN} = "${base_libdir}/libgcc*"
This is changing the packging of libgcc too, not just libgcc-nativesdk.
It is not correct to be putting the dynamic linking symlinks in anything
but the -dev package so the above and the line below are therefore wrong
too.
> FILES_${PN}-dev = " \
> - ${base_libdir}/libgcc*.so \
> ${libdir}/${TARGET_SYS}/${BINV}/crt* \
> ${libdir}/${TARGET_SYS}/${BINV}/libgcc*"
>
> @@ -29,9 +28,10 @@ do_install () {
> if [ -f ${D}${libdir}/nof/libgcc_s.so ]; then
> mv ${D}${libdir}/nof/libgcc* ${D}${base_libdir}
> else
> - mv ${D}${libdir}/libgcc* ${D}${base_libdir} || true
> + cp ${D}${libdir}/${TARGET_SYS}/${BINV}/libgcc* ${D}${base_libdir}
> fi
Equally, you're moving a static library from the -dev package into the
main package which is wrong, you only need that if you're doing
development.
Are you sure your problem is not that you didn't have the libgcc-dev
package installed?
Cheers,
Richard
next prev parent reply other threads:[~2011-10-28 9:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 4:20 finding libgcc.a with meta-toolchain-sdk toolchain Kumar Gala
2011-08-10 6:54 ` Khem Raj
2011-08-10 9:19 ` Phil Blundell
2011-08-10 12:43 ` Kumar Gala
2011-08-10 12:50 ` Phil Blundell
2011-10-27 3:07 ` [RFC] Fix libgcc nativesdk to install libgcc.a in good location for tools Matthew McClintock
2011-10-27 3:40 ` James Limbouris
2011-10-27 4:20 ` McClintock Matthew-B29882
2011-10-28 9:03 ` Richard Purdie [this message]
2011-10-28 19:35 ` McClintock Matthew-B29882
2011-10-28 19:36 ` McClintock Matthew-B29882
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=1319792621.22423.7.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox