This one's fairly minor... When compiling obexftp-0.22 *without* the ruby USE flag, the ebuild will still set the environment var RUBY to /usr/bin/ruby18 during econf. Despite having --disable-ruby specified in the configure line, though, the build system will attempt to call /usr/bin/ruby18 during the compilation process, which will fail for a user who doesn't have ruby installed. The relevant bits from the compilation: make[3]: Entering directory '/var/tmp/portage/app-mobilephone/obexftp-0.22/work/obexftp-0.22/swig/ruby' PREFIX=/usr /usr/bin/ruby18 extconf.rb --with-obexftp-include=../.. /bin/sh: /usr/bin/ruby18: No such file or directory make[3]: *** [Makefile.ruby] Error 127 If you alter the ebuild so that $RUBY is only defined when the ruby USE flag is on, the problem takes care of itself. I'm guessing that that's an easier workaround then trying to fix the build system itself. Reproducible: Always Steps to Reproduce:
Fixed in all current obexftp versions, w/o revision bump.
