Differences between base-gcc and gcc packages? [Solved]

[ShadowCat8]

Greetings,

I am a little confused about the differences between these two packages, thanks to the recent updates, and it leaves me with a couple questions:

1. Is it expected that when you have both sys-devel/base-gcc and sys-devel/gcc installed on a system, routine updates would update the sys-devel/base-gcc package and not the sys-devel/gcc package?
2. Having run the updates through Sulfur, is it expected that the gcc-config gets set automatically to the new sys-devel/base-gcc package?
3. Is it expected that the sys-devel/base-gcc does not provide a "gcc" executable?
4. Apart from the missing executable, what are the differences between these packages?

To show what I am referring to, here is the output from the terminal:

Code: Select all

tech7 ~ # gcc -v
Using built-in specs.
Reading specs from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/vanilla.specs
Reading specs from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/hardenednossp.specs
Reading specs from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/hardenednopie.specs
COLLECT_GCC=/usr/x86_64-pc-linux-gnu/gcc-bin/4.5.3/gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/4.5.3/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/gcc-4.5.3/configure --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.5.3 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.5.3 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.5.3/man --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.5.3/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/include/g++-v4 --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --disable-altivec --disable-fixed-point --with-ppl --with-cloog --disable-ppl-version-check --with-cloog-include=/usr/include/cloog-ppl --disable-lto --enable-nls --without-included-gettext --with-system-zlib --disable-werror --enable-secureplt --enable-multilib --enable-libmudflap --disable-libssp --enable-esp --enable-libgomp --with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/4.5.3/python --enable-checking=release --enable-objc-gc --enable-languages=c,c++,java,objc,obj-c++,fortran --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-targets=all --with-bugurl=http://bugs.gentoo.org/ --with-pkgversion='Gentoo Hardened 4.5.3-r2 p1.1, pie-0.4.7'
Thread model: posix
gcc version 4.5.3 (Gentoo Hardened 4.5.3-r2 p1.1, pie-0.4.7)
tech7 ~ # gcc-config -l
 [1] x86_64-pc-linux-gnu-4.5.3
 [2] x86_64-pc-linux-gnu-4.5.3-hardenednopie
 [3] x86_64-pc-linux-gnu-4.5.3-hardenednopiessp
 [4] x86_64-pc-linux-gnu-4.5.3-hardenednossp
 [5] x86_64-pc-linux-gnu-4.5.3-vanilla *
tech7 ~ # sulfur
 * Switching native-compiler to x86_64-pc-linux-gnu-4.6.3-vanilla ...
/usr/bin/gcc-config: line 239: ///usr/x86_64-pc-linux-gnu/gcc-bin/4.6.3/gcc: No such file or directory
touch: failed to get attributes of ‘//usr/bin/x86_64-pc-linux-gnu-cpp’: No such file or directory
>>> Regenerating /etc/ld.so.cache...                                      [ ok ]

 * If you intend to use the gcc from the new profile in an already
 * running shell, please remember to do:

 *   . /etc/profile

tech7 ~ # env-update && source /etc/profile
>>> Regenerating /etc/ld.so.cache...
tech7 ~ # which gcc
which: no gcc in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.6.3)
tech7 ~ # gcc-config -l
 [1] x86_64-pc-linux-gnu-4.5.3
 [2] x86_64-pc-linux-gnu-4.5.3-hardenednopie
 [3] x86_64-pc-linux-gnu-4.5.3-hardenednopiessp
 [4] x86_64-pc-linux-gnu-4.5.3-hardenednossp
 [5] x86_64-pc-linux-gnu-4.5.3-vanilla
 [6] x86_64-pc-linux-gnu-4.6.3
 [7] x86_64-pc-linux-gnu-4.6.3-hardenednopie
 [8] x86_64-pc-linux-gnu-4.6.3-hardenednopiessp
 [9] x86_64-pc-linux-gnu-4.6.3-hardenednossp
 [10] x86_64-pc-linux-gnu-4.6.3-vanilla *
