nfsroot-2.6.13.4-1.19-20051122-cobalt-noscsi stage3-mipsel4-2006.0 1. Discrepancy in installation docs: Chapter 5b fails to mention that the stage tarballs for cobalt are in the 'experimental' directory. 2. Discrepancy/missing component: The documentation suggests using the optional mirrorselect tool, but the tool itself is missing. 3. Error - Chapter 6a, Code Listing 4: mount -o bind /dev /mnt/gentoo/dev fails with the following error: mount: Mounting /dev on /mnt/gentoo/dev failed: Invalid argument 4. Error - Chapter 6a: after chroot, update-env fails with: !!! Failed to complete python imports. There are internal modules for !!! python and failure here indicates that you have a problem with python !!! itself and thus portage is no able to continue processing. !!! You might consider starting python with verbose flags to see what has !!! gone wrong. Here is the information we got for this exception: /usr/lib/python2.4/lib-dynload/cPickle.so: symbol __strtol_internal, version GLIBC_2.0 not defined in file libc.so.6 with link time reference It is impossible to continue installation from this point. Note: After chroot, type 'mount'. It also fails, with this error: mount: relocation error: mount: symbol __strtol_internal, version GLIBC_2.0 not defined in file libc.so.6 with link time reference
Sorry--it's 'env-update', rather than 'update-env'...
Move your documentation comments to a separate bug, please. Don't file bugs about unrelated issues, they can't be assigned.
(In reply to comment #0) > nfsroot-2.6.13.4-1.19-20051122-cobalt-noscsi > stage3-mipsel4-2006.0 > > 1. Discrepancy in installation docs: Chapter 5b fails to mention that the > stage tarballs for cobalt are in the 'experimental' directory. Shouldn't be a problem. The only reason that they aren't is that we haven't had a proper release in a while, which will change with 2006.1. > 2. Discrepancy/missing component: The documentation suggests using the > optional mirrorselect tool, but the tool itself is missing. Not really a documentation problem...more of a problem with the actual stage tarballs themselves. You should have filed a bug with respect to that. > 3. Error - Chapter 6a, Code Listing 4: mount -o bind /dev /mnt/gentoo/dev > fails with the following error: > mount: Mounting /dev on /mnt/gentoo/dev failed: Invalid argument Again, not a docs problem. Sounds like a bug with the install media. > 4. Error - Chapter 6a: after chroot, update-env fails with: > !!! Failed to complete python imports. There are internal modules for > !!! python and failure here indicates that you have a problem with python > !!! itself and thus portage is no able to continue processing. > > !!! You might consider starting python with verbose flags to see what has > !!! gone wrong. Here is the information we got for this exception: > /usr/lib/python2.4/lib-dynload/cPickle.so: symbol __strtol_internal, > version > GLIBC_2.0 not defined in file libc.so.6 with link time reference > > It is impossible to continue installation from this point. Sounds like the older stage tarballs themselves are rather broken, although this is the first we've heard of any such problem to my knowledge. Repeat, not a documentation problem. > Note: After chroot, type 'mount'. It also fails, with this error: > mount: relocation error: mount: symbol __strtol_internal, version GLIBC_2.0 > not defined in file libc.so.6 with link time reference See above. Any comments from you cobalt type folks?
Damn, this bug slipped under my radar... I better get to work. > 3. Error - Chapter 6a, Code Listing 4: mount -o bind /dev /mnt/gentoo/dev > fails with the following error: > mount: Mounting /dev on /mnt/gentoo/dev failed: Invalid argument Okay, this looks like a limitation of busybox mount. I'll investigate further. > 4. Error - Chapter 6a: after chroot, update-env fails with: > !!! Failed to complete python imports. There are internal modules for > !!! python and failure here indicates that you have a problem with python > !!! itself and thus portage is no able to continue processing. > v !!! You might consider starting python with verbose flags to see what has > !!! gone wrong. Here is the information we got for this exception: > /usr/lib/python2.4/lib-dynload/cPickle.so: symbol __strtol_internal, > version > GLIBC_2.0 not defined in file libc.so.6 with link time reference Bizzare... when I do a stage3 build, I pick up the binary packages generated, and use those to update my Qube's root fs... thus I would've expected to see that error by now. Are you sure the tarball downloaded and extracted okay? For what it's worth, I'll soon be doing pre-2007.0 builds ... thus I may soon have new stages to try.
I haven't heard anything more on this matter. That said... 2007.0 has been built for a while now, and testing shows that everything seems to be working as expected. (There are a few packages that fail `make check` -- many of these fail exactly the same way on big endian systems.) I'm in the process of getting some µClibc stages cobbled together so that I can produce some newer netboot images. This is taking a while however, due to some issues I'm having with µClibc, as well as needing to start from scratch. I'll mark this bug TEST-REQUEST for now, feel free to reopen it if the problem still persists.
