Opened 15 years ago

Closed 15 years ago

Last modified 13 years ago

#20159 closed defect (worksforme)

glibmm: glibmm-2.20.0: No such file or directory

Reported by: thewoolleyman@… Owned by: dbevans (David B. Evans)
Priority: Normal Milestone:
Component: ports Version: 1.7.1
Keywords: Cc:
Port: glibmm

Description (last modified by mf2k (Frank Schima))

I found this bug (#18999), but that isn't my problem. My /opt/local/etc/macports/variants.conf and /usr/local/etc/macports/variants.conf are empty.

Attached is a file output from running the suggested commands from that ticket:

http://gist.github.com/140502

Thanks, -- Chad

Attachments (2)

gobby_fail.txt (144.4 KB) - added by thewoolleyman@… 15 years ago.
Output from running http://gist.github.com/140502
gobby_fail_different_machine.txt (831 bytes) - added by thewoolleyman@… 15 years ago.

Download all attachments as: .zip

Change History (11)

Changed 15 years ago by thewoolleyman@…

Attachment: gobby_fail.txt added

Output from running http://gist.github.com/140502

comment:1 Changed 15 years ago by thewoolleyman@…

Cc: thewoolleyman@… added

Cc Me!

comment:2 Changed 15 years ago by thewoolleyman@…

Attaching another file with the (truncated, just the error) output from a failed gobby install on a different machine...

Changed 15 years ago by thewoolleyman@…

comment:3 Changed 15 years ago by blb@…

Owner: changed from macports-tickets@… to devans@…
Port: glibmm added
Summary: Gobby not working for meglibmm fails to build during install of Gobby

Your first error:

DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_glibmm/work/glibmm-2.20.0" && ./configure --prefix=/opt/local'
sh: line 0: cd: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_glibmm/work/glibmm-2.20.0: No such file or directory
Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_glibmm/work/glibmm-2.20.0" && ./configure --prefix=/opt/local " returned error 1
Command output: sh: line 0: cd: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_glibmm/work/glibmm-2.20.0: No such file or directory

appears to be an issue with glibmm; I'm not sure why it can't find that directory which should exist upon extracting. Try a sudo port clean --work glibmm and then try your initial install of gobby again.

The second error sounds like a missing dependency, but there isn't enough information to go on to determine which port is having the issue there; full debug output would be needed. However, if it isn't glibmm, please open a new ticket for that.

comment:4 Changed 15 years ago by mf2k (Frank Schima)

Description: modified (diff)

comment:5 Changed 15 years ago by dbevans (David B. Evans)

Cc: thewoolleyman@… removed

First of all, the fact that you have macports files in /usr/local is suspicious. MacPorts doesn't install anything there by default and installing files manually in /usr/local (not using MacPorts usually causes problems.

To test if this is causing problems, just temporarily move /usr/local to /usr/local.bak and try building glibmm again.

sudo port clean glibmm
sudo port -d build glibmm

removing you from CC because the ticket reporter is automatically copied.

comment:6 Changed 15 years ago by thewoolleyman@…

I have opened a new ticket for the second error, with the full debug output attached: #20183

comment:7 Changed 15 years ago by thewoolleyman@…

sudo port clean --work glibmm worked for me. After that, gobby installed and ran fine. I also renamed /usr/local/etc to /usr/local/etc.bak. Thanks for the help!

comment:8 Changed 15 years ago by dbevans (David B. Evans)

Resolution: worksforme
Status: newclosed

comment:9 in reply to:  3 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)

Summary: glibmm fails to build during install of Gobbyglibmm: glibmm-2.20.0: No such file or directory

Replying to blb@…:

I'm not sure why it can't find that directory which should exist upon extracting.

This was probably caused by #29223.

Note: See TracTickets for help on using tickets.