On Wed, 11 Jul 2007 15:35:44 -0700
snowcrash+freebsd <[EMAIL PROTECTED]> mentioned:

> hi yuri,
> 
> > > known issue? something /i/ need to do?
> > > thanks!
> >
> > Builds here. Can you try without those extra CFLAGS?
> 
> 
> per suggestion, changing in my
> 
>       /usr/local/etc/ports.conf
> 
> 
>       *:\
>       CFLAGS= -O2 -pipe -funroll-loops -s -frename-registers 
> -fomit-frame-pointer | \
>       CXXFLAGS= -O2 -pipe -funroll-loops -s -frename-registers
>       
>       ...
>       
>       lang/ruby18:\
> +++     CFLAGS= -O2 -pipe            | \
> +++     CXXFLAGS= -O2 -pipe          | \
>         WITHOUT_PTHREADS=true        | \
>         WITHOUT_ONIGURUMA=true       | \
>         WITHOUT_GCPATCH=true         | \
>         WITHOUT_IPV6=true            | \
>         WITHOUT_RDOC=true            | \
>         WITHOUT_DEBUG=true           | \
>         BATCH=Yes
>       ...
> 
> then (since a prior 'deinstall' of ruby18 while monkeying around with
> this temporarily killed my 'portinstall' ...),
> 
>       cd /usr/ports/lang/ruby18
>       make deinstall rmconfig clean install
> 
> seems to behave itself now, completing without error.
> 
> and, fwiw, a subsequent,
> 
>       cd /usr/ports/ports-mgmt/portupgrade
>       make deinstall rmconfig install clean
> 
> which depends on the ruby install, also builds ok.
> 
> so, it seems that the port version bump from,
> 
>       ruby-1.8.6,1
> 
> to,
> 
>       ruby-1.8.6_1,1
> 
> introduces a 'sensitivity' to one or more of those C*FLAGS ... as, the
> prior version built just fine.
> 

Builds fine with your cflags on i386/current.

Could you, please, send me your `dmesg` output as well as the coredump
along with the executable,  that produces it?

-- 
Stanislav Sedov
ST4096-RIPE

Attachment: pgpODmC2HlhMc.pgp
Description: PGP signature

Reply via email to