You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@stdcxx.apache.org by "Martin Sebor (JIRA)" <ji...@apache.org> on 2011/03/05 22:03:45 UTC
[jira] Assigned: (STDCXX-1051) Stdcxx build process needs to be
able to run configuration executable files created by the build system
during configuration step on emulators in order to cross compile the
library.
[ https://issues.apache.org/jira/browse/STDCXX-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Sebor reassigned STDCXX-1051:
------------------------------------
Assignee: Martin Sebor
> Stdcxx build process needs to be able to run configuration executable files created by the build system during configuration step on emulators in order to cross compile the library.
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: STDCXX-1051
> URL: https://issues.apache.org/jira/browse/STDCXX-1051
> Project: C++ Standard Library
> Issue Type: Improvement
> Components: Build and Installation
> Reporter: Wojciech Meyer
> Assignee: Martin Sebor
> Attachments: STDCXX-1051-cross-compilation.patch
>
>
> We are trying to cross compile stdcxx library. The problem we are facing
> is that there is no way of telling stdcxx build system, that we don't
> want to run configuration files created by configuration step by build
> system directly on a host system (through a shell).
> For instance, this command (taken from log):
> ./UNISTD_DECL
> invoked during configuration process runs natively the executable through
> a shell.
> However we want to be able to run it on a emulator like this:
> <path to our emulator> UNISTD_DECL
> This command will run the UNISTD_DECL through an emulator.
> The patch we are proposing, is to introduce a new Makefile variable, called
> EXEC_RUNNER, which allows us to do it.
> EXEC_RUNNER defaults to "/usr/bin/sh -c". so it does not interfere with
> the rest of build process (at least on Unix/MSys/Cygwin environment,
> pure Win32 platform has completely separate build system).
> Patch is against `trunk'.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira