Error while building realview_pbx_a9 BSP with the new build system

[Sebastian Huber]

On 03/08/2020 18:25, Gedare Bloom wrote:

> On Mon, Aug 3, 2020 at 10:17 AM Utkarsh Rai<utkarsh.rai60 at gmail.com>  wrote:
>> When I use the above branch I get the following error on './waf install ' -
>>
>> Build failed
>> Traceback (most recent call last):
>>    File "/home/utkarsh/new_build/rtems/.waf-2.0.20-36f5354d605298f6a89c09e0c7ef6c1d/waflib/Task.py", line 180, in process
>>      ret=self.run()
>>    File "/home/utkarsh/new_build/rtems/.waf-2.0.20-36f5354d605298f6a89c09e0c7ef6c1d/waflib/Build.py", line 554, in run
>>      x.parent.mkdir()
>>    File "/home/utkarsh/new_build/rtems/.waf-2.0.20-36f5354d605298f6a89c09e0c7ef6c1d/waflib/Node.py", line 179, in mkdir
>>      self.parent.mkdir()
>>    File "/home/utkarsh/new_build/rtems/.waf-2.0.20-36f5354d605298f6a89c09e0c7ef6c1d/waflib/Node.py", line 179, in mkdir
>>      self.parent.mkdir()
>>    File "/home/utkarsh/new_build/rtems/.waf-2.0.20-36f5354d605298f6a89c09e0c7ef6c1d/waflib/Node.py", line 179, in mkdir
>>      self.parent.mkdir()
>>    File "/home/utkarsh/new_build/rtems/.waf-2.0.20-36f5354d605298f6a89c09e0c7ef6c1d/waflib/Node.py", line 179, in mkdir
>>      self.parent.mkdir()
>>    File "/home/utkarsh/new_build/rtems/.waf-2.0.20-36f5354d605298f6a89c09e0c7ef6c1d/waflib/Node.py", line 179, in mkdir
>>      self.parent.mkdir()
>>    File "/home/utkarsh/new_build/rtems/.waf-2.0.20-36f5354d605298f6a89c09e0c7ef6c1d/waflib/Node.py", line 188, in mkdir
>>      raise Errors.WafError('Could not create the directory %r'%self)
>> WafError: Could not create the directory /opt/rtems
>>
> Most likely you don't have a /opt/rtems directory, and that is being
> used as a default prefix for install. Try to set the prefix/install
> point yourself to a directory you 'own' already.
>
> The other option is to create /opt/rtems, and chown to your user, e.g.,
>
> sudo mkdir /opt/rtems
> sudo chown utkarsh:utkarsh /opt/rtems
>
> this works fine for single-user *nix development
>
I think we should cover this somehow in the documentation. This looks 
like a common issue for someone using this for the first time.