Configure Error No Suitable Python Interpreter Found
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us syslog ng no suitable python interpreter found Learn more about Stack Overflow the company Business Learn more about hiring developers
Configure Error No Suitable Apr Found
or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up installing gedit in linux with python 2.7.3 up vote 0 down vote favorite I have tried to install 2 versions of gedit in linux with python version of 2.7.3 gedit 3.8.1 and gedit 3.7.6 both come with error when i use ./configure "configure: error: no suitable Python interpreter found" can I know which version of gedit to install to suit with my python version? python linux gedit share|improve this question asked Aug 21 '13 at 8:55 Ely 198 configure also tells you which Python version it was looking for. –interjay Aug 21 '13 at 8:59 im new to Linux (installed it few hours ago), sorry if my question is not that clear. when i Type python -V it shows that it is installed with python 2.7.3, when I tried to install gedit 3.8.1 and gedit 3.7.6 it comes up with a configuration error, should I install something first? –Ely Aug 21 '13 at 9:00 what version of linux are you using? You might just be able to use a package manager thingy or apt-get. I don't think this is the right place for this question by the way... –Sheena Aug 21 '13 at 9:01 it says that i need python interpreter with version >= 3.2.3, what version of gedit should I need for python version 2.7.3? Im using Ubuntu 12.04 LTS –Ely Aug 21 '13 at 9:01 so you need to install that then. There are some pretty big differences between python 2 and 3 –Sheena Aug 21 '13 at 9:02 | show 2 more comments 1 Answer 1 active oldest votes up vote
Support Search GitHub This repository Watch 113 Star 1,153 Fork 237 fontforge/fontforge Code Issues 757 Pull requests 10 Projects 1 Wiki Pulse Graphs New issue fontforge compilation error in centos 6.4 machine. #1288 Closed sathishks opened this Issue Mar 12, 2014 · 4 comments Projects None yet Labels None yet Milestone No milestone Assignees No one assigned 4 participants sathishks commented Mar 12, 2014 I am trying to install latest fontforge version 2.0. I downloaded from the following link given by https://github.com/fontforge/fontforge/releases. i am getting http://stackoverflow.com/questions/18352991/installing-gedit-in-linux-with-python-2-7-3 below said error, plz give me resolution or fix,refer the error for below file. checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking how to create a https://github.com/fontforge/fontforge/issues/1288 pax tar archive... gnutar checking whether to disable maintainer-specific portions of Makefiles... yes checking for style of include used by make... GNU 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 dependency style of gcc... gcc3 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 minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define EXTENSIONS... yes checking for
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Trying to portupgrade /usr/ports/textproc/gnome-doc-utils I generally run portupgrade -a on https://lists.freebsd.org/pipermail/freebsd-gnome/2006-October/015628.html Friday before I leave work so it's done when I come in https://bugzilla.redhat.com/show_bug.cgi?id=815033 Monday. This Monday it failed, and I've been trying since then to get things back on track. I've cvsupped several time since Friday, and I always do ports-all Seems like it's related to other Python problems. I've added PYTHON_VERSION=python2.4 to /etc/make.conf and cleaned up some no suitable stuff so these are the only python ports I have installed: # pkg_info | grep python python-2.4.3,1 The "meta-port" for the stable version of Python interprete python24-2.4.3_3 An interpreted object-oriented programming language Appropriate logs included. Let me know if there's any more information I can provide. # sh gnomelogalyzer.sh Generating build log. Please wait... done. The cause of configure error no your build failure is not known to gnomelogalyzer.sh. Before e-mailing the build log to the FreeBSD GNOME team at freebsd-gnome at FreeBSD.org, TRY EACH OF THE FOLLOWING: * If you are generating your own logfile, make sure to generate it with something similar to: "make 2>&1 | tee /path/to/logfile" (sh/bash/ksh/zsh) or "make |& tee /path/to/logfile" (csh/tcsh) * Make sure your cvsup(1) configuration file specifies the 'ports-all' collection * Run cvsup(1) and attempt the build again * Check /usr/ports/UPDATING for information pertinent to your build failure * 99% of the commonly reported build failures can be solved by running "portupgrade -a" * Read the FAQs at http://www.FreeBSD.org/gnome/ * Search the archives of freebsd-gnome at FreeBSD.org. Archives can be searched at http://www.freebsd.org/gnome/index.html#search If you have not performed each of the above suggestions, don't bother asking for help. The chances are good that you'll simply be told to perform one of the aforementioned steps. # pkg_info ORBit2-2.14.3 High-performance CORBA ORB with support for the C language a2ps-a4-4.13b_3 Formats an ascii file for p
For Printing -XML -Clone This Bug -Last Comment First Last Prev Next This bug is not in your last search results. Bug815033 - rpmbuild : no suitable Python interpreter found Summary: rpmbuild : no suitable Python interpreter found Status: CLOSED ERRATA Aliases: None Product: Red Hat Gluster Storage Classification: Red Hat Component: build (Show other bugs) Sub Component: --- Version: 1.0 Hardware: x86_64 Linux Priority medium Severity medium TargetMilestone: --- TargetRelease: --- Assigned To: Amar Tumballi QA Contact: Docs Contact: URL: Whiteboard: Keywords: Depends On: GLUSTER-2925 Blocks: 811632 Show dependency tree /graph Reported: 2012-04-22 03:19 EDT by Scott Haines Modified: 2015-01-22 10:29 EST (History) CC List: 6 users (show) fharshav gluster-bugs i.r.1783 lakshmipathi vijay vraman See Also: Fixed In Version: Doc Type: Bug Fix Doc Text: Story Points: --- Clone Of: GLUSTER-2925 Environment: Last Closed: 2012-05-01 07:17:49 EDT Type: --- Regression: --- Mount Type: --- Documentation: --- CRM: Verified Versions: Category: --- oVirt Team: --- RHEL 7.3 requirements from Atomic Host: Cloudforms Team: --- Attachments (Terms of Use) Add an attachment (proposed patch, testcase, etc.) Groups: None (edit) Description Scott Haines 2012-04-22 03:19:34 EDT +++ This bug was initially created as a clone of Bug #764657 +++ The problem now is : Obsoletes: glusterfs-client < 3.1.0 Checking for unpackaged file(s): /usr/lib/rpm/check-files /var/tmp/glusterfs-3.2.0-1-root Checking for unpackaged file(s): /usr/lib/rpm/check-files /var/tmp/glusterfs-3.2.0-1-root RPM build errors: cannot open Pubkeys index using db3 - No such file or directory (2) File not found: /var/tmp/glusterfs-3.2.0-1-root/etc/init.d/glusterd --- Additional comment from i.r.1783@gmx.net on 2011-05-22 13:00:13 EDT --- Created attachment 496 --- Additional comment from i.r.1783@gmx.net on 2011-05-22 15:51:02 EDT --- My buildmachine is a opensuse 11.4 64bit box. I build for SLES11SP1. I have following error when I call build --clean --rpms /mnt/iso1:/mnt/iso2:/mnt/iso3 --dist sles11 --arch x86_64 --root /tmp/gluster320 glusterfs.spec checking for a Python interpreter with version >= 2.4... none configure: error: no suitable Python interpreter found error: Bad exit status from /var/tmp/rpm-tmp.44682 (%build) RPM build errors: cannot open Pubkeys index using db3 - No such file or directory (2) Bad exit status from /var/tmp/rpm-tmp.44682 (%build) I added within glusterfs.spec a new subjection: BuildRequires: python-devel After that the buildenvironment is correct and it starts compiling. --- Additional comment from lakshmipathi@gluster.com on 2011-07-26