Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

[67ae7d]: TROUBLESHOOTING Maximize Restore History

Download this file

TROUBLESHOOTING    110 lines (68 with data), 3.8 kB

Possible problems:
------------------

* Compilation of applications that compiled fine with libgpod 0.4.2
  fail with libgpod 0.5.0 or later because of unknown symbols.

With version 0.5.0 of libgpod the namespace has been cleaned up. All
exported symbols now start with either ITDB or Itdb. Applications
using the old symbols will have to be adapted. Please see the
ChangeLog entry from 27 April 2007 for details on the renaming.

------------------------------------------------------------

* If you get an error stating

"possibly undefined macro: AC_PROG_INTLTOOL"

when running ./autogen.sh you need to install the "intltool"
package. On Debian

"apt-get install intltool"

will do that for you.


------------------------------------------------------------

* If you get an error stating

"checking for XML::Parser... configure: error: XML::Parser perl module is required for intltool"

you need to install the libxml-parser package. On Debian

"apt-get install libxml-parser-perl"

will do that for you.


------------------------------------------------------------

* "/bin/sh: ../mkinstalldirs: No such file or directory"

If you get this error, you are probably using automake >= 1.8.
Automake 1.8 does no longer install the mkinstalldirs file, and
gettext 0.14.4 does still depend on it... (automake 1.9.6 seems
to work fine, btw.)

Do a 'locate gettext/mkinstalldirs' and copy it over, then run
./autogen.sh again for good measure.

------------------------------------------------------------

* "config.status: error: cannot find input file: po/Makefile.in.in"

Upgrade intltool. 0.33 seems to work.

------------------------------------------------------------

* "array size missing in `padding'"

Older versions of gcc don't seem to understand the construct. You can
either change the 'padding[]' strings to 'padding[0]' (not tested) or
upgrade your gcc to a more recent version (gcc-3.2 has been reported
to work) fine.

------------------------------------------------------------

* Compiling for 64bit systems

The current autoconf/automake setup doesn't set the correct
installation path on 64bit systems. To work around this issue and to
get the libraries installed in the correct locations you need to
specify a couple extra parameters to autogen.sh (or configure). If your
installation prefix is '/opt/gnome' use the following:

./autogen.sh --prefix=/opt/gnome --enable-libsuffix=64 --libdir=/opt/gnome/lib64

If you use a different prefix, replace '/opt/gnome' accordingly.

Added on 2007/1/15: Note that I don't have any problems on my Debian
4.1.1-13 system and won't have to do any of this.

------------------------------------------------------------

* Packages required to build python bindings

On Debian the following packages are required:

python (e.g. python2.4)
python-dev (e.g. python2.4-dev)
python-mutagen

These are needed for full photo/thumbnail support:
python-gtk2-dev (and python-gobject-dev, if using python-gtk2-dev >= 2.10)

------------------------------------------------------------

* The hal callout doesn't run automatically to setup SysInfoExtended

If you have hal and libsgutils installed before running autogen.sh or configure,
a hal callout and .fdi file will be built and installed. This will query an iPod
when it is plugged in and save the SysInfoExtended file in the proper place.
This should be completely automatic. However, for this to work, the callout must
be installed in hal's callout path. $libdir/hal/scripts is the most portable
location (hal's $libdir can be found using pkg-config). If the default paths for
the callout or fdi file are not detected properly, you can specify the proper
locations manually, via configure:

    $ ./configure --with-hal-callouts-dir=DIR --with-hal-fdi-dir=DIR