Skip to contentSkip to conversation

Support for systems without [gs]etitimer API

PATCH New Eugeniy Meshcheryakov 2 participants 2 messages Jan 2, 2014

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Support for systems without [gs]etitimer API

Hi,

After enabling the testsuite execution when building Debian packages I noticed that the testsuite fails on Debian/Hurd. Every testcase was failing with Unix_error exception, because while Hurd has getitimer function, it just returns ENOSYS error there.

The attached patch detects whether the system has working getitimer function, and if not, makes coccinelle use alarm() API instead.

With this patch coccinelle builds fine on all Debian architectures with 386 successful test cases (expected: 377).

Regards,
Eugeniy Meshcheryakov
-------------- next part --------------
A non-text attachment was scrubbed...
Name: detect-itimer.diff
Type: text/x-diff
Size: 369 bytes
Desc: not available
URL: <https://systeme.lip6.fr/pipermail/cocci/attachments/20140102/a1b7f518/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <https://systeme.lip6.fr/pipermail/cocci/attachments/20140102/a1b7f518/attachment.asc>

Applied
#1 lore raw

PATCH 1/1 Support for systems without [gs]etitimer API

Quoted 7 lines · Eugeniy Meshcheryakov

Hi,

After enabling the testsuite execution when building Debian packages I noticed that the testsuite fails on Debian/Hurd. Every testcase was failing with Unix_error exception, because while Hurd has getitimer function, it just returns ENOSYS error there.

Quoted 5 lines

The attached patch detects whether the system has working getitimer function, and if not, makes coccinelle use alarm() API instead.

With this patch coccinelle builds fine on all Debian architectures with 386 successful test cases (expected: 377).

Applied. Thanks!

julia