Neil Bothwick wrote: > On Mon, 22 Jul 2019 14:37:23 -0500, Dale wrote: > >> I was hoping updating the other packages might change something or help >> emerge figure out a new path but it doesn't appear to have helped. Once >> again, I removed everything I thought ruby related from /etc/portage. >> Emerge wanted some added back but I still end up back with that error. > What is RUBY_TARGETS set to? > > emerge --info | grep RUBY_TARGETS > >
This is the ruby related parts. RUBY_TARGETS="ruby24 ruby25" USE_EXPAND="ABI_MIPS ABI_PPC ABI_RISCV ABI_S390 ABI_X86 ALSA_CARDS APACHE2_MODULES APACHE2_MPMS CALLIGRA_FEATURES CAMERAS COLLECTD_PLUGINS CPU_FLAGS_ARM CPU_FLAGS_X86 CURL_SSL ELIBC ENLIGHTENMENT_MODULES FFTOOLS GPSD_PROTOCOLS GRUB_PLATFORMS INPUT_DEVICES KERNEL L10N LCD_DEVICES LIBREOFFICE_EXTENSIONS LIRC_DEVICES LLVM_TARGETS MONKEYD_PLUGINS NETBEANS_MODULES NGINX_MODULES_HTTP NGINX_MODULES_MAIL NGINX_MODULES_STREAM OFED_DRIVERS OFFICE_IMPLEMENTATION OPENMPI_FABRICS OPENMPI_OFED_FEATURES OPENMPI_RM PHP_TARGETS POSTGRES_TARGETS PYTHON_SINGLE_TARGET PYTHON_TARGETS QEMU_SOFTMMU_TARGETS QEMU_USER_TARGETS ROS_MESSAGES RUBY_TARGETS SANE_BACKENDS USERLAND UWSGI_PLUGINS VIDEO_CARDS VOICEMAIL_STORAGE XFCE_PLUGINS XTABLES_ADDONS" I tried adding a line in make.conf to force ruby25 but it still shows up as disabled in the emerge output so I commented out my entries. It seems to be hard disabled somewhere. Maybe the ebuild itself. I dunno. This is confusing. Ideas? Dale :-) :-)
