Fails to build with Vala autotools support not installed

Bug #1497038 reported by tele1234567891
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Light Display Manager
Fix Released
Medium
Unassigned
1.16
Fix Released
Medium
Unassigned

Bug Description

I use PCLinuxOS 64 bit Mate
source code: lightdm-1.16.2
and I have:

$ ./configure
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 whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-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 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/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 x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-unknown-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 -m elf_x86_64) 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... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... no
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether to enable maintainer-specific portions of Makefiles... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for gobject-introspection... no
./configure: line 15705: syntax error near unexpected token `0.16'
./configure: line 15705: `VAPIGEN_CHECK(0.16)'

I installed also lib64girepository-devel for gobject-introspection, but not helped,
I don't understand "VAPIGEN_CHECK(0.16)" , any tips ?
Maybe this is from vala ? I use Vala 0.28.1

Related branches

description: updated
Revision history for this message
Robert Ancell (robert-ancell) wrote :

Do you have /usr/share/vala-0.28/vapigen.m4 installed?

Revision history for this message
Robert Ancell (robert-ancell) wrote :

Actually, that's probably /usr/share/aclocal/vapigen.m4 - Debian / Ubuntu uses some symlink magic to have multiple versions of this file.

Revision history for this message
tele1234567891 (swojskichlopak) wrote :

$ locate vapigen.m4
/usr/share/aclocal/vapigen.m4

$ rpm -qf /usr/share/aclocal/vapigen.m4
lib64vala-devel-0.28.1-1pclos2015

Revision history for this message
tele1234567891 (swojskichlopak) wrote :

I created simlink

# ls -l
total 16
drwxr-xr-x 2 root root 16384 Sep 1 17:45 vapi/
lrwxrwxrwx 1 root root 29 Sep 21 10:19 vapigen.m4 -> /usr/share/aclocal/vapigen.m4
[root@localhost vala-0.28]# pwd
/usr/share/vala-0.28

but I have
checking pkg-config is at least version 0.9.0... yes
checking for gobject-introspection... yes
./configure: line 15705: syntax error near unexpected token `0.16'
./configure: line 15705: `VAPIGEN_CHECK(0.16)'

line is strange for me in .configure

#----------------------------------------------------------------------------------------------------

else
  HAVE_INTROSPECTION_TRUE='#'
  HAVE_INTROSPECTION_FALSE=
fi

VAPIGEN_CHECK(0.16)

for ac_header in security/pam_appl.h
do :
  ac_fn_c_check_header_mongrel "$LINENO" "security/pam_appl.h" "ac_cv_header_security_pam_appl_h" "$ac_includes_default"
#----------------------------------------------------------------------------------------------------

I removed "VAPIGEN_CHECK(0.16)" line for tests.

Revision history for this message
tele1234567891 (swojskichlopak) wrote :

#----------------------------------------------------------------------------------------------------------------
config.status: executing po/stamp-it commands

                    Light Display Manager 1.16.2
                    ===========================

        prefix: /usr/local
        Greeter session: default
        Greeter user: lightdm
        User session: default
        GObject introspection: yes
        Vala bindings:
        liblightdm-qt: yes
        liblightdm-qt5: yes
        libaudit support: yes
        Enable tests: yes

#----------------------------------------------------------------------------------------------------------------

Revision history for this message
tele1234567891 (swojskichlopak) wrote :

#------------------------------------------------------------------------------------
]$ make
make all-recursive
make[1]: Entering directory '/home/gg/Downloads/te2/lightdm-1.16.2'
Making all in common
make[2]: Entering directory '/home/gg/Downloads/te2/lightdm-1.16.2/common'
  CC libcommon_la-configuration.lo
  CC libcommon_la-dmrc.lo
  CC libcommon_la-privileges.lo
  CC libcommon_la-user-list.lo
  CCLD libcommon.la
make[2]: Leaving directory '/home/gg/Downloads/te2/lightdm-1.16.2/common'
Making all in liblightdm-gobject
make[2]: Entering directory '/home/gg/Downloads/te2/lightdm-1.16.2/liblightdm-gobject'
Makefile:1007: *** missing separator. Stop.
make[2]: Leaving directory '/home/gg/Downloads/te2/lightdm-1.16.2/liblightdm-gobject'
Makefile:469: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/gg/Downloads/te2/lightdm-1.16.2'
Makefile:400: recipe for target 'all' failed
make: *** [all] Error 2
#--------------------------------------------------------------------------

Revision history for this message
Robert Ancell (robert-ancell) wrote :

I added vapigen.m4 into the m4/ directory and it now can configure without Vala installed.

Changed in lightdm:
status: New → Fix Committed
milestone: none → 1.17.0
importance: Undecided → Medium
Revision history for this message
tele1234567891 (swojskichlopak) wrote :

Can I download your 1.17.0 to test ?

Revision history for this message
Robert Ancell (robert-ancell) wrote :

1.17.0 is not yet released but you can get it from the bzr branch:
$ bzr branch lp:simple-scan

Revision history for this message
tele1234567891 (swojskichlopak) wrote :

 - Thanks for source code, I tried build, and I need pause,
because ./configure want "packagekit"
I don't have this in own repository,

 - I tried compile packagekit and

configure: error: Package requirements (libsystemd) were not met:
No package 'libsystemd' found

 - I don't use systemd in PCLinuxOS , and we don't have this lib, so I need pause work for now.

Revision history for this message
Robert Ancell (robert-ancell) wrote :

OK, I'll look at making the PackageKit support optional.

Revision history for this message
Robert Ancell (robert-ancell) wrote :

PackageKit support is now optional - please try again.

Revision history for this message
Robert Ancell (robert-ancell) wrote :

Hang on - I've confused my packages. You want lp:lightdm, not lp:simple-scan. Sorry.

Revision history for this message
tele1234567891 (swojskichlopak) wrote :

 bzr branch lp:lightdm

./configure with success :D

#------------------------------------------------------------------------------------------------------------------------
config.status: executing po/stamp-it commands

                    Light Display Manager 1.16.0
                    ===========================

        prefix: /usr/local
        Greeter session: default
        Greeter user: lightdm
        User session: default
        GObject introspection: yes
        Vala bindings: yes
        liblightdm-qt: yes
        liblightdm-qt5: yes
        libaudit support: yes
        Enable tests: yes

make
...
  CXX liblightdm_qt_3_la-greeter.lo
  CXX liblightdm_qt_3_la-power.lo
  CXX liblightdm_qt_3_la-sessionsmodel.lo
  CXX liblightdm_qt_3_la-usersmodel.lo
  CXXLD liblightdm-qt-3.la
  CXX liblightdm_qt5_3_la-greeter.lo
In file included from greeter.cpp:296:0:
greeter_moc5.cpp:13:2: error: #error "This file was generated using the moc from 4.8.7. It"
 #error "This file was generated using the moc from 4.8.7. It"
  ^
greeter_moc5.cpp:14:2: error: #error "cannot be used with the include files from this version of Qt."
 #error "cannot be used with the include files from this version of Qt."
  ^
#------------------------------------------------------------------------------------------------------------------------
I guesses 4.8.7 this is qt4 and I need rebuild "Music On Console" with qt5.
Yes ?
I will try update it tomorow.

Revision history for this message
tele1234567891 (swojskichlopak) wrote :

Edit.
Google say about also " Meta-Object Compiler (moc) "
Sounds better because this is plugin Qt,
but I can not find source code.

Revision history for this message
Robert Ancell (robert-ancell) wrote :

Check if a make clean removes the moc generated files and regenerates them, Otherwise something is going weird with your Qt install. You can disable Qt support with --disable-liblightdm-qt (Qt4) and --disable-liblightdm-qt5 (Qt5) when running configure.

Revision history for this message
tele1234567891 (swojskichlopak) wrote :

Success ! :D

#------------------------------------------------------------------------
$ locate moc | grep usr | grep qt
/usr/lib64/qt4/bin/moc
/usr/lib64/qt4/mkspecs/features/moc.prf
/usr/lib64/qt4/mkspecs/features/symbian/moc.prf
/usr/lib64/qt5/bin/moc
/usr/lib64/qt5/include/QtCore/5.4.2/QtCore/private/qmetaobject_moc_p.h
/usr/lib64/qt5/mkspecs/features/moc.prf

$ rpm -qf /usr/lib64/qt4/bin/moc
lib64qt4-devel-4.8.7-1pclos2015

$ rpm -qf /usr/lib64/qt5/bin/moc
qtbase5-common-devel-5.4.2-1pclos2015
 #------------------------------------------------------------------------
I uninstalled lib64qt4-devel and run ./autogen.sh , ./configure , make
and looks good :D
Thanks for help !

summary: - line 15705: `VAPIGEN_CHECK(0.16)'
+ Fails to build with Vala autotools support not installed
Changed in lightdm:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.