| View previous topic :: View next topic |
| Author |
Message |
sinanqapudan
Apprentice
Joined: 26 Oct 2004
Posts: 234
Location: Milan
|
 Posted: Wed Aug 31, 2011 8:02 pm Post subject: |
 |
|
Probably you meant eselect gcc
| Code: | sargon ~ # ls /usr/bin/gcc*
/usr/bin/gcc /usr/bin/gcc-4.4.5 /usr/bin/gcc-config
sargon ~ # ls -l /usr/bin/gcc*
-rwxr-xr-x 1 root root 9568 Aug 30 22:43 /usr/bin/gcc
lrwxrwxrwx 1 root root 58 Aug 30 22:43 /usr/bin/gcc-4.4.5 -> /usr/i686-pc-linux-gnu/gcc-bin/4.4.5/i686-pc-linux-gnu-gcc
-rwxr-xr-x 1 root root 21703 Jul 12 22:52 /usr/bin/gcc-config
sargon ~ # eselect gcc
!!! Error: Can't load module gcc
|
but if you meant instead eselect g++
| Code: | sargon ~ # eselect g++
!!! Error: Can't load module g++
exiting
|
|
|
| Back to top |
|
 |
sinanqapudan
Apprentice
Joined: 26 Oct 2004
Posts: 234
Location: Milan
|
| Posted: Wed Aug 31, 2011 10:46 pm Post subject: |
|
|
Now this is weird. I've just been able to build a new kernel, whilst I was expecting another compile fail. The kernel does not boot, but it is strange I've been able to build it at all!!
I also tried to run emerge -e system, and it starts compiling fine. The output also claims to have switched the native gcc compiler to gcc-4.4.5 and then exits at dev-libs/icu-4.8. This is the build log:
| Code: |
[32;01m * [39;49;00mPackage: dev-libs/icu-4.8
[32;01m * [39;49;00mRepository: gentoo
[32;01m * [39;49;00mMaintainer: arfrever.fta@gmail.com neurogeek@gentoo.org
[32;01m * [39;49;00mUSE: elibc_glibc kernel_linux userland_GNU x86
[32;01m * [39;49;00mFEATURES: sandbox
>>> Unpacking source...
>>> Unpacking icu4c-4_8-src.tgz to /var/tmp/portage/dev-libs/icu-4.8/work
>>> Source unpacked in /var/tmp/portage/dev-libs/icu-4.8/work
>>> Preparing source in /var/tmp/portage/dev-libs/icu-4.8/work/icu/source ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/dev-libs/icu-4.8/work/icu/source ...
* econf: updating icu/source/config.guess with /usr/share/gnuconfig/config.guess
* econf: updating icu/source/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-debug --disable-samples --disable-static
checking for ICU version numbers... release 4.8, library 48.0, unicode version 6.0
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking whether to build debug libraries... no
checking whether to build release libraries... yes
checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether i686-pc-linux-gnu-gcc accepts -g... yes
checking for i686-pc-linux-gnu-gcc option to accept ISO C89... none needed
checking for i686-pc-linux-gnu-g++... no
checking for i686-pc-linux-gnu-c++... no
checking for i686-pc-linux-gnu-gpp... no
checking for i686-pc-linux-gnu-aCC... no
checking for i686-pc-linux-gnu-CC... no
checking for i686-pc-linux-gnu-cxx... no
checking for i686-pc-linux-gnu-cc++... no
checking for i686-pc-linux-gnu-cl.exe... no
checking for i686-pc-linux-gnu-FCC... no
checking for i686-pc-linux-gnu-KCC... no
checking for i686-pc-linux-gnu-RCC... no
checking for i686-pc-linux-gnu-xlC_r... no
checking for i686-pc-linux-gnu-xlC... no
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl.exe... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking whether we are using the GNU C++ compiler... no
checking whether g++ accepts -g... no
checking how to run the C preprocessor... i686-pc-linux-gnu-gcc -E
checking for a BSD-compatible install... /usr/bin/install -c
checking for gmake... /usr/bin/gmake
checking for doxygen... no
checking checking for executable suffix...
checking whether strict compiling is on... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking size of void *... 4
checking whether runnable 64 bit binaries are built by default... no
checking which Makefile fragment to use for i686-pc-linux-gnu... mh-linux
checking for floor in -lm... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking whether to enable auto cleanup of libraries... no
checking whether to enable draft APIs... yes
checking for library API export... yes
checking for i686-pc-linux-gnu-ranlib... i686-pc-linux-gnu-ranlib
checking for i686-pc-linux-gnu-ar... i686-pc-linux-gnu-ar
checking whether to enable renaming of symbols... yes
checking whether to enable function and data tracing... no
checking whether to enable dynamic loading of plugins... checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for library containing dlopen... -ldl
checking for dlopen... yes
checking for gettimeofday... yes
checking for definition of U_INLINE for C... __inline__
checking if we have a C++ compiler... no
configure: error: C++ compiler g++ does not work or no compiler found
!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/dev-libs/icu-4.8/work/icu/source/config.log
[31;01m*[0m ERROR: dev-libs/icu-4.8 failed (configure phase):
[31;01m*[0m econf failed
[31;01m*[0m
[31;01m*[0m Call stack:
[31;01m*[0m ebuild.sh, line 56: Called src_configure
[31;01m*[0m environment, line 2453: Called econf '--disable-debug' '--disable-samples' '--disable-static'
[31;01m*[0m ebuild.sh, line 561: Called die
[31;01m*[0m The specific snippet of code:
[31;01m*[0m die "econf failed"
[31;01m*[0m
[31;01m*[0m If you need support, post the output of 'emerge --info =dev-libs/icu-4.8',
[31;01m*[0m the complete build log and the output of 'emerge -pqv =dev-libs/icu-4.8'.
[31;01m*[0m The complete build log is located at '/var/tmp/portage/dev-libs/icu-4.8/temp/build.log'.
[31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/dev-libs/icu-4.8/temp/environment'.
[31;01m*[0m S: '/var/tmp/portage/dev-libs/icu-4.8/work/icu/source' |
|
|
| Back to top |
|
|
DaggyStyle
Watchman
Joined: 22 Mar 2006
Posts: 5910
|
| Posted: Thu Sep 01, 2011 5:14 am Post subject: |
|
|
run gcc-config 1 and see if /usr/bin/g++ exists.
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein |
|
| Back to top |
|
|
sinanqapudan
Apprentice
Joined: 26 Oct 2004
Posts: 234
Location: Milan
|
| Posted: Thu Sep 01, 2011 6:01 am Post subject: |
|
|
This is the output of gcc-config 1:
| Code: | sargon ~ # gcc-config 1
* Switching native-compiler to i686-pc-linux-gnu-4.4.5 ... [ ok ] |
No file g++ exists in the /usr/bin directory. |
|
| Back to top |
|
|
DaggyStyle
Watchman
Joined: 22 Mar 2006
Posts: 5910
|
| Posted: Thu Sep 01, 2011 6:52 am Post subject: |
|
|
| sinanqapudan wrote: | This is the output of gcc-config 1:
| Code: | sargon ~ # gcc-config 1
* Switching native-compiler to i686-pc-linux-gnu-4.4.5 ... [ ok ] |
No file g++ exists in the /usr/bin directory. |
just for the heck of it, keyword gcc-4.5.3 and emerge it, run gcc-config for it an see if the file was created, run gcc-config again for the first one and see if the file is still there and the version is 4.4.5, then you're ok, you can unmerge 4.5.3, if it is still there but not changed, I recommand you either try reemering gcc-config or stay with 4.5.3
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein |
|
| Back to top |
|
|
sinanqapudan
Apprentice
Joined: 26 Oct 2004
Posts: 234
Location: Milan
|
| Posted: Thu Sep 01, 2011 7:25 am Post subject: |
|
|
Portage keeps complaining about sys-devel/gcc-4.5.3 not being a valid package atom, I must be making some mistakes in keywording it, I run:
| Code: | echo "sys-devel/gcc **" >> /etc/portage/package.accept_keywords
|
and
| Code: | | echo "sys-devel/gcc**" >> /etc/portage/package.accept_keywords |
and
| Code: | | echo "sys-devel/gcc-4.5.3" >> /etc/portage/package.accept_keywords |
but this is what I get when trying to emerge it:
| Code: | sargon ~ # emerge -pv sys-devel/gcc-4.5.3
--- Invalid atom in /etc/portage/package.accept_keywords: sys-devel/gcc**
--- Invalid atom in /etc/portage/package.accept_keywords: sys-devel/gcc-4.5.3
!!! 'sys-devel/gcc-4.5.3' is not a valid package atom.
!!! Please check ebuild(5) for full details.
|
What mistakes am I making? |
|
| Back to top |
|
|
DaggyStyle
Watchman
Joined: 22 Mar 2006
Posts: 5910
|
| Posted: Thu Sep 01, 2011 7:33 am Post subject: |
|
|
| Code: | | echo "=sys-devel/gcc-4.5.3" >> /etc/portage/package.keywords |
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein |
|
| Back to top |
|
|
sinanqapudan
Apprentice
Joined: 26 Oct 2004
Posts: 234
Location: Milan
|
| Posted: Thu Sep 01, 2011 9:23 am Post subject: |
|
|
This is what I get:
| Code: | sargon ~ # gcc-config -l
[1] i686-pc-linux-gnu-4.4.5 *
[2] i686-pc-linux-gnu-4.5.3
|
Then:
| Code: | sargon ~ # gcc-config 2
* Switching native-compiler to i686-pc-linux-gnu-4.5.3 ...
--- Invalid atom in /etc/portage/package.accept_keywords: sys-devel/gcc**
--- Invalid atom in /etc/portage/package.accept_keywords: sys-devel/gcc-4.5.3
>>> 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
sargon ~ # gcc-config 1
* Switching native-compiler to i686-pc-linux-gnu-4.4.5 ...
--- Invalid atom in /etc/portage/package.accept_keywords: sys-devel/gcc**
--- Invalid atom in /etc/portage/package.accept_keywords: sys-devel/gcc-4.5.3
>>> 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
|
But still no file g++ exists in the /usr/bin directory. |
|
| Back to top |
|
|
DaggyStyle
Watchman
Joined: 22 Mar 2006
Posts: 5910
|
| Posted: Thu Sep 01, 2011 10:12 am Post subject: |
|
|
did you ran . /etc/profile ?
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein |
|
| Back to top |
|
|
sinanqapudan
Apprentice
Joined: 26 Oct 2004
Posts: 234
Location: Milan
|
| Posted: Thu Sep 01, 2011 10:30 am Post subject: |
|
|
Yes I run it after the second switch, that is after:
| Code: | sargon ~ # gcc-config 1
* Switching native-compiler to i686-pc-linux-gnu-4.4.5 ...
--- Invalid atom in /etc/portage/package.accept_keywords: sys-devel/gcc**
--- Invalid atom in /etc/portage/package.accept_keywords: sys-devel/gcc-4.5.3
>>> Regenerating /etc/ld.so.cache... [ ok ] |
I run
| Code: | | sargon ~ # . /etc/profile |
But still no file g++ in the /usr/bin directory. |
|
| Back to top |
|
|
sinanqapudan
Apprentice
Joined: 26 Oct 2004
Posts: 234
Location: Milan
|
| Posted: Thu Sep 01, 2011 8:46 pm Post subject: |
|
|
Apparently we've run out of ideas ....
Anyone out there willing to lend a hand? |
|
| Back to top |
|
|
sinanqapudan
Apprentice
Joined: 26 Oct 2004
Posts: 234
Location: Milan
|
| Posted: Sun Sep 11, 2011 12:23 pm Post subject: |
|
|
I think we can mark this thread as UNRESOLVED and close it. I rebuilt the system from scratch but had no better luck, stil stuck with KDE not working, albeit for a different reason...
In case you are interested:
https://forums.gentoo.org/viewtopic-p-6810950.html#6810950 |
|
| Back to top |
|
|
DaggyStyle
Watchman
Joined: 22 Mar 2006
Posts: 5910
|
| Posted: Sun Sep 11, 2011 2:52 pm Post subject: |
|
|
| sinanqapudan wrote: | I think we can mark this thread as UNRESOLVED and close it. I rebuilt the system from scratch but had no better luck, stil stuck with KDE not working, albeit for a different reason...
In case you are interested:
https://forums.gentoo.org/viewtopic-p-6810950.html#6810950 |
do a complete clean install without old configs
then add back the confs you need
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein |
|
| Back to top |
|
|
Spidey
Apprentice
Joined: 07 Sep 2006
Posts: 269
|
| Posted: Sun Sep 11, 2011 11:33 pm Post subject: |
|
|
| I didn't read the full thread, but have you already shared your USE flags for gcc? |
|
| Back to top |
|
|
sinanqapudan
Apprentice
Joined: 26 Oct 2004
Posts: 234
Location: Milan
|
| Posted: Mon Sep 12, 2011 8:07 am Post subject: |
|
|
| Thanks for yoour interest in this topic, but it is now too late... |
|
| Back to top |
|
|
franzf
Advocate
Joined: 29 Mar 2005
Posts: 4565
|
| Posted: Wed Sep 14, 2011 7:36 am Post subject: |
|
|
Setting "nocxx"-Useflag and wondering that there is no g++ is quite funny :/
| Code: | # quse -D nocxx
global:nocxx: Disable support for C++ (DON'T USE THIS UNLESS YOU KNOW WHAT YOU'RE DOING) |
Disable nocxx and all your problems should be gone. |
|
| Back to top |
|
|
sinanqapudan
Apprentice
Joined: 26 Oct 2004
Posts: 234
Location: Milan
|
| Posted: Wed Sep 14, 2011 4:05 pm Post subject: |
|
|
Franzf,
| Quote: | Setting "nocxx"-Useflag and wondering that there is no g++ is quite funny :/
Code:
# quse -D nocxx
global:nocxx: Disable support for C++ (DON'T USE THIS UNLESS YOU KNOW WHAT YOU'RE DOING)
Disable nocxx and all your problems should be gone. |
thanks for yous suggestion, but as I said before, I rebuilt the system from scratch. My problems are gone... |
|
| Back to top |
|
|
|
Desktop Environments