tech7 ~ # equo update
>>  @@ Repositories synchronization ...
>>   # Sabayon Linux Official Repository
>>   # Repository URL: http://pkg.sabayon.org/standard/sabayon-weekly/database/amd64/5
>>   # Repository local path: /var/lib/entropy/client/database/amd64/sabayon-weekly/standard/amd64/5
>>   # Repository API: 3
>>    Attention: repository is already up to date.
>>  @@  Notice board: sabayon-weekly
>>     [0] [Tue, 12 Jun 2012 08:57:09 +0000] Title: LibreOffice freezes in Sabayon 9
>>     [1] [Fri, 13 Jul 2012 12:42:20 +0000] Title: Upcoming important updates for ATI/AMD GPU owners
tech7 ~ # equo query installed gcc
>>  @@ Searching...
>>      @@ Package: sys-devel/base-gcc-4.5.3-r2 branch: 5, [__system__]
>>         Installed:     version: 4.5.3-r2 ~ tag: NoTag ~ revision: 0
>>         Slot:          4.5
>>         Homepage:      http://gcc.gnu.org/
>>         Description:   The GNU Compiler Collection
>>         License:       FDL-1.2 GPL-3 LGPL-3 gcc-runtime-library-exception-3.1 libgcc libstdc++
>>      @@ Package: sys-devel/base-gcc-4.6.3 branch: 5, [__system__]
>>         Installed:     version: 4.6.3 ~ tag: NoTag ~ revision: 0
>>         Slot:          4.6
>>         Homepage:      http://gcc.gnu.org/
>>         Description:   The GNU Compiler Collection
>>         License:       FDL-1.2 GPL-3 LGPL-3 gcc-runtime-library-exception-3.1 libgcc libstdc++
>>      @@ Package: sys-devel/gcc-4.5.3-r2 branch: 5, [__system__]
>>         Installed:     version: 4.5.3-r2 ~ tag: NoTag ~ revision: 0
>>         Slot:          4.5
>>         Homepage:      http://gcc.gnu.org/
>>         Description:   The GNU Compiler Collection
>>         License:       FDL-1.2 GPL-3 LGPL-3 gcc-runtime-library-exception-3.1 libgcc libstdc++
>>      @@ Package: sys-devel/gcc-config-1.5-r2 branch: 5, [__system__]
>>         Installed:     version: 1.5-r2 ~ tag: NoTag ~ revision: 0
>>         Slot:          0
>>         Homepage:      http://www.gentoo.org/
>>         Description:   Utility to change the gcc compiler
>>                        being used
>>         License:       GPL-2
>>  Keyword:  gcc
>>  Found:    4 entries
tech7 ~ #

So, the base question is: Is this expected behavior or a bug?

TIA for your assistance.

[wolfden]

In our base-gcc ebuild it states

Code: Select all

# Since Sabayon's gcc ebuild are split into two parts, we have to
   # build gcc with a different version of gcc, or terrible breakage
   # will occur after sys-devel/base-gcc is installed, but the
   # partner sys-devel/gcc still needs to be built.

   # While it is possible to rebuild Sabayon's split gcc from
   # the same version, we have to disallow this also since
   # we have no way of discerning if a configuration change
   # is significant enough to cause breakage.


Not sure if that answers your one question or not, can't remember why we split it, but apparently to save on breakage lol

gcc-config should all be handled automatically with updates

[ShadowCat8]

Greetings,

Thank you for your response, Wolfden. Yes, that answers the base question, and in fact, answers all but one, though I think I figured that last one out myself; only the shared libraries and env files are in sys-devel/base-gcc. All binaries, headers and other libraries are in sys-devel/gcc.

Of course, that leaves me with a few more questions about build- and work-flow, but those are questions for another time when I am a little more familiar with the inner workings of Sabayon.

Thanks again for your time and response.