Can't compile under Arch Linux i686

Question

Can't compile under Arch Linux i686

roobie opened this issue 13 years ago · comments

Hello!

I've tried to compile this on my Arch Linux computer, but it won't.

The following commands are used.

$ PYTHON=python2 PYTHON_VERSION=2.7 ./autogen.sh
$ PYTHON=python2 PYTHON_VERSION=2.7 ./configure PYTHON_LDFLAGS="-L/usr/lib/python2.7" --prefix=/usr

which leads to the following output:

checking for a BSD-compatible install... /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 build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking how to print strings... printf
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 for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert i686-pc-linux-gnu file names to i686-pc-linux-gnu format... func_convert_file_noop
checking how to convert i686-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... no
checking if : is a manifest tool... no
checking how to run the C preprocessor... gcc -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 for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
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 dependency style of gcc... (cached) gcc3
checking for a sed that does not truncate output... (cached) /bin/sed
checking for python... /usr/bin/python
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
checking for string.h... (cached) yes
checking assert.h usability... yes
checking assert.h presence... yes
checking for assert.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking for dlfcn.h... (cached) yes
checking regex.h usability... yes
checking regex.h presence... yes
checking for regex.h... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for gtk... yes
checking for geany... yes
checking for python2.7... (cached) /usr/bin/python
checking for a version of Python >= '2.1.0'... yes
checking for a version of Python >= '2.6'... yes
checking for the distutils Python package... yes
checking for Python include path... -I/usr/include/python3.2mu
checking for Python library path... -L/usr/lib/python2.7
checking for Python site-packages path... /usr/lib/python3.2/site-packages
checking python extra libraries...  -lpthread -ldl  -lutil
checking python extra linking flags... -Xlinker -export-dynamic
checking consistency of all components of python development environment... no
configure: error: in `/home/roobie/share/Dropbox/devel/geany-zencoding':
configure: error: 
  Could not link test program to Python. Maybe the main Python library has been
  installed in some non-standard library path. If so, pass it to configure,
  via the LDFLAGS environment variable.
  Example: ./configure LDFLAGS="-L/usr/non-standard-path/python/lib"
  ============================================================================
   ERROR!
   You probably have to install the development version of the Python package
   for your distribution.  The exact name of this package varies among them.
  ============================================================================

See `config.log' for more details

RAJ commented 12 years ago

k

Matthew Brush · Answer 1 · Thu Nov 03 2011 08:36:03 GMT+0800 (China Standard Time)

Do you have Python 2 development stuff? On Debian/Ubuntu the package is called python-dev. You could also just compile Python from source and get it.

Also these lines are concerning:
checking for Python include path... -I/usr/include/python3.2mu
checking for Python site-packages path... /usr/lib/python3.2/site-packages

Maybe try setting the preprocessor flags variable too, something like:
PYTHON_CPPFLAGS="-I/usr/include/python2.7"

Unfortunately I can't help much more with Arch since I stopped using it when they completely broken Python 2 support :)

Björn Roberg · Answer 2 · Fri Nov 04 2011 02:13:22 GMT+0800 (China Standard Time)

Yup, got the headers in /usr/include. (Arch always supplies the '-dev' package together with the standard package).

I agree... I did play around with LDFLAGS, since it told me to do it... But I'll try the PYTHON_CPPFLAGS now.

And it's true, Python is somewhat b0rken on Arch :'( But that ain't gonna make me leave ;)

No problem.. I'll give you an update if it works.

Thx

Björn Roberg · Answer 3 · Fri Nov 04 2011 02:48:11 GMT+0800 (China Standard Time)

Allright... Tried this:

$ PYTHON=python2 PYTHON_VERSION=2.7 ./configure PYTHON_CPPFLAGS="-I/usr/include/python2.7" PYTHON_LDFLAGS="-L/usr/lib/python2.7" --prefix=/usr

Does not work, though.

However, I would like you to take a quick look at this:

        #
    # Check for site packages
    #
    { $as_echo "$as_me:${as_lineno-$LINENO}: checking for Python site-packages path" >&5
$as_echo_n "checking for Python site-packages path... " >&6; }
    if test -z "$PYTHON_SITE_PKG"; then
        PYTHON_SITE_PKG=`$PYTHON -c "import distutils.sysconfig; \
            print (distutils.sysconfig.get_python_lib(0,0));"`
    fi
    { $as_echo "$as_me:${as_lineno-$LINENO}: result: $PYTHON_SITE_PKG" >&5
$as_echo "$PYTHON_SITE_PKG" >&6; }

It's from the configure script.
When I execute the following command (extracted from the snippet above:

$ PYTHON="/usr/bin/python2"; $PYTHON -c "import distutils.sysconfig; \
            print (distutils.sysconfig.get_python_lib(0,0));"

I get:

/usr/lib/python2.7/site-packages

As expected, however, the configure script still outputs that:

checking for Python site-packages path... /usr/lib/python3.2/site-packages

Even though I've exported PYTHON='/usr/bin/python2'
Truly wierd... :/

Matthew Brush · Answer 4 · Fri Nov 04 2011 12:22:20 GMT+0800 (China Standard Time)

I'm not too sure, I'm no Autotools expert, I've used this m4 thing to detect all the Python stuff:
https://github.com/codebrainz/geany-zencoding/blob/master/m4/ax_python_devel.m4

That's likely got the answer and surely it's where the stuff in the configure script is coming from. You could possibly try temporarily removing and creating a new /usr/bin/python link that points to 2.x python and then change it back to point to 3.x python right after compiling/installing the plugin. It might work around the issue.

Sagar Chalise · Answer 5 · Tue Nov 15 2011 00:02:31 GMT+0800 (China Standard Time)

I finally got this working under arch after patching configure.ac. I built an aur package for this https://aur.archlinux.org/packages.php?ID=53989

Matthew Brush · Answer 6 · Tue Nov 15 2011 01:32:04 GMT+0800 (China Standard Time)

Cool, glad it didn't need any majour changes.

FWIW, I don't think it depends on geany-plugins, just geany and python2 probably would do it.