Installed, but "make.conf" looks bare

Has Gentoo changed over the years so much that “make.conf” has changed the way it looks or is something wrong here?
I havn,t used gentoo for a while ,but I remember “make.conf” being more optional it seemed. I installed CalculateLinux & thought “make.conf” would have been automatically
setup.
Even the cxflags have been hashed
Could someone give me an example of what 64bit make.conf should look like,or is it ok?
I didnt want to emerge yet unless its setup right.

I think the numbers are supposed to be #hashes at start of lines as I posted them as.

JASONS-BRAAAIN etc # cat /etc/make.conf

#------------------------------------------------------------------------------ 
 # Modified Calculate-install 2.2.16 
 # Processed template files: 
 # /usr/share/calculate/templates/install/1merge/portage/make.conf 
#------------------------------------------------------------------------------ 

#------------------- 
 # Basic build option 
#------------------- 
 # Exception of the software. The list of possible flags can be found here: 
 # /var/lib/layman/calculate/profiles/desc/calculate.desc 
 # Separated by a space. To remove programs, do update `emerge -uDN world`, 
 # and then delete the packages by running `emerge -ac`. 
#CALCULATE="" 

 # Valid license. Need to specify for such packages as: 
 # net-wireless/broadcom-sta, dev-java/sun-jdk and others. 
ACCEPT_LICENSE="*" 

 # Alternative mirror updates repository. In case of problems with access 
 # at the beginning try to update the overlay by running `layman-s calculate`. 
#PORTAGE_BINHOST="http://77.88.19.68/calculate/CLD/grp/x86_64" 
#PORTAGE_BINHOST="ftp://ftp.linux.kiev.ua/pub/Linux/Calculate/CLD/grp/x86_64" 
#PORTAGE_BINHOST="ftp://opennix.tula.su/calculate/CLD/grp/x86_64" 
#PORTAGE_BINHOST="http://mirror.cnet.kz/calculate/CLD/grp/x86_64" 

 # Connecting overlays layman. You should not change this setting, as this may 
 # disrupt the package manager. 
source /var/lib/layman/make.conf 

#----------------- 
 # Compiler Options 
#----------------- 
 # Additional options passed to the compiler. The flag "-march=native" 
 # Optimize the program by your hardware. 
#CFLAGS="-O2 -march=native -pipe" 
#CXXFLAGS="${CFLAGS}" 

#------------------- 
 # Faster Compilation 
#------------------- 
 # Number of parallel processes that run when you install. 
MAKEOPTS="-j9" 

 # The number of packets for simultaneous assembly. 
#EMERGE_DEFAULT_OPTS="--jobs=4"

