On Mon, Aug 3, 2020 at 10:17 AM Utkarsh Rai <utkarsh.ra...@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
> On Mon, Aug 3, 2020 at 9:42 PM Sebastian Huber
> <sebastian.hu...@embedded-brains.de> wrote:
>>
>> On 03/08/2020 16:41, Utkarsh Rai wrote:
>>
>> > Hello,
>> > I have been trying out the new build system. Unfortunately, while
>> > building for the realview_pbx_a9 BSP I get the following error on '
>> > ./waf install ' -
>> >
>> > "
>> > Waf: Entering directory `/home/utkarsh/new_build/rtems/build'
>> > Waf: Leaving directory `/home/utkarsh/new_build/rtems/build'
>> > 'install' finished successfully (0.289s)
>> > Waf: Entering directory
>> > `/home/utkarsh/new_build/rtems/build/arm/realview_pbx_a9_qemu'
>> > Waf: Leaving directory
>> > `/home/utkarsh/new_build/rtems/build/arm/realview_pbx_a9_qemu'
>> >
>> > source not found: 'cpukit/include/rtems/system.h' in bld(target='',
>> > idx=59, install_task=
>> > {task 139909380107600: inst -> }, dest='${BSP_INCLUDEDIR}/rtems',
>> > tg_idx_count=59, meths=['process_install_task', 'process_rule',
>> > 'process_source'], _name='', source=[],
>> > install_to='${BSP_INCLUDEDIR}/rtems',
>> > path=/home/utkarsh/new_build/rtems,
>> > install_from=['cpukit/include/rtems/assoc.h'
>> > [...]
>> > "
>> > My config.ini file has all the contents of './waf bsp_defaults
>> > --rtems-bsps=arm/realview_pbx_a9'. Can you please point out my mistake?
>> I stopped to maintain the build branch.
>>
>> Could you please use this branch:
>>
>> https://git.rtems.org/sebh/rtems.git/log/?h=build-2
>>
>> Using the new build system in the current state is not really advisable.
>> I will do forced pushes to the build-2 branch.
>>
> _______________________________________________
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
