#46815 closed defect (invalid)
Selfupdate still fails on "readline in /usr/local" after cleanout
Reported by: | dsmithhfx@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | base | Version: | 2.0.3 |
Keywords: | Cc: | ||
Port: |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Hi,
I can't get port version 2.03 (OSX10.4.11/ppc/G5 tower) to selfupdate, it fails with
make[2]: *** [registry.dylib] Error 1 make[1]: *** [all] Error 1 make: *** [all] Error 1 shell command "cd /opt/local/var/macports/sources/rsync.macports.org/release/base && CC=/usr/bin/cc ./configure --prefix=/opt/local --with-tclpackage=/Library/Tcl --with-install-user=root --with-install-group=admin --with-directory-mode=0755 && make && make install SELFUPDATING=1" returned error 2 DEBUG: Error installing new MacPorts base: shell command failed (see log for details) while executing "macports::selfupdate [array get global_options] base_updated" Error: /opt/local/bin/port: port selfupdate failed: Error installing new MacPorts base: shell command failed (see log for details)
After some digging through tickets e.g. #11742, it appears that readline may be the culprit. Early in the selfupdate output there appears
---> MacPorts base is outdated, installing new version 2.3.3 DEBUG: Permissions OK Warning: Disabling readline support due to readline in /usr/local
Even after completely clearing all instances of *readline" from my /usr directory (so
sudo find /usr -name "*readline*"
returns nothing, and
sudo port -f deactivate readline
I'm really stuck here, running really outdated apache2 etc. Any help appreciated!
Attachments (2)
Change History (7)
Changed 10 years ago by dsmithhfx@…
Attachment: | Selfupdate-Output-021015-2.txt added |
---|
comment:1 follow-up: 2 Changed 10 years ago by neverpanic (Clemens Lang)
Changed 10 years ago by dsmithhfx@…
Attachment: | config.log added |
---|
comment:2 Changed 10 years ago by dsmithhfx@…
Replying to cal@…: Thanks for responding!
sudo find /usr -name "*sqlite3*" /usr/bin/sqlite3 /usr/include/sqlite3.h /usr/lib/libsqlite3.0.8.6.dylib /usr/lib/libsqlite3.0.dylib /usr/lib/libsqlite3.dylib /usr/lib/sqlite3 /usr/lib/sqlite3/libtclsqlite3.dylib /usr/local/bin/sqlite3 /usr/local/include/sqlite3.h /usr/local/include/sqlite3ext.h /usr/local/lib/libsqlite3.0.8.6.dylib /usr/local/lib/libsqlite3.0.dylib /usr/local/lib/libsqlite3.a /usr/local/lib/libsqlite3.dylib /usr/local/lib/libsqlite3.la /usr/local/lib/pkgconfig/sqlite3.pc [bunch of ruby gems] /usr/share/man/man1/sqlite3.1
config.log attached
comment:3 follow-up: 4 Changed 10 years ago by neverpanic (Clemens Lang)
Resolution: | → invalid |
---|---|
Status: | new → closed |
Yeah, the check picks up the sqlite3.h
from your sqlite installation in /usr/local
, but the link happens against /usr/lib/libsqlite3.dylib
, so it fails.
Move /usr/local/include
aside for a while and re-try and it'll work. We don't support having stuff in /usr/local
for precisely this reason. We cannot easily make the compiler ignore these locations.
comment:5 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|---|
Keywords: | selfupdate removed |
Problem is
It seems your version of sqlite3 is too old to support
sqlite3_prepare_v2
. MacPorts has a configure-time check to fall back tosqlite3_prepare
if it isn't available, but that seems to have failed in your case. Please attach/opt/local/var/macports/sources/rsync.macports.org/release/base/config.log
.Do you happen to have an
sqlite3.h
somewhere in/usr/local
, because it seems the newer header is available, but the newer library isn't (or isn't being found).