Hi!

I got a strange error here building uclibc stages:

I used experimental/x86/embedded/stages/stage3-x86-uclibc-2006.1.tar.bz2
from a mirror as seed stage and i used cflags, ldflags, arch and profile
from the make.conf/make.profile in that stage. When i try to build my
stage1 i get the following:

<error>
emerge --quiet --usepkg --buildpkg --newuse --oneshot --nodeps portage
emerge --quiet --usepkg --buildpkg --newuse --noreplace --oneshot
sys-apps/grep virtual/gzip sys-devel/binutils app-shells/bash
sys-apps/net-tools sys-devel/patch sys-devel/flex sys-apps/gawk
app-arch/tar sys-apps/sed virtual/libc sys-devel/bison sys-apps/texinfo
sys-apps/file app-arch/bzip2 net-misc/rsync sys-apps/debianutils
sys-devel/automake virtual/editor sys-apps/coreutils sys-devel/make
sys-apps/shadow sys-apps/findutils virtual/os-headers dev-lang/perl
net-misc/wget sys-devel/libtool sys-apps/diffutils sys-apps/less
sys-apps/baselayout dev-lang/python >=sys-apps/portage-2.0.51.22
sys-devel/autoconf sys-devel/gnuconfig sys-devel/gcc 

!!! All ebuilds that could satisfy "virtual/libc" have been masked.
!!! One of the following masked packages is required to complete your
request:
- sys-libs/glibc-2.5-r4 (masked by: package.mask)
- sys-libs/glibc-2.4-r4 (masked by: package.mask)
- sys-libs/glibc-2.6 (masked by: package.mask, missing keyword)
- sys-libs/glibc-2.3.6-r4 (masked by: package.mask)
- sys-libs/glibc-2.3.6-r5 (masked by: package.mask)
- sys-libs/glibc-2.3.2-r12 (masked by: package.mask)
- sys-libs/glibc-2.3.5-r3 (masked by: package.mask)
- sys-libs/glibc-2.2.5-r10 (masked by: package.mask)
- sys-libs/glibc-2.5-r2 (masked by: package.mask)
- sys-libs/glibc-2.5-r3 (masked by: package.mask)

For more information, see MASKED PACKAGES section in the emerge man page
or 
refer to the Gentoo Handbook.


!!! catalyst: run script failed.


Traceback (most recent call last):
  File "modules/generic_stage_target.py", line 1048, in run_local
    cmd("/bin/bash "+self.settings["controller_file"]+" run","run script
failed.",env=self.env)
  File "/usr/lib/catalyst/modules/catalyst_support.py", line 485, in cmd
    raise CatalystError,myexc
CatalystError: <unprintable instance object>
None

!!! catalyst: Stage build aborting due to error.


Catalyst aborting....
</error>

I cannot say, why this happens. When untar the stage and portage
snapshot, bind mount the it together, copy resolv.conf, chroot and do
the mentioned emerge commands in the chroot, it works. Any idea where
this effect comes from?

Thanks,
        Philipp

-- 
[EMAIL PROTECTED] mailing list

Reply via email to