ruby18 not compiling on -CURRENT

[SANETO Takanori]

I had same problem.
It seems a bug in tr. (tr -d '\015' <confdefs.h produces empty output)
In latest -CURRENT (usr.bin/tr/cset.c 1.2), it was fixed and ruby18 can be
built just fine.

----- Original Message ----- 
From: "Sean McNeil" <sean at mcneil.com>
To: "Akinori MUSHA" <knu at iDaemons.org>
Cc: <freebsd-ports at freebsd.org>
Sent: Wednesday, July 14, 2004 7:08 AM
Subject: Re: ruby18 not compiling on -CURRENT


> On Tue, 2004-07-13 at 12:56, Akinori MUSHA wrote:
> > At Tue, 13 Jul 2004 11:13:41 -0700,
> > Sean McNeil wrote:
> > > Here is the error I get on my amd64 box running -CURRENT:
> > >
> > > cc -O -pipe   -fPIC -I. -I. -c array.c
> > > In file included from missing.h:133,
> > >                  from ruby.h:670,
> > >                  from main.c:13:
> > > /usr/include/varargs.h:34:2: #error "<varargs.h> is obsolete with this
> > > version of GCC."
> > > /usr/include/varargs.h:35:2: #error "Change your code to use
<stdarg.h>
> > > instead."
> >
> > And what do config.log and config.h say about stdarg.h?
>
> config.log is available at www.mcneil.com/~sean/config.log and it has
> problems with
>   minix/config.h: No such file or directory
> in a couple of places, but the cache at the end says:
> rb_cv_stdarg=yes
> config.h is empty, though.
>
> Sean
>
>
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
>