Patch for compilation errors with INN 2.3.2
roman at pobox.com
Fri Jul 20 07:32:27 UTC 2001
I came to the mistaken conclusion that nobody used forte C
to compile inn since there was a problem getting configure
to properly detect and link in the appropriate libraries
when using it and the --with-openssl option (it would seem
that Forte C is a bit pickier about the order in which the
libraries are linked in). The reason I thought/think that
the compiler might be to blame is that I tried to
reinitialising the history* files (as well as the cycbuffs
used for CNFS) several times, through several recompiles
(with the same configure options) using Forte C and never
was able to get grephistory to give me the correct tokens.
As soon as I recompiled (with exactly the same options)
using gcc, the problem went away and everything is working
as one would expect. I think we might be running an
unpatched version of Forte C, when I get to work tomorrow I
can find out if this is the case. It's always possible that
the problem is somewhere between the keyboard and the chair,
but I've taken a lot of time and made an effort to try to
rule it out in this case. :-)
I can set up another news box with the forte C compiled
version of INN to reproduce the problem and then I will mail
you the resulting history*. How does that sound?
On Fri, Jul 20, 2001 at 06:57:17AM +0100, Alex Kiernan wrote:
>Russ Allbery <rra at stanford.edu> writes:
>> Roman Gollent <roman at pobox.com> writes:
>> > Ok, I feel reasonably confident at this point that grephistory/dbz works
>> > as it should (having recompiled with gcc). I would highly recommend
>> > that you add an advisory note to INSTALL that warns against attempting
>> > to use Forte C to compile INN.
>> I'm very curious what broke... sounds like I need to try building my test
>> server with Forte C and figure it out. INN should support any ANSI
>> compiler. Are there any more details?
>Forte C 6u1 is all I use - I don't even have gcc installed on any of
>my build boxes, so I want to see what's really going on with this
>before blaming the compiler.
>Alex Kiernan, Principal Engineer, Development, Thus PLC
More information about the inn-bugs