At Wed, 01 Nov 2006 19:32:13 -0500,
Matt Kettler wrote:
>
> AIDA Shinra wrote:
> > At Fri, 27 Oct 2006 20:27:27 -0400,
> >> Ok, upon further testing, it stops blowing up if I build with ./configure.
> >>
> >> Only when I use: "--enable-dnsrbl --with-libbind=/usr/lib/" does it blow up.
> >> That suggests that my build of libbind isn't thread safe.
> >
> > I think --with-libbind=/usr/local is appropreate here.
>
> OK.
>
> >
> >> I tried adding --enable-threads to the configure for bind, rebuilt/reinistalled
> >> libbind (strangely only libbind.a changed, the .so had the same md5sum as the
> >> old one. Yes I did make clean first.. so it did rebuild it.). No help.
> >
> > It is intentional design. BIND guys do not hope existing programs
> > link spontaneously new libbind spontaneously.
> >
> >> This is the configure I'm using in bind 9.2.1:
> >>
> >> /configure --with-libtool --enable-libbind --enable-threads
> >> --with-randomdev=/dev/random
> >>
> >> (and yes, I'm correctly moving libbind.* from /usr/local/lib to /usr/lib where
> >> ld will find them)
> >
> > It looks dangerous. It may lead ABI crashes between /usr/include/*.h
> > and /usr/lib/libbind.a.
> >
>
>
> Ok, so I did the following:
>
> 1) removed libbind.* from /usr/lib/, leaving them in /usr/local/lib/ where binds
> build process put them.
BIND may put headers and libraries at /usr/local/bind/{include,lib} in
some situation. Are you sure libbind.a was at /usr/local/lib and
headers were at /usr/local/include?
> 2) modified /etc/ld.so.conf to include /usr/local/lib, and ran ldconfig to build
> the cache.
The libbind.a is a static library. No need for ldconfig.
> 3) rebuilt milter-greylist:
> ./configure --enable-dnsrbl --with-libbind=/usr/local/lib/
> make clean
> make
>
> Still crashes, same way.
Don't addappend /lib/ after --with-libbind=/usr/local.
Then tell me your make log and the result of "ldd milter-greylist".Message
Re: [milter-greylist] Re: milter-greylist 3.0rc6 segmentation fault.
2006-11-02 by AIDA Shinra
Attachments
- No local attachments were found for this message.