I had a good compilation on Gentoo-x86 2005.1 with attached ebuild file, which is modified according to Gentoo ebuild guildeline and ebuild maintainer's comments. Please include this ebuild for final release if possible. There are some warning messages (example below) during compilation, but I checked previously that these can be safely ignored and seems there is no clear instruction on how to deal with it. Warning message example: " usr/lib/openser/modules/maxfwd.so usr/lib/openser/modules/maxfwd.so will contain runtime text relocations Text relocations require a lot of extra work to be preformed by the dynamic linker which will cause serious performance impact on IA-32 and might not function properly on other architectures hppa for example. If you are a programmer please take a closer look at this package and consider writing a patch which addresses this problem." -- Cheng On Oct 27, 2005, at 2:58 AM, Daniel-Constantin Mierla wrote:

See below. On 10/27/05, Daniel-Constantin Mierla <daniel(a)voice-system.ro> wrote: The warning message comes from Gentoo's Portage. Among the steps of building and installing the package source, there is a step of examing ELF binaries. In fact, it has such warning message for each .so file. I already saw such warnings months ago when I deal with OpenSER's ebuild for the first time. I did some google back then, and seems it's ok to ignore them. I don't know about others, but two Gentoo machines running OpenSER installed by this ebuild work fine in our internal testing environment (casual testing by a few people though).

Sure, I can do that. My goal on this one is actually getting the ebuild accepted into official ebuild tree. That way, folks running Gentoo can easily install OpenSER without looking around. :-)

- Cheng

Hi! some question: for radius support - is radiusclient-ng 5.1 fine? what about TLS: IMO it should be compiled by default, or we should have both: packages with TLS and without TLS support. I think it is not a good idea to announce "first TLS-enabled" SIP proxy and then the compiled packages are not TLS capable. Thus, then we also has to add the openssl packages to the requriments for the openser package. regards klaus Daniel-Constantin Mierla wrote: _______________________________________________ Users mailing list Users(a)openser.org http://openser.org/cgi-bin/mailman/listinfo/users

Bogdan-Andrei Iancu wrote: Sure. But is it possible to add the openssl package to the requriments for debian, e.g. dynamically when TLS==1 ?

regards klaus