had to use make config instead while in installation final steps (i was installing 1.4rc2 from stage1)
mmh..this is strange since ncurses is part of our base packages. did you have issues while installing ncurses itself?
I just ran into this same issue. Using the 1.4_rc2 iso, I copied the stage tarball from the cdrom rather than downloading from the gentoo site. Proceeded with a stage 1 install on x86 hardware. Emerge -s ncurses showed an installed 5.3-r1, but I re-emerged ncurses anyway. Also did another 'etc-update'. Made no difference even though the emerge completed successfully, so I ran a 'make config' just like 4rno did. Got an error that the system couldn't find cc when I tried a 'make dep', so I copied one of my other kernels over and continued with the install. No other problems, and the whole thing is working fine now. 'Make menuconfig' runs correctly now too. Gotta figure it's something about the stage tarball on the iso...
Workaround: env-update source /etc/profile This is becuse gcc-3.2 is used in the tarball, but the bootstrap will install gcc-3.2.1 thus requiring new enviroment variables.
Aliz -- is there any way for us to fix this? I'll cc azarah on this one too.
The possible solutions I can come up with are: 1. Have gcc-3.2.1 already in the tarballs 2. In the installation how-to, add the workaround after bootstrapping 3. Force env-update and source /etc/profile.env in bootstrap.sh after gcc is compiled (after emerge -c gcc)
Assigning to jhhudso for QA testing....
Yep, unfortunate issue with -r6. It should be fixed when the new stages with -r6 comes out. Jared, give me a shout if you need any info/whatever.
This issue remains outstanding in the new iso released lastnight. http://www.ibiblio.org/gentoo/experimental/x86/livecd/livecd-basic-x86-2003011300.iso env-update source /etc/profile Fixed the issue. HTH
We are just currently busy testing gcc-config-1.3.0, but it also adresses the problem. If you want, please test it and let me know of issues ...
*** This bug has been marked as a duplicate of 12819 ***
*** Bug 14905 has been marked as a duplicate of this bug. ***