Lesson In Debugging Code

brando56894 · 2008-08-25 01:33:25

Can someone explain to me how to figure out what went wrong when compiling a program from source? I took 2 classes about 7 years ago in highschool about C++ but the main thing I want to learn is how to figure out make errors.

For example, I know I dont have a necessary package installed for this but I cant figure out what it is, can someone explain why it failed to build?

>> compiz <<

 * Updating compiz
Already up-to-date.
 * Cleaning old compile
make: *** No rule to make target `clean'.  Stop.
 * Configuring new version
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal
configure.ac:197: warning: macro `AM_GCONF_SOURCE_2' not found in library
autoreconf: configure.ac: tracing
autoreconf: running: libtoolize --copy
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
configure.ac:197: warning: macro `AM_GCONF_SOURCE_2' not found in library
autoreconf: running: /usr/bin/autoconf
autoreconf: running: /usr/bin/autoheader
autoreconf: running: automake --add-missing --copy --no-force
kde/window-decorator-kde4/Makefile.am:38: `%'-style pattern rules are a GNU make extension
kde/window-decorator/Makefile.am:32: `%'-style pattern rules are a GNU make extension
kde/window-decorator/Makefile.am:35: `%'-style pattern rules are a GNU make extension
kde/window-decorator/Makefile.am:38: `%'-style pattern rules are a GNU make extension
metadata/Makefile.am:77: GCONF_SCHEMAS_INSTALL does not appear in AM_CONDITIONAL
metadata/Makefile.am:40: patsubst %.xml.in,compiz-%.schemas,$(xml_in_files: non-POSIX variable name
metadata/Makefile.am:40: (probably a GNU make extension)
metadata/Makefile.am:43: `%'-style pattern rules are a GNU make extension
metadata/Makefile.am:53: patsubst %.xml.in,compiz-%.kcfg,$(xml_in_files: non-POSIX variable name
metadata/Makefile.am:53: (probably a GNU make extension)
metadata/Makefile.am:57: `%'-style pattern rules are a GNU make extension
metadata/Makefile.am:58: subst compiz-,,$*: non-POSIX variable name
metadata/Makefile.am:58: (probably a GNU make extension)
autoreconf: automake failed with exit status: 1
 -> compiz's autogen.sh reports errors. Bailing.
______________________________________________

Failed to build compiz. No reason to continue.

this is from the git-compiz script made by omega over on the compiz forums btw

ladislaio · 2008-08-25 02:27:44

Why are you installing from source? The latest dev build of compiz is in the community repro(0.7.6), and if you need the git build there is a pacbuild in the AUR.

If you do not know how to use the AUR, then read over these wiki pages:
http://wiki.archlinux.org/index.php/Arc … tory_(AUR)
http://wiki.archlinux.org/index.php/Aurbuild

brando56894 · 2008-08-25 02:49:19

im compiling from source because im a noob when it comes to arch lol, ive been using kubuntu/mint for a few years and doing this was the easiest way to get the newest compiz build. is the git build in AUR updated frequently (every few days or a week)? if it isn't i would like to use this script if possible since whenever it is ran it grabs ALL of the plugins and updates for Compiz-Fusion, Emerald and CCSM.

Last edited by brando56894 (2008-08-25 02:59:59)

ladislaio · 2008-08-25 03:02:40

The compiz-kde-git AUR pacbuild uses Git to download and build the latest compiz. Chase the links I gave you - using pacbuilds is not hard.

brando56894 · 2008-08-25 03:08:21

oh ok, i read about AUR and ABS before and read that they were user submitted packages and I just assumed that it was a user that took the source from git and submitted it to AUR. I'm reading up on both of them now. It may not be difficult to use but it is a big change compared to what im used to.

rooloo · 2008-08-25 03:30:19

brando56894 wrote:

oh ok, i read about AUR and ABS before and read that they were user submitted packages and I just assumed that it was a user that took the source from git and submitted it to AUR. I'm reading up on both of them now. It may not be difficult to use but it is a big change compared to what im used to.

don't let the little things scare you.

brando56894 · 2008-08-25 03:39:05

oh they dont it just takes some getting used to, i just like the git-compiz script because it did everything for you (yes i know this against the arch philosophy). all i had to do to install (or update to the latest version) was navigate to the directory where the script was and type ./git-compiz --with-desktop=kde and it did everything for me. im learning about how to do this the arch way and see how it fares against what im used to. the newest version of compiz i could find was from june 8th 2008. im sure theyve changed something in over two months.

Last edited by brando56894 (2008-08-25 03:43:49)

rooloo · 2008-08-25 11:04:21

http://aur.archlinux.org/packages.php?ID=5904

here is compiz-git, yes the daye is 2007, but that is the beauty of abs/makpkg. It DOESN'T matter, if the PKGBUILD is set checkout the latest master branch then the package that is made will be the latest version of the compiz-git repository.

Once you have the PKGBUILD/files downloaded to a directory it's as easy as...

makepkg

anyday of the week and you will have the latest compiz version ready to be installed in a package through pacman.

Arch Linux

#1 2008-08-25 01:33:25

Lesson In Debugging Code

#2 2008-08-25 02:27:44

Re: Lesson In Debugging Code

#3 2008-08-25 02:49:19

Re: Lesson In Debugging Code

#4 2008-08-25 03:02:40

Re: Lesson In Debugging Code

#5 2008-08-25 03:08:21

Re: Lesson In Debugging Code

#6 2008-08-25 03:30:19

Re: Lesson In Debugging Code

#7 2008-08-25 03:39:05

Re: Lesson In Debugging Code

#8 2008-08-25 11:04:21

Re: Lesson In Debugging Code

Board footer