From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFT] GCC 4.8 recipes
Date: Thu, 28 Mar 2013 17:49:59 +0000 [thread overview]
Message-ID: <1364492999.28471.166.camel@ted> (raw)
In-Reply-To: <658D26C6-1631-456F-BD30-320466130D6C@gmail.com>
On Thu, 2013-03-28 at 09:07 -0700, Khem Raj wrote:
> On Mar 28, 2013, at 8:46 AM, Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org> wrote:
>
> > 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.
>
>
> Nice
>
> >
> > Problem was with paths - lib contra lib64. Will look at it more next week.
> >
> > <aarch64.diff>
>
>
> Well I guess aarch64 is kind of_special_ here. look into multilib we have done
> for other architectures. e.g. for x86_64 if you inherit multilib class it uses 'lib64'
> otherwise it uses 'lib' thats for historic reasons but for arm you could always use lib64
> why its not so ?
The build system should use whichever is configured as $libdir for any
given target.
Cheers,
Richard
next prev parent reply other threads:[~2013-03-28 18:07 UTC|newest]
Thread overview: 29+ 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
2013-03-28 16:07 ` Khem Raj
2013-03-28 17:49 ` Richard Purdie [this message]
2013-03-29 8:13 ` Elvis Dowson
2013-03-29 8:13 ` [OE-core] " Elvis Dowson
2013-03-29 8:18 ` Khem Raj
2013-03-29 8:18 ` [OE-core] " Khem Raj
2013-03-29 14:55 ` Martin Jansa
2013-03-29 14:55 ` [OE-core] " Martin Jansa
2013-03-30 9:03 ` Martin Jansa
2013-03-30 9:03 ` [OE-core] " Martin Jansa
2013-04-01 9:52 ` Martin Jansa
2013-04-01 9:52 ` [OE-core] " Martin Jansa
2013-04-02 14:22 ` Khem Raj
2013-04-02 14:22 ` [OE-core] " Khem Raj
2013-04-20 0:32 ` Khem Raj
2013-04-20 0:32 ` [OE-core] " Khem Raj
2013-05-10 12:53 ` Martin Jansa
2013-05-10 12:53 ` [OE-core] " 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
2013-04-11 14:23 ` [RFT] GCC 4.8 recipes Jack Mitchell
2013-04-15 2:14 ` 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=1364492999.28471.166.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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.