> On 24 Oct 2018, at 6:29 pm, Malte Münch <m...@stablerock.de> wrote: > > 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:
Great, I will push it. Thank you for testing and reporting back. > [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 At the end of the log is the shell command used to find the header. Could you please run that command in a shell and if you add ‘-d’ the shell will trace itself. Also do you know where ArchLinux puts the python header? >> Is this link from a package or something you have done? > > I asked me that as well, i knew this question would come :D It is any interesting issue that now exists. > 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. This makes sense to me but not all distributions see this the same way. Chris _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
