Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 37866 - compile of sys-libs/pam_mysql-0.5 failed
Summary: compile of sys-libs/pam_mysql-0.5 failed
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: PAM Gentoo Team (OBSOLETE)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-11 01:10 UTC by Daniel Harik
Modified: 2004-01-12 00:44 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Harik 2004-01-11 01:10:17 UTC
emerge pam_mysql
Calculating dependencies ...done!
>>> emerge (1 of 1) sys-libs/pam_mysql-0.5 to /
>>> md5 src_uri ;-) pam_mysql-0.5.tar.gz
>>> Unpacking source...
>>> Unpacking pam_mysql-0.5.tar.gz to /var/tmp/portage/pam_mysql-0.5/work
>>> Source unpacked.
mkdir -p ./dynamic
gcc -O3 -mcpu=i686 -funroll-loops -pipe -Dlinux -DLINUX_PAM -ansi -D_POSIX_SOURC E -Wall -Wwrite-strings -Wpointer-arith -Wcast-qual -Wcast-align -Wtraditional - Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Winline -Wshadow -peda ntic -fPIC -DPAM_DYNAMIC  -c pam_mysql.c -o dynamic/pam_mysql.o
gcc -shared -Xlinker -x -L/usr/lib/mysql -lz -o pam_mysql.so dynamic/pam_mysql.o  -lmysqlclient -lcrypt
/usr/lib/gcc-lib/i486-pc-linux-gnu/3.2.3/../../../../i486-pc-linux-gnu/bin/ld: cannot find -lmysqlclient
collect2: ld returned 1 exit status
make: *** [pam_mysql.so] Error 1
 
!!! ERROR: sys-libs/pam_mysql-0.5 failed.
!!! Function src_compile, Line 29, Exitcode 2
!!! (no error message)


emerge info
Portage 2.0.49-r4 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 2.6.1)
=================================================================
System uname: 2.6.1 i686 Celeron (Mendocino)
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O3 -mcpu=i686 -funroll-loops -pipe"
CHOST="i486-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/config /usr/kde/3/share/config /var/bind"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-O3 -mcpu=i686 -funroll-loops -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="sandbox ccache autoaddcvs"
GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 oss apm arts avi crypt cups encode foomaticdb gif gtk gtk2 imlib jpeg kde gnome libg++ libwww mad mikmod motif mpeg ncurses nls oggvorbis opengl pdflib png qt quicktime sdl slang spell svga truetype X xml2 xmms xv zlib gdbm berkdb readline java mysql gpm tcpd pam ssl perl python"
 


Reproducible: Always
Steps to Reproduce:
Comment 1 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2004-01-11 03:06:39 UTC
it seems you don't have mysql installed. please upgrade your portage, and then repeat this, if it still fails, emerge mysql then try yet again.
Comment 2 Daniel Harik 2004-01-11 06:11:32 UTC
I havent used portage to install mysql, i've tryind doing make manually, still i'm getting this error, though mysql  is installed  default location.
Comment 3 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2004-01-11 13:56:57 UTC
it won't work with mysql's upstream default location, as pam_mysql expects that you are using the instance of mysql in the portage tree so that it knows where everything it needs is.

why haven't you used the copy of mysql in the portage tree, any specific shortcomings it has that you need?
Comment 4 Daniel Harik 2004-01-11 23:02:24 UTC
just too many mysql releases by gentoo guys :)
dont feal like recompiling it 10 times per release on production server :(
no offense, same with postfix, everytime i remerge new postfix my config is messed up
Comment 5 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2004-01-12 00:44:32 UTC
just because there is a new version available, doesn't mean you have to upgrade it.

i've got boxes still running mysql-4.0.11 because they are production and there has been no suitable time to take them offline long enough for that upgrade yet.

mysql has very few revisions by us compared to some other packages, it really won't hurt you to use it, and as for the config stuff, just don't overwrite your config when you do etc-update.

if you wish to persist in using a custom mysql, play with the pam_mysql ebuild yourself, you need to add the library path for mysqlclient into it, as "-L...."