Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [RFT] GCC 4.8 recipes
Date: Thu, 28 Mar 2013 16:46:22 +0100	[thread overview]
Message-ID: <515465CE.6080803@linaro.org> (raw)
In-Reply-To: <51540716.40400@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 439 bytes --]

W dniu 28.03.2013 10:02, Marcin Juszkiewicz pisze:
> W dniu 28.03.2013 06:51, Khem Raj pisze:
>> I have added gcc 4.8 recipes and the branch is here 
>>
>> git://git.openembedded.org/openembedded-core-contrib kraj/gcc-4.8
> 
> Übercool! Will do tests with aarch64.

After some hacking (see attachment) I got it built and booted
core-image-minimal.

Problem was with paths - lib contra lib64. Will look at it more next week.


[-- Attachment #2: aarch64.diff --]
[-- Type: text/x-diff, Size: 1492 bytes --]

diff --git a/meta/recipes-devtools/gcc/gcc-package-runtime.inc b/meta/recipes-devtools/gcc/gcc-package-runtime.inc
index 2e2f75a..39f053c 100644
--- a/meta/recipes-devtools/gcc/gcc-package-runtime.inc
+++ b/meta/recipes-devtools/gcc/gcc-package-runtime.inc
@@ -78,3 +78,13 @@ FILES_libgomp-staticdev = "\
 do_package_write_ipk[depends] += "virtual/${MLPREFIX}libc:do_packagedata"
 do_package_write_deb[depends] += "virtual/${MLPREFIX}libc:do_packagedata"
 do_package_write_rpm[depends] += "virtual/${MLPREFIX}libc:do_packagedata"
+
+do_install_append_aarch64() {
+
+    if [ -d ${D}${libdir}64 ]; then
+        mv ${D}${libdir}64/* ${D}${libdir}
+    fi
+    if [ -d ${D}${libdir}64/.debug ]; then
+        mv ${D}${libdir}64/.debug ${D}${libdir}/.debug
+    fi
+}
diff --git a/meta/recipes-devtools/gcc/libgcc_4.8.bb b/meta/recipes-devtools/gcc/libgcc_4.8.bb
index 47669a2..51ed2ff 100644
--- a/meta/recipes-devtools/gcc/libgcc_4.8.bb
+++ b/meta/recipes-devtools/gcc/libgcc_4.8.bb
@@ -51,7 +51,11 @@ 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
+        if [ -f ${D}${libdir}64/libgcc_s.so ]; then
+            mv ${D}${libdir}64/libgcc* ${D}${base_libdir}
+        else
+            mv ${D}${libdir}64/libgcc* ${D}${base_libdir} || true
+        fi
 	fi
 
 	# install the runtime in /usr/lib/ not in /usr/lib/gcc on target

  reply	other threads:[~2013-03-28 16:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-28  5:51 [RFT] GCC 4.8 recipes Khem Raj
2013-03-28  7:36 ` Yi Qingliang
2013-03-28  8:29   ` Koen Kooi
2013-03-28  9:49     ` Yi Qingliang
2013-03-28  9:02 ` Marcin Juszkiewicz
2013-03-28 15:46   ` Marcin Juszkiewicz [this message]
2013-03-28 16:07     ` Khem Raj
2013-03-28 17:49       ` Richard Purdie
2013-03-29  8:13 ` Elvis Dowson
2013-03-29  8:18   ` Khem Raj
2013-03-29 14:55 ` Martin Jansa
2013-03-30  9:03   ` Martin Jansa
2013-04-01  9:52     ` Martin Jansa
2013-04-02 14:22       ` Khem Raj
2013-04-20  0:32         ` Khem Raj
2013-05-10 12:53           ` Martin Jansa
2013-05-14 16:29             ` [RFC][PATCH] gcc-4.8: temporary disable thumb Martin Jansa
2013-05-14 21:14               ` Khem Raj
2013-09-18 23:58               ` [PATCH] " Martin Jansa

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=515465CE.6080803@linaro.org \
    --to=marcin.juszkiewicz@linaro.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