All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: hjl.tools@gmail.com
Subject: Re: [PATCH 00/11] recipe fixes for x32 toolchain
Date: Mon, 05 Dec 2011 22:47:55 +0000	[thread overview]
Message-ID: <1323125275.25960.105.camel@ted> (raw)
In-Reply-To: <cover.1322856805.git.nitin.a.kamble@intel.com>

On Fri, 2011-12-02 at 12:19 -0800, nitin.a.kamble@intel.com wrote:
> From: Nitin A Kamble <nitin.a.kamble@intel.com>
> 
> These commits fixes building of various recipes with x32 toolchain
> for x32 target/machines. And these do not affect these recipes for
> other non-x32 targets.
> 
> X32 is new ABI for x86-64 architecture.
> For more information refer: https://sites.google.com/site/x32abi/
> 
> Thanks,
> Nitin
> 
> The following changes since commit 9be6d59b78510443d0944513503d515df13caa45:
> 
>   dpkg-native: Fix perl path (2011-12-02 15:31:08 +0000)
> 
> are available in the git repository at:
>   git://git.pokylinux.org/poky-contrib nitin/x32
>   http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin.x32
> 
> Nitin A Kamble (11):
>   gst-fluendo-mpegdemux: rework the CC hack
>   mdadm: fix CC definition in the Makefile

There was some feedback on these which I haven't looked into fully.

>   openssl-1.0.0e: fix to wotk with x32 toolchain
>   gmp: fix the recipe for x32 target
>   mesa-dri, mesa-xlib: fix compilation with x32 toolchain
>   glib-2.0: fix compilatoin with x32 toolchain
>   libxt: fix compilatoin with x32 toolchain
>   liboil: patch source code for x32
>   xproto: fix compilation with x32 toolchain
>   libaio: patch source code for x32
>   libatomics-ops: patch source code for x32

These looked reasonable so I've merged them, thanks.

Richard




      parent reply	other threads:[~2011-12-05 22:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02 20:19 [PATCH 00/11] recipe fixes for x32 toolchain nitin.a.kamble
2011-12-02 20:19 ` [PATCH 01/11] gst-fluendo-mpegdemux: rework the CC hack nitin.a.kamble
2011-12-03 17:53   ` Khem Raj
2011-12-05 16:59     ` Kamble, Nitin A
2011-12-02 20:20 ` [PATCH 02/11] mdadm: fix CC definition in the Makefile nitin.a.kamble
2011-12-03 18:08   ` Paul Menzel
2011-12-05 16:58     ` Kamble, Nitin A
2011-12-02 20:20 ` [PATCH 03/11] openssl-1.0.0e: fix to wotk with x32 toolchain nitin.a.kamble
2011-12-02 20:20 ` [PATCH 04/11] gmp: fix the recipe for x32 target nitin.a.kamble
2011-12-02 20:20 ` [PATCH 05/11] mesa-dri, mesa-xlib: fix compilation with x32 toolchain nitin.a.kamble
2011-12-02 20:20 ` [PATCH 06/11] glib-2.0: fix compilatoin " nitin.a.kamble
2011-12-02 20:20 ` [PATCH 07/11] libxt: " nitin.a.kamble
2011-12-02 20:20 ` [PATCH 08/11] liboil: patch source code for x32 nitin.a.kamble
2011-12-02 20:20 ` [PATCH 09/11] xproto: fix compilation with x32 toolchain nitin.a.kamble
2011-12-02 20:20 ` [PATCH 10/11] libaio: patch source code for x32 nitin.a.kamble
2011-12-02 20:20 ` [PATCH 11/11] libatomics-ops: " nitin.a.kamble
2011-12-05 22:47 ` Richard Purdie [this message]

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=1323125275.25960.105.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=hjl.tools@gmail.com \
    --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 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.