Re: [Exim] Bug in compiling 3.34

Páxina inicial
Borrar esta mensaxe
Responder a esta mensaxe
Autor: Phil Pennock
Data:  
Para: George R . Kasica
CC: exim-users
Asunto: Re: [Exim] Bug in compiling 3.34
On 2001-12-27 at 06:02 -0600, George R . Kasica wrote:
> I'm very aware linux is actually an OS/and or kernel, and for the info


Sorry; I can only go on the evidence available.

> your asking: it WAS Caldera a long time ago but over the last 3 years
> with enhancements and upgrades is more generic than Caldera now.


Do these enhancements/upgrades include a different resolver library?

> Sorry again for not being as PRECISE as yourself, a Makefile Bug
> possibly.


I don't see this. Because ...

> >So you have -lresolv after dns.o on the command-line, so any resolver
> >functions should be found.


Yet they weren't. So your libresolv apparently isn't exporting the
relevant symbols.

You mentioned several rebuilds; have you tried unpacking a fresh source
hierarchy, putting Local/Makefile (and the eximon.conf file, if desired)
in place, and then trying again? Clean go.

> >And they're not. So the resolver functions aren't being linked to. So
> >you're using a really strange set-up, not like any other modern Linux.
> I don't think its THAT strange, other code has compiled just fine in
> the past including 3.33.


Well, something strange is going on. libc is automatically linked,
unless gcc is told not to. -lresolv was there, despite apparently not
being needed (that, or your host(1) command doesn't work). So the
"missing" symbols should all be there. No-one else has reported
problems with a Linux distribution, so it seems to be specific to your
environment. Which is a highly hacked-about system.

If a system has had three years of custom modifications made to it, the
sysadmin should be able to handle the demands of a custom environment
and, when asking for help, know to describe what's different and
recognise that if a widely-used package works for everyone else, it
might very well not be a 'bug' in the package.

> [root@eagle /lib]# ldd `type -p host`
>         libc.so.6 => /usr/local/lib/libc.so.6 (0x40015000)
>         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)


Do you happen to recall if the previous build recognised your system as
Linux-libc5 instead of Linux? What did your system start out as? What
is your current exim binary linked against?
--
Just because an idea is popular don't make it right. -- Jim from 'Huck Finn'