🚀 go-pugleaf

> Nntp-Posting-Host: leps5.phys.psu.edu

> In article <1gqdsgINNom1@rodan.UU.NET> rsalz@rodan.UU.NET (Rich Salz) writes:
>>INN includes the NNTP1.5 'clientlib' API, built on top of the INN routines
>>documented in libinn.3.  I have built rn with them.  I have never built trn,
>>but as long as it doesn't stray outside the clientlib set, it should be
>>possible to edit trn/Makefile so that it links with libinn.a before 
>>the NNTP clinetlib.

> That's the problem.  If you want to build trn with the ability to read the
> threads via NNTP, it wants a few extra routines in the clientlib (those are
> provided by the patches in the trn/nntp directory).  Maybe if I get time I will
> try to massage the trn patches into INN's clientlib.  (Or has anyone else done
> this? :-) )

It's easy to check.  All I did was use the nntp.h from nntp-1.5.11t 
and link trn against INN's clientlib.  Looked at the undefined symbols and
found them in the trn patch.
The only trn patches that needs to be added into INN's clientlib are
rawcheck_serv and rawget_serv. ( I didn't actually patch it into INN's
clientlib yet. )

The trn binary I built with INN libs seems to run fine.

--
|                                     ** Place Disclaimer Here  **            |
| Tasuki Hirata                "Hell, if you understand everything I say,     |
| sukes@eng.umd.edu                   you'd be me."  --  Miles Davis          |