[asterisk-bugs] [JIRA] (ASTERISK-24663) [patch] Unnamed semaphore autoconf check fails on cross compilation

[abelbeck (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-24663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224394#comment-224394 ] 

abelbeck commented on ASTERISK-24663:
-------------------------------------

# uname -a
Linux pbx4 3.2.62-astlinux #1 SMP PREEMPT Sun Jan 11 09:56:52 CST 2015 i686 GNU/Linux

We use eglibc via a crosstool-ng toolchain and the Buildroot environment.

Since these are embedded devices, selecting the most efficient method "HAS_WORKING_SEMAPHORE 1" is good.

> [patch] Unnamed semaphore autoconf check fails on cross compilation
> -------------------------------------------------------------------
>
>                 Key: ASTERISK-24663
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24663
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>    Affects Versions: 13.1.0
>         Environment: AstLinux 1.2
>            Reporter: abelbeck
>         Attachments: asterisk-13-anonymous-semaphores.patch
>
>
> The Asterisk 13 configure.ac checks for HAS_WORKING_SEMAPHORE but does not have an option for cross-compiling so it fails with an exit.
> {noformat}
> checking for working unnamed semaphores... configure: error: in `/home/user/astlinux/1.0/output/build/asterisk-13.1.0':
> configure: error: cannot run test program while cross compiling
> See `config.log' for more details
> {noformat}
> Attached is patch that defaults to "HAS_WORKING_SEMAPHORE 1" if cross-compiling is detected.  I'm not sure if this is correct default, but seems to work for cross-compiling Linux.
> If this is worth a configure option, I'll leave that to the autoconf gurus.



--
This message was sent by Atlassian JIRA
(v6.2#6252)