Opened 9 years ago

Closed 3 years ago

#49640 closed defect (invalid)

Failed to configure libtool

Reported by: marco.righi@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.3.4
Keywords: Cc: olouisnard@…, larryv (Lawrence Velázquez)
Port: libtool

Description (last modified by ryandesign (Ryan Carsten Schmidt))

sudo port upgrade outdated
--->  Configuring libtool
Error: Failed to configure libtool, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libtool/libtool/work/libtool-2.4.6/config.log
Error: org.macports.configure for port libtool returned: configure failure: command execution failed
Please see the log file for port libtool for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libtool/libtool/main.log
Error: Unable to upgrade port: 1
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets

Change History (5)

comment:1 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Description: modified (diff)
Port: libtool added
Priority: HighNormal

Please attach the main.log file and the config.log file mentioned in the error message you showed us. Without the information in those files, we cannot know why this problem occurred.

comment:2 in reply to:  1 ; Changed 9 years ago by olouisnard@…

Replying to ryandesign@…:

Please attach the main.log file and the config.log file mentioned in the error message you showed us. Without the information in those files, we cannot know why this problem occurred.

I have exactly the same problem. Do you allow me to send you these two files, although I did not create the ticket myself ?

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

Cc: olouisnard@… added

Replying to olouisnard@…:

Replying to ryandesign@…:

Please attach the main.log file and the config.log file mentioned in the error message you showed us. Without the information in those files, we cannot know why this problem occurred.

I have exactly the same problem. Do you allow me to send you these two files, although I did not create the ticket myself ?

Please file a new ticket and attach your files there. Since we have not seen the reporter's files, we do not know what the problem is, so we cannot know whether your problem is the same or different.

comment:4 Changed 9 years ago by larryv (Lawrence Velázquez)

Cc: larryv@… added

Cc Me!

comment:5 Changed 3 years ago by michaelld (Michael Dickens)

Resolution: invalid
Status: newclosed

Guessing whatever issue(s) were found here are resolved. If not, please reopen and provide info as to what's going on.

Note: See TracTickets for help on using tickets.