I’m wondering as well if it being a fairly fresh install if I would have to Rebuild all p[kgs if I was to uncomment these or if its to late.

#CFLAGS="-O2 -march=native -pipe" 
#CXXFLAGS="${CFLAGS}"

What I mainly would like to know is,if I did need to make some changes,which file would need altering.
My “emerge.info” seems to be what the “make.conf” should look like or would of looked like when I last used a Gentoo Distro. Where does “emerge.info” get its info from? maybe thats the file that could be used if needed.

Thanks AnyOne

Ive also noticed that alot of “Package Files” in /etc/portage are Folders instead of files. Like “package.use & package.mask etc”, And I have had to change them to files. I checked the livecd to see if its the same as my installed,& they were.

Here is /etc/make.conf from Gentoo Stage3:

 # These settings were set by the catalyst build script that automatically
 # built this stage.
 # Please consult /usr/share/portage/config/make.conf.example for a more
 # detailed example.
CFLAGS="-O2 -march=i686 -pipe"
CXXFLAGS="${CFLAGS}"
 # WARNING: Changing your CHOST is not something that should be done lightly.
 # Please consult http://www.gentoo.org/doc/en/change-chost.xml before changing.
CHOST="i686-pc-linux-gnu"

These settings are in the profile distribution.

/etc/make.conf file has been prepared for you by analogy with others, such as /etc/samba/smb.conf.default. In it you can change the settings, or they do not change.

In Gentoo Stage3 no file /etc/portage/package.keywords (use, unmask) and others. You will not find even the directory /etc/portage. We have created the necessary directories, so that you have less doubt. package.keywords can be a file or directory. Portage supports it. In this case, the directory may be several package.keywords files with any names. It’s convenient.

But where or how would I add things like xtra Use Flags etc…
Could it be wise to add or copy my “emerge.info” to “make.conf” or just leave it?
I have found commands etc that I have used to add “Use Flags & unmasking & so on” but dont know where to physically do this or go to if needed. Even just some hints could be helpful as I am having trouble pointing google to any decent examples.
One of the reasons is I tried to install Portato & had to do some unmasking but it is still complaining ,So I installed PortHole for now.
Here is the output for Portato & my “emerge.info” -I think I will be right with installing Portato eventually if & when I work out this Slot Problem & another “unmask” issue still left.

*** emerge --pretend --nospinner --noreplace app-portage/portato ***
000002 
000003 These are the packages that would be merged, in order:
000004 
000005 Calculating dependencies  ... done!
000006 
000007 !!! Multiple package instances within a single package slot have been pulled
000008 !!! into the dependency graph, resulting in a slot conflict:
000009 
000010 x11-libs/pango:0
000011 
000012   (x11-libs/pango-1.28.3-r1::gentoo, installed) pulled in by
000013     (no parents that aren't satisfied by other packages in this slot)
000014 
000015   (x11-libs/pango-1.28.4::gentoo, ebuild scheduled for merge) pulled in by
000016     >=x11-libs/pango-1.20[introspection?] required by (x11-libs/gtk+-2.24.4::gentoo, ebuild scheduled for merge)
000017 
000018 
000019 !!! Enabling --newuse and --update might solve this conflict.
000020 !!! If not, it might help emerge to give a more specific suggestion.
000021 
000022 
000023 emerge: there are no ebuilds built with USE flags to satisfy "dev-lang/python:2.7[sqlite?,threads]".
000024 !!! One of the following packages is required to complete your request:
000025 - dev-lang/python-2.7.1-r1 (Change USE: +sqlite)
000026 - app-portage/portato-9999 (Change USE: -sqlite)
000027 (dependency required by "app-portage/portato-9999" [ebuild])
000028 (dependency required by "app-portage/portato" [argument])
000029 *** process completed ***

Thanks

Please show contains of all files in /etc/portage/package.* and /etc/make.conf.

Is this what you mean, -these are from original folders that I renamed so I could add them as files instead.

  # ls /etc/portage/package.*
/etc/portage/package.keywords  /etc/portage/package.keywords~  /etc/portage/package.mask  /etc/portage/package.unmask  /etc/portage/package.unmask~  /etc/portage/package.use  /etc/portage/package.use~

/

It seems to me that the emerge.info is collected from different profiles. I think i’ll have to learn the processes as I go along.

Oh’Well. GOD BLESS.

Actually People or someone could of helped clear this up,or give me peace of mind if They or Someone said,“Yep,thats the same as what we have after we have installed CalculateLinux” , “So theirs nothing wrong with your Make.Conf, because its the same as ours after we installed it”.
At least thats how I think I would of read my Question if it was someone elses.
Amazing.
All is well

I just want to appologise as it seems the original folders in /etc/portage that I thought were wrong & should have been files ,actually seem to have been setup right all along. I changed back to using folders & found files were created automatically inside them.
I just want to say, I stopped using gentoo some time back & I am glad I gave this distro a go as this is an excellent put together OS. I don,t think I have had a linux distro do what it does so cleanly. I just need to learn which files & commands to alter or use instead of being able to just alter your “make,conf” file like in the past.
Ive even found installing tarballs & running portable software & portable jars a real treat, -especially considering my desktop is 64bit as well.
In fact I think this could be the best linux desktop I have ever used by far.