m2005 untar error on msys2 (tar01 directory)

[Chris Johns]

On 5/5/20 3:44 pm, Sebastian Huber wrote:
> On 05/05/2020 07:41, Chris Johns wrote:
> 
>> On 5/5/20 3:34 pm, Sebastian Huber wrote:
>>> On 05/05/2020 07:22, Chris Johns wrote:
>>>
>>>> On 5/5/20 3:20 pm, Sebastian Huber wrote:
>>>>> In a msys2 shell I get:
>>>>>
>>>>> $ ../source-builder/sb-set-builder --prefix=/opt/rtems/5 5/rtems-sparc
>>>>> error: no hosts defaults found; please add
>>>>
>>>> What does `python source-builder/sb/windows.py` show?
>>> $ python source-builder/sb/windows.py
>>> Traceback (most recent call last):
>>>    File "source-builder/sb/windows.py", line 192, in <module>
>>>      pprint.pprint(load())
>>>    File "source-builder/sb/windows.py", line 64, in load
>>>      raise error.general('invalid POSIX python for Windows')
>>> error.general: error: invalid POSIX python for Windows
>>
>> What does `os.uname()` return?
> 
> In the msys shell:
> 
> $ python
> Python 3.7.4 (default, Jul 11 2019, 09:35:14)

That is what I have installed.

> [GCC 9.1.0] on msys
> Type "help", "copyright", "credits" or "license" for more information.
>  >>> import os
>  >>> os.uname()
> posix.uname_result(sysname='MSYS_NT-6.1-7601', nodename='Blub', 
> release='3.0.7-338.x86_64', version='2019-07-11 10:58 UTC', 
> machine='x86_64')

I have ...

 >>> os.uname()
posix.uname_result(sysname='MINGW64_NT-10.0-18362', nodename='weng', 
release='3.0.7-338.x86_64', version='2019-07-11 10:58 UTC', 
machine='x86_64')

I have never seen `MSYS_NT` before.

I am running Window-10 on real hardware running Version 1903, OS build 
18362.778. I have not picked up the feature update yet. I am remote to 
the machine and do not want to try.

> In the mingw64 shell:
> 
> $ python
> Python 3.8.2 (default, Feb 27 2020, 05:27:33)  [GCC 9.2.0 64 bit 
> (AMD64)] on win32

This is wrong python, the os.name() check is only done on POSIX builds 
of python.

> Type "help", "copyright", "credits" or "license" for more information.
>  >>> import os
>  >>> os.uname()
> Traceback (most recent call last):
>    File "<stdin>", line 1, in <module>
> AttributeError: module 'os' has no attribute 'uname'
> 

Correct, it is not a posix build.

Using the m2005-1 snapshot I ran `windows.py` from same `msys` python 
without error ...

$ python source-builder/sb/windows.py
{'___setup_shell': ('exe', 'required', '%{__sh}'),
  '__bash': ('exe', 'required', 'bash'),
  '__bison': ('exe', 'required', 'bison'),
  '__bzip2': ('exe', 'required', 'bzip2'),
  '__cat': ('exe', 'required', 'cat'),
  '__cc': ('exe', 'required', 'x86_64-w64-mingw32-gcc'),
  '__chgrp': ('exe', 'required', 'chgrp'),
  '__chmod': ('exe', 'required', 'chmod'),
[snip]
  '_usr': ('dir', 'optional', '/opt/local'),
  '_var': ('dir', 'optional', '/opt/local/var'),
  '_windows_os': ('none', 'none', 'mingw32'),
  'gdb_python2': '/c/msys64/mingw64/bin/python2.exe',
  'gdb_python3': '/c/msys64/mingw64/bin/python3.exe'}

Chris