You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Vladimir Beliaev (JIRA)" <ji...@apache.org> on 2007/02/27 15:12:05 UTC
[jira] Created: (HARMONY-3255) [drlvm][winx64][build]
COMPILER_CFG_SCRIPT must be set automatically
[drlvm][winx64][build] COMPILER_CFG_SCRIPT must be set automatically
---------------------------------------------------------------------
Key: HARMONY-3255
URL: https://issues.apache.org/jira/browse/HARMONY-3255
Project: Harmony
Issue Type: Improvement
Components: DRLVM
Environment: windows/em64t
Reporter: Vladimir Beliaev
I tried to build drlvm (after classlib build) according to federated build instruction & failed at very beginning with:
<trunk>/working_vm/build $ ./build.bat update
error: Cannot guess the location of compiler configuration script
Please set COMPILER_CFG_SCRIPT and/or CXX
*
* Please, refer to README.txt for details.
*
The mentioned README.txt redirects to ../README.txt (.......), and this ../README.txt says nothing about setting COMPILER_CFG_SCRIPT, it just claims "The supported configurations are Windows* IA-32 and Linux* IA-32."...
Anyway, to pass windows/em64t build one needs to export COMPILER_CFG_SCRIPT=EM64T in terminal before the build (can be used as workaround for now).
Would be helpfull to get this setting done automatically in drlvm build files.
Thanks
Vladimir Beliaev
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (HARMONY-3255) [drlvm][winx64][build]
COMPILER_CFG_SCRIPT must be set automatically
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Shimansky closed HARMONY-3255.
--------------------------------------
No response, assuming ok.
> [drlvm][winx64][build] COMPILER_CFG_SCRIPT must be set automatically
> ---------------------------------------------------------------------
>
> Key: HARMONY-3255
> URL: https://issues.apache.org/jira/browse/HARMONY-3255
> Project: Harmony
> Issue Type: Improvement
> Components: DRLVM
> Environment: windows/em64t
> Reporter: Vladimir Beliaev
> Assignee: Gregory Shimansky
> Attachments: H3255.patch
>
>
> I tried to build drlvm (after classlib build) according to federated build instruction & failed at very beginning with:
> <trunk>/working_vm/build $ ./build.bat update
> error: Cannot guess the location of compiler configuration script
> Please set COMPILER_CFG_SCRIPT and/or CXX
> *
> * Please, refer to README.txt for details.
> *
> The mentioned README.txt redirects to ../README.txt (.......), and this ../README.txt says nothing about setting COMPILER_CFG_SCRIPT, it just claims "The supported configurations are Windows* IA-32 and Linux* IA-32."...
> Anyway, to pass windows/em64t build one needs to export COMPILER_CFG_SCRIPT=EM64T in terminal before the build (can be used as workaround for now).
> Would be helpfull to get this setting done automatically in drlvm build files.
> Thanks
> Vladimir Beliaev
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HARMONY-3255) [drlvm][winx64][build]
COMPILER_CFG_SCRIPT must be set automatically
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Shimansky resolved HARMONY-3255.
----------------------------------------
Resolution: Fixed
Patch applied at 512802. Please check that it was applied as expected.
> [drlvm][winx64][build] COMPILER_CFG_SCRIPT must be set automatically
> ---------------------------------------------------------------------
>
> Key: HARMONY-3255
> URL: https://issues.apache.org/jira/browse/HARMONY-3255
> Project: Harmony
> Issue Type: Improvement
> Components: DRLVM
> Environment: windows/em64t
> Reporter: Vladimir Beliaev
> Assigned To: Gregory Shimansky
> Attachments: H3255.patch
>
>
> I tried to build drlvm (after classlib build) according to federated build instruction & failed at very beginning with:
> <trunk>/working_vm/build $ ./build.bat update
> error: Cannot guess the location of compiler configuration script
> Please set COMPILER_CFG_SCRIPT and/or CXX
> *
> * Please, refer to README.txt for details.
> *
> The mentioned README.txt redirects to ../README.txt (.......), and this ../README.txt says nothing about setting COMPILER_CFG_SCRIPT, it just claims "The supported configurations are Windows* IA-32 and Linux* IA-32."...
> Anyway, to pass windows/em64t build one needs to export COMPILER_CFG_SCRIPT=EM64T in terminal before the build (can be used as workaround for now).
> Would be helpfull to get this setting done automatically in drlvm build files.
> Thanks
> Vladimir Beliaev
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-3255) [drlvm][winx64][build]
COMPILER_CFG_SCRIPT must be set automatically
Posted by "Pavel Pervov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Pervov updated HARMONY-3255:
----------------------------------
Attachment: H3255.patch
The patch fixes the requirement of defining COMPILER_CFG_SCRIPT on x86_64 platform.
It now defaults to Microsoft Visual Studio 2005.
> [drlvm][winx64][build] COMPILER_CFG_SCRIPT must be set automatically
> ---------------------------------------------------------------------
>
> Key: HARMONY-3255
> URL: https://issues.apache.org/jira/browse/HARMONY-3255
> Project: Harmony
> Issue Type: Improvement
> Components: DRLVM
> Environment: windows/em64t
> Reporter: Vladimir Beliaev
> Attachments: H3255.patch
>
>
> I tried to build drlvm (after classlib build) according to federated build instruction & failed at very beginning with:
> <trunk>/working_vm/build $ ./build.bat update
> error: Cannot guess the location of compiler configuration script
> Please set COMPILER_CFG_SCRIPT and/or CXX
> *
> * Please, refer to README.txt for details.
> *
> The mentioned README.txt redirects to ../README.txt (.......), and this ../README.txt says nothing about setting COMPILER_CFG_SCRIPT, it just claims "The supported configurations are Windows* IA-32 and Linux* IA-32."...
> Anyway, to pass windows/em64t build one needs to export COMPILER_CFG_SCRIPT=EM64T in terminal before the build (can be used as workaround for now).
> Would be helpfull to get this setting done automatically in drlvm build files.
> Thanks
> Vladimir Beliaev
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HARMONY-3255) [drlvm][winx64][build]
COMPILER_CFG_SCRIPT must be set automatically
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Shimansky reassigned HARMONY-3255:
------------------------------------------
Assignee: Gregory Shimansky
> [drlvm][winx64][build] COMPILER_CFG_SCRIPT must be set automatically
> ---------------------------------------------------------------------
>
> Key: HARMONY-3255
> URL: https://issues.apache.org/jira/browse/HARMONY-3255
> Project: Harmony
> Issue Type: Improvement
> Components: DRLVM
> Environment: windows/em64t
> Reporter: Vladimir Beliaev
> Assigned To: Gregory Shimansky
> Attachments: H3255.patch
>
>
> I tried to build drlvm (after classlib build) according to federated build instruction & failed at very beginning with:
> <trunk>/working_vm/build $ ./build.bat update
> error: Cannot guess the location of compiler configuration script
> Please set COMPILER_CFG_SCRIPT and/or CXX
> *
> * Please, refer to README.txt for details.
> *
> The mentioned README.txt redirects to ../README.txt (.......), and this ../README.txt says nothing about setting COMPILER_CFG_SCRIPT, it just claims "The supported configurations are Windows* IA-32 and Linux* IA-32."...
> Anyway, to pass windows/em64t build one needs to export COMPILER_CFG_SCRIPT=EM64T in terminal before the build (can be used as workaround for now).
> Would be helpfull to get this setting done automatically in drlvm build files.
> Thanks
> Vladimir Beliaev
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-3255) [drlvm][winx64][build]
COMPILER_CFG_SCRIPT must be set automatically
Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Beliaev updated HARMONY-3255:
--------------------------------------
Patch Info: [Patch Available]
> [drlvm][winx64][build] COMPILER_CFG_SCRIPT must be set automatically
> ---------------------------------------------------------------------
>
> Key: HARMONY-3255
> URL: https://issues.apache.org/jira/browse/HARMONY-3255
> Project: Harmony
> Issue Type: Improvement
> Components: DRLVM
> Environment: windows/em64t
> Reporter: Vladimir Beliaev
> Attachments: H3255.patch
>
>
> I tried to build drlvm (after classlib build) according to federated build instruction & failed at very beginning with:
> <trunk>/working_vm/build $ ./build.bat update
> error: Cannot guess the location of compiler configuration script
> Please set COMPILER_CFG_SCRIPT and/or CXX
> *
> * Please, refer to README.txt for details.
> *
> The mentioned README.txt redirects to ../README.txt (.......), and this ../README.txt says nothing about setting COMPILER_CFG_SCRIPT, it just claims "The supported configurations are Windows* IA-32 and Linux* IA-32."...
> Anyway, to pass windows/em64t build one needs to export COMPILER_CFG_SCRIPT=EM64T in terminal before the build (can be used as workaround for now).
> Would be helpfull to get this setting done automatically in drlvm build files.
> Thanks
> Vladimir Beliaev
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.