From: bilal.tas@dcl.com.tr
To: ptxdist@pengutronix.de
Subject: [ptxdist] ptxdist-2012.03.0 some python development files could not be found
Date: Tue, 22 Apr 2014 11:48:27 +0300 [thread overview]
Message-ID: <9680960ed12803245dfdcd4197375e74@dcl.com.tr> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 4290 bytes --]
Hello,
I'm trying install ptxdist-2012.03.0 I get this error:
configure: error: some python development files could not be found,
you are likely using suse or redhat system as host. In this case please
install he python-devel packages
But I have installed pyhton 2.7
My
BSP is support only ptxdist-2012.03.0 (Phytec PD13.2.3)
My OS ubuntu
13.04 x86
-----My Log------
checking build system type...
i686-pc-linux-gnu
checking host system type...
i686-pc-linux-gnu
checking for ptxdist patches... yes
checking for
gcc... gcc
checking whether the C compiler works... yes
checking for C
compiler default output file name... a.out
checking for suffix of
executables...
checking whether we are cross compiling... no
checking
for suffix of object files... o
checking whether we are using the GNU C
compiler... yes
checking whether gcc accepts -g... yes
checking for gcc
option to accept ISO C89... none needed
checking how to run the C
preprocessor... gcc -E
checking for grep that handles long lines and
-e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C
header files... yes
checking for sys/types.h... yes
checking for
sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h...
yes
checking for memory.h... yes
checking for strings.h... yes
checking
for inttypes.h... yes
checking for stdint.h... yes
checking for
unistd.h... yes
checking regex.h usability... yes
checking regex.h
presence... yes
checking for regex.h... yes
checking for library
containing regcomp... none required
checking for library containing
mvaddch... -lncurses
checking ncurses.h usability... yes
checking
ncurses.h presence... yes
checking for ncurses.h... yes
checking menu.h
usability... yes
checking menu.h presence... yes
checking for menu.h...
yes
checking whether #! works in shell scripts... yes
checking for
bash... /bin/bash
checking for sed... /bin/sed
checking sed version...
4.2.2
checking for GNU chmod... /bin/chmod
checking for GNU chown...
/bin/chown
checking for GNU mv... /bin/mv
checking for GNU cp...
/bin/cp
checking for GNU rm... /bin/rm
checking for GNU rmdir...
/bin/rmdir
checking for GNU md5sum... /usr/bin/md5sum
checking for GNU
mkdir... /bin/mkdir
checking for GNU install...
/usr/bin/install
checking for GNU stat... /usr/bin/stat
checking for GNU
mknod... /bin/mknod
checking for GNU tar... /bin/tar
checking for
egrep... (cached) /bin/grep -E
checking for a BSD-compatible install...
/usr/bin/install -c
checking for gcc... (cached) gcc
checking whether we
are using the GNU C compiler... (cached) yes
checking whether gcc
accepts -g... (cached) yes
checking for gcc option to accept ISO C89...
(cached) none needed
checking for g++... g++
checking whether we are
using the GNU C++ compiler... yes
checking whether g++ accepts -g...
yes
checking for gawk... gawk
checking for gawk...
/usr/bin/gawk
checking awk version... 4.0.1
checking for flex...
flex
checking lex output file root... lex.yy
checking lex library...
-lfl
checking whether yytext is a pointer... yes
checking for flex...
/usr/bin/flex
checking for bison... bison -y
checking for bison...
/usr/bin/bison
checking whether yacc is bison++... no, this is
good
checking yacc/bison version... 2.7.12
checking for makeinfo...
/usr/bin/makeinfo
checking for bunzip2... /bin/bunzip2
checking for
gunzip... /bin/gunzip
checking for gunzip... /bin/gunzip
checking for
readlink... /bin/readlink
checking for mktemp... /bin/mktemp
checking
for wget... /usr/bin/wget
checking for dirname...
/usr/bin/dirname
checking for cat... /bin/cat
checking for find...
/usr/bin/find
checking find version... 4.4.2
checking for xargs...
/usr/bin/xargs
checking if xargs -r works as expected... ok
checking for
sort... /usr/bin/sort
checking for gmake... no
checking for gnumake...
no
checking for make... /usr/bin/make
checking for file...
/usr/bin/file
checking for msgfmt... /usr/bin/msgfmt
checking for tty...
/usr/bin/tty
checking for gcc... /usr/bin/gcc
CHECKING FOR PYTHON2.7...
/USR/BIN/PYTHON2.7
CHECKING WHETHER /USR/BIN/PYTHON2.7 FINDS
DISTUTILS... YES
checking whether python development files are
present... no
configure: error: some python development files could not
be found, you are
likely using suse or redhat system as host. In this
case
please install the python-devel packages
[-- Attachment #1.2: Type: text/html, Size: 5165 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2014-04-22 8:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 8:48 bilal.tas [this message]
2014-04-22 9:09 ` Alexander Aring
2014-04-22 9:19 ` [ptxdist] ptxdist-2012.03.0 some python development filescouldnot " bilal.tas
2014-04-22 9:25 ` Alexander Aring
2014-04-22 9:28 ` Alexander Aring
2014-04-22 9:35 ` [ptxdist] ptxdist-2012.03.0 some pythondevelopmentfilescouldnot " bilal.tas
2014-04-22 9:41 ` Alexander Aring
2014-04-22 9:50 ` [ptxdist] ptxdist-2012.03.0 somepythondevelopmentfilescouldnotbe found bilal.tas
2014-04-22 9:57 ` Alexander Aring
2014-04-22 10:02 ` [ptxdist] ptxdist-2012.03.0somepythondevelopmentfilescouldnotbefound bilal.tas
2014-04-22 11:18 ` Alexander Aring
2014-04-22 11:25 ` bilal.tas
2014-04-22 11:27 ` Alexander Aring
2014-04-22 11:33 ` bilal.tas
2014-04-22 11:50 ` Alexander Aring
2014-04-22 9:35 ` [ptxdist] ptxdist-2012.03.0 some python development filescouldnot be found Marc Kleine-Budde
2014-04-22 9:37 ` Alexander Aring
2014-04-22 9:37 ` [ptxdist] ptxdist-2012.03.0 some pythondevelopmentfilescouldnot " bilal.tas
2014-04-22 12:24 ` [ptxdist] ptxdist-2012.03.0 some python development files could not " Alexander Aring
2014-04-23 6:34 ` [ptxdist] ptxdist-2012.03.0 some python development files couldnot " Bilal TAŞ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9680960ed12803245dfdcd4197375e74@dcl.com.tr \
--to=bilal.tas@dcl.com.tr \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox