[gentoo-user] Re: oracle-jdk-bin-11
Hi James, On Mon, 23 Jul 2018 17:13:14 -0400 james wrote: > On 07/21/18 11:10, Jörg Schaible wrote: >> Hi, >> >> is someone aware of the existence of an ebuild for Java 11 e.g. >> somewhere in the overlays? Or has someone already crafted one and is >> willing to share it? >> >> Cheers, >> Jörg > > My response is:: > > https://github.com/Obsidian-StudiosInc/os-xtoo/#xtoo-overlay > > I'm just learning/hacking java, so please provide me with robust > feedback so I know if this offering is great, or needs improvement > (what/where) and what it is missing, from your point of view. Coding in > Java is easy; understanding the history, gotcha and devining Oracle's > future intentions is often not clear to me. Hence, feedback is greatly > appreciated, on this list, privately or to a forum is all ok. > Just help me navigate the java landscape. I'd really like to work with > java on both gentoo and windows 7/10. I'm starting fresh with Java-11. Thanks for the interesting pointer and I will certainly look at the ebuild for Java 11 to adjust it for my needs. However, the overlay is not for me. I use Gentoo as my development platform and as library developer I have a need for a wide range of JDKs: $ java-config -L The following VMs are available for generation-2: 1) Blackdown JDK 1.4.2.03 [blackdown-jdk-1.4.2] 2) IBM JDK 1.4.2.13_p9 [ibm-jdk-bin-1.4] 3) IBM JDK 1.5.0.12_p5 [ibm-jdk-bin-1.5] 4) IBM JDK 1.6.0.9_p2 [ibm-jdk-bin-1.6] 5) IBM JDK 1.7.0.5 [ibm-jdk-bin-1.7] 6) IcedTea JDK 6.1.13.9 [icedtea-bin-6] 7) IcedTea JDK 7.2.6.11 [icedtea-bin-7] 8) IcedTea JDK 3.8.0 [icedtea-bin-8] 9) JamVM JDK 2.0.0 [jamvm] 10) Oracle JDK 1.7.0.80 [oracle-jdk-bin-1.7] 11) Oracle JDK 1.8.0.172 [oracle-jdk-bin-1.8] *) Oracle JDK 10.0.1 [oracle-jdk-bin-10] 13) Oracle JDK 9.0.4 [oracle-jdk-bin-9] 14) Sun JDK 1.5.0.22 [sun-jdk-1.5] 15) Sun JDK 1.6.0.45 [sun-jdk-1.6] Therefore I am not interested in replacing java-config with something else nor can I live with with the supported JDKs from the overlay, especially since it tries to replace dev-java/* from the standard Gentoo tree. Cheers, Jörg > > > hth, > James
Re: [gentoo-user] Re: scanner problem : latest
On Tue, 24 Jul 2018 10:14:32 -0400, Philip Webb wrote: > > For future reference, start the Mint installer with "ubiquity -b", > > then it doesn't install a boot loader at all > > and you can add it to your Gentoo bootloader after rebooting. > > I started the Mint installer by clicking on its desktop button. > What is 'ubiquity' & how would I use it ? Ubiquity is the installer prom, which is run by the desktop icon with no arguments. Running it from a terminal with -b means no bootloader is installed. -- Neil Bothwick "Time is the best teacher., unfortunately it kills all the students" pgpQgee4FIs9z.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Upgrading gcc from 6.4 to 7.3
2018-07-24 22:00 GMT+03:00 gevisz : > 2018-06-20 14:16 GMT+03:00 Mick : >> On Wednesday, 20 June 2018 11:43:32 BST gevisz wrote: >>> After updating portage tree today, portage >>> suggested to upgrade gcc from 6.4 to 7.3 >>> version what I have done just now. >>> >>> Nevertheless, >>> # gcc-config --list-profiles >>> [1] x86_64-pc-linux-gnu-6.4.0 * >>> [2] x86_64-pc-linux-gnu-7.3.0 >>> shows that I still have version 6.4 as a default. >> >> I'm on gcc-7.3.0-r3 and have not noticed any problems on 3 boxen so far. >> >> >>> As https://wiki.gentoo.org/wiki/Upgrading_GCC >>> still do not have any specific instructions on >>> switching to gcc version 7.3, I am still afread >>> of switching to gcc version 7.3 and would like >>> to ask if anybody encountered some problem >>> after switching to gcc version 7.3 and which >>> packages should be rebuild after such switching. >>> >>> Thank you in advance for your help. >> >> I didn't have to rebuild anything, but if you have reasons to fear breakage >> you can rebuild your toolchain: >> >> 1. Use gcc-config to select x86_64-pc-linux-gnu-7.3.0 >> 2. Re-source /etc/profile by running in your current console/terminal: >> . /etc/profile >> 3. Re-emerge libtool: >> emerge -1 sys-devel/libtool >> 4. Re-emerge the following packages in this order: >> emerge -1 sys-devel/gcc-7.3.0-r3 >> emerge -1 sys-devel/binutils >> emerge -1 sys-libs/glibc >> 5. You could if you want re-emerge your entire system, 'emerge -e @world' or >> if you would rather conserve electricity wait as different packages come up >> for an update over time. >> >> If my experience to date holds true and for a general purpose desktop none of >> the above rebuilds are necessary, other than switching your gcc to 7.3.0. > > You forgot the 6th item: > > 6. Recompile the kernel. > > Just today, virtualbox-modules refused to compile because of this. > Thanks to Michael Orlitzky for the tip how to interpret portage messages. By the way, this recommendation is absent from Gentoo wiki on updating gcc.
Re: [gentoo-user] Upgrading gcc from 6.4 to 7.3
2018-06-20 14:16 GMT+03:00 Mick : > On Wednesday, 20 June 2018 11:43:32 BST gevisz wrote: >> After updating portage tree today, portage >> suggested to upgrade gcc from 6.4 to 7.3 >> version what I have done just now. >> >> Nevertheless, >> # gcc-config --list-profiles >> [1] x86_64-pc-linux-gnu-6.4.0 * >> [2] x86_64-pc-linux-gnu-7.3.0 >> shows that I still have version 6.4 as a default. > > I'm on gcc-7.3.0-r3 and have not noticed any problems on 3 boxen so far. > > >> As https://wiki.gentoo.org/wiki/Upgrading_GCC >> still do not have any specific instructions on >> switching to gcc version 7.3, I am still afread >> of switching to gcc version 7.3 and would like >> to ask if anybody encountered some problem >> after switching to gcc version 7.3 and which >> packages should be rebuild after such switching. >> >> Thank you in advance for your help. > > I didn't have to rebuild anything, but if you have reasons to fear breakage > you can rebuild your toolchain: > > 1. Use gcc-config to select x86_64-pc-linux-gnu-7.3.0 > 2. Re-source /etc/profile by running in your current console/terminal: > . /etc/profile > 3. Re-emerge libtool: > emerge -1 sys-devel/libtool > 4. Re-emerge the following packages in this order: > emerge -1 sys-devel/gcc-7.3.0-r3 > emerge -1 sys-devel/binutils > emerge -1 sys-libs/glibc > 5. You could if you want re-emerge your entire system, 'emerge -e @world' or > if you would rather conserve electricity wait as different packages come up > for an update over time. > > If my experience to date holds true and for a general purpose desktop none of > the above rebuilds are necessary, other than switching your gcc to 7.3.0. You forgot the 6th item: 6. Recompile the kernel. Just today, virtualbox-modules refused to compile because of this. Thanks to Michael Orlitzky for the tip how to interpret portage messages.
Re: [gentoo-user] virtualbox-modules fails to update: incompatible gcc/plugin versions
2018-07-24 19:16 GMT+03:00 Michael Orlitzky : > On 07/24/2018 04:18 AM, gevisz wrote: >> # emerge --update --deep --with-bdeps=y --newuse --backtrack=120 --ask world >> >> Shall I recompile gcc? >> > > Nope, recompile your kernel. > > Your kernel and virtualbox-modules (which incorporates stuff from your > kernel build) both need to be compiled with the same version of gcc. Yes, it helped. Thank you.
Re: [gentoo-user] virtualbox-modules fails to update: incompatible gcc/plugin versions
On 07/24/2018 04:18 AM, gevisz wrote: > # emerge --update --deep --with-bdeps=y --newuse --backtrack=120 --ask world > > Shall I recompile gcc? > Nope, recompile your kernel. Your kernel and virtualbox-modules (which incorporates stuff from your kernel build) both need to be compiled with the same version of gcc.
Re: [gentoo-user] LibreOffice and openldap
On Tuesday, 24 July 2018 17.15.29 CEST Andrew Lowe wrote: > Anyone got any insight? Upstream bug: https://bugs.documentfoundation.org/show_bug.cgi?id=71538 -- https://fturco.gitlab.com/ signature.asc Description: This is a digitally signed message part.
[gentoo-user] LibreOffice and openldap
Hi all, I'm in the process of installing LibreOffice. Doing: emerge --ask libreoffice gives a big list of dependencies, as I would expect. One of them is openldap. I thought that that was a bit strange, as I am a home user, not corporate so I tried to turn it off. I placed a "-ldap" in make.conf, I don't want it anywhere, but it still appeared in the dependency list. A google search turned up this bug: https://bugs.documentfoundation.org/show_bug.cgi?id=57417 which says, if I've read it correctly, that LDAP is not in LibreOffice anymore. If this is the case, why is there a dependency, https://gitweb.gentoo.org/repo/gentoo.git/tree/app-office/libreoffice/libreoffice-6.0.5.2-r1.ebuild line 136 - I may have misread this bit, I'm just starting to read the whole ebuild doco. Anyone got any insight? Andrew
Re: [gentoo-user] Re: scanner problem : latest
180723 Neil Bothwick wrote: > On Fri, 20 Jul 2018 09:04:26 -0400, Philip Webb wrote: >> Linux Mint 19 leads you along to a point where you've told it >> where to install, you click 'proceed' & it chugs along nicely, >> then it says it's trying to install a bootloader >> without asking whether you want it to or where to do it. > For future reference, start the Mint installer with "ubiquity -b", > then it doesn't install a boot loader at all > and you can add it to your Gentoo bootloader after rebooting. I started the Mint installer by clicking on its desktop button. What is 'ubiquity' & how would I use it ? > WinErr 018: Unrecoverable error - System has been destroyed. > Buy a new one. Old Windows licence is not valid anymore. That's how I felt for 30 min after Mint played its dirty trick above (grin). -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
Re: [gentoo-user] Gentoo-sources : stable versions
On Sunday, 1 July 2018 16:58:15 BST Mick wrote: > On Saturday, 30 June 2018 10:28:11 BST Philip Webb wrote: > > 180626 Rich Freeman wrote: > > > On Tue, Jun 26, 2018 at 8:58 PM Philip Webb wrote: > > >> Does anyone know why the latest stable version of Gentoo-sources is > > >> 4.9.xx ? I installed 4.9.16 , which I continue to use, on 2017-04-06 . > > >> The tree contains versions of 4.14 4.16 4.17 , but all are still > > >> testing. > > > > > > I believe that some had been complaining about stability issues with > > > 4.14, > > > but personally I've been fine with it, and since I have a Ryzen CPU > > > I want something that has the SMT support enabled ... > > > I don't know what the Gentoo plans are for 4.14 - > > > I know they've been avoiding it for a while. > > > I'm not sure if they ever plan to move to it > > > or if they're just hoping to skip it entirely. > > > I think we sb getting a new longterm sometime in the next few months. > > > > Well, wonders never cease (smile) : Gentoo-sources-4.14.52 is now stable ! > > > > I've emerged it & will probably install it tomorrow. > > Hopefully, this will also allow me to upgrade to Nvidia-drivers-396.24-r1 > > . > > > > As always, my thanks to the volunteers involved. > > Hear, hear! > > However, 4.14.52 like all kernels after the 4.9.x series badly break the > Dell XPS USB WiFi and bluetooth Broadcom chip. :-( > > The moment I switch on the darn thing with or without starting net.wlan0 and > with or without starting bluetooth I get two runaway systemd-udev processes > chewing up CPU time. Bluetooth does not work at all. > > 23767 root 20 0 38016 5184 2888 S 40.9 0.1 0:07.35 /lib/ > systemd/systemd-udevd --daemon > 785 root 20 0 56112 22572 2732 S 26.1 0.6 0:03.50 /lib/ > systemd/systemd-udevd --daemon > > udev appears to be fighting against the kernel by binding and unbinding the > Broadcom devices: > > KERNEL[6760.138491] bind /devices/pci:00/:00:1d.0/ > usb2/2-1/2-1.6/2-1.6.2/2-1.6.2:1.0 (usb) > KERNEL[6760.138640] unbind /devices/pci:00/:00:1d.0/ > usb2/2-1/2-1.6/2-1.6.2/2-1.6.2:1.0 (usb) > UDEV [6760.139080] bind /devices/pci:00/:00:1d.0/ > usb2/2-1/2-1.6/2-1.6.2/2-1.6.2:1.0 (usb) > KERNEL[6760.143273] bind /devices/pci:00/:00:1d.0/ > usb2/2-1/2-1.6/2-1.6.2/2-1.6.2:1.0 (usb) > KERNEL[6760.143500] unbind /devices/pci:00/:00:1d.0/ > usb2/2-1/2-1.6/2-1.6.2/2-1.6.2:1.0 (usb) > UDEV [6760.143817] unbind /devices/pci:00/:00:1d.0/ > usb2/2-1/2-1.6/2-1.6.2/2-1.6.2:1.0 (usb) > > which are scrolling by endlessly at V high speed. These are the offending > devices: > > Bus 002 Device 017: ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth > Mini-card > .. > Bus 002 Device 014: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part > of BCM2046 Bluetooth) > > Killing /lib/systemd/systemd-udevd --daemon causes my USB mouse to no longer > be recognised. > > Is there a clever way of getting out of this race condition and is there a > way to troubleshoot it further without going into kernel debugging at this > stage? Sadly no solution yet, but there is a report requesting a buggy kernel commit to be reverted: https://bugzilla.kernel.org/show_bug.cgi?id=199035 -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] virtualbox-modules fails to update: incompatible gcc/plugin versions
2018-07-24 12:25 GMT+03:00 Helmut Jarausch : > Just for the record, > I compiled this version with gcc-8.1.0-r3 without any problems. > > Helmut I currently use the latest current stable version of gcc: 7.3.0-r3. My current gcc-7.3.0-r3 was compiled with the previous stable version of it, that is 6.4.0-r1.
Re: [gentoo-user] virtualbox-modules fails to update: incompatible gcc/plugin versions
Just for the record, I compiled this version with gcc-8.1.0-r3 without any problems. Helmut
[gentoo-user] virtualbox-modules fails to update: incompatible gcc/plugin versions
# emerge --update --deep --with-bdeps=y --newuse --backtrack=120 --ask world These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] app-emulation/virtualbox-modules-5.2.14 [5.1.36] [ebuild U ] app-emulation/virtualbox-5.2.14-r1 [5.1.36] [ebuild U ] app-emulation/virtualbox-extpack-oracle-5.2.14.123301 [5.1.36.122089] Would you like to merge these packages? [Yes/No] y >>> Verifying ebuild manifests >>> Emerging (1 of 3) app-emulation/virtualbox-modules-5.2.14::gentoo ... cc1: error: incompatible gcc/plugin versions cc1: error: fail to initialize plugin ./scripts/gcc-plugins/cyc_complexity_plugin.so make[4]: *** [/usr/src/linux-4.9.95-gentoo/scripts/Makefile.build:293: /var/tmp/portage/app-emulation/virtualbox-modules-5.2.14/work/vboxdrv/linux/SUPDrv-linux.o] Error 1 make[4]: *** Waiting for unfinished jobs cc1: error: incompatible gcc/plugin versions cc1: error: fail to initialize plugin ./scripts/gcc-plugins/cyc_complexity_plugin.so make[4]: *** [/usr/src/linux-4.9.95-gentoo/scripts/Makefile.build:293: /var/tmp/portage/app-emulation/virtualbox-modules-5.2.14/work/vboxdrv/SUPDrv.o] Error 1 make[3]: *** [/usr/src/linux-4.9.95-gentoo/Makefile:1508: _module_/var/tmp/portage/app-emulation/virtualbox-modules-5.2.14/work/vboxdrv] Error 2 make[3]: Leaving directory '/usr/src/linux-4.9.95-gentoo' make[2]: *** [Makefile:152: sub-make] Error 2 make[2]: Leaving directory '/usr/src/linux-4.9.95-gentoo' make[1]: *** [/var/tmp/portage/app-emulation/virtualbox-modules-5.2.14/work/vboxdrv/Makefile.include.footer:101: vboxdrv] Error 2 make[1]: Leaving directory '/var/tmp/portage/app-emulation/virtualbox-modules-5.2.14/work/vboxdrv' make: *** [Makefile:49: all] Error 2 * ERROR: app-emulation/virtualbox-modules-5.2.14::gentoo failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=app-emulation/virtualbox-modules-5.2.14::gentoo'`, * the complete build log and the output of `emerge -pqv '=app-emulation/virtualbox-modules-5.2.14::gentoo'`. * The complete build log is located at '/var/log/portage/app-emulation:virtualbox-modules-5.2.14:20180724-080859.log'. * The ebuild environment file is located at '/var/tmp/portage/app-emulation/virtualbox-modules-5.2.14/temp/environment'. * Working directory: '/var/tmp/portage/app-emulation/virtualbox-modules-5.2.14/work' * S: '/var/tmp/portage/app-emulation/virtualbox-modules-5.2.14/work' >>> Failed to emerge app-emulation/virtualbox-modules-5.2.14, Log file: >>> >>> '/var/log/portage/app-emulation:virtualbox-modules-5.2.14:20180724-080859.log' Shall I recompile gcc?
