| View previous topic :: View next topic |
| Author |
Message |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54220
Location: 56N 3W
|
 Posted: Sun Dec 25, 2016 7:38 pm Post subject: |
 |
|
wrc1944,
| Code: | $ wgetpaste /etc/portage/patches/dev-util/ragel-6.9/ragel_gcc-6.2.patch
Your paste can be seen here: https://paste.pound-python.org/show/05AmCmUoQzEvTbTal8fs/ |
Drop that pastebin into that file on your system.
You won't have that directory yet either.
Works on arm64.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
 |
asturm
Developer
Joined: 05 Apr 2007
Posts: 8935
|
| Posted: Sun Dec 25, 2016 11:13 pm Post subject: |
|
|
| wrc1944 wrote: | | No gcc-6.3.0 ebuild in portage yet. |
GCC-6.3.0 is now in tree. |
|
| Back to top |
|
|
wrc1944
Advocate
Joined: 15 Aug 2002
Posts: 3435
Location: Gainesville, Florida
|
| Posted: Mon Dec 26, 2016 12:06 am Post subject: |
|
|
Asturm, Tony0945, mv, Neddy, & all,
Thanks much for the feedback! 
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11 |
|
| Back to top |
|
|
Tony0945
Watchman
Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA
|
| Posted: Mon Dec 26, 2016 12:52 am Post subject: |
|
|
| wrc1944 wrote: | Asturm, Tony0945, mv, Neddy, & all,
Thanks much for the feedback! |
Merry Christmas!/Happy Hannukah (I'm Hebrew spelling challenged). Thank you! This thread has spurred me to switch from 4.9.4 to 5.4.0 I've emerged 5.4, selected it with gcc-config, re-emerged libtool and run the revdep-rebuild command listed in the news item. Right now, it's on package 44 of 122. Probably be done tomorrow.
A thought! Do I need to rebuild the kernel also? It's not C++ but didn't the C interface change too? |
|
| Back to top |
|
|
wrc1944
Advocate
Joined: 15 Aug 2002
Posts: 3435
Location: Gainesville, Florida
|
| Posted: Mon Dec 26, 2016 12:54 am Post subject: |
|
|
For those interested, after searching some mirrors, portage finally found the source and patches packages for 6.3.0, and here's the first config phase.
Gcc-6.3.0 -s currently compiling- more later. If anyone would like to see more of the check phase, I can post it up on pastebin. The gentoo mirror that had 6.3.0 is https://dev.gentoo.org/~zorry/
| Code: | 2016-12-25 19:31:18 (4.10 MB/s) - ‘/usr/portage/distfiles/gcc-6.3.0-patches-1.0.tar.bz2’ saved [7596/7596]
* gcc-6.3.0-patches-1.0.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ]
>>> Unpacking source...
>>> Unpacking gcc-6.3.0.tar.bz2 to /var/tmp/portage/sys-devel/gcc-6.3.0/work
>>> Unpacking gcc-6.3.0-patches-1.0.tar.bz2 to /var/tmp/portage/sys-devel/gcc-6.3.0/work
>>> Source unpacked in /var/tmp/portage/sys-devel/gcc-6.3.0/work
>>> Preparing source in /var/tmp/portage/sys-devel/gcc-6.3.0/work/gcc-6.3.0 ...
* Applying Gentoo patches ...
* 10_all_default-fortify-source.patch ... [ ok ]
* 11_all_default-warn-format-security.patch ... [ ok ]
* 12_all_default-warn-trampolines.patch ... [ ok ]
* 13_all_default-ssp-fix.patch ... [ ok ]
* 25_all_alpha-mieee-default.patch ... [ ok ]
* 29_all_arm_armv4t-default.patch ... [ ok ]
* 34_all_ia64_note.GNU-stack.patch ... [ ok ]
* 42_all_superh_default-multilib.patch ... [ ok ]
* 50_all_libiberty-asprintf.patch ... [ ok ]
* 51_all_libiberty-pic.patch ... [ ok ]
* 54_all_nopie-all-flags.patch ... [ ok ]
* 55_all_extra-options.patch ... [ ok ]
* 90_all_pr55930-dependency-tracking.patch ... [ ok ]
* Done with patching
* updating multilib directories to be: ../lib64 ../lib32
* Running elibtoolize in: gcc-6.3.0/
* Applying portage/2.2 patch ...
* Applying sed/1.5.6 patch ...
* Applying as-needed/2.2.6 patch ...
* Using GNU config files from /usr/share/gnuconfig
* Updating config.sub [ ok ]
* Updating libjava/libltdl/config.sub [ ok ]
* Updating libjava/classpath/config.sub [ ok ]
* Updating config.guess [ ok ]
* Updating libjava/libltdl/config.guess [ ok ]
* Updating libjava/classpath/config.guess [ ok ]
* Fixing misc issues in configure files
* Applying gcc-configure-texinfo.patch ... [ ok ]
* Touching generated files
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/sys-devel/gcc-6.3.0/work/gcc-6.3.0 ...
* strip-flags: CFLAGS: changed '-march=native -O2 -pipe -fomit-frame-pointer -ftree-vectorize -fipa-icf' to '-march=native -O2 -pipe'
* strip-flags: CXXFLAGS: changed '-march=native -O2 -pipe -fomit-frame-pointer -ftree-vectorize -fipa-icf' to '-march=native -O2 -pipe'
* CFLAGS="-march=native -O2 -pipe"
* CXXFLAGS="-march=native -O2 -pipe"
* LDFLAGS="-Wl,-O1 -Wl,--as-needed"
* PREFIX: /usr
* BINPATH: /usr/x86_64-pc-linux-gnu/gcc-bin/6.3.0
* LIBPATH: /usr/lib/gcc/x86_64-pc-linux-gnu/6.3.0
* DATAPATH: /usr/share/gcc-data/x86_64-pc-linux-gnu/6.3.0
* STDCXX_INCDIR: /usr/lib/gcc/x86_64-pc-linux-gnu/6.3.0/include/g++-v6
* Languages: c,c++,fortran
* Configuring GCC with:
* --host=x86_64-pc-linux-gnu
* --build=x86_64-pc-linux-gnu
* --prefix=/usr
* --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/6.3.0
* --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/6.3.0/include
* --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/6.3.0
* --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/6.3.0/man
* --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/6.3.0/info
* --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/6.3.0/include/g++-v6
* --with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/6.3.0/python
* --enable-languages=c,c++,fortran
* --enable-obsolete
* --enable-secureplt
* --disable-werror
* --with-system-zlib
* --enable-nls
* --without-included-gettext
* --enable-checking=release
* --with-bugurl=https://bugs.gentoo.org/
* --with-pkgversion=Gentoo 6.3.0 p1.0
* --disable-esp
* --enable-libstdcxx-time
* --enable-shared
* --enable-threads=posix
* --enable-__cxa_atexit
* --enable-clocale=gnu
* --enable-multilib
* --with-multilib-list=m32,m64
* --disable-altivec
* --disable-fixed-point
* --enable-targets=all
* --disable-libgcj
* --enable-libgomp
* --disable-libmudflap
* --disable-libssp
* --disable-libcilkrts
* --disable-libmpx
* --enable-vtable-verify
* --enable-libvtv
* --enable-lto
* --without-isl
* --enable-libsanitizer
* --disable-default-pie
* --disable-default-ssp
/var/tmp/portage/sys-devel/gcc-6.3.0/work/gcc-6.3.0/configure --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/6.3.0 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/6.3.0/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/6.3.0 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/6.3.0/man --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/6.3.0/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/6.3.0/include/g++-v6 --with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/6.3.0/python --enable-languages=c,c++,fortran --enable-obsolete --enable-secureplt --disable-werror --with-system-zlib --enable-nls --without-included-gettext --enable-checking=release --with-bugurl=https://bugs.gentoo.org/ --with-pkgversion=Gentoo 6.3.0 p1.0 --disable-esp --enable-libstdcxx-time --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-multilib --with-multilib-list=m32,m64 --disable-altivec --disable-fixed-point --enable-targets=all --disable-libgcj --enable-libgomp --disable-libmudflap --disable-libssp --disable-libcilkrts --disable-libmpx --enable-vtable-verify --enable-libvtv --enable-lto --without-isl --enable-libsanitizer --disable-default-pie --disable-default-ssp checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking for a BSD-compatible install... /usr/lib/portage/python3.4/ebuild-helpers/xattr/install -c
checking whether ln works... yes
checking whether ln -s works... yes
checking for a sed that does not truncate output... /bin/sed
checking for gawk... gawk
checking for libatomic support... yes
checking for libitm support... yes
checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes
checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... none needed
checking for x86_64-pc-linux-gnu-g++... x86_64-pc-linux-gnu-g++
checking whether we are using the GNU C++ compiler... yes
checking whether x86_64-pc-linux-gnu-g++ accepts -g... yes
checking whether g++ accepts -static-libstdc++ -static-libgcc... yes
checking for x86_64-pc-linux-gnu-gnatbind... no
checking for gnatbind... no
checking for x86_64-pc-linux-gnu-gnatmake... no
checking for gnatmake... no
checking whether compiler driver understands Ada... no
checking how to compare bootstrapped objects... cmp --ignore-initial=16 $$f1 $$f2
checking for objdir... .libs
checking for the correct version of gmp.h... yes
checking for the correct version of mpfr.h... yes
checking for the correct version of mpc.h... yes
checking for the correct version of the gmp/mpfr/mpc libraries... yes
*** This configuration is not supported in the following subdirectories:
zlib target-zlib target-libjava gnattools gotools target-libada target-libgo target-libffi target-libobjc target-libcilkrts target-liboffloadmic target-libmpx target-libssp target-boehm-gc
(Any other directories should still work fine.) |
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11
Last edited by wrc1944 on Mon Dec 26, 2016 1:19 am; edited 1 time in total |
|
| Back to top |
|
|
wrc1944
Advocate
Joined: 15 Aug 2002
Posts: 3435
Location: Gainesville, Florida
|
| Posted: Mon Dec 26, 2016 1:06 am Post subject: |
|
|
Tony0945 wrote: | Quote: | | A thought! Do I need to rebuild the kernel also? It's not C++ but didn't the C interface change too? |
Not sure about the kernel requirements- but it-the move from 5.4 to 6.2.0 was pretty easy, I assume because the c++ ABI update stuff was already done. From 4.9.4 is problably a bit more involved.
After you move over and set 5.4, I would definitely rebuild the toolchain first, then run an emerge -e1 @ system --keep-going as the first thing. Then maybe build a new kernel, if only for the hell-of-it, and reboot. 
My practice in these situations has been only after you can get all @system rebuilt with 5.4 should you try a full emerge -e1 @world --keep-going.
Oh yeah- IIRC, that's what I did with moving from 4.9.3 to 5.4. (It's been a while).
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11 |
|
| Back to top |
|
|
wrc1944
Advocate
Joined: 15 Aug 2002
Posts: 3435
Location: Gainesville, Florida
|
| Posted: Mon Dec 26, 2016 1:15 am Post subject: |
|
|
OK- gcc-6.3.0 compiled and installed fine- no issues.
Think I'll call it a day on this, and set 6.3.0 as default tomorrow and maybe rebuild the toolchain first, and then maybe even -e @system too.
Maybe asturm and/or mv could tell us if this toolchain and system rebuilding after going to 6.3.0 from 6.2.0-r1 is really necessary?
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11
Last edited by wrc1944 on Mon Dec 26, 2016 7:09 am; edited 1 time in total |
|
| Back to top |
|
|
saboya
Guru
Joined: 28 Nov 2006
Posts: 552
Location: Brazil
|
| Posted: Mon Dec 26, 2016 2:10 am Post subject: |
|
|
| Migrated to 5.4 last week and was just waiting for 6.3 to hit the tree to switch. Compiling 6.3.0 right now Will recompile toolchain then system, I'll report if I have any issues. |
|
| Back to top |
|
|
mv
Watchman
Joined: 20 Apr 2005
Posts: 6747
|
| Posted: Mon Dec 26, 2016 6:43 am Post subject: |
|
|
| wrc1944 wrote: | | rebuilding after going to 6.3.0 from 6.2.0-r1 is really necessary? |
There might be serious bugs or bugfixes, of course - one would need to check every single change in detail - but normally for minor version bumps no recompilation is necessary; probably it would have been noted somewhere if this version bump would have been an exception.
Reocmpilation of the kernel should probably never be necessary: this would be required only after extraordinary ABI change in gcc or binutils which AFAIK didn't happen since many years. |
|
| Back to top |
|
|
wrc1944
Advocate
Joined: 15 Aug 2002
Posts: 3435
Location: Gainesville, Florida
|
| Posted: Mon Dec 26, 2016 7:05 am Post subject: |
|
|
Thanks mv,
Good to know.
BTW, just rebuilt toolchain with gcc-6.3.0, and then completed an emerge -e1 @system rebuild with no issues. revdep-rebuild says system is consistent.
Guess I will go ahead and an do emerge -e1 @world tomorrow anyway, just to assure myself there are no problems. My although aging amd FX-8320 8-core churns through all the rebuilds pretty quickly, compared to years past.
This is turning out to be virtually trouble-free so far, in large measure thanks to all the great info and advice you guys are posting. Much appreciated.
BTW again, just noticed that the 6.2.0-r1 and 6.3.0 ebuilds are identical, so apparently it was just remamed. Nothing is changed in the files directory, but there is a line in the manifest file for 6.3.0.
UPDATE: emerge -e @world rebuild completed fully, except for one package, dev-util/ragel-6.9:0, which I expected becuse I forgot to try and address it before I started the rebuild.
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11 |
|
| Back to top |
|
|
Tony0945
Watchman
Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA
|
| Posted: Tue Feb 14, 2017 5:12 pm Post subject: |
|
|
Updated to 5.4 with no issues. Migrated to 6.3.0 over the last few days using this script that I think came from wrc1944 | Code: | emerge -av =sys-devel/gcc-6.3.0
emerge -av linux-headers binutils glibc gcc libtool portage
emerge -aev1 @system --keep-going
emerge -aev1 @world --keep-going
|
A few things in system failed but emerged OK on emerge --resume, probably an order thing.
The world ebuild was LONG and six ebuilds failed, all in my local overlay.
| Code: | real 1426m17.492s
user 1772m41.120s
sys 538m16.788s
six packages failed
|
Three of the packages were old ebuilds no longer in the gentoo tree that I haven't built for ages. One was missing the tarball and the other two had signed/unsigned char issues that older gcc tolerated but gcc 6 fails when assigned a large hex byte value to a signed char. I wrote patches that corrected the coding errors. One was an ebuild I wrote that needed autotools update. One was copied from another another overlay and the tarball is still missing. The source has switched to git and apparently only has the "live" code now.
The sixth was the serious ebuild. This was x11-wm/lumina, which i maintain in my local overlay since my filed bug (with fix) was ignored. | Code: |
"stdlib.h: No such file or directory" |
This IS a gcc 6 bug, one that upstream has dismissed as "Won't fix" https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70129. I found the workaround on the ArchLinux user repository https://aur.tuna.tsinghua.edu.cn/packages/lumina-desktop-git/. This one may affect other qt5 packages. | Code: | --- /usr/local/portage/x11-wm/lumina/lumina-1.2.0.ebuild.old 2016-12-19 20:13:01.851550082 -0600
+++ /usr/local/portage/x11-wm/lumina/lumina-1.2.0.ebuild 2017-02-13 22:19:51.009991842 -0600
@@ -42,6 +42,7 @@
src_configure(){
eqmake5 PREFIX="${ROOT}usr" L_BINDIR="${ROOT}usr/bin" \
L_ETCDIR="${ROOT}etc" L_LIBDIR="${ROOT}usr/$(get_libdir)" \
+ QMAKE_CFLAGS_ISYSTEM= PREFIX="/usr" \
LIBPREFIX="${ROOT}usr/$(get_libdir)" DESTDIR="${D}" CONFIG+="NO_I18N"
}
|
I hope you don't mind this long post. It took me a day and a half to fix this, so I thought I'd share. |
|
| Back to top |
|
|
Juippisi
Developer
Joined: 30 Sep 2005
Posts: 723
Location: /home
|
| Posted: Wed Feb 15, 2017 7:51 am Post subject: |
|
|
| Is unmasking GCC-6 for ~ users depending on these open bugs? |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54220
Location: 56N 3W
|
| Posted: Wed Feb 15, 2017 9:21 am Post subject: |
|
|
Juippisi,
That's right. You can unmask it for yourself now if you want.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
Juippisi
Developer
Joined: 30 Sep 2005
Posts: 723
Location: /home
|
| Posted: Wed Feb 15, 2017 9:41 am Post subject: |
|
|
Thanks,
I'll wait I guess. :) |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Unsupported Software
