In message <20180321055215.jm3ybhkz4vqgs...@mycre.ws>,
Robert Edmonds wrote:
>{... long explanation of why things are as they are, snipped...}
Thanks for all this Robert. I guess it all makes sense. I just
loath complexity. But sometimes it is unavoidable.
>If you are parsing packets and c
Ronald F. Guilmette wrote:
> In message <20180320205558.23ld7b2orcfky...@mycre.ws>,
> Robert Edmonds wrote:
>
> >Rick Dicaire wrote:
> >> For libbind9, https://packages.ubuntu.com/trusty/libbind9-90
> >
> >You would also need the ".so" symlink in order to link with -lbind9,
> >which is in this p
Tony Finch wrote:
> So the classic libc resolver API is basically the BIND4 libbind, and the
> resolvers in glibc and the BSDs still descend from this codebase.
>
> BIND8 was a significant revision of the BIND code (e.g. the improved
> configuration syntax, support for DNS extensions) but I get th
In message ,
Tony Finch wrote:
>BIND9 was a new codebase with very different internal library APIs, and an
>ambition to completely revamp the libc -> resolver interface - this is
>what the lwresd stuff was about. But no unix adopted this new design into
>its libc, so the ambition withered.
>
>S
Ronald F. Guilmette wrote:
>
> Second, I wish I undrstood your comment that the the files that appear
> on my Ubuntu system and whose names begin with "libbind9" are "unrelated"
> to the "real thing" (ISC) library of the same name.
There are a couple of events that make this confusing (the BIND4
In message <20180320205558.23ld7b2orcfky...@mycre.ws>,
Robert Edmonds wrote:
>Rick Dicaire wrote:
>> For libbind9, https://packages.ubuntu.com/trusty/libbind9-90
>
>You would also need the ".so" symlink in order to link with -lbind9,
>which is in this package:
>https://packages.ubuntu.com/trust
In message <20180320205115.wanrlpfisxx6g...@mycre.ws>,
Robert Edmonds wrote:
>It should be in the SYNOPSIS section :-)
>
>http://manpages.ubuntu.com/manpages/trusty/en/man3/resolver.3.html
>...
>Link with -lresolv.
Doh! yea. You're right. It's right there. Didn't notice.
(Argu
Rick Dicaire wrote:
> For libbind9, https://packages.ubuntu.com/trusty/libbind9-90
You would also need the ".so" symlink in order to link with -lbind9,
which is in this package:
https://packages.ubuntu.com/trusty/libbind-dev. This package is
confusingly named, though, it should probably have been
Ronald F. Guilmette wrote:
> In message <20180320193041.d2bwvgkgyvqem...@mycre.ws>,
> Robert Edmonds wrote:
>
> >For glibc versions that are less than about ten years old, these should
> >be available in libresolv, which is part of glibc.
>
> Thanks Robert! I added -lresolv to the link and now
For libbind9, https://packages.ubuntu.com/trusty/libbind9-90
On Tue, Mar 20, 2018 at 4:02 PM, Ronald F. Guilmette
wrote:
>
> In message <20180320193041.d2bwvgkgyvqem...@mycre.ws>,
> Robert Edmonds wrote:
>
> >> I am porting some code of mine from FreeBSD to this Ubuntu system
> >> and I'm getti
In message <20180320193041.d2bwvgkgyvqem...@mycre.ws>,
Robert Edmonds wrote:
>> I am porting some code of mine from FreeBSD to this Ubuntu system
>> and I'm getting the following unresolved symbols at link time:
>>
>> __res_query
>> __res_mkquery
>> __res_send
>>
>> It seems appar
Ronald F. Guilmette wrote:
> Apologies in advance to all. I am probably just making some
> bonehead mistake or small typo, but...
>
> Can someone please instruct me as to the proper way to link to
> libbind9 on Ubuntu 14.02 LTS?
>
> I am porting some code of mine from FreeBSD to this Ubuntu syst
Apologies in advance to all. I am probably just making some
bonehead mistake or small typo, but...
Can someone please instruct me as to the proper way to link to
libbind9 on Ubuntu 14.02 LTS?
I am porting some code of mine from FreeBSD to this Ubuntu system
and I'm getting the following unresol
13 matches
Mail list logo
