net/rrdtool fails to build when ruby is installed?

2007-05-05 Thread Kian Mohageri
Hi guys,

I'm running into an error (seen below) when attempting to build the
latest net/rrdtool when Ruby is installed.

I updated all of the dependencies first to make sure they weren't stale,
but the problem persists.  Ruby support is built by default if Ruby is
installed.  I removed Ruby, and the build finishes.

Strangely, it seems the problem only happens with gmake, which the port
prefers.  Running 'make' in the offending directory manually results in
RRD.so being built correctly.

Any advice would be much appreciated... I wouldn't be surprised if I
somehow screwed up, but I'm not sure how.

Kian

-- snip --
gmake[4]: Leaving directory
`/usr/ports/net/rrdtool/work/rrdtool-1.2.23/bindings/perl-shared'
cd ruby && /usr/local/bin/ruby extconf.rb && gmake EPREFIX=/usr/local
sitedir=/usr/local/lib/ruby
checking for rrd_create() in -lrrd... yes
creating Makefile
gmake[4]: Entering directory
`/usr/ports/net/rrdtool/work/rrdtool-1.2.23/bindings/ruby'
Makefile:144: Commands were specified for file `RRD.so' at Makefile:114,
Makefile:144: but `RRD.so' is now considered the same file as
`/usr/local/lib/ruby/1.8/i386-freebsd6/RRD.so'.
Makefile:144: Commands for
`/usr/local/lib/ruby/1.8/i386-freebsd6/RRD.so' will be ignored in favor
of those for `RRD.so'.
gmake[4]: Circular /usr/local/lib/ruby/1.8/i386-freebsd6/RRD.so <-
/usr/local/lib/ruby/1.8/i386-freebsd6/RRD.so dependency dropped.
cc -I. -I. -I/usr/local/lib/ruby/1.8/i386-freebsd6 -I. -I../../src
-fPIC -O2 -fno-strict-aliasing -pipe-fPIC  -c main.c
/usr/bin/install -c -o root -g wheel -m 0755 RRD.so
/usr/local/lib/ruby/1.8/i386-freebsd6
install: RRD.so: No such file or directory
gmake[4]: *** [/usr/local/lib/ruby/1.8/i386-freebsd6/RRD.so] Error 71
gmake[4]: Leaving directory
`/usr/ports/net/rrdtool/work/rrdtool-1.2.23/bindings/ruby'
gmake[3]: *** [ruby] Error 2
gmake[3]: Leaving directory
`/usr/ports/net/rrdtool/work/rrdtool-1.2.23/bindings'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory
`/usr/ports/net/rrdtool/work/rrdtool-1.2.23/bindings'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/ports/net/rrdtool/work/rrdtool-1.2.23'
gmake: *** [all] Error 2
*** Error code 2

Stop in /usr/ports/net/rrdtool.
*** Error code 1

Stop in /usr/ports/net/rrdtool.
--
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: net/rrdtool fails to build when ruby is installed?

2007-05-06 Thread Henrik Brix Andersen
Hi,

On Sat, May 05, 2007 at 04:25:41PM -0700, Kian Mohageri wrote:
> I'm running into an error (seen below) when attempting to build the
> latest net/rrdtool when Ruby is installed.

Others (including me) have encountered the exact same issue - see the
ports/112412 PR.

Regards,
Brix
-- 
Henrik Brix Andersen <[EMAIL PROTECTED]>


pgp3yR4KwTmAm.pgp
Description: PGP signature


Re: net/rrdtool fails to build when ruby is installed?

2007-05-07 Thread Steve Clement

Henrik Brix Andersen wrote:

Hi,

On Sat, May 05, 2007 at 04:25:41PM -0700, Kian Mohageri wrote:
  

I'm running into an error (seen below) when attempting to build the
latest net/rrdtool when Ruby is installed.



A first step would be adding the ruby module to the port, see the 
attached diff against the port, if the maintainer could do us the honors :)


As this disable the ruby module by default most users would be "safe" 
for now.


And perhaps someone already found out what causes
the compile issue "against ruby/with gmake"

cheers,

Steve Clement
--- MakefileMon May  7 15:16:59 2007
+++ /usr/ports/net/rrdtool/Makefile Mon May  7 15:14:28 2007
@@ -25,9 +25,19 @@
 
 CONFIGURE_ARGS=--enable-perl-site-install --disable-tcl
 
-OPTIONS=   PYTHON_MODULE   "Build PYTHON bindings" off
+OPTIONS+=  PYTHON_MODULE   "Build PYTHON bindings" off
+OPTIONS+=  RUBY_MODULE "Build RUBY bindings" off
 
 .include 
+.if defined(WITH_RUBY_MODULE)
+USE_RUBY=  yes
+.include "${PORTSDIR}/Mk/bsd.ruby.mk"
+PLIST_SUB+=WITH_RUBY=""
+CONFIGURE_ARGS+=   --enable-ruby
+.else
+CONFIGURE_ARGS+=   --disable-ruby
+PLIST_SUB+=WITH_RUBY="@comment "
+.endif
 .if defined(WITH_PYTHON_MODULE)
 USE_PYTHON=yes
 .include "${PORTSDIR}/Mk/bsd.python.mk"
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: net/rrdtool fails to build when ruby is installed?

2007-05-07 Thread Dmitry Sivachenko
Thank you all for the report.

I will surely fix that after ports thaw...



On Mon, May 07, 2007 at 03:20:21PM +0200, Steve Clement wrote:
> Henrik Brix Andersen wrote:
> >Hi,
> >
> >On Sat, May 05, 2007 at 04:25:41PM -0700, Kian Mohageri wrote:
> >  
> >>I'm running into an error (seen below) when attempting to build the
> >>latest net/rrdtool when Ruby is installed.
> >>
> 
> A first step would be adding the ruby module to the port, see the 
> attached diff against the port, if the maintainer could do us the honors :)
> 
> As this disable the ruby module by default most users would be "safe" 
> for now.
> 
> And perhaps someone already found out what causes
> the compile issue "against ruby/with gmake"
> 
> cheers,
> 
> Steve Clement

> --- Makefile  Mon May  7 15:16:59 2007
> +++ /usr/ports/net/rrdtool/Makefile   Mon May  7 15:14:28 2007
> @@ -25,9 +25,19 @@
>  
>  CONFIGURE_ARGS=  --enable-perl-site-install --disable-tcl
>  
> -OPTIONS= PYTHON_MODULE   "Build PYTHON bindings" off
> +OPTIONS+=PYTHON_MODULE   "Build PYTHON bindings" off
> +OPTIONS+=RUBY_MODULE "Build RUBY bindings" off
>  
>  .include 
> +.if defined(WITH_RUBY_MODULE)
> +USE_RUBY=yes
> +.include "${PORTSDIR}/Mk/bsd.ruby.mk"
> +PLIST_SUB+=  WITH_RUBY=""
> +CONFIGURE_ARGS+= --enable-ruby
> +.else
> +CONFIGURE_ARGS+= --disable-ruby
> +PLIST_SUB+=  WITH_RUBY="@comment "
> +.endif
>  .if defined(WITH_PYTHON_MODULE)
>  USE_PYTHON=  yes
>  .include "${PORTSDIR}/Mk/bsd.python.mk"

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"