Hi Chris,
thanks for your answer. I said yesterday: "it worked fine before commit
13f4c379997b53b204d8534d198da2fa35dd5630" that was actually not true.
The first part worked fine but lateron the GDB build failed. I solved
that issue by reverting even further back.
Your patch works well for the first part:
[mamu@verstappen rtems]$ ../source-builder/sb-set-builder
--prefix=/home/mamu/vcs/git/development/rtems/5 --dry-run --trace
5/rtems-sparc
RTEMS Source Builder - Set Builder, 5 (1e9075af6803 modified)
Build Set: 5/rtems-sparc
Build Set: 5/rtems-autotools.bset
Build Set: 5/rtems-autotools-internal.bset
config: tools/rtems-autoconf-2.69-1.cfg
package: autoconf-2.69-x86_64-linux-gnu-1
See error report: rsb-report-autoconf-2.69-x86_64-linux-gnu-1.txt
config: tools/rtems-automake-1.12.6-1.cfg
package: automake-1.12.6-x86_64-linux-gnu-1
See error report: rsb-report-automake-1.12.6-x86_64-linux-gnu-1.txt
cleaning: autoconf-2.69-x86_64-linux-gnu-1
cleaning: automake-1.12.6-x86_64-linux-gnu-1
Build Sizes: usage: 0.000B total: 135.959MB (sources: 135.710MB,
patches: 254.826KB, installed 0.000B)
Build Set: Time 0:00:02.362507
Build Set: 5/rtems-autotools-base.bset
config: tools/rtems-autoconf-2.69-1.cfg
package: autoconf-2.69-x86_64-linux-gnu-1
See error report: rsb-report-autoconf-2.69-x86_64-linux-gnu-1.txt
reporting: tools/rtems-autoconf-2.69-1.cfg ->
autoconf-2.69-x86_64-linux-gnu-1.txt
reporting: tools/rtems-autoconf-2.69-1.cfg ->
autoconf-2.69-x86_64-linux-gnu-1.xml
config: tools/rtems-automake-1.12.6-1.cfg
package: automake-1.12.6-x86_64-linux-gnu-1
See error report: rsb-report-automake-1.12.6-x86_64-linux-gnu-1.txt
reporting: tools/rtems-automake-1.12.6-1.cfg ->
automake-1.12.6-x86_64-linux-gnu-1.txt
reporting: tools/rtems-automake-1.12.6-1.cfg ->
automake-1.12.6-x86_64-linux-gnu-1.xml
installing: autoconf-2.69-x86_64-linux-gnu-1 ->
/home/mamu/vcs/git/development/rtems/5
installing: automake-1.12.6-x86_64-linux-gnu-1 ->
/home/mamu/vcs/git/development/rtems/5
cleaning: autoconf-2.69-x86_64-linux-gnu-1
cleaning: automake-1.12.6-x86_64-linux-gnu-1
Build Sizes: usage: 0.000B total: 135.959MB (sources: 135.710MB,
patches: 254.826KB, installed 0.000B)
Build Set: Time 0:00:06.290691
Build Set: Time 0:00:08.658924
config: devel/expat-2.1.0-1.cfg
package: expat-2.1.0-x86_64-linux-gnu-1
See error report: rsb-report-expat-2.1.0-x86_64-linux-gnu-1.txt
reporting: devel/expat-2.1.0-1.cfg -> expat-2.1.0-x86_64-linux-gnu-1.txt
reporting: devel/expat-2.1.0-1.cfg -> expat-2.1.0-x86_64-linux-gnu-1.xml
config: tools/rtems-gdb-8.0.1-1.cfg
error: config error: gdb-common-1.cfg:87: "gdb: python: header file not
found: python2.7/Python.h, please install"
Build FAILED
Build Set: Time 0:00:09.203917
Build FAILED
> Is this link from a package or something you have done?
I asked me that as well, i knew this question would come :D I don't know
but i think this is standard. The Archlinux-Wiki says:
Any program requiring Python 2 needs to point to /usr/bin/python2,
instead of /usr/bin/python, which points to Python 3.
Best,
Malte
On 10/24/18 2:12 AM, Chris Johns wrote:
> On 23/10/2018 23:47, Malte Münch wrote:
>> Hi,
>>
>> i have difficulties running the source builder on Archlinux. It worked
>> fine before commit 13f4c379997b53b204d8534d198da2fa35dd5630 (sb: Add
>> support to search for a suitable version of python.) Know it stops with
>> the following error:
>
> Many thanks for testing and reporting the issue.
>
>>
>> [mamu@verstappen rtems]$ ../source-builder/sb-set-builder
>> --prefix="$HOME/vcs/git/development/rtems/5" 5/rtems-sparc
>> RTEMS Source Builder - Set Builder, 5 (818f3960325a modified)
>> Traceback (most recent call last):
>> File "../source-builder/sb/cmd-set-builder.py", line 26, in <module>
>> setbuilder.run()
>> File
>> "/home/mamu/vcs/git/development/rtems/rsb/source-builder/sb/setbuilder.py",
>> line 618, in run
>> b = buildset(bset, configs, opts)
>> File
>> "/home/mamu/vcs/git/development/rtems/rsb/source-builder/sb/setbuilder.py",
>> line 82, in __init__
>> log.trace(str(self.macros))
>> File
>> "/home/mamu/vcs/git/development/rtems/rsb/source-builder/sb/macros.py",
>> line 129, in __str__
>> text += l[0:text_len]
>> UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 7:
>> ordinal not in range(128)
>
> Interesting. I have been changing the macros.py support in the RSB to support
> Unicode because long paths in Windows need to be Unicode. I have been
> attempting
> to catch all I could.
>
> Could you please try this patch for me?
>
> diff --git a/source-builder/sb/macros.py b/source-builder/sb/macros.py
> index 2abe386..9ba6cac 100644
> --- a/source-builder/sb/macros.py
> +++ b/source-builder/sb/macros.py
> @@ -123,6 +123,7 @@ class macros:
> lc = 0
> for l in ds:
> lc += 1
> + l = self._unicode_to_str(l)
> while len(l):
> if indent:
> text += ' %21s %10s %12s' % (' ', ' ', ' ')
>
> To test please add '--dry-run --trace' to the sb-set-builder command. If it
> does
> try a build.
>
>>
>>
>> If i revert back to 8992d20b8c28af7c95c8b95da054aa9d94521426 it works
>> fine. I wish i could provide a path so it works for arch but i did not
>> understand the way the wrapper script works.
>>
>> I am running Archlinux with the following locations (links):
>>
>> [mamu@verstappen rtems]$ which python
>> /usr/bin/python
>> [mamu@verstappen rtems]$ which python2
>> /usr/bin/python2
>> [mamu@verstappen rtems]$ which python3
>> /usr/bin/python3
>> [mamu@verstappen rtems]$ ls -lah /usr/bin/python
>> lrwxrwxrwx 1 root root 7 15. Sep 21:13 /usr/bin/python -> python3
>
> Is this link from a package or something you have done?
>
> I have changed the RSB to select python2 first, then python3 and then python.
>
> Thanks
> Chris
>
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
