Opened 10 years ago

Closed 10 years ago

#45244 closed defect (worksforme)

gegl: error: The type name `string' could not be found

Reported by: martyz@… Owned by: dbevans (David B. Evans)
Priority: Normal Milestone:
Component: ports Version: 2.3.1
Keywords: Cc:
Port: gegl

Description

Hello guys, this is my first post here so sorry for any gaps. I'm running Mavericks 10.9.5 with Xcode Version 6.0.1 (6A317), Command Line Tools (OS X 10.9) for Xcode 6, release date Sep 16 2014. MacPorts is 2.3.1 and up to date. But I'm not able to upgrade or install any package. Steps I tried:

  • reinstall command line tools
  • sudo xcodebuild -license
  • sudo port clean all
    ~ $ sudo port selfupdate 
    --->  Updating MacPorts base sources using rsync
    MacPorts base version 2.3.1 installed,
    MacPorts base version 2.3.1 downloaded.
    --->  Updating the ports tree
    --->  MacPorts base is already the latest version
    
    The ports tree has been updated. To upgrade your installed ports, you should run
      port upgrade outdated
    

and then upgrade

sudo port upgrade outdated
Password:
--->  Computing dependencies for gegl
--->  Fetching archive for gegl
--->  Attempting to fetch gegl-0.2.0_13+python27+x11.darwin_13.x86_64.tbz2 from http://nue.de.packages.macports.org/macports/packages/gegl
--->  Attempting to fetch gegl-0.2.0_13+python27+x11.darwin_13.x86_64.tbz2 from http://lil.fr.packages.macports.org/gegl
--->  Attempting to fetch gegl-0.2.0_13+python27+x11.darwin_13.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/gegl
--->  Fetching distfiles for gegl
--->  Verifying checksums for gegl
--->  Extracting gegl
--->  Applying patches to gegl
--->  Configuring gegl
--->  Building gegl
Error: org.macports.build for port gegl returned: command execution failed
Please see the log file for port gegl for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_gegl/gegl/main.log
Error: Unable to upgrade port: 1
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets

so I ended up in this ticket system :-) On my other mac same sequence (with no need to clean) succeeded, but here I can't get over strange gegl error.

Attachments (2)

main.log (533.0 KB) - added by martyz@… 10 years ago.
main-success.log (1.5 MB) - added by dbevans (David B. Evans) 10 years ago.
Maintainer's successful build log

Change History (9)

Changed 10 years ago by martyz@…

Attachment: main.log added

comment:1 Changed 10 years ago by martyz@…

and sorry for bad Component selection - should be base, but I have no idea how to change that :-S Thanks.

comment:2 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)

Keywords: gegl error upgrade removed
Owner: changed from macports-tickets@… to devans@…
Port: gegl added
Summary: MacPorts 2.3.1 upgrade outdated - Unable to upgrade portgegl: error: The type name `string' could not be found

"ports" is the correct component.

The relevant failure in the log seems to be:

:info:build /opt/local/bin/g-ir-compiler --includedir="." --includedir="/opt/local/share/gir-1.0" --includedir=. Gegl-0.2.gir -o Gegl-0.2.typelib
:info:build /opt/local/bin/vapigen --library=gegl-0.2 --metadatadir=./ Gegl-0.2.gir
:info:build Gegl-0.2.metadata:2.1-2.25: warning: metadata never used
:info:build module_register_type skip
:info:build ^^^^^^^^^^^^^^^^^^^^^^^^^
:info:build Gegl-0.2.gir:4837.45-4837.45: error: The type name `string' could not be found
:info:build           <type name="utf8" c:type="const gchar*"/>
:info:build                                             ^

comment:3 Changed 10 years ago by martyz@…

Thank you for reply Ryan, honestly I have no clue how to fix this, even when I focus on highlighted part of mail.log... Please push me slightly more :-). What in environment declares string? Or is problem that metadata has been never used? I even uninstalled inactive and leaves, but gegl still freaking out (and me also)... Thx

Martin

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

Status: newassigned

The port builds successfully for me using exactly the same setup. I'm attaching the successful build log. The lines corresponding to your failure are as follows

:info:build /opt/local/bin/g-ir-compiler --includedir="." --includedir="/opt/local/share/gir-1.0" --includedir=. Gegl-0.2.gir -o Gegl-0.2.typelib
:info:build /opt/local/bin/vapigen --library=gegl-0.2 --metadatadir=./ Gegl-0.2.gir
:info:build Gegl-0.2.metadata:2.1-2.25: warning: metadata never used
:info:build module_register_type skip
:info:build ^^^^^^^^^^^^^^^^^^^^^^^^^
:info:build Generation succeeded - 1 warning(s)

so the metadata warning doesn't seem to be pertinent. Perhaps the gir or typelib files for one of gegl's dependencies is missing or corrupted (possibly glib2?). In this case, perhaps a forced rebuild of the offending dependencies might help. But that's just a guess on my part.

At any rate, based on my success and yours on another machine, it seems there's something not quite right with your installation here. Not much help I'm afraid.

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

Attachment: main-success.log added

Maintainer's successful build log

comment:5 Changed 10 years ago by martyz@…

Thank you for your effort and time, really. I will try to force rebuild all gegl dependencies and they start from scratch, shouldn't hurt that much :-)

Take care

comment:6 Changed 10 years ago by martyz@…

Wow, thanks for a hint! What I did:

uninstall gegl
deps gegl
build pkgconfig  intltool w3m autoconf automake lib tool python27 babl gtk2 gobject-introspection jpeg lua openexr exiv2 libopenraw librsvg libsdl ffmpeg libspiro lensfun vala gegl
install gegl
upgrade outdated

and wohooo - no complaints, everything up and running :-) Thankx once again.
Martin

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

Resolution: worksforme
Status: assignedclosed

Great. Glad it worked.

Note: See TracTickets for help on using tickets.