cant build chromium image due to mask changes required error.

[Ashish S]

Hello,

I am not able to proceed to build an image due to the following error..

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

The following mask changes are necessary to proceed:

#required by chromeos-base/chromeos-0.0.1-r166, required by chromeos (argument)

# /build/arm-generic/etc/portage/package.mask:

>=chromeos-base/chromeos-chrome-22.0.1195.0_rc-r1

NOTE: This --autounmask behavior can be disabled by setting

      EMERGE_DEFAULT_OPTS="--autounmask=n" in make.conf.

Use --autounmask-write to write changes to config files (honoring CONFIG_PROTECT).

An error occurred in your build so your latest output directory is invalid.

Would you like to delete the output directory (y/N)? y

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

I am building as follows..

cros_workon --board=$BOARD start chromeos-chrome   

cros_chrome_make --board=$BOARD

build_image --board=${BOARD} --noenable_rootfs_verification dev

any help ?

Thanks.

[tigerand]

I'm having the exact same problem.  I'm trying to build an image with a modified kernel, and build_image refuses to run, and there's NO explanation of what's going on.  It says:

"

The following mask changes are necessary to proceed:

#required by virtual/linux-sources-0.0.1, required by chromeos-base/chromeos-0.0.1-r168, required by chromeos (argument)

# /build/x86-generic/etc/portage/package.mask:

>=sys-kernel/chromeos-kernel-3.4-r1265

NOTE: This --autounmask behavior can be disabled by setting

      EMERGE_DEFAULT_OPTS="--autounmask=n" in make.conf.

Use --autounmask-write to write changes to config files (honoring CONFIG_PROTECT).

An error occurred in your build so your latest output directory is invalid.

Would you like to delete the output directory (y/N)? y

"

OK, I give up, what-the-firetruck do you mean, "The following mask changes are necessary to proceed"?  Hello, how about documenting some of this?  A change means you had something, you modified it, and now you have something new.  So this blurb of text explains NOTHING about what change is necessary, and it definitely doesn't explain how I get build_image to build the image with my locally built package like it used to do.  Nor does it explain "this behavior" or what will happen or not happen if I add that string to the make.conf file.

If you make any changes to the file /build/x86-generic/etc/portage/package.mask, it just builds the image with the non-modified kernel, which is, of course, useless.

This brokeness was introduced only in the last month or so, because I've done this many times successfully, and never encountered this until now.

Not mentioned anywhere on the wiki page, of course.  Can someone please instruct on how to proceed from here, and at the same time, can those responsible for breaking this please update the wiki like you're supposed to?

Frustrating to have major changes introduced but not documented.  Engineering 101, kids.

[Jonathan Kliegman]

On Fri, Aug 10, 2012 at 11:27 AM, tigerand <tige...@gmail.com> wrote:

I'm having the exact same problem.  I'm trying to build an image with a modified kernel, and build_image refuses to run, and there's NO explanation of what's going on.  It says:

You aren't having the same problem, the masked package is different. 

"

The following mask changes are necessary to proceed:

#required by virtual/linux-sources-0.0.1, required by chromeos-base/chromeos-0.0.1-r168, required by chromeos (argument)

# /build/x86-generic/etc/portage/package.mask:

>=sys-kernel/chromeos-kernel-3.4-r1265

NOTE: This --autounmask behavior can be disabled by setting

      EMERGE_DEFAULT_OPTS="--autounmask=n" in make.conf.

Use --autounmask-write to write changes to config files (honoring CONFIG_PROTECT).

An error occurred in your build so your latest output directory is invalid.

Would you like to delete the output directory (y/N)? y

"

OK, I give up, what-the-firetruck do you mean, "The following mask changes are necessary to proceed"?  Hello, how about documenting some of this?  A change means you had something, you modified it, and now you have something new.  So this blurb of text explains NOTHING about what change is necessary, and it definitely doesn't explain how I get build_image to build the image with my locally built package like it used to do.  Nor does it explain "this behavior" or what will happen or not happen if I add that string to the make.conf file.

This is a portage error, not a chromium OS one.  Changing it would involve working with the Portage developers to fix.

The message does give a suggestion for how to processed - adding that line will force it to allow chromeos-kernel-3.4-r1265 to work.

If you make any changes to the file /build/x86-generic/etc/portage/package.mask, it just builds the image with the non-modified kernel, which is, of course, useless.

This brokeness was introduced only in the last month or so, because I've done this many times successfully, and never encountered this until now.

I'm not aware of any changes with how you would build a new kernel that affect workflow.  I've been using the same one for longer than that without needing to change. 

Not mentioned anywhere on the wiki page, of course.  Can someone please instruct on how to proceed from here, and at the same time, can those responsible for breaking this please update the wiki like you're supposed to? 

Frustrating to have major changes introduced but not documented.  Engineering 101, kids.

It would be more useful if you listed the steps that got you here instead of assuming something is horribly broken and that everyone working on the project is incompetent.  The output of 'cros_workon --board=x86-generic list' would also help.  Environment variables and the exact commands you've run are also useful.

As for your specific error, its one I see if I run 'repo sync' in between build_packages and build_images.  Or if I don't use cros_workon correctly (running 'cros_workon --board=x86-generic stop chromeos-kernel' after building the kernel but before build_image is called).

If that doesn't fix your issue feel free to respond with more details.  But please keep it constructive, you'll get more people willing to help you then.

On Monday, July 9, 2012 2:46:22 AM UTC-7, Ashish S wrote:

Hello,

I am not able to proceed to build an image due to the following error..

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

The following mask changes are necessary to proceed:

#required by chromeos-base/chromeos-0.0.1-r166, required by chromeos (argument)

# /build/arm-generic/etc/portage/package.mask:

>=chromeos-base/chromeos-chrome-22.0.1195.0_rc-r1

NOTE: This --autounmask behavior can be disabled by setting

      EMERGE_DEFAULT_OPTS="--autounmask=n" in make.conf.

Use --autounmask-write to write changes to config files (honoring CONFIG_PROTECT).

An error occurred in your build so your latest output directory is invalid.

Would you like to delete the output directory (y/N)? y

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

I am building as follows..

cros_workon --board=$BOARD start chromeos-chrome   

cros_chrome_make --board=$BOARD

build_image --board=${BOARD} --noenable_rootfs_verification dev

any help ?

Thanks.

--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en