[SOLVED] pygobject3 slackbuild fails on -current

brobr · 03-17-2015, 12:22 PM

This might seem a revival of pygobject3-slackbuild-fails-4175504336/,
but in -current I get this error when building pygobject-3.10.2 with python3.4 installed (incl pycairo3 and gnome-common) alongside multilib and python2.7

Code:

pygobject-3.10.2/gi/pygi-invoke.h
patching file Makefile.am
patching file gi/Makefile.am
lcov not installed, not enabling code coverage
/usr/bin/gnome-autogen.sh
checking for autoconf >= 2.53...
  testing autoconf2.50... not found.
  testing autoconf... found 2.69
checking for automake >= 1.9...
  testing automake-1.11... not found.
  testing automake-1.10... not found.
  testing automake-1.9... not found.
***Error***: You must have automake >= 1.9 installed
  to build pygobject.  Download the appropriate package for
  from your distribution or get the source tarball at
    http://ftp.gnu.org/pub/gnu/automake/automake-1.9.tar.gz

The automake version looks ok:

Code:

bash-4.3$ automake --version
automake (GNU automake) 1.14.1

Any ideas?

ReaperX7 · 03-17-2015, 12:37 PM

Can you report this here?

http://www.linuxquestions.org/questi...ad-4175532869/

Currently we are getting packages ready for 14.2 using -Current, plus please contact the package maintainer about this.

willysr · 03-17-2015, 02:20 PM

try to remove the patch part. I have it working here wit Python3 and all the new deps mentioned in the README

brobr · 03-17-2015, 02:49 PM

Quote:

Originally Posted by willysr

try to remove the patch part.

Thanks for the suggestion, but commenting that line out in the Slackbuild to

Code:

if $(python3 -c 'import sys' 2>/dev/null); then
#  patch -p1 < $CWD/python3.4.patch
  PYTHON=python3
  ./autogen.sh
fi

did not make a difference...

EDIT:

when including the patch but replacing ./autogen.sh with /usr/bin/autoconf (as suggested on pygobject3-slackbuild-fails-4175504336#post5167070

I get

Code:

checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating pygobject-3.0.pc
config.status: creating pygobject-3.0-uninstalled.pc
config.status: creating gi/Makefile
config.status: creating gi/repository/Makefile
config.status: creating gi/overrides/Makefile
config.status: creating gi/_glib/Makefile
config.status: creating gi/_gobject/Makefile
config.status: creating examples/Makefile
config.status: creating tests/Makefile
config.status: creating pygtkcompat/Makefile
config.status: creating PKG-INFO
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands

	pygobject 3.10.2

	Using python interpreter:	/usr/bin/python3
	libffi support:			yes
	cairo support:			yes
	thread support:			yes
	code coverage support:          no

 cd . && /bin/sh /home/sbo_64/tmp/sbopkg.cbmGMh/pygobject-3.10.2/missing automake-1.14 --foreign Makefile
configure.ac:47: error: version mismatch.  This is Automake 1.14.1,
configure.ac:47: but the definition used by this AM_INIT_AUTOMAKE
configure.ac:47: comes from Automake 1.14.  You should recreate
configure.ac:47: aclocal.m4 with aclocal and run automake again.
WARNING: 'automake-1.14' is probably too old.
         You should only need it if you modified 'Makefile.am' or
         'configure.ac' or m4 files included by 'configure.ac'.
         The 'automake' program is part of the GNU Automake package:
         <http://www.gnu.org/software/automake>
         It also requires GNU Autoconf, GNU m4 and Perl in order to run:
         <http://www.gnu.org/software/autoconf>
         <http://www.gnu.org/software/m4/>
         <http://www.perl.org/>
make: *** [Makefile.in] Error 63

willysr · 03-17-2015, 03:02 PM

In my case (my MSB project), i don't need python3, so i removed the if ... fi block and it does work well

brobr · 03-17-2015, 03:32 PM

Quote:

Originally Posted by willysr

i don't need python3, i removed the if ... fi block

Hi Willy, I assume you do not have python3 installed then, next to python2...
In my case I have that (for programming) and therefore end up with this

Code:

  File "/usr/lib64/python3.4/py_compile.py", line 6, in <module>
    import importlib._bootstrap
  File "/usr/lib64/python3.4/importlib/__init__.py", line 40, in <module>
    import types
  File "/home/sbo_64/tmp/sbopkg.cbmGMh/pygobject-3.10.2/gi/types.py", line 28, in <module>
    from . import _gobject
SystemError: Parent module '' not loaded, cannot perform relative import
make[3]: *** [install-pygiPYTHON] Error 1
make[3]: Leaving directory `/home/sbo_64/tmp/sbopkg.cbmGMh/pygobject-3.10.2/gi'
make[2]: *** [install-am] Error 2
make[2]: Leaving directory `/home/sbo_64/tmp/sbopkg.cbmGMh/pygobject-3.10.2/gi'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/home/sbo_64/tmp/sbopkg.cbmGMh/pygobject-3.10.2/gi'
make: *** [install-recursive] Error 1
Cleaning up...

willysr · 03-17-2015, 06:40 PM

No, i did install Python 3, but i don't need Python3 support, so i removed the support for python3, thus remove the if ... fi block which is to support python 3 instead of python 2

brobr · 03-17-2015, 07:04 PM

Hmmm, okay.... the problem seems that whatever I do (I removed gnome-common and py3cairo) python3 is used

Code:

checking for a Python interpreter with version >= 2.7... python3
checking for python3... /usr/bin/python3
checking for python3 version... 3.4
.....
.....
config.status: executing libtool commands

	pygobject 3.10.2

	Using python interpreter:	/usr/bin/python3
	libffi support:			yes
	cairo support:			yes
	thread support:			yes
	code coverage support:          no

but loading python itself shows that 2.7.5 is default

Code:

bash-4.3$ which python
/usr/bin/python
bash-4.3$ python
Python 2.7.5 (default, May 29 2013, 02:28:51) 
[GCC 4.8.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>>

willysr · 03-17-2015, 07:40 PM

i think you interpret my message differently

i do have python3 and gnome-common and py3cairo installed, but since i don't want to have python3 support inside pygobject3, i simply remove the code in the SlackBuild that add support for it. So in my case, it will be python2 only.

brobr · 03-18-2015, 06:33 AM

Hi Willy,

Thanks again for you suggestions. I have done what you advised (commented out the whole if-fi block) but that gave the error above, also when the libraries (gnome-common; py3cairo) required for python3-support have been removed; the error occurs earlier. How can I get the build-process point to Python 2 instead of 3? Or should I install pygobject3 from within Python 2 using easy-install?

willysr · 03-18-2015, 08:58 AM

Hm... i tested using sbopkg and here's what i do:
install gnome-common, py3cairo and python3
next i run sbopkg -b pygobject3 which tried to build it and here's what i got

Code:

pygobject-3.10.2/gi/pygi-invoke.h
patching file Makefile.am
patching file gi/Makefile.am
lcov not installed, not enabling code coverage
/usr/bin/gnome-autogen.sh
checking for automake >= 1.11.2...
testing automake... found 1.14.1
checking for autoreconf >= 2.53...
testing autoreconf... found 2.69
checking for pkg-config >= 0.14.0...
testing pkg-config... found 0.25
Checking for required M4 macros...
Checking for forbidden M4 macros...
Processing ./configure.ac
Running autoreconf...
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force --warnings=no-portability -I m4 ${ACLOCAL_FLAGS}
/usr/share/aclocal/imlib.m4:9: warning: underquoted definition of AM_PATH_IMLIB
/usr/share/aclocal/imlib.m4:9: run info Automake 'Extending aclocal'
/usr/share/aclocal/imlib.m4:9: or see http://www.gnu.org/software/automake/manual/automake.html#Extending-aclocal
autoreconf: configure.ac: tracing
autoreconf: running: libtoolize --copy --force
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
/usr/share/aclocal/imlib.m4:9: warning: underquoted definition of AM_PATH_IMLIB
/usr/share/aclocal/imlib.m4:9: run info Automake 'Extending aclocal'
/usr/share/aclocal/imlib.m4:9: or see http://www.gnu.org/software/automake/manual/automake.html#Extending-aclocal
autoreconf: running: /usr/bin/autoconf --force --warnings=no-portability
autoreconf: running: /usr/bin/autoheader --force --warnings=no-portability
autoreconf: running: automake --add-missing --copy --force-missing --warnings=no-portability
configure.ac:79: installing './compile'
configure.ac:47: installing './missing'
gi/Makefile.am: installing './depcomp'
tests/Makefile.am:5: warning: source file '$(GI_DATADIR)/tests/gimarshallingtests.c' is in a subdirectory,
tests/Makefile.am:5: but option 'subdir-objects' is disabled
automake: warning: possible forward-incompatibility.
automake: At least a source file is in a subdirectory, but the 'subdir-objects'
automake: automake option hasn't been enabled. For now, the corresponding output
automake: object file(s) will be placed in the top-level directory. However,
automake: this behaviour will change in future Automake versions: they will
automake: unconditionally cause object files to be placed in the same subdirectory
automake: of the corresponding sources.
automake: You are advised to start using 'subdir-objects' option throughout your
automake: project, to avoid future incompatibilities.
tests/Makefile.am:28: warning: source file '$(GI_DATADIR)/tests/regress.c' is in a subdirectory,
tests/Makefile.am:28: but option 'subdir-objects' is disabled
autoreconf: Leaving directory `.'
Running ./configure ...
configure: WARNING: you should use --build, --host, --target
checking whether make supports nested variables... yes
checking for a BSD-compatible install... /bin/ginstall -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 for some Win32 platform... no
checking for native Win32... no
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 whether gcc understands -c and -o together... yes
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/i486-slackware-linux/bin/ld
checking if the linker (/usr/i486-slackware-linux/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 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/i486-slackware-linux/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... dlltool
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 a working dd... /bin/dd
checking how to truncate binary pipes... /bin/dd bs=4096 count=1
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/i486-slackware-linux/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 for shl_load... no
checking for shl_load in -ldld... no
checking for dlopen... no
checking for dlopen in -ldl... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... no
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 library containing strerror... none required
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 whether gcc understands -c and -o together... (cached) yes
checking dependency style of gcc... (cached) gcc3
checking for a Python interpreter with version >= 2.7... python3
checking for python3... /usr/bin/python3
checking for python3 version... 3.4
checking for python3 platform... linux
checking for python3 script directory... ${prefix}/lib/python3.4/site-packages
checking for python3 extension module directory... ${exec_prefix}/lib/python3.4/site-packages
checking for /usr/bin/python3 >= 3.1... yes
checking for python version... (cached) 3.4
checking for python platform... (cached) linux
checking for python script directory... (cached) ${prefix}/lib/python3.4/site-packages
checking for python extension module directory... (cached) ${exec_prefix}/lib/python3.4/site-packages
checking for headers required to compile python extensions... found
checking for PySignal_SetWakeupFd in Python.h... yes
checking for python module thread... no
checking for python module _thread... yes
checking whether to enable threading in pygobject... yes
./configure: line 13697: ./libtool: No such file or directory
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.16... yes
checking for GLIB - version >= 2.35.9... yes (version 2.36.4)
checking for ffi... checking for FFI... yes
checking for GIO... yes
checking for GI... yes
checking for CAIRO... yes
checking for PYCAIRO... yes
checking whether gcc understands -Wall... yes
checking whether gcc understands -Wstrict-prototypes... yes
checking whether gcc understands -Wnested-externs... yes
checking whether gcc understands -Werror=missing-prototypes... yes
checking whether gcc understands -Werror=implicit-function-declaration... yes
checking whether gcc understands -Werror=pointer-arith... yes
checking whether gcc understands -Werror=init-self... yes
checking whether gcc understands -Werror=format-security... no
checking whether gcc understands -Werror=format=2... yes
checking whether gcc understands -Werror=missing-include-dirs... yes
checking what warning flags to pass to the C compiler... -Wall -Wstrict-prototypes -Wnested-externs -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self -Werror=format=2 -Werror=missing-include-dirs
checking what language compliance flags to pass to the C compiler...
checking for Gnome code coverage support... yes
checking whether to build with code coverage support... no
checking whether gcc understands -Wall... yes
checking whether gcc understands -Werror=unused-variable... yes
checking whether gcc understands -fno-strict-aliasing... yes
checking whether gcc understands -std=c9x... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating pygobject-3.0.pc
config.status: creating pygobject-3.0-uninstalled.pc
config.status: creating gi/Makefile
config.status: creating gi/repository/Makefile
config.status: creating gi/overrides/Makefile
config.status: creating gi/_glib/Makefile
config.status: creating gi/_gobject/Makefile
config.status: creating examples/Makefile
config.status: creating tests/Makefile
config.status: creating pygtkcompat/Makefile
config.status: creating PKG-INFO
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands

pygobject 3.10.2

Using python interpreter: /usr/bin/python3
libffi support: yes
cairo support: yes
thread support: yes
code coverage support: no

Now type `make' to compile pygobject
checking whether make supports nested variables... yes
checking for a BSD-compatible install... /bin/ginstall -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... i486-slackware-linux-gnu
checking host system type... i486-slackware-linux-gnu
checking for some Win32 platform... no
checking for native Win32... no
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 whether gcc understands -c and -o together... yes
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/i486-slackware-linux/bin/ld
checking if the linker (/usr/i486-slackware-linux/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 how to convert i486-slackware-linux-gnu file names to i486-slackware-linux-gnu format... func_convert_file_noop
checking how to convert i486-slackware-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/i486-slackware-linux/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... dlltool
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 a working dd... /bin/dd
checking how to truncate binary pipes... /bin/dd bs=4096 count=1
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/i486-slackware-linux/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 for shl_load... no
checking for shl_load in -ldld... no
checking for dlopen... no
checking for dlopen in -ldl... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... no
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 library containing strerror... none required
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 whether gcc understands -c and -o together... (cached) yes
checking dependency style of gcc... (cached) gcc3
checking for a Python interpreter with version >= 2.7... python3
checking for python3... /usr/bin/python3
checking for python3 version... 3.4
checking for python3 platform... linux
checking for python3 script directory... ${prefix}/lib/python3.4/site-packages
checking for python3 extension module directory... ${exec_prefix}/lib/python3.4/site-packages
checking for /usr/bin/python3 >= 3.1... yes
checking for python version... (cached) 3.4
checking for python platform... (cached) linux
checking for python script directory... (cached) ${prefix}/lib/python3.4/site-packages
checking for python extension module directory... (cached) ${exec_prefix}/lib/python3.4/site-packages
checking for headers required to compile python extensions... found
checking for PySignal_SetWakeupFd in Python.h... yes
checking for python module thread... no
checking for python module _thread... yes
checking whether to enable threading in pygobject... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.16... yes
checking for GLIB - version >= 2.35.9... yes (version 2.36.4)
checking for ffi... checking for FFI... yes
checking for GIO... yes
checking for GI... yes
checking for CAIRO... yes
checking for PYCAIRO... yes
checking whether gcc understands -Wall... yes
checking whether gcc understands -Wstrict-prototypes... yes
checking whether gcc understands -Wnested-externs... yes
checking whether gcc understands -Werror=missing-prototypes... yes
checking whether gcc understands -Werror=implicit-function-declaration... yes
checking whether gcc understands -Werror=pointer-arith... yes
checking whether gcc understands -Werror=init-self... yes
checking whether gcc understands -Werror=format-security... no
checking whether gcc understands -Werror=format=2... yes
checking whether gcc understands -Werror=missing-include-dirs... yes
checking what warning flags to pass to the C compiler... -Wall -Wstrict-prototypes -Wnested-externs -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self -Werror=format=2 -Werror=missing-include-dirs
checking what language compliance flags to pass to the C compiler...
checking for Gnome code coverage support... yes
checking whether to build with code coverage support... no
checking whether gcc understands -Wall... yes
checking whether gcc understands -Werror=unused-variable... yes
checking whether gcc understands -fno-strict-aliasing... yes
checking whether gcc understands -std=c9x... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating pygobject-3.0.pc
config.status: creating pygobject-3.0-uninstalled.pc
config.status: creating gi/Makefile
config.status: creating gi/repository/Makefile
config.status: creating gi/overrides/Makefile
config.status: creating gi/_glib/Makefile
config.status: creating gi/_gobject/Makefile
config.status: creating examples/Makefile
config.status: creating tests/Makefile
config.status: creating pygtkcompat/Makefile
config.status: creating PKG-INFO
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands

pygobject 3.10.2

Using python interpreter: /usr/bin/python3
libffi support: yes
cairo support: yes
thread support: yes
code coverage support: no

make all-recursive
make[1]: Entering directory `/tmp/sbopkg.RHvM8f/pygobject-3.10.2'
Making all in examples
make[2]: Entering directory `/tmp/sbopkg.RHvM8f/pygobject-3.10.2/examples'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/tmp/sbopkg.RHvM8f/pygobject-3.10.2/examples'
Making all in gi
make[2]: Entering directory `/tmp/sbopkg.RHvM8f/pygobject-3.10.2/gi'
Making all in repository
make[3]: Entering directory `/tmp/sbopkg.RHvM8f/pygobject-3.10.2/gi/repository'
for f in __init__.py; do \
[ -e ./$f ] || ln -s ./$f ./$f; \
done
make[3]: Leaving directory `/tmp/sbopkg.RHvM8f/pygobject-3.10.2/gi/repository'
Making all in overrides
make[3]: Entering directory `/tmp/sbopkg.RHvM8f/pygobject-3.10.2/gi/overrides'
for f in GLib.py Gtk.py Gdk.py GObject.py Gio.py GIMarshallingTests.py Pango.py keysyms.py __init__.py; do \
[ -e ./$f ] || ln -s ./$f ./$f; \
done
make[3]: Leaving directory `/tmp/sbopkg.RHvM8f/pygobject-3.10.2/gi/overrides'
Making all in _glib
make[3]: Entering directory `/tmp/sbopkg.RHvM8f/pygobject-3.10.2/gi/_glib'
CC libpyglib_gi_2_0_python3_la-pyglib.lo
CCLD libpyglib-gi-2.0-python3.la
CC _glib_la-glibmodule.lo
CC _glib_la-pygoptioncontext.lo
CC _glib_la-pygoptiongroup.lo
CC _glib_la-pygspawn.lo
CCLD _glib.la
ln -s -f .libs/_glib.cpython-34m.so _glib.cpython-34m.so
for f in __init__.py option.py; do \
[ -e ./$f ] || ln -s ./$f ./$f; \
done
make[3]: Leaving directory `/tmp/sbopkg.RHvM8f/pygobject-3.10.2/gi/_glib'
Making all in _gobject
make[3]: Entering directory `/tmp/sbopkg.RHvM8f/pygobject-3.10.2/gi/_gobject'
CC _gobject_la-gobjectmodule.lo
CC _gobject_la-pygboxed.lo
CC _gobject_la-pygenum.lo
CC _gobject_la-pygflags.lo
CC _gobject_la-pyginterface.lo
CC _gobject_la-pygobject.lo
pygobject.c: In function pygobject_data_free:
pygobject.c:117:26: warning: state may be used uninitialized in this function [-Wmaybe-uninitialized]
pyglib_gil_state_release(state);
^
CC _gobject_la-pygparamspec.lo
CC _gobject_la-pygpointer.lo
CC _gobject_la-pygtype.lo
pygtype.c: In function pyg_value_array_from_pyobject:
pygtype.c:682:5: warning: g_value_array_new is deprecated (declared at /usr/include/glib-2.0/gobject/gvaluearray.h:69): Use 'GArray' instead [-Wdeprecated-declarations]
value_array = g_value_array_new(len);
^
pygtype.c:692:13: warning: g_value_array_free is deprecated (declared at /usr/include/glib-2.0/gobject/gvaluearray.h:72): Use 'GArray' instead [-Wdeprecated-declarations]
g_value_array_free(value_array);
^
pygtype.c:704:17: warning: g_value_array_free is deprecated (declared at /usr/include/glib-2.0/gobject/gvaluearray.h:72): Use 'GArray' instead [-Wdeprecated-declarations]
g_value_array_free(value_array);
^
pygtype.c:717:13: warning: g_value_array_free is deprecated (declared at /usr/include/glib-2.0/gobject/gvaluearray.h:72): Use 'GArray' instead [-Wdeprecated-declarations]
g_value_array_free(value_array);
^
pygtype.c:722:9: warning: g_value_array_append is deprecated (declared at /usr/include/glib-2.0/gobject/gvaluearray.h:82): Use 'GArray' instead [-Wdeprecated-declarations]
g_value_array_append(value_array, &item_value);
^
pygtype.c: In function pyg_value_from_pyobject_with_error:
pygtype.c:1028:17: warning: g_value_array_get_type is deprecated (declared at /usr/include/glib-2.0/gobject/gvaluearray.h:62): Use 'GArray' instead [-Wdeprecated-declarations]
G_VALUE_HOLDS(value, G_TYPE_VALUE_ARRAY))
^
pygtype.c: In function pyg_value_as_pyobject:
pygtype.c:1246:9: warning: g_value_array_get_type is deprecated (declared at /usr/include/glib-2.0/gobject/gvaluearray.h:62): Use 'GArray' instead [-Wdeprecated-declarations]
} else if (G_VALUE_HOLDS(value, G_TYPE_VALUE_ARRAY)) {
^
CCLD _gobject.la
ln -s -f .libs/_gobject.cpython-34m.so _gobject.cpython-34m.so
for f in __init__.py constants.py propertyhelper.py signalhelper.py; do \
[ -e ./$f ] || ln -s ./$f ./$f; \
done
make[3]: Leaving directory `/tmp/sbopkg.RHvM8f/pygobject-3.10.2/gi/_gobject'
make[3]: Entering directory `/tmp/sbopkg.RHvM8f/pygobject-3.10.2/gi'
CC _gi_la-pygi-repository.lo
CC _gi_la-pygi-info.lo
CC _gi_la-pygi-foreign.lo
CC _gi_la-pygi-struct.lo
CC _gi_la-pygi-source.lo
CC _gi_la-pygi-argument.lo
CC _gi_la-pygi-type.lo
CC _gi_la-pygi-boxed.lo
CC _gi_la-pygi-closure.lo
CC _gi_la-pygi-ccallback.lo
CC _gi_la-pygi-property.lo
CC _gi_la-pygi-signal-closure.lo
CC _gi_la-gimodule.lo
CC _gi_la-pygi-invoke.lo
CC _gi_la-pygi-cache.lo
CC _gi_la-pygi-marshal-from-py.lo
CC _gi_la-pygi-marshal-to-py.lo
CC _gi_la-pygi-marshal-cleanup.lo
CCLD _gi.la
CC _gi_cairo_la-pygi-foreign-cairo.lo
CCLD _gi_cairo.la
ln -s -f .libs/_gi.cpython-34m.so _gi.cpython-34m.so
ln -s -f .libs/_gi_cairo.cpython-34m.so _gi_cairo.cpython-34m.so
make[3]: Leaving directory `/tmp/sbopkg.RHvM8f/pygobject-3.10.2/gi'
make[2]: Leaving directory `/tmp/sbopkg.RHvM8f/pygobject-3.10.2/gi'
Making all in tests
make[2]: Entering directory `/tmp/sbopkg.RHvM8f/pygobject-3.10.2/tests'
CC libgimarshallingtests_la-gimarshallingtests.lo
GEN libgimarshallingtests.la
test -L libgimarshallingtests.so || ln -s .libs/libgimarshallingtests.so libgimarshallingtests.so
CC libregress_la-regress.lo
GEN libregress.la
test -L libregress.so || ln -s .libs/libregress.so libregress.so
CC testhelper_la-testhelpermodule.lo
testhelpermodule.c: In function _wrap_test_value_array:
testhelpermodule.c:516:3: warning: g_value_array_get_type is deprecated (declared at /usr/include/glib-2.0/gobject/gvaluearray.h:62): Use 'GArray' instead [-Wdeprecated-declarations]
g_value_init(value, G_TYPE_VALUE_ARRAY);
^
CC testhelper_la-test-floating.lo
CC testhelper_la-test-thread.lo
CC testhelper_la-test-unknown.lo
GEN testhelper.la
test -L testhelper.so || ln -s .libs/testhelper.so testhelper.so
make[2]: Leaving directory `/tmp/sbopkg.RHvM8f/pygobject-3.10.2/tests'
Making all in pygtkcompat
make[2]: Entering directory `/tmp/sbopkg.RHvM8f/pygobject-3.10.2/pygtkcompat'
for f in __init__.py generictreemodel.py pygtkcompat.py; do \
[ -e ./$f ] || ln -s ./$f ./$f; \
done
make[2]: Leaving directory `/tmp/sbopkg.RHvM8f/pygobject-3.10.2/pygtkcompat'
make[2]: Entering directory `/tmp/sbopkg.RHvM8f/pygobject-3.10.2'
for f in gi/__init__.py gi/types.py gi/module.py gi/importer.py gi/pygtkcompat.py gi/docstring.py; do \
[ -e ./$f ] || \
ln -s /tmp/sbopkg.RHvM8f/pygobject-3.10.2/$f ./$f; \
done
...

i truncate the output due to the limit in LQ, but at the end, it built fine

brobr · 03-18-2015, 09:41 AM

Hi Willy,

There is a difference between your and my process:
You get

Code:

/usr/bin/gnome-autogen.sh
checking for automake >= 1.11.2...
  testing automake... found 1.14.1
checking for autoreconf >= 2.53...
  testing autoreconf... found 2.69
checking for pkg-config >= 0.14.0...

But my expected automake is found to be different, and it all stalls. Further, your system does not call autoconf, but autoreconf instead

Code:

/usr/bin/gnome-autogen.sh
checking for autoconf >= 2.53...
  testing autoconf2.50... not found.
  testing autoconf... found 2.69
checking for automake >= 1.9...
  testing automake-1.11... not found.
  testing automake-1.10... not found.
  testing automake-1.9... not found.
***Error***: You must have automake >= 1.9 installed

Did I use a wrong patch-file? Which repository are you using???

willysr · 03-18-2015, 11:07 AM

i'm using the official SBo repository

brobr · 03-19-2015, 12:48 PM

Same here.. I have multilib installed as well.. would that change anything?

willysr · 03-19-2015, 05:34 PM

multilib requires special attention as mentioned in the FAQ
http://slackbuilds.org/faq/#multilib

not all of us test the packages in multilib environment (there is no official support for multilib)