Search the Community
Showing results for tags 'gcc'.
-
Hi guys , I'm stuck with gcc-7.3.1-r5 refusing to build : checking whether fprintf_unlocked is declared... no checking whether fputc_unlocked is declared... yes checking whether fputs_unlocked is declared... yes checking whether fread_unlocked is declared... yes checking whether fwrite_unlocked is declared... yes checking whether getchar_unlocked is declared... yes checking whether getc_unlocked is declared... yes checking whether putchar_unlocked is declared... yes checking whether putc_unlocked is declared... yes checking whether getrlimit is declared... yes checking whether setrlim
-
Hi all, I am unable to update my binutils. At first I received errors about conflicts and the files pointed to some /usr/share/locale files. I tried searching through forums and attempted various solutions, and I just made it worse. Has anyone else encountered this before? 1) I attempted to update (emerge -auDN --with-bdeps=y) 2) I unmerged binutils (DONT DO THIS!!!) 3) I tried to restore binutils and was able to get a version back # eselect binutils show x86_64-pc-linux-gnu-2.24 4) I tried removing the "-march=native" flags in my make,conf, but it did not cha
-
!!! All ebuilds that could satisfy "gcc" have been masked. !!! One of the following masked packages is required to complete your request: - sys-devel/gcc-7.3.0::core-kit (masked by: corruption) - sys-devel/gcc-7.2.0::core-kit (masked by: corruption) - sys-devel/gcc-6.4.0::core-kit (masked by: corruption) - sys-devel/gcc-6.3.0::core-kit (masked by: corruption) - sys-devel/gcc-5.4.0-r1::core-kit (masked by: corruption) - sys-devel/gcc-5.4.0::core-kit (masked by: corruption) - sys-devel/gcc-5.3.0-r2::core-kit (masked by: corruption) - sys-devel/gcc-5.3.0-r1::core-kit (masked by:
-
I am building funtoo root images for a different target architecture than the build system and wondering if that is causing some packages to fail to run. I am starting with a generic subarch: https://www.funtoo.org/Generic_64 And, I modify /etc/make.conf to: CHOST="x86_64-pc-linux-gnu" CFLAGS="-march=x86-64 -O2 -pipe" CXXFLAGS="-march=x86-64 -O2 -pipe" CPU_FLAGS_X86="mmx mmxext sse sse2" I do that to hopefully ensure that gcc won't build for my system which is an i7 and the target systems are a 64-bit Intel Atom and a 64-bit AMD netbook processor. H
-
Hi, I'm already using the gcc version 7.3, I wonder if I need reinstall the gcc if change the kits to version 1.2 ? or just keep the tutorial skip that step.
-
Hi folks, I read that on Gentoo news, about the update on system profile to them : https://www.gentoo.org/support/news-items/2017-11-30-new-17-profiles.html and I ask if I need rebuild the whole system ? I mean, I was using gcc 5.4.0 and I upgrade to 6.4 both withour hardened, so I need rebuild ?
-
hi folks, I'm in new installation and I'm follow that guide about upgrade gcc : https://wiki.gentoo.org/wiki/Upgrading_GCC the commands : Install new version of compiler emerge -u sys-devel/gcc show the versions gcc-config -l choose the new version gcc-config 2 reinstall libtool emerge --ask --oneshot sys-devel/libtool remove the old version emerge --ask --depclean =sys-devel/gcc-4.9.3 until here all fine and perfect, but my doubt is about recompile the toolchain, I need just recompile the depedencies with revdep-rebuild --library 'libstdc++.so.6' -- --exc
-
Hi folks, I wonder if may I use the Gentoo ebuild to install the GCC 5.4, I looked and the funtoo gcc 5.3-r1 ebuild is different of gentoo 5.3 or 5.4 ebuild is safe use the gentoo ebuild to do that ?
-
I was wondering if there are plans to merge gcc-5.1 and gcc-5.2 into Funtoo Portage. As a C/C++ developer, having the latest compilers is helpful for me. I know the ebuilds are a bit less monolithic than the Gentoo ebuilds. What would be involved if someone wanted to try to maintain them?
-
I'm a new Funtoo user. I've had it on my atom-powered SBC for about six months with no problems. The build log is 11MB. I'm including just the part where it fails. I would have linked the whole thing but a couple of pastebins rejected it. I would appreciate any advice on fixing the build. $ emerge -pvq '=sys-libs/glibc-2.20-r2' [ebuild U ] sys-libs/glibc-2.20-r2 [2.20-r1] USE="(multilib) -debug -gd (-hardened) -nscd -profile (-selinux) -suid -systemtap -vanilla" $ emerge --info '=sys-libs/glibc-2.20-r2' Portage 2.3.6-r9 (funtoo/1.0/linux-gnu/arch/x86-64bit, gcc-4.9.2, glibc-2.20-r1, 4
-
I'm trying to update from glibc-2.19 to glibc-2.20-r1. I've also tried to update gcc-4.8.4 to gcc-4.9.2-r1. Both throw an error that I don't understand. I'm attaching my build.log file and the output from emerge --info. Thanks for the help. Whoops! Too big. Here's hopefully relevant parts: > make -j2 -s glibc-test > make -j2 -s glibc-test >>>> Unpacking source... > <builtin>: recipe for target 'glibc-test' failed > [32;01m*[0m Auto adding -march=x86_64 to CFLAGS_x86 #185404 > [32;01m*[0m Checking gcc for __thread support ... > [A[72C [34;0
-
Hello, What is the correct way of updating gcc to 4.9.2? It is asking for an unmask but I doubt it is the correct way of doing things.