From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] gcc: Package libstdc++ gdb python helpers into dev package
Date: Fri, 22 Jul 2011 13:24:45 -0400 [thread overview]
Message-ID: <4E29B25D.8030503@balister.org> (raw)
In-Reply-To: <1307648104-24260-1-git-send-email-raj.khem@gmail.com>
On 06/09/2011 03:35 PM, Khem Raj wrote:
> People are seeing these errrors from ldconfig
> libstdc++.so.6.0.14-gdb.py is not an ELF file - it has the wrong magic
> bytes at the start.
>
> this file is moved into gdb's autoload directory
> if it exists there then gdb will find it when debugging
> and it wont be in the paths where ldconfig looks for
> libraries.
>
> Signed-off-by: Khem Raj<raj.khem@gmail.com>
Finally,
Tested-by: Philip Balister <philip@balister.org>
No more annoying message when I run ldconfig. Getting this fix in will
reduce my support emails by a small, but noticeable amount.
Philip
> ---
> recipes/gcc/gcc-4.5.inc | 2 +-
> recipes/gcc/gcc-package-cross.inc | 8 +++++++-
> recipes/gcc/gcc-package-target.inc | 4 ++++
> 3 files changed, 12 insertions(+), 2 deletions(-)
>
> diff --git a/recipes/gcc/gcc-4.5.inc b/recipes/gcc/gcc-4.5.inc
> index aa5bb00..69229ef 100644
> --- a/recipes/gcc/gcc-4.5.inc
> +++ b/recipes/gcc/gcc-4.5.inc
> @@ -8,7 +8,7 @@ DEPENDS = "mpfr gmp libmpc libelf"
> NATIVEDEPS = "mpfr-native gmp-native libmpc-native"
>
>
> -INC_PR = "r36"
> +INC_PR = "r37"
>
> SRCREV = "170880"
> PV = "4.5"
> diff --git a/recipes/gcc/gcc-package-cross.inc b/recipes/gcc/gcc-package-cross.inc
> index f9a7eeb..1533069 100644
> --- a/recipes/gcc/gcc-package-cross.inc
> +++ b/recipes/gcc/gcc-package-cross.inc
> @@ -4,7 +4,7 @@ PACKAGE_STRIP = "no"
>
> SHLIBSDIR = "${STAGING_DIR_TARGET}/shlibs"
>
> -PACKAGES = "libgcc libssp libstdc++ libg2c libgfortran"
> +PACKAGES = "libgcc libssp libstdc++ libg2c libgfortran libstdc++-dev libgcc-dev"
>
> # Called from within gcc-cross, so libdir is set wrong
> FILES_libg2c = "${target_libdir}/libg2c.so.*"
> @@ -18,6 +18,7 @@ FILES_libgcc-dev = "${target_libdir}/libgcc_s.so"
>
> FILES_libstdc++ = "${target_libdir}/libstdc++.so.*"
>
> +FILES_libstdc++-dev = "${target_datadir}/gdb/auto-load/${libdir}/libstdc++.so.*-gdb.py*"
> do_install () {
> oe_runmake 'DESTDIR=${D}' install
> install -d ${D}${target_base_libdir}
> @@ -68,5 +69,10 @@ GROUP ( libgcc_s.so.1 libgcc.a )"> ${D}${target_libdir}/libgcc_s.so
> # We use libiberty from binutils or binutils-cross
> rm -f ${D}${libdir}/libiberty.a
> rm -f ${D}${target_libdir}/libiberty.a
> + if [ -f ${D}${target_libdir}/libstdc++.so.*-gdb.py ]; then
> + # move the gdb python helpers to gdb auto-load directory
> + install -d ${D}${target_datadir}/gdb/auto-load${target_libdir}
> + mv -f ${D}${target_libdir}/libstdc++.so.*-gdb.py* ${D}${target_datadir}/gdb/auto-load${target_libdir}
> + fi
> }
>
> diff --git a/recipes/gcc/gcc-package-target.inc b/recipes/gcc/gcc-package-target.inc
> index 5cfe47b..959b9ec 100644
> --- a/recipes/gcc/gcc-package-target.inc
> +++ b/recipes/gcc/gcc-package-target.inc
> @@ -83,6 +83,7 @@ FILES_libstdc++-dev = "\
> ${libdir}/libsupc++.la \
> ${libdir}/libsupc++.a \
> "
> +FILES_libstdc++-dev += "${datadir}/gdb/auto-load/${libdir}/libstdc++.so.*-gdb.py*"
>
> FILES_libgfortran-dev = "${libdir}/libgfortran.a \
> ${libdir}/libgfortran.so \
> @@ -168,4 +169,7 @@ GROUP ( libgcc_s.so.1 libgcc.a )"> ${D}${libdir}/libgcc_s.so
>
> # Remove precompiled c++ headers as they are really big
> rm -rf ${D}${includedir}/c++/${BINV}/${TARGET_SYS}/bits/*.gch
> + # move the gdb python helpers to gdb auto-load directory
> + install -d ${D}${datadir}/gdb/auto-load/${libdir}
> + mv ${D}${libdir}/libstdc++.so.*-gdb.py* ${D}${datadir}/gdb/auto-load${libdir}
> }
next prev parent reply other threads:[~2011-07-22 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 19:35 [PATCH] gcc: Package libstdc++ gdb python helpers into dev package Khem Raj
2011-07-22 17:24 ` Philip Balister [this message]
2011-07-22 20:21 ` Khem Raj
2011-07-23 15:09 ` Chris Verges
2011-07-23 15:59 ` Philip Balister
2011-07-23 18:15 ` Koen Kooi
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=4E29B25D.8030503@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@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.