You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Isaac Chiang <is...@gmail.com> on 2013/03/15 03:51:03 UTC
Suggestion for INSTALL markdown
Hi all:
Recently when I tried to install the CS from source, I
encountered a compilation problem.
The log looks like following :
[INFO] Apache CloudStack apidocs ......................... FAILURE [7.302s]
[INFO] Apache CloudStack marvin .......................... SKIPPED
[INFO] Apache CloudStack cloudmonkey cli ................. SKIPPED
[INFO] Apache CloudStack DevCloud ........................ SKIPPED
[INFO] Apache CloudStack DevCloud-KVM .................... SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 4:26.526s
[INFO] Finished at: Fri Mar 15 10:09:58 CST 2013
[INFO] Final Memory: 56M/430M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile) on project
cloud-apidoc: Command execution failed. Process exited with an error: 1
(Exit value: 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR] mvn <goals> -rf :cloud-apidoc
And I found a mail thread discussing about the situation :
http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201210.mbox/%3CD86CDBE4-59C1-4106-A6CE-E16E31BA1D9B@basho.com%3E
After looking into this, the root cause is due to the python version in the
environment.
When I use python with v3.2, the program compilation fails. But it works
fine with python v2.7
As there are many difference between python 2 and 3, is it possible for
INSTALL.md to mention
the suitable python version for compiling?
Thanks
Best Regards
Isaac
--
Gentoo solution:
1. $ eselect python list
[1] python2.7
[2] python3.2 *
2. $ eselect python set 1
3. $ eselect python list
[1] python2.7 *
[2] python3.2
Re: Suggestion for INSTALL markdown
Posted by Sebastien Goasguen <ru...@gmail.com>.
On Mar 15, 2013, at 3:13 AM, prasanna <ts...@apache.org> wrote:
> Python 3000 is a whole different beast. Likely many of our agent
> scripts won't work either. So +1 for adding the caveat in the docs.
> Considering python 3x support when distros depose 2.7 out of their
> repos seems like the way to go. Thoughts?
I have not checked adoption of 3x lately, but I would tend to put this as a low priority work.
I don't see distros dropping 2.7 anytime soon.
Would be me, I would work on something else :)
-sebastien
>
> On 15 March 2013 09:57, Rohit Yadav <bh...@apache.org> wrote:
>> I think we need to make it python version friendly, weird but it works
>> on 2.7 should n't it work on 3.x? Let's fix this, meanwhile I can add
>> info about python version in 2.7 but it should be needed.
>>
>> Regards.
>>
>> On Fri, Mar 15, 2013 at 8:21 AM, Isaac Chiang <is...@gmail.com> wrote:
>>> Hi all:
>>> Recently when I tried to install the CS from source, I
>>> encountered a compilation problem.
>>> The log looks like following :
>>>
>>> [INFO] Apache CloudStack apidocs ......................... FAILURE [7.302s]
>>> [INFO] Apache CloudStack marvin .......................... SKIPPED
>>> [INFO] Apache CloudStack cloudmonkey cli ................. SKIPPED
>>> [INFO] Apache CloudStack DevCloud ........................ SKIPPED
>>> [INFO] Apache CloudStack DevCloud-KVM .................... SKIPPED
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] BUILD FAILURE
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Total time: 4:26.526s
>>> [INFO] Finished at: Fri Mar 15 10:09:58 CST 2013
>>> [INFO] Final Memory: 56M/430M
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [ERROR] Failed to execute goal
>>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile) on project
>>> cloud-apidoc: Command execution failed. Process exited with an error: 1
>>> (Exit value: 1) -> [Help 1]
>>> [ERROR]
>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
>>> switch.
>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>> [ERROR]
>>> [ERROR] For more information about the errors and possible solutions,
>>> please read the following articles:
>>> [ERROR] [Help 1]
>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>>> [ERROR]
>>> [ERROR] After correcting the problems, you can resume the build with the
>>> command
>>> [ERROR] mvn <goals> -rf :cloud-apidoc
>>>
>>> And I found a mail thread discussing about the situation :
>>> http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201210.mbox/%3CD86CDBE4-59C1-4106-A6CE-E16E31BA1D9B@basho.com%3E
>>>
>>> After looking into this, the root cause is due to the python version in the
>>> environment.
>>> When I use python with v3.2, the program compilation fails. But it works
>>> fine with python v2.7
>>>
>>> As there are many difference between python 2 and 3, is it possible for
>>> INSTALL.md to mention
>>> the suitable python version for compiling?
>>>
>>> Thanks
>>>
>>> Best Regards
>>>
>>> Isaac
>>>
>>>
>>>
>>> --
>>> Gentoo solution:
>>> 1. $ eselect python list
>>> [1] python2.7
>>> [2] python3.2 *
>>> 2. $ eselect python set 1
>>> 3. $ eselect python list
>>> [1] python2.7 *
>>> [2] python3.2
Re: Suggestion for INSTALL markdown
Posted by prasanna <ts...@apache.org>.
Python 3000 is a whole different beast. Likely many of our agent
scripts won't work either. So +1 for adding the caveat in the docs.
Considering python 3x support when distros depose 2.7 out of their
repos seems like the way to go. Thoughts?
On 15 March 2013 09:57, Rohit Yadav <bh...@apache.org> wrote:
> I think we need to make it python version friendly, weird but it works
> on 2.7 should n't it work on 3.x? Let's fix this, meanwhile I can add
> info about python version in 2.7 but it should be needed.
>
> Regards.
>
> On Fri, Mar 15, 2013 at 8:21 AM, Isaac Chiang <is...@gmail.com> wrote:
>> Hi all:
>> Recently when I tried to install the CS from source, I
>> encountered a compilation problem.
>> The log looks like following :
>>
>> [INFO] Apache CloudStack apidocs ......................... FAILURE [7.302s]
>> [INFO] Apache CloudStack marvin .......................... SKIPPED
>> [INFO] Apache CloudStack cloudmonkey cli ................. SKIPPED
>> [INFO] Apache CloudStack DevCloud ........................ SKIPPED
>> [INFO] Apache CloudStack DevCloud-KVM .................... SKIPPED
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 4:26.526s
>> [INFO] Finished at: Fri Mar 15 10:09:58 CST 2013
>> [INFO] Final Memory: 56M/430M
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] Failed to execute goal
>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile) on project
>> cloud-apidoc: Command execution failed. Process exited with an error: 1
>> (Exit value: 1) -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
>> switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>> [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with the
>> command
>> [ERROR] mvn <goals> -rf :cloud-apidoc
>>
>> And I found a mail thread discussing about the situation :
>> http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201210.mbox/%3CD86CDBE4-59C1-4106-A6CE-E16E31BA1D9B@basho.com%3E
>>
>> After looking into this, the root cause is due to the python version in the
>> environment.
>> When I use python with v3.2, the program compilation fails. But it works
>> fine with python v2.7
>>
>> As there are many difference between python 2 and 3, is it possible for
>> INSTALL.md to mention
>> the suitable python version for compiling?
>>
>> Thanks
>>
>> Best Regards
>>
>> Isaac
>>
>>
>>
>> --
>> Gentoo solution:
>> 1. $ eselect python list
>> [1] python2.7
>> [2] python3.2 *
>> 2. $ eselect python set 1
>> 3. $ eselect python list
>> [1] python2.7 *
>> [2] python3.2
Re: Suggestion for INSTALL markdown
Posted by Rohit Yadav <bh...@apache.org>.
I think we need to make it python version friendly, weird but it works
on 2.7 should n't it work on 3.x? Let's fix this, meanwhile I can add
info about python version in 2.7 but it should be needed.
Regards.
On Fri, Mar 15, 2013 at 8:21 AM, Isaac Chiang <is...@gmail.com> wrote:
> Hi all:
> Recently when I tried to install the CS from source, I
> encountered a compilation problem.
> The log looks like following :
>
> [INFO] Apache CloudStack apidocs ......................... FAILURE [7.302s]
> [INFO] Apache CloudStack marvin .......................... SKIPPED
> [INFO] Apache CloudStack cloudmonkey cli ................. SKIPPED
> [INFO] Apache CloudStack DevCloud ........................ SKIPPED
> [INFO] Apache CloudStack DevCloud-KVM .................... SKIPPED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 4:26.526s
> [INFO] Finished at: Fri Mar 15 10:09:58 CST 2013
> [INFO] Final Memory: 56M/430M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile) on project
> cloud-apidoc: Command execution failed. Process exited with an error: 1
> (Exit value: 1) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn <goals> -rf :cloud-apidoc
>
> And I found a mail thread discussing about the situation :
> http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201210.mbox/%3CD86CDBE4-59C1-4106-A6CE-E16E31BA1D9B@basho.com%3E
>
> After looking into this, the root cause is due to the python version in the
> environment.
> When I use python with v3.2, the program compilation fails. But it works
> fine with python v2.7
>
> As there are many difference between python 2 and 3, is it possible for
> INSTALL.md to mention
> the suitable python version for compiling?
>
> Thanks
>
> Best Regards
>
> Isaac
>
>
>
> --
> Gentoo solution:
> 1. $ eselect python list
> [1] python2.7
> [2] python3.2 *
> 2. $ eselect python set 1
> 3. $ eselect python list
> [1] python2.7 *
> [2] python3.2