When building subversion-1.2.3-r3 with ruby use flag set, the Makefile seems to be buggy on my system. I think it's located in : /var/tmp/portage/subversion-1.2.3-r3/work/subversion-1.2.3/Makefile.in at line 127,128 ("SWIG_RB_COMPILE = @SWIG_RB_COMPILE@" is converted to "SWIG_RB_COMPILE = none" on my system) Resulting in this command on my system : /bin/sh /var/tmp/portage/subversion-1.2.3-r3/work/subversion-1.2.3/libtool --tag=CC --silent --mode=compile none -DLINUX=2 -D_REENTRANT -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I/var/tmp/portage/subversion-1.2.3-r3/work/subversion-1.2.3/subversion/bindings/swig -I/var/tmp/portage/subversion-1.2.3-r3/work/subversion-1.2.3/subversion/include -I/usr/lib/swig1.3 -DSVN_SWIG_VERSION=103021 -DSWIG_TABLE_TYPE=subversion -I/usr/include/apr-0 -I/usr/include/apr-0 -I/usr/include/db4.2 -I/var/tmp/portage/subversion-1.2.3-r3/work/subversion-1.2.3/subversion/bindings/swig/ruby/libsvn_swig_ruby -prefer-pic -c -o subversion/bindings/swig/ruby/svn_client.lo subversion/bindings/swig/ruby/svn_client.c and so the command "none" doesn't exist. Reproducible: Always Steps to Reproduce: 1. USE="apache2 ruby" emerge -av =subversion-1.2.3-r3 2. build error Actual Results: [...] make[2]: Leaving directory `/var/tmp/portage/subversion-1.2.3-r3/work/subversion-1.2.3/subversion/bindings/swig/perl/native' make[1]: Leaving directory `/var/tmp/portage/subversion-1.2.3-r3/work/subversion-1.2.3/subversion/bindings/swig/perl/native' /usr/bin/swig -ruby -I/var/tmp/portage/subversion-1.2.3-r3/work/subversion-1.2.3/subversion/bindings/swig -I/var/tmp/portage/subversion-1.2.3-r3/work/subversion-1.2.3/subversion/include -I/usr/lib/swig1.3 -DSVN_SWIG_VERSION=103021 -DSWIG_TABLE_TYPE=subversion -I/usr/include/apr-0 -I/usr/include/apr-0 -I/usr/include/db4.2 -I/var/tmp/portage/subversion-1.2.3-r3/work/subversion-1.2.3/subversion/bindings/swig/ruby/libsvn_swig_ruby -o subversion/bindings/swig/ruby/svn_client.c /var/tmp/portage/subversion-1.2.3-r3/work/subversion-1.2.3/subversion/bindings/swig/svn_client.i /bin/sh /var/tmp/portage/subversion-1.2.3-r3/work/subversion-1.2.3/libtool --tag=CC --silent --mode=compile none -DLINUX=2 -D_REENTRANT -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I/var/tmp/portage/subversion-1.2.3-r3/work/subversion-1.2.3/subversion/bindings/swig -I/var/tmp/portage/subversion-1.2.3-r3/work/subversion-1.2.3/subversion/include -I/usr/lib/swig1.3 -DSVN_SWIG_VERSION=103021 -DSWIG_TABLE_TYPE=subversion -I/usr/include/apr-0 -I/usr/include/apr-0 -I/usr/include/db4.2 -I/var/tmp/portage/subversion-1.2.3-r3/work/subversion-1.2.3/subversion/bindings/swig/ruby/libsvn_swig_ruby -prefer-pic -c -o subversion/bindings/swig/ruby/svn_client.lo subversion/bindings/swig/ruby/svn_client.c /var/tmp/portage/subversion-1.2.3-r3/work/subversion-1.2.3/libtool: line 1238: none: command not found make: *** [subversion/bindings/swig/ruby/svn_client.lo] Error 1 !!! ERROR: dev-util/subversion-1.2.3-r3 failed. !!! Function src_compile, Line 136, Exitcode 2 !!! Ruby library building failed Expected Results: subversion-1.2.3-r3 should have been compiled
confirmed, the same happens to me
I've seen some strange stuffs : 1) the patch subversion-swig.m4-ruby.patch which apply to subversion-source/build/ac-macros/swig.m4 201 if test "$RUBY" != "none" -a \ 202 "$SWIG_SUITABLE" = "yes" -a \ 203 "$SWIG_VERSION" -ge "103024"; then 2) and then if conditions are meet it set : AC_CACHE_CHECK([how to compile Ruby extensions], [svn_cv_ruby_compile],[ svn_cv_ruby_compile="`$RUBY -rrbconfig -e 'print Config::CONFIG.fetch(%q(CC)), %q( ), Config::CONFIG.fetch(%q(CFLAGS))'` \$(SWIG_RB_INCLUDES)" ]) SWIG_RB_COMPILE="$svn_cv_ruby_compile" 3) but it seems that my swig version is 1.3.21 @ ./configure : checking swig version... 1.3.21 4) so it's maybe a wrong check on dependencies in subversion ebuild
Same here... I'll investigate this further tomorrow (if there's not a patch by then. ;-))
Works (compiles) with ~x86 swig (1.3.25). USE="-ruby" emerge subversion works fine, too.
This ebuild failure is happening on my system also. The USE flags and swig/subversion versions involved: subversion-1.2.3-r3 [1.2.3-r2] -apache2 -bash-completion +berkdb -emacs +java +nls -nowebdav +perl +python +ruby +zlib 0 kB swig-1.3.21 +X -doc -guile +java +perl -php +python +ruby +tcltk 0 kB The build error is: /var/tmp/portage/subversion-1.2.3-r3/work/subversion-1.2.3/libtool: line 1262: none: command not found
Explicitly using USE="-ruby" did allow me to successfully emerge subversion...
Chris: Is there a chance that swig 1.3.25 is stabilized? In the meantime I've updated the dependencies, and put -r3 back in testing. It does require a newer swig release.
The same happened to me today while trying to upgrade subversion-1.2.3-r2 (x86/stable) to the 1.2.3-r2 (x86/stable). And I have "+ruby" in my USE flags. A private 'libtool'? Nice quirk :-) /bin/sh /var/tmp/portage/subversion-1.2.3-r3/work/subversion-1.2.3/libtool --tag=CC --silent --mode=compile none -DLINUX=2 -D_REENTRANT -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I/var/tmp/portage/subversion-1.2.3-r3/work/subversion-1.2.3/subversion/bindings/swig -I/var/tmp/portage/subversion-1.2.3-r3/work/subversion-1.2.3/subversion/include -I/usr/lib/swig1.3 -DSVN_SWIG_VERSION=103021 -DSWIG_TABLE_TYPE=subversion -I/usr/include/apr-0 -I/usr/include/apr-0 -I/usr/include/db4.2 -I/var/tmp/portage/subversion-1.2.3-r3/work/subversion-1.2.3/subversion/bindings/swig/ruby/libsvn_swig_ruby -prefer-pic -c -o subversion/bindings/swig/ruby/svn_client.lo subversion/bindings/swig/ruby/svn_client.c /var/tmp/portage/subversion-1.2.3-r3/work/subversion-1.2.3/libtool: line 1262: none: command not found make: *** [subversion/bindings/swig/ruby/svn_client.lo] Error 1 -- Guess someone didn't test the package with all possible supported USE flags. I did that myself too when writing some patched .ebuild. I was surprised how many small problems arose when I tried different USE flags combinations (and there were only three of them total!)
Basically I hadn't realised that the ruby bindings require a newer swig. As my systems run testing, my swig version is 1.3.25. One of the two swig versions accepted for the ruby bindings. I'm sorry for all the inconvenience. Please sync your repository.
