Trying to follow these instructions:
(http://dev.mysql.com/doc/refman/5.1/en/ha-memcached-interfaces-mysqludf.html)
shell> tar zxf memcached_functions_mysql-1.1.tar.gz
shell> cd memcached_functions_mysql-1.1
shell> # If memcached library is not found, set LDFLAGS=-Llibrary_directory before next command.
shell> ./configure --with-mysql=/usr/local/mysql/bin/mysql_config
When I run:
sudo ./configure --with-mysql=/usr/lib64/mysql/mysql_config
I get this at the end of output:
checking for libmemcached >= 0.17... configure: error: libmemcached not found
So I tried to set LDFLAGS as instructed above but don't know the "library_directory" path.
How can I find it?
Update 1: As per response below. libmemcached IS installed:
sudo yum install libmemcached
Loaded plugins: downloadonly, replace, rhnplugin, security
epel | 3.7 kB 00:00
ius | 2.2 kB 00:00
rackspace-rhel-x86_64-server-5.6.z-common | 871 B 00:00
rhel-x86_64-server-5.6.z | 1.3 kB 00:00
Excluding Packages in global exclude list
Finished
Setting up Install Process
Package libmemcached-0.31-1.1.el5.x86_64 already installed and latest version
Nothing to do
Thanks
You're missing libmemcached-devel, it probably needs headers too.
Related
I need to install sshpass on my AWS beanstalk when it is deployed.
I created a new clone to check that I could do it from the ssh shell command line and found that unless I specified the epel repo, it would not find the package:
$ sudo yum -y install sshpass
Failed to set locale, defaulting to C
Loaded plugins: priorities, update-motd, upgrade-helper
amzn-main | 2.1 kB 00:00:00
amzn-updates | 2.5 kB 00:00:00
No package sshpass available.
Error: Nothing to do
but this works:
$ sudo yum --enablerepo=epel -y install sshpass
Failed to set locale, defaulting to C
Loaded plugins: priorities, update-motd, upgrade-helper
1070 packages excluded due to repository priority protections
Resolving Dependencies
--> Running transaction check
---> Package sshpass.x86_64 0:1.06-1.el6 will be installed
--> Finished Dependency Resolution
Dependencies Resolved
==================================================================================================================================================================
Package Arch Version Repository Size
==================================================================================================================================================================
Installing:
sshpass x86_64 1.06-1.el6 epel 20 k
Transaction Summary
==================================================================================================================================================================
Install 1 Package
Total download size: 20 k
Installed size: 34 k
Downloading packages:
sshpass-1.06-1.el6.x86_64.rpm | 20 kB 00:00:00
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Installing : sshpass-1.06-1.el6.x86_64 1/1
Verifying : sshpass-1.06-1.el6.x86_64 1/1
Installed:
sshpass.x86_64 0:1.06-1.el6
Complete!
So how would I do this in the .ebextensions/-1-packages/install-packages.config file?
The syntax is defined in the AWS example as follows:
packages:
yum:
libmemcached: []
ruby-devel: []
gcc: []
rpm:
epel: http://download.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm
rubygems:
chef: '0.10.2'
But I'm not sure how to implement that for my case where i just want to tell it to use the epel repo
packages:
yum:
...
...
sshpass: []
I'm guessing the above won't automatically cause it to use the epel repo?
There might be a better way, but this worked:
commands:
24-sshpass:
command: "yum --enablerepo=epel -y install sshpass"
Hello need help with this error:
[root#localhost ~]# rpm --addsign php-composer-ca-bundle-1.0.2-1.fc22.remi.noarc
rpm: /usr/bin/rpmsign: No existe el fichero o el directorio
[root#localhost ~]# mkdir /usr/bin/rpmsign
rpm: /usr/bin/rpmsign: Permiso denegado
System is Fedora 22
no internet conection to solve via yum install
You are getting an error message which says that the file /usr/bin/rpmsign doesn't exist:
rpm: /usr/bin/rpmsign: No existe el fichero o el directorio
(In English, that would be rpm: /usr/bin/rpmsign: No such file or directory.)
You respond to that by just creating the missing thing as a directory with mkdir:
[root#localhost ~]# mkdir /usr/bin/rpmsign
I guess that follows a certain logic, but the thing is, that can't be just any file. RPM is looking for the actual rpmsign executable. You get the error Permiso denegado (permission denied) when RPM tries to execute that directory. (I'm assuming there's a missing line in your question, where you try to run rpm --addsign again`.)
So, what you need to do is first rmdir /usr/bin/rpmsign, because the directory you created will get in the way of installing the actual RPM. It happens that this is provided by the rpm-sign package. You can find that by running dnf whatprovides /usr/bin/rpmsign — or, you can actually just straight-up tell DNF (or Yum; doesn't matter) to install it:
$ sudo dnf install /usr/bin/rpmsign
Last metadata expiration check: 2:45:11 ago on Wed May 4 08:23:32 2016.
Dependencies resolved.
================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
rpm-sign x86_64 4.13.0-0.rc1.13.fc23 updates 55 k
Transaction Summary
================================================================================
Install 1 Package
Total download size: 55 k
Installed size: 17 k
Is this ok [y/N]: y
Downloading Packages:
rpm-sign-4.13.0-0.rc1.13.fc23.x86_64.rpm 140 kB/s | 55 kB 00:00
--------------------------------------------------------------------------------
Total 44 kB/s | 55 kB 00:01
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Installing : rpm-sign-4.13.0-0.rc1.13.fc23.x86_64 1/1
Verifying : rpm-sign-4.13.0-0.rc1.13.fc23.x86_64 1/1
Installed:
rpm-sign.x86_64 4.13.0-0.rc1.13.fc23
Complete!
I made the attempt at enabling EPEL on my Fedora 22 machine by running
wget http://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-5.noarch.rpm
Then
sudo rpm -ivh epel-release-7-5.noarch.rpm
And now when I run
dnf repolist
I get the following
[sinux1#horrible-host ~]$ sudo dnf repolist
Extra Packages for Enterprise Linux 7 - x86_64 1.8 MB/s | 9.0 MB 00:05
Failed to open: /var/cache/dnf/epel-2b6dfc5904c26562/repodata/49c4e3bd54f19136521be9b254830c954369cc22ce1b661db502ebef13b0004c-updateinfo.xml.bz2.
[sinux1#horrible-host ~]$
I'm stuck and not sure what my next step is. How can I reverse what I did, and what would have been the proper way of enabling EPEL?
Thanks for any input
This is what appears to have worked for me.
Remove the epel repo
rm -rf /etc/yum.repos.d/epel*
then try install epel via dnf
dnf clean all
dnf install epel-release
I did the same as Sinux Tine and ended up in some sort of deadlock.
First try to do like Rup says.
If everything fails, try the following as a last resort. It worked for me.
> su
> cd /var/cache/dnf/epel-2b6dfc5904c26562/repodata
> mkdir throwaway
> mv 49c4e3bd54f19136521be9b254830c954369cc22ce1b661db502ebef13b0004c-updateinfo.xml.bz2 throwaway
That effectively deletes the file which dnf says it cannot open.
When and if the problem is solved, you can delete the throwaway directory and its contents.
Current libsolv version does not have bz2 compression.
Solution: enable bunzip2 compression in libsolv, Basically 'yum update libsolv', then reinstall epel-release.
To complement the answer for Centos 7, I followed the next steps:
Download the libsolv-0.6.14-1.el7 wich was patched
Install it
sudo rpm -ivh libsolv-0.6.14-1.el7.centos.x86_64.rpm
If we get a conflict with the previous version
warning: libsolv-0.6.14-1.el7.centos.x86_64.rpm: Header V3 RSA/SHA1 Signature, key ID 1b6f9f55: NOKEY
Preparing... ################################# [100%]
file /usr/lib64/libsolv.so.0 from install of libsolv-0.6.14-1.el7.centos.x86_64 conflicts with file from package libsolv-0.6.11-1.el7.x86_64
file /usr/lib64/libsolvext.so.0 from install of libsolv-0.6.14-1.el7.centos.x86_64 conflicts with file from package libsolv-0.6.11-1.el7.x86_64
We proceed to remove the previous version
sudo yum erase libsolv-0.6.11-1.el7.x86_64
and install the patched libsolv package
sudo rpm -ivh libsolv-0.6.14-1.el7.centos.x86_64.rpm
We need to reinstall the dnf package manager, because it was removed after to remove the libsolv so we install with the following command.
sudo yum install dnf
We validate it using sudo dnf repolist now it, give us the right output.
Using metadata from Mon Jun 13 10:53:11 2016
repo id repo name status
base CentOS-7 - Base 9,007
I am trying to build mysql rpm, I downloaded the src rpm from mysql (mysl-5.6.26-1.el6.src.rpm) and followed these steps
1. rpm -i MySQL-5.6.26-1.el6.src.rpm
2. cd ~/rpmbuild
3. rpmbuild -v -bb SPECS/mysql.spec
This builds mysql-server-*.rpm, but the binaries and libraries inside the rpm are not stripped. Currently the mysqld and mysqld-debug combined together are more than 100M.
How do I build an rpm with stripped binaries?
Current rpm size
-rw-rw-r--. 1 XXXX XXXXXXX 52M Jul 31 17:43 /home/XXXX/rpmbuild/RPMS/x86_64/MySQL-server-5.6.19-1.linux_glibc.x86_64.rpm
I want to upgrade mariadb from 5.5... to 10. But when I run "yum update -y", screen show like below:
Upgrading directly from MySQL <unrecognized version package MariaDB-server-5.5.36-1.el6.x86_64
MariaDB-server-5.5.36-1.el6.x86_64 is not installed> to MariaDB 10.0 may not
be safe in all cases. A manual dump and restore using mysqldump is
recommended. It is important to review the MariaDB manual's Upgrading
section for version-specific incompatibilities.
A manual upgrade is required.
- Ensure that you have a complete, working backup of your data and my.cnf
files
- Shut down the MySQL server cleanly
- Remove the existing MySQL packages. Usually this command will
list the packages you should remove:
rpm -qa | grep -i '^mysql-'
You may choose to use 'rpm --nodeps -ev <package-name>' to remove
the package which contains the mysqlclient shared library. The
library will be reinstalled by the MariaDB-shared package.
- Install the new MariaDB packages supplied by Monty Program AB
- Ensure that the MariaDB server is started
- Run the 'mysql_upgrade' program
How can I fix this issue?
I fix by myself, I post here for anyone need:
I run,
rpm -qa | grep -i '^maria'
Screen show:
MariaDB-common-10.0.12-1
MariaDB-client-10.0.12-1
MariaDB-server-5.5.38-1
MariaDB-shared-10.0.12-1
My "MariaDB-server" is still 5.5, I stop and remove it (backup all before do change anything):
yum remove MariaDB-server
then install again:
yum install MariaDB-server
screen:
Total size: 56 M
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Installing : MariaDB-server 1/1
Installed:
MariaDB-server.i386 0:10.0.12-1
run again:
rpm -qa | grep -i '^maria'
screen show:
MariaDB-common-10.0.12-1
MariaDB-client-10.0.12-1
MariaDB-server-10.0.12-1
MariaDB-shared-10.0.12-1
It's OK.
I recently found steps on the official MariaDB website for upgrading to the latest stable version.
under /etc/yum.repos.d/ add MariaDB.repo with the following configs:
[mariadb]
name = MariaDB
baseurl = http://yum.mariadb.org/10.2/centos7-amd64
gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
gpgcheck=1
Run sudo yum install MariaDB-server MariaDB-client
Full steps can be found in this tutorial