apache: size mismatch symbol(_res) and symbol(_sys_errlist)

[Nick Guenther]

On 8/28/06, Lou Hevly <soc at visca.com> wrote:
> At 09:57 28/08/06 -0400, Nick Guenther wrote:
> >On 8/28/06, Lou Hevly <soc at visca.com> wrote:
> > > Greetings:
> > >
> > > After doing an update from 3.7 to 3.8, when starting up apache
> > using:
> > > '/usr/sbin/httpd -u -DSSL'
> > >
> > > I get the following message, which I don't understand:
> > >
> > > /usr/sbin/httpd:/usr/lib/libc.so.34.2: /usr/lib/libc.so.38.2 :
> > WARNING:
> > > symbol(_res) size mismatch, relink your program
> > > /usr/sbin/httpd:/usr/lib/libc.so.34.2: /usr/lib/libc.so.38.2 :
> > WARNING:
> > > symbol(_sys_errlist) size mismatch, relink your program
> > >
> > > The server works fine.
> > >
> > > Then, after upgrading to 3.9, I get a similar message:
> > >
> > > /usr/sbin/httpd:/usr/lib/libc.so.34.2: /usr/lib/libc.so.39.0 :
> > WARNING:
> > > symbol(_res) size mismatch, relink your program
> > > /usr/sbin/httpd:/usr/lib/libc.so.34.2: /usr/lib/libc.so.39.0 :
> > WARNING:
> > > symbol(_sys_errlist) size mismatch, relink your program
> > >
> > > Can anyone please explain what the problem is here?
> > >
> > > Thank-you.
> >
> >Your libc doesn't seem to match your httpd. Somehow. Odd. Maybe there
> >is something in the FAQ.
>
> I Googled with no helpful result the following:
>
> site:openbsd.org inurl:faq libc httpd
>
> Does this look right?
> lou:/usr/lib
> $ ls -l libc.*
> -r--r--r--  1 root  bin  7996316 Mar  2 09:06 libc.a
> -r--r--r--  1 root  bin   657260 Nov  2  2004 libc.so.30.3
> -r--r--r--  1 root  bin   677742 Sep 17  2004 libc.so.34.1
> -r--r--r--  1 root  bin   693081 Mar 20  2005 libc.so.34.2
> -r--r--r--  1 root  bin   683405 Sep 10  2005 libc.so.38.2
> -r--r--r--  1 root  bin  3953440 Mar  2 09:06 libc.so.39.0
>
> >Maybe your httpd has some kind of nonstandard
> >hack in it.

I really have no idea. Google however does:
http://www.gnu.org/software/libc/FAQ.html#s-2.20

The strange thing though is why it's cropped up. Are you sure you
updated httpd correctly? If you did, then there seems to be some
deeper bug lurking here.

-Nick