Re: [exim] compile errors on 4.61 pipe transport build error…

Pàgina inicial
Delete this message
Reply to this message
Autor: Jim Pazarena
Data:  
A: exim-users
Assumptes vells: Re: [exim] compile errors on 4.61 .. 2nd try
Assumpte: Re: [exim] compile errors on 4.61 pipe transport build error failure
W B Hacker wrote:
> Jim Pazarena wrote:
>
>> first message had a silly typo; sorry
>
>
> Dunno if this fits, but problems w/r pipe transport build were discused
> very recently under thread:
>
> "FreeBSD pipe_transport_setup build failure"
>
> Wherein the flag " -lutil " seemed to have (sometimes) been required.
>


adding -lutil worked perfectly.

FreeBSD 6.0, direct compilation from exim distribution

> FWIW, exim-postgresql 4.61 from ports has compiled w/o that flag, and
> w/o error for me on several 4.11-STABLE servers *while running*, using
> the 'portupgrade' tool, then '~/exim.sh restart'. Effectively zero
> offline time, and no hassle.
>
> But no special flags, either.
>
> HOWEVER, neither of your posts said:
>
> - *which version* of FreeBSD:
> i,e - 4.11, 5.X, 6.X, or 7.X,
>
> OR
>
> - if you were working from the ports, or from the master tarball + edit
> of local build configuration.
>
> HTH,
>
> Bill
>
>>
>> this is the first time in YEARS that I had a compile error with a
>> new version of exim on FreeBSD
>>
>> the error message from gcc is at the very bottom. I would appreciate
>> it if someone could point me in the right direction to troubleshoot
>> this.
>>
>> regards,
>> Jim
>>
>> gcc dk.c
>>
>> awk '{ print ($1+1) }' cnumber.h > cnumber.temp
>> rm -f cnumber.h; mv cnumber.temp cnumber.h
>> gcc version.c
>> rm -f exim
>> gcc -o exim
>> transports/transports.a(pipe.o)(.text+0x36): In function
>> `pipe_transport_setup':
>> : undefined reference to `login_getpwclass'
>> transports/transports.a(pipe.o)(.text+0x4d): In function
>> `pipe_transport_setup':
>> : undefined reference to `setclassresources'
>> transports/transports.a(pipe.o)(.text+0x5b): In function
>> `pipe_transport_setup':
>> : undefined reference to `login_close'
>> *** Error code 1


Thanks!
Jim