Solved MySQL update

Mwh65

Member

Thanks: 3
Messages: 93

#1
Since updating MySQL 5.6.39_1 to 5.6.39_2 I now receive the following line when upgrading any port ...

No such file or directory @ realpath_rec - /usr/local/lib/compat/pkg/libmysqlclient.so.18

Which is correct but there is a file called libmysqlclient_r.so.18

A bit concerned it has failed to upgrade correctly.
 

SirDice

Administrator
Staff member
Administrator
Moderator

Thanks: 6,785
Messages: 28,552

#2
I'm wondering why it's looking in the compat/ directory at all, the library should be /usr/local/lib/mysql/libmysqlclient.so.18. What version of FreeBSD are you using and did you perhaps do a major version upgrade recently?
 
OP
OP
M

Mwh65

Member

Thanks: 3
Messages: 93

#3
FreeBSD version is 10.3 and the libmysqlclient.so.18 file is indeed in the path you mentioned and dated 5th April.

No major upgrade of MySQL recently.
 

DutchDaemon

Administrator
Staff member
Administrator
Moderator
Developer

Thanks: 2,734
Messages: 11,261

#6
grep -i mysql /etc/rc.conf? /cat /etc/make.conf? Setting flags anywhere?
 
OP
OP
M

Mwh65

Member

Thanks: 3
Messages: 93

#7
In /etc/rc.conf I have ...
Code:
mysql_enable="YES"
In /etc/make.conf I have ...
Code:
DEFAULT_VERSIONS= perl5=5.26
 

DutchDaemon

Administrator
Staff member
Administrator
Moderator
Developer

Thanks: 2,734
Messages: 11,261

#9
I haven't used portupgrade in ages, but I remember this option from portmaster:
Code:
     After the port is built, if the -w option is being used, all shared
     libraries installed by the old port (if any) will be saved to
     /usr/local/lib/compat/pkg.  After installation if there are any new files
     with the same names as those in /usr/local/lib/compat/pkg the old files
     will be deleted, and ldconfig(8) will be run via /etc/rc.d/ldconfig.
 
OP
OP
M

Mwh65

Member

Thanks: 3
Messages: 93

#11
On closer inspection the /usr/local/lib/compat/pkg/libmysqlclient_r.so.18 file is a symbolic link. If I try to download the file it says it doesn't exit. The file though is dated 9th February 2018.

Could that file be causing this ?
 
Last edited by a moderator:

SirDice

Administrator
Staff member
Administrator
Moderator

Thanks: 6,785
Messages: 28,552

#12
You can probably remove everything in /usr/local/lib/compat/pkg, you're not going to need it if the updates have all been successful.
 
Top