I am using Ubuntu 14.04. After removing package "libpython2.7-dev:amd64" and "python2.7-dev", I got following error message in "rsb-report-sparc-rtems4.12-gdb-7.9-x86_64-linux-gnu-1.txt":
checking for python... /usr/bin/python checking for python2.7... no configure: error: python is missing or unusable make[1]: *** [configure-gdb] Error 1 make[1]: Leaving directory `/data/jason/rtems/rtems-source-builder/rtems/build/sparc-rtems4.12-gdb-7.9-x86_64-linux-gnu-1/build' make: *** [all] Error 2 shell cmd failed: /bin/sh -ex /data/jason/rtems/rtems-source-builder/rtems/build/sparc-rtems4.12-gdb-7.9-x86_64-linux-gnu-1/doit error: building sparc-rtems4.12-gdb-7.9-x86_64-linux-gnu-1 A more detailed config log can be found at "build/sparc-rtems4.12-gdb-7.9-x86_64-linux-gnu-1/build/gdb/config.log". I think it is what joel is asking for. Error message in "build/sparc-rtems4.12-gdb-7.9-x86_64-linux-gnu-1/build/gdb/config.log": configure:8265: result: /usr/bin/python configure:8403: checking for python2.7 configure:8421: /usr/bin/gcc -O2 -pipe -I/data/jason/rtems/rtems-source-builder/rtems/build/tmp/sb-jason/4.12/rtems-sparc/data/jason/rtems/4.12/include -o conftest -g -O2 -I/data/jason/rtems/rtems-source-builder/rtems/build/tmp/sb-jason/4.12/rtems-sparc/data/jason/rtems/4.12/include -I/usr/include/python2.7 -I/usr/include/python2.7 -static-libstdc++ -static-libgcc -L/data/jason/rtems/rtems-source-builder/rtems/build/tmp/sb-jason/4.12/rtems-sparc/data/jason/rtems/4.12/lib conftest.c -ldl -lncurses -lm -ldl -lpthread -ldl -lutil -lm -lpython2.7 -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions >&5 conftest.c:51:20: fatal error: Python.h: No such file or directory #include "Python.h" ^ compilation terminated. configure:8421: $? = 1 Regards, Jason Wong On 11 February 2016 at 19:44, punit vara <punitv...@gmail.com> wrote: > On Wed, Feb 10, 2016 at 11:45 PM, Joel Sherrill <j...@rtems.org> wrote: > > We need the config.log from the subdirectory where the failure occurred. > > This looks like one from the top directory, > > > > Look at the build log to see what directory the build failed in and grab > > that one. > > > > FWIW a quick google for this issue on Ubuntu showed someone suggested: > > > > sudo apt-get install python-dev > > > > Have you done that? > > > > --joel > > > > On Wed, Feb 10, 2016 at 11:50 AM, punit vara <punitv...@gmail.com> > wrote: > >> > >> On Tue, Feb 9, 2016 at 8:21 PM, Joel Sherrill <j...@rtems.org> wrote: > >> > > >> > > >> > On Tue, Feb 9, 2016 at 8:15 AM, punit vara <punitv...@gmail.com> > wrote: > >> >> > >> >> On Tue, Feb 9, 2016 at 6:56 PM, Aun-Ali Zaidi <ad...@kodeit.net> > wrote: > >> >> > Hi, > >> >> > > >> >> > I was having the same problem yesterday and managed to find a fix > by > >> >> > installing libpython2.7-dev: > >> >> > > >> >> > sudo apt-get install libpython2.7-dev > >> >> > > >> >> > Aun-Ali Zaidi > >> >> > > >> >> > >> >> Thanks Aun-Ali. I have tried but again I am getting same error. > >> >> Because this package would get installed when you install > >> >> python2.7-dev > >> > > >> > > >> > Can you look in the config.log for gdb where the failure occurred? Or > >> > even > >> > at the configure.in/ac script in its source. It is looking for a very > >> > specific > >> > file to link against and failing. > >> > > >> > yum have a "provides" subcommand to search for which package provides > >> > a specific file. Apt must have a similar capability. > >> > > >> > So you can figure out the file gdb needs to link and the corresponding > >> > package which includes it. > >> > > >> > --joel > >> > > >> >> > >> >> _______________________________________________ > >> >> devel mailing list > >> >> devel@rtems.org > >> >> http://lists.rtems.org/mailman/listinfo/devel > >> > > >> > > >> > >> Yes I agree with you Joel. From line 129 I found errors if you can > >> help me out. Perhaps somebody can help me I am attaching config.log > >> file from > >> > >> > >> > /home/punit/development/rtems/src/rtems-source-builder/rtems/build/arm-rtems4.12-gdb-7.9-x86_64-linux-gnu-1/build > > > > > Yes I tried that before but same error. I am attaching log file I > have sent config.log from failure subdirectory. I have provided > location in previous mail which is the same as shown in this log file. > If I am wrong let me. > > Thanks for support. > > _______________________________________________ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel > -- Regards, Jason Wong
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel