peter green wrote:
>> It looks like you forgot to really Cc them BTW?
> I did but I resent the mail seperately to them afterwards.

Ah, found it. Looks like I'm not CC'ed on that anymore though. I think
"it used to not work otherwise" seems like a very good reason for me to
use the static lib. :-)

Someone had bitlbee removed from testing now, stating eglibc migration
as the reason. I wonder what that means?

> What system are you getting those errors with? in my sid chroot there
> doesn't seem to be any problem linking bitlbee with libresolv.so instead
> of libresolv.a, doing so produces a package with a sane dependency on
> libc6 and an objdump shows all those symbols being in libresolv.so and
> having sane versioning.
> 
Oh, crap. :-( I forgot to re-add -lresolv. With that, things now do work
indeed. I wonder since when that is the case. I can see that at least
2.3.6.ds1-13etch9+ doesn't like this yet. That doesn't really narrow it
down too much yet though. :-)

But in that case, I'll just do a source NMU. I'm not sure if this
actually fixes this exact problem, but at least it's more correct.


Wilmer.

-- 
+-------- .''`.     - -- ---+  +        - -- --- ---- ----- ------+
| wilmer : :'  :  gaast.net |  | OSS Programmer   www.bitlbee.org |
| lintux `. `~'  debian.org |  | Full-time geek  wilmer.gaast.net |
+--- -- -  ` ---------------+  +------ ----- ---- --- -- -        +

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to