Discussion for MacPorts development

Jeremy Lavergne | 12 Jun 2012 22:32

strnlen

While some packages--at least arj--were not expecting Lion to provide its own strnlen [1], it seems the
opposite has also come true in ykpers [2].

Do we have a preferred implementation of strnlen to include in OSes earlier than Lion? Otherwise, I plan to
implement in ykpers the version that is being disabled in arj.

 [1] https://trac.macports.org/ticket/30078
 [2] http://build.macports.org/builders/buildports-snowleopard-x86_64/builds/8089/steps/compile/logs/stdio

Attachment (smime.p7s): application/pkcs7-signature, 8 KiB

While some packages--at least arj--were not expecting Lion to provide its own strnlen [1], it seems the
opposite has also come true in ykpers [2].

Do we have a preferred implementation of strnlen to include in OSes earlier than Lion? Otherwise, I plan to
implement in ykpers the version that is being disabled in arj.

 [1] https://trac.macports.org/ticket/30078
 [2] http://build.macports.org/builders/buildports-snowleopard-x86_64/builds/8089/steps/compile/logs/stdio

headers

Jeremy Huddleston | 12 Jun 2012 22:42

Re: strnlen


On Jun 12, 2012, at 13:32, Jeremy Lavergne
<jeremy@...> wrote:

> While some packages--at least arj--were not expecting Lion to provide its own strnlen [1], it seems the
opposite has also come true in ykpers [2].
> 
> Do we have a preferred implementation of strnlen to include in OSes earlier than Lion?

Make sure the licenses are compatible.  My guess is that the FreeBSD version should be fine for your use.

http://opensource.apple.com/source/Libc/Libc-763.13/string/FreeBSD/strnlen.c

> Otherwise, I plan to implement in ykpers the version that is being disabled in arj.
> 
> [1] https://trac.macports.org/ticket/30078
> [2] http://build.macports.org/builders/buildports-snowleopard-x86_64/builds/8089/steps/compile/logs/stdio