Patchwork [0/6] Misc changes relating to toolchain and image gen

login
register
mail settings
Submitter Mark Hatle
Date Nov. 13, 2013, 1:23 a.m.
Message ID <cover.1384305535.git.mark.hatle@windriver.com>
Download mbox
Permalink /patch/61551/
State New
Headers show

Pull-request

git://git.yoctoproject.org/poky-contrib mhatle/misc1

Comments

Mark Hatle - Nov. 13, 2013, 1:23 a.m.
A few misc fixes relating to toolchain and image generation.

The first two in the set simply updated gcc to remove the -symlinks package
in favor of update-alternatives.

The next fixes an issue w/ the previous binutils patch and upgrades.

Next 2 update packagegroups to make revise and use the 
packagegroup-core-buildessentials.

The final patch fixes an issue w/ the image generatation.  If the 
IMAGE_INSTALL contains a dependency instead of a package name, the system
was not able to translate it into a package.  This now works properly.

Note, there is a case where an unresolvable set could be determined (rare,
but it is possible), in this case the user would need to add whatever is
required to fix it to the IMAGE_INSTALL.  (This could happen when 2 or more
conflicting packages all have the same provide, but none of them are in
the IMAGE_INSTALL line.  The system will attempt to determine which to
use, by checking if any of them are already in the IMAGE_INSTALL -- otherwise
it chooses the first entry.  If something else implied by a packagegroup
chooses a different version, a conflict would be generated.)

The following changes since commit 616354f13732d13c17434d5b60b166f691c25761:

  binutils: Add gnu-config-native to DEPENDS (2013-11-12 16:00:20 +0000)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib mhatle/misc1
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=mhatle/misc1

Mark Hatle (6):
  gcc: Use alternatives for the *-symlinks packages.
  gcc: Drop *-symlinks
  binutils: Ensure old -symlinks packages get removed
  packagegroups: Remove toolchain *-symlinks packages
  packagegroup-self-hosted: Use packagegroup-core-buildessentials
  package_rpm: Allow translation of requirement to package name

 meta/classes/package_rpm.bbclass                   |  79 +++++++++++++++-
 .../packagegroup-core-buildessential.bb            |   4 -
 .../packagegroups/packagegroup-self-hosted.bb      |  16 +---
 meta/recipes-devtools/binutils/binutils.inc        |   1 +
 meta/recipes-devtools/gcc/gcc-target.inc           | 103 +++++++++++++--------
 5 files changed, 141 insertions(+), 62 deletions(-)
Otavio Salvador - Nov. 13, 2013, 1:33 a.m.
On Tue, Nov 12, 2013 at 11:23 PM, Mark Hatle <mark.hatle@windriver.com> wrote:
> A few misc fixes relating to toolchain and image generation.
>
> The first two in the set simply updated gcc to remove the -symlinks package
> in favor of update-alternatives.
>
> The next fixes an issue w/ the previous binutils patch and upgrades.
>
> Next 2 update packagegroups to make revise and use the
> packagegroup-core-buildessentials.
>
> The final patch fixes an issue w/ the image generatation.  If the
> IMAGE_INSTALL contains a dependency instead of a package name, the system
> was not able to translate it into a package.  This now works properly.
>
> Note, there is a case where an unresolvable set could be determined (rare,
> but it is possible), in this case the user would need to add whatever is
> required to fix it to the IMAGE_INSTALL.  (This could happen when 2 or more
> conflicting packages all have the same provide, but none of them are in
> the IMAGE_INSTALL line.  The system will attempt to determine which to
> use, by checking if any of them are already in the IMAGE_INSTALL -- otherwise
> it chooses the first entry.  If something else implied by a packagegroup
> chooses a different version, a conflict would be generated.)

Which package backends has been tested  with those changes?
Mark Hatle - Nov. 13, 2013, 2:01 a.m.
On 11/12/13, 7:33 PM, Otavio Salvador wrote:
> On Tue, Nov 12, 2013 at 11:23 PM, Mark Hatle <mark.hatle@windriver.com> wrote:
>> A few misc fixes relating to toolchain and image generation.
>>
>> The first two in the set simply updated gcc to remove the -symlinks package
>> in favor of update-alternatives.
>>
>> The next fixes an issue w/ the previous binutils patch and upgrades.
>>
>> Next 2 update packagegroups to make revise and use the
>> packagegroup-core-buildessentials.
>>
>> The final patch fixes an issue w/ the image generatation.  If the
>> IMAGE_INSTALL contains a dependency instead of a package name, the system
>> was not able to translate it into a package.  This now works properly.
>>
>> Note, there is a case where an unresolvable set could be determined (rare,
>> but it is possible), in this case the user would need to add whatever is
>> required to fix it to the IMAGE_INSTALL.  (This could happen when 2 or more
>> conflicting packages all have the same provide, but none of them are in
>> the IMAGE_INSTALL line.  The system will attempt to determine which to
>> use, by checking if any of them are already in the IMAGE_INSTALL -- otherwise
>> it chooses the first entry.  If something else implied by a packagegroup
>> chooses a different version, a conflict would be generated.)
>
> Which package backends has been tested  with those changes?
>

6/6 only affects RPM.  So only RPM back end.

The other changes are generic and follow the existing models.  However, I only 
tested the RPM backend.

(Note v2 of 5/6 and 6/6 has been sent.  I accidentally sent a version prior to 
two minor revisions.)

--Mark
Mark Hatle - Nov. 13, 2013, 3:42 a.m.
On 11/12/13, 8:01 PM, Mark Hatle wrote:
> On 11/12/13, 7:33 PM, Otavio Salvador wrote:
>> On Tue, Nov 12, 2013 at 11:23 PM, Mark Hatle <mark.hatle@windriver.com> wrote:
>>> A few misc fixes relating to toolchain and image generation.
>>>
>>> The first two in the set simply updated gcc to remove the -symlinks package
>>> in favor of update-alternatives.
>>>
>>> The next fixes an issue w/ the previous binutils patch and upgrades.
>>>
>>> Next 2 update packagegroups to make revise and use the
>>> packagegroup-core-buildessentials.
>>>
>>> The final patch fixes an issue w/ the image generatation.  If the
>>> IMAGE_INSTALL contains a dependency instead of a package name, the system
>>> was not able to translate it into a package.  This now works properly.
>>>
>>> Note, there is a case where an unresolvable set could be determined (rare,
>>> but it is possible), in this case the user would need to add whatever is
>>> required to fix it to the IMAGE_INSTALL.  (This could happen when 2 or more
>>> conflicting packages all have the same provide, but none of them are in
>>> the IMAGE_INSTALL line.  The system will attempt to determine which to
>>> use, by checking if any of them are already in the IMAGE_INSTALL -- otherwise
>>> it chooses the first entry.  If something else implied by a packagegroup
>>> chooses a different version, a conflict would be generated.)
>>
>> Which package backends has been tested  with those changes?
>>
>
> 6/6 only affects RPM.  So only RPM back end.
>
> The other changes are generic and follow the existing models.  However, I only
> tested the RPM backend.

BTW I just verified that the 1-5/6 work properly with an opkg backend as well.

--Mark

> (Note v2 of 5/6 and 6/6 has been sent.  I accidentally sent a version prior to
> two minor revisions.)
>
> --Mark
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
Saul Wold - Nov. 19, 2013, 12:40 a.m.
On 11/12/2013 05:23 PM, Mark Hatle wrote:
> A few misc fixes relating to toolchain and image generation.
>
> The first two in the set simply updated gcc to remove the -symlinks package
> in favor of update-alternatives.
>
> The next fixes an issue w/ the previous binutils patch and upgrades.
>
> Next 2 update packagegroups to make revise and use the
> packagegroup-core-buildessentials.
>
> The final patch fixes an issue w/ the image generatation.  If the
> IMAGE_INSTALL contains a dependency instead of a package name, the system
> was not able to translate it into a package.  This now works properly.
>
> Note, there is a case where an unresolvable set could be determined (rare,
> but it is possible), in this case the user would need to add whatever is
> required to fix it to the IMAGE_INSTALL.  (This could happen when 2 or more
> conflicting packages all have the same provide, but none of them are in
> the IMAGE_INSTALL line.  The system will attempt to determine which to
> use, by checking if any of them are already in the IMAGE_INSTALL -- otherwise
> it chooses the first entry.  If something else implied by a packagegroup
> chooses a different version, a conflict would be generated.)
>
> The following changes since commit 616354f13732d13c17434d5b60b166f691c25761:
>
>    binutils: Add gnu-config-native to DEPENDS (2013-11-12 16:00:20 +0000)
>
> are available in the git repository at:
>
>    git://git.yoctoproject.org/poky-contrib mhatle/misc1
>    http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=mhatle/misc1
>
> Mark Hatle (6):
>    gcc: Use alternatives for the *-symlinks packages.
>    gcc: Drop *-symlinks

Mark

This change set seems to be giving the Autobuilder some issues, please 
take a look at the AB (for example: 
http://autobuilder.yoctoproject.org:8011/builders/nightly-mips/builds/1/steps/Building%20Images/logs/stdio

Thanks
	Sau!

>    binutils: Ensure old -symlinks packages get removed
>    packagegroups: Remove toolchain *-symlinks packages
>    packagegroup-self-hosted: Use packagegroup-core-buildessentials
>    package_rpm: Allow translation of requirement to package name
>
>   meta/classes/package_rpm.bbclass                   |  79 +++++++++++++++-
>   .../packagegroup-core-buildessential.bb            |   4 -
>   .../packagegroups/packagegroup-self-hosted.bb      |  16 +---
>   meta/recipes-devtools/binutils/binutils.inc        |   1 +
>   meta/recipes-devtools/gcc/gcc-target.inc           | 103 +++++++++++++--------
>   5 files changed, 141 insertions(+), 62 deletions(-)
>