From: Saul Wold <saul.wold@intel.com>
To: "Kamble, Nitin A" <nitin.a.kamble@intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/6] gmp: also generate the libgmpcxx library
Date: Fri, 21 Oct 2011 00:54:40 -0700 [thread overview]
Message-ID: <4EA12540.9020002@intel.com> (raw)
In-Reply-To: <9DA5872FEF993D41B7173F58FCF6BE94E32D2390@orsmsx504.amr.corp.intel.com>
On 10/20/2011 11:04 PM, Kamble, Nitin A wrote:
>
>
>> -----Original Message-----
>> From: Saul Wold [mailto:saul.wold@intel.com]
>> Sent: Thursday, October 20, 2011 12:50 AM
>> To: Patches and discussions about the oe-core layer
>> Cc: Kamble, Nitin A
>> Subject: Re: [OE-core] [PATCH 2/6] gmp: also generate the libgmpcxx
>> library
>>
>> On 10/18/2011 05:30 PM, nitin.a.kamble@intel.com wrote:
>>> From: Nitin A Kamble<nitin.a.kamble@intel.com>
>>>
>>> configure runs few checks to make sure c++ compiler and runtime are
>> working as expected
>>> with the --enable-cxx=detect option.
>>>
>> Somehow this change has also changed what the gmp package provides,
>> before this change the package provided libgmp10 via PKG_gmp: libgmp10,
>> after this change, the libgmp10 is no longer provided and causes other
>> breakage.
>>
>> The example case I found was a coreutils package that was built prior
>> to
>> this change failed to fulfill it's dependencies after this change when
>> creating an image. If I rebuild coreutils with the newer gmp build,
>> then all is well, I think we need to understand this better before
>> making this change.
>>
>> Did something else change in the packaging that would cause use to look
>> the mapping above?
>>
> Saul,
> In my testing I did not get any of these issues you mentioned above.
>
> Also I tried to reproduce the issue with coreutils as mentioned above, and I can not reproduce the issue for creations of an image. Can you verify the issue one more time?
>
Just to confirm, did you have a build of coreutils prior to your gmp
changes? Which image did you build? Be sure you build an image that
includes coreutils, such at an -sdk image.
I can easily reproduce this issue.
Sau!
> Thanks,
> Nitin
>
>>
>> Sau!
>>
>>
>>> Signed-off-by: Nitin A Kamble<nitin.a.kamble@intel.com>
>>> ---
>>> meta/recipes-support/gmp/gmp.inc | 2 ++
>>> meta/recipes-support/gmp/gmp_4.2.1.bb | 2 +-
>>> meta/recipes-support/gmp/gmp_5.0.2.bb | 2 +-
>>> 3 files changed, 4 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/meta/recipes-support/gmp/gmp.inc b/meta/recipes-
>> support/gmp/gmp.inc
>>> index 66349e6..3c662a0 100644
>>> --- a/meta/recipes-support/gmp/gmp.inc
>>> +++ b/meta/recipes-support/gmp/gmp.inc
>>> @@ -14,3 +14,5 @@ ARM_INSTRUCTION_SET = "arm"
>>> acpaths = ""
>>>
>>> BBCLASSEXTEND = "native nativesdk"
>>> +
>>> +EXTRA_OECONF += " --enable-cxx=detect"
>>> diff --git a/meta/recipes-support/gmp/gmp_4.2.1.bb b/meta/recipes-
>> support/gmp/gmp_4.2.1.bb
>>> index 74da6b8..97ac4b2 100644
>>> --- a/meta/recipes-support/gmp/gmp_4.2.1.bb
>>> +++ b/meta/recipes-support/gmp/gmp_4.2.1.bb
>>> @@ -6,7 +6,7 @@ LICENSE = "LGPLv2.1+"
>>> LIC_FILES_CHKSUM =
>> "file://COPYING;md5=892f569a555ba9c07a568a7c0c4fa63a \
>>>
>> file://COPYING.LIB;md5=fbc093901857fcd118f065f900982c24 \
>>> file://gmp-
>> h.in;startline=6;endline=21;md5=5e25ffd16996faba8c1cd27b04b16099"
>>> -PR = "r0"
>>> +PR = "r1"
>>>
>>> SRC_URI = "${GNU_MIRROR}/gmp/${BP}.tar.bz2 \
>>> file://disable-stdc.patch"
>>> diff --git a/meta/recipes-support/gmp/gmp_5.0.2.bb b/meta/recipes-
>> support/gmp/gmp_5.0.2.bb
>>> index 03fef45..f80971e 100644
>>> --- a/meta/recipes-support/gmp/gmp_5.0.2.bb
>>> +++ b/meta/recipes-support/gmp/gmp_5.0.2.bb
>>> @@ -2,7 +2,7 @@ require gmp.inc
>>> LICENSE="LGPLv3&GPLv3"
>>> LIC_FILES_CHKSUM =
>> "file://COPYING;md5=d32239bcb673463ab874e80d47fae504 \
>>>
>> file://version.c;endline=18;md5=d8c56b52b9092346b9f93b4da65ef790"
>>> -PR = "r0"
>>> +PR = "r1"
>>>
>>> SRC_URI_append += "file://sh4-asmfix.patch \
>>> file://use-includedir.patch "
>
next prev parent reply other threads:[~2011-10-21 8:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 0:30 [PATCH 0/6] recipe upgrades + some fixes nitin.a.kamble
2011-10-19 0:30 ` [PATCH 1/6] x86 tune files: set baselib for x32 tune as libx32 nitin.a.kamble
2011-10-19 0:30 ` [PATCH 2/6] gmp: also generate the libgmpcxx library nitin.a.kamble
2011-10-20 7:50 ` Saul Wold
2011-10-20 8:01 ` Koen Kooi
2011-10-20 9:01 ` Phil Blundell
2011-10-21 6:04 ` Kamble, Nitin A
2011-10-21 7:54 ` Saul Wold [this message]
2011-10-21 16:54 ` Kamble, Nitin A
2011-10-19 0:30 ` [PATCH 3/6] python-scons: upgrade from 2.0.1 to 2.1.0 nitin.a.kamble
2011-10-19 0:30 ` [PATCH 4/6] python-dbus: upgrade from 0.83.2 to 0.84.0 nitin.a.kamble
2011-10-19 0:30 ` [PATCH 5/6] libxml-parser-perl: upgrade from 2.40 to 2.41 nitin.a.kamble
2011-10-19 0:31 ` [PATCH 6/6] distro-tracking: update data for some toolchain recipes nitin.a.kamble
2011-10-20 17:12 ` [PATCH 0/6] recipe upgrades + some fixes Saul Wold
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=4EA12540.9020002@intel.com \
--to=saul.wold@intel.com \
--cc=nitin.a.kamble@intel.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.