On Thu, May 20, 2021 at 01:13:51AM -0500, Ryan Schmidt
<[email protected]> wrote:
> On May 19, 2021, at 18:31, Bjarne D Mathiesen wrote:
>
> > Ryan Schmidt wrote:
> >> Looks like support for the "ALTER TABLE ... RENAME COLUMN" syntax
> >> first appeared in SQLite 3.25.0, and MacPorts base is coded only to
> >> use the "RENAME COLUMN" syntax with SQLite 3.25.0 and later; for
> >> earlier versions, a different method is used:
> >>
> >> What version of SQLite does your version of macOS have? Run:
> >>
> >> /usr/bin/sqlite3 --version
> >>
> >> I'm on macOS High Sierra with SQLite 3.19.3 and I haven't seen that
> >> problem.
> >
> > Qs:
> > 1) does MacPorts !explicitly! request /usr/bin/sqlite3
>
> MacPorts uses /usr/lib/libsqlite3.dylib.
>
> > -or- does MacPorts use the one found in ${PATH}
>
> > 2) is it advantagerous for MacPorts to use sqlite3 >= 3.25.0
> >
> > eg for 10.6.8 I've got :
> >
> > #=> /usr/bin/sqlite3 --version
> > 3.6.12
> > #=> which sqlite3
> > /opt/local/bin/sqlite3
> > #=> sqlite3 --version
> > 3.35.5 2021-04-19 18:32:05 1b256d97b ... e98fae886
>
> MacPorts by default uses the version of SQLite included with macOS. MacPorts
> 2.7.0 is compatible with every version of SQLite that comes with every
> supported version of macOS (10.4 and later including 11).
>
> The problem here may be that the version of SQLite whose headers were found
> at build time is different from the version of SQLite whose library was found
> at runtime. See the ticket.
When I disable /usr/lib/libsqlite3.dylib by renaming it,
the error changes to a symbol lookup failure:
> port help
dlopen(/opt/local/libexec/macports/lib/macports1.0/MacPorts.dylib, 6): can't
resolve symbol _kDADiskDescriptionMediaBSDNameKey in
/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation because
dependent dylib #2 could not be loaded in
/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
while executing
"load /opt/local/libexec/macports/lib/macports1.0/MacPorts.dylib"
("package ifneeded macports 1.0" script)
invoked from within
"package require macports"
(file "/opt/local/bin/port" line 46)
Oops. And now PAM/su/sudo are now broken. I shouldn't have done that. :-)
cheers,
raf