Opened 10 years ago

Closed 10 years ago

#42595 closed defect (fixed)

libgpod configure failure

Reported by: luigi.barbieri12@… Owned by: rmstonecipher@…
Priority: Normal Milestone:
Component: ports Version: 2.2.1
Keywords: Cc: dbevans (David B. Evans)
Port: libgpod

Description (last modified by neverpanic (Clemens Lang))

iMac-xxxxx:~ home$ sudo port install digikam
--->  Computing dependencies for digikam
--->  Dependencies to be installed: libgpod
--->  Configuring libgpod
Error: Failed to configure libgpod, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_libgpod/libgpod/work/libgpod-0.8.0/config.log
Error: org.macports.configure for port libgpod returned: configure failure: command execution failed
Error: Failed to install libgpod
Please see the log file for port libgpod for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_libgpod/libgpod/main.log
Error: The following dependencies were not installed: libgpod
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port digikam failed

Note that

  1. in an other mac I use the install went flawless: identical 10.9.1 Macos identical port self update and upgrade
  2. all other dependencies were installed flawlessly
  3. I repeated after port clean: no differences

Thanks so much in anycase Luigi

Attachments (1)

libgpod_config.log_txt.txt (40.9 KB) - added by luigi.barbieri12@… 10 years ago.
log file generayed

Download all attachments as: .zip

Change History (5)

Changed 10 years ago by luigi.barbieri12@…

Attachment: libgpod_config.log_txt.txt added

log file generayed

comment:1 Changed 10 years ago by neverpanic (Clemens Lang)

Description: modified (diff)
Keywords: libgpod - digikam removed
Owner: changed from macports-tickets@… to rmstonecipher@…

Please use WikiFormatting when posting in Trac and preview your post. When reporting bugs against ports, please Cc the maintainers (port info --maintainer libpod), if any.

Looks like a missing dependency on p$verison-xml-parser to me.

comment:2 Changed 10 years ago by neverpanic (Clemens Lang)

Cc: devans@… added

Might need a similar fix as in r117325 or r117330, but I suppose devans would know more about that (I actually don't know what the problem with intltool is, I just vaguely remember there was some perl-related issue with it).

comment:3 Changed 10 years ago by dbevans (David B. Evans)

Fix committed in r117357.

This occurs when the perl variants for intltool and perl5 do not match and the port's configure file was generated upstream using the version of intltool.m4 that is distributed with intltool. This is occurring more often now that the default variant for intltool has been changed to +perl5_16 and people are still using perl5 +perl5_12.

The MacPorts intltool port patches intltool.m4 to avoid this problem. The necessary fix is to regenerate the configure file using our patched intltool.m4. How this is done for a specific port depends on how its configure.ac is constructed, whether intltoolize needs to be run in the reconfiguration procedure, etc.

comment:4 Changed 10 years ago by dbevans (David B. Evans)

Resolution: fixed
Status: newclosed
Summary: ligpod configure failurelibgpod configure failure
Note: See TracTickets for help on using tickets.