I downloaded minimal CD. and followed thier handbook for installation.

I tried emerging genkernel. But it returned such as,

ebuild.sh:line 23: error dyn_compile, src_compile..
...
I also tried using --pretend option to know its USE flags an updated USE variable in /etc/make.conf . But no use.
Finally i decided to compile the source myself. (#emerge gentoo-sources)
when i #make in /usr/src/linux, the same error appears( No bug report genrated , must be ur hardware or OS problem.)

Its a "OS problem." I recommend you pass on genkernel for now and continue with the install.

Have you never compiled your own kernel before? Or just in a hurry?

What version of the kernel/genkernel script are you trying to compile/run? It is masked or no? What version of gcc? What architecture?

You say you tried *emerging* genkernel...does that error generate during emerging the genkernel package (specifically), or while emerge is handling dependencies?

OK sry I tried re-installing from scratch again.




I had never compiled kernel before.......I was trying to emerge genkernel. But some ebuild error came...Also while updating portage after --sync , some segmentation fault occured,..

THis is my emerge --info( http://pastebin.ca/425179 )


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


QA Notice: USE Flag 'elibc_glibc' not in IUSE for sys-devel/gettext-0.16.1
./loadmsgcat.c: In function '_nl_load_domain':
./loadmsgcat.c:1295: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://bugs.gentoo.org/> for instructions.
Preprocessed source stored into /var/tmp/portage/gettext-0.16.1/temp/ccjaQAyP.out file, please attach this to your bugreport.
make[3]: *** [loadmsgcat.lo] Error 1
make[3]: *** Waiting for unfinished jobs....
make[2]: *** [all-recursive] Error 1
make[1]: *** [all] Error 2
make: *** [all-recursive] Error 1

!!! ERROR: sys-devel/gettext-0.16.1 failed.
Call stack:
ebuild.sh, line 1539: Called dyn_compile
ebuild.sh, line 939: Called src_compile
gettext-0.16.1.ebuild, line 58: Called die

!!! (no error message)
!!! If you need support, post the topmost build error, and the call stack if relevant.





The first line says USE flag should have elibc_glibc. But as u can see in the "emerge --info", USE flag has elibc_glibc and i have updated /etc/make.conf also for USE="elibc_glibc" and then did "emerge --newuse portage 2>error.log
And the above statements are the errors

Architecture is x86...trying install from minimal CD

gettext doesn't have the option for "elibc_glibc" USE flag...strange that portage would complain about gettext, seeing as how portage is the one with that USE flag.

I'm currently running ~amd64, so I can't be much assistance with x86 specific problems, but I can offer some advice:

Get to know the /etc/portage/package.* files. (They don't exist unless you create them...man portage has info about them...package.keywords can have entries like "sys-devel/gettext ~x86" to use packages that are masked for testing, package.use controls what USE flags are enabled on a package-by-package basis, package.unmask controls what packages are specifically unmasked (in case you don't want to run ~x86 globally), and package.mask is the opposite (for masking packages that behave badly))

With these files, you can control what packages are compiled with what USE flags, what packages are unmasked (if you're using, say x86 and not ~x86), and whatnot. This is generally better than globally enabling a USE flag (although in this particular incident, no harm is done enabling elibc_glibc since (to my knowledge), portage is the only package that uses that USE flag).

Did you change your CFLAGS, and did you use a recent x86 install disk the first time around?

Hope this helps some.

USE Flag 'elibc_glibc' not in IUSE for sys-devel/gettext-0.16.1

The above is not an error.

internal compiler error: Segmentation fault

Now, this is a problem. If you get random segfaults then you have a hardware problem, most likely bad RAM.

Edit: In case you have repeatable segfaults then the source is buggy or corrupted, run emerge --sync and try again.

Thanks to all...

@Rocket257, I wil surely try your method......

And regarding my RAM, its completely alright. I tested it with memtest86 in Ubuntu

May be gentoo doesnt like my hard.

In case you want to know - if memtest says the RAM is OK it means nothing. Some people have reported memtest reported errors on 6th or 7th day of continuous running.

Yes. You are right..
I ran memtest86 for the second time and i got 3lakh errors in my RAM.. I should change my RAM