Opened 14 years ago
Closed 14 years ago
#25328 closed defect (fixed)
libgda4: libtool: Version mismatch error
Reported by: | blueberrybadger@… | Owned by: | jyrkiwahlstedt |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.9.1 |
Keywords: | Cc: | dbevans (David B. Evans) | |
Port: | libgda4 |
Description (last modified by mf2k (Frank Schima))
ran sudo port install gramps
and go this error message:
:info:build Warning: the following items did not execute (for libgda4): org.macports.activate org.macports.build org.macports.destroot org.macports.install :notice:build Log for libgda4 is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_databases_libgda4/main.log
See attached log for full details
Attachments (1)
Change History (13)
Changed 14 years ago by blueberrybadger@…
comment:1 follow-up: 3 Changed 14 years ago by mf2k (Frank Schima)
Cc: | devans@… added |
---|---|
Description: | modified (diff) |
Owner: | changed from macports-tickets@… to jwa@… |
Port: | libgda4 added |
comment:3 Changed 14 years ago by blueberrybadger@…
Replying to macsforever2000@…:
You did not provide the actual error message, but fortunately you attached the mail log and it does contain it.
What is the output of the following?
port installed libtool
libtool @2.2.10_0 (active)
comment:4 Changed 14 years ago by mf2k (Frank Schima)
So this error is rather puzzling:
:info:build libtool: Version mismatch error. This is libtool 2.2.6b Debian-2.2.6b-2ubuntu1, but the :info:build libtool: definition of this LT_INIT comes from libtool 2.2.10. :info:build libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6b Debian-2.2.6b-2ubuntu1 :info:build libtool: and run autoconf again.
comment:5 Changed 14 years ago by nerdling (Jeremy Lavergne)
Likely, the portfile needs use_autoreconf yes
added to it.
Do so in these steps (add it at the bottom of the file that opens after the first command):
sudo port edit libgda4 sudo port clean libgda4 sudo port install libgda4
Let us know if that does the trick.
comment:6 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Summary: | the following items did not execute (for libgda4) → libgda4: libtool: Version mismatch error |
---|
Did r69164 fix this?
comment:7 Changed 14 years ago by blueberrybadger@…
Can't work out how to come out of editing the file
comment:8 follow-up: 9 Changed 14 years ago by jyrkiwahlstedt
Resolution: | → fixed |
---|---|
Status: | new → closed |
libtool mismatch fixed in r69164
comment:9 follow-up: 12 Changed 14 years ago by blueberrybadger@…
Resolution: | fixed |
---|---|
Status: | closed → reopened |
comment:10 follow-up: 11 Changed 14 years ago by sewebster@…
Don't worry about editing the file anymore, just run
sudo port selfupdate sudo port clean libgda4 sudo port install libgda4 sudo port install gramps
and hopefully it will work. If you were having trouble quitting the text editor that opened as a result of "sudo port edit libgda4" then I think the default editor is vi, and the way to exit is by typing
:q
comment:11 Changed 14 years ago by jyrkiwahlstedt
Replying to sewebster@…:
Don't worry about editing the file anymore, just run
sudo port selfupdate sudo port clean libgda4 sudo port install libgda4 sudo port install grampsand hopefully it will work. If you were having trouble quitting the text editor that opened as a result of "sudo port edit libgda4" then I think the default editor is vi, and the way to exit is by typing
:q
Well, vi is a strange one, but its advantage is always being there. The advice given holds, if you do no changes. If changes have been done, do:
:wq
to save the changes, or:
:q!
to discard them.
comment:12 Changed 14 years ago by jyrkiwahlstedt
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Replying to blueberrybadger@…:
Replying to jwa@…:
libtool mismatch fixed in r69164
I don't know if this is fixed or not. I asked for assistance on how to edit the file...
Ok, the ticket was originally about libtool mismatch, hence the ticket is closed. Editing files is not something to create a ticket about (though you can ask advice somewhere else), sorry.
So pls let this stay closed, unless the mismatch pops up again.
You did not provide the actual error message, but fortunately you attached the mail log and it does contain it.
What is the output of the following?