From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [2011.03-maintenance] Problem building gcc
Date: Thu, 28 Jul 2011 09:38:53 +0200 [thread overview]
Message-ID: <j0r3md$jq5$1@dough.gmane.org> (raw)
In-Reply-To: <4E3104D3.7050702@dresearch-fe.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 28-07-11 08:42, Steffen Sledz schreef:
> I've problems building gcc from the 2011.03-maintenance branch. The do_install step fails with
>
> | + mv '/home/sledz/work/angstrom-setup-scripts/build/tmp-angstrom_2008_1/work/armv7a-angstrom-linux-gnueabi/gcc-4.3.3-r24.1/image/usr/lib/libstdc++.so.*-gdb.py*'
> /home/sledz/work/angstrom-setup-scripts/build/tmp-angstrom_2008_1/work/armv7a-angstrom-linux-gnueabi/gcc-4.3.3-r24.1/image/usr/share/gdb/auto-load/usr/lib | mv: cannot stat
> `/home/sledz/work/angstrom-setup-scripts/build/tmp-angstrom_2008_1/work/armv7a-angstrom-linux-gnueabi/gcc-4.3.3-r24.1/image/usr/lib/libstdc++.so.*-gdb.py*': No such file or directory NOTE: package gcc-4.3.3-r24.1: task do_install: Failed ERROR: Function 'do_install' failed (see
> /home/sledz/work/angstrom-setup-scripts/build/tmp-angstrom_2008_1/work/armv7a-angstrom-linux-gnueabi/gcc-4.3.3-r24.1/temp/log.do_install.14408 for further information) ERROR: Task 2 (/home/sledz/work/angstrom-setup-scripts/sources/openembedded/recipes/gcc/gcc_4.3.3.bb, do_install) failed with
> exit code '1' ERROR: '/home/sledz/work/angstrom-setup-scripts/sources/openembedded/recipes/gcc/gcc_4.3.3.bb' failed
>
> A way to reproduce the problem is using the current Ångström oebb.sh script:
>
> MACHINE=beagleboard ./oebb.sh bitbake gcc
>
> My build host is running a 64-bit openSUSE 11.4.
>
Can you try:
diff --git a/recipes/gcc/gcc-package-target.inc b/recipes/gcc/gcc-package-target.inc
index 33567da..7d3f4ae 100644
- --- a/recipes/gcc/gcc-package-target.inc
+++ b/recipes/gcc/gcc-package-target.inc
@@ -171,5 +171,5 @@ GROUP ( libgcc_s.so.1 libgcc.a )" > ${D}${libdir}/libgcc_s.so
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}
+ mv ${D}${libdir}/libstdc++.so.*-gdb.py* ${D}${datadir}/gdb/auto-load${libdir} || true
}
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFOMRINMkyGM64RGpERAmHUAJ9ujUhTt4aw9jT49EaNRY7cUuD7hgCeOsBJ
vcTtJYmXd5igGAygUTQr5Og=
=nwkq
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-07-28 7:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 6:42 [2011.03-maintenance] Problem building gcc Steffen Sledz
2011-07-28 7:38 ` Koen Kooi [this message]
2011-07-28 8:25 ` Steffen Sledz
2011-07-28 15:23 ` Khem Raj
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='j0r3md$jq5$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--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.