Bug #17712 Making 5.0.18 from source fails to build server-tools/instance-manager
Submitted: 24 Feb 2006 21:22 Modified: 5 Apr 2006 9:33
Reporter: James Dugal Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.0.18 OS:Solaris (Solaris 8)
Assigned to: CPU Architecture:Any

[24 Feb 2006 21:22] James Dugal
Description:
I get this error making 5.0.18 server from source, under Solaris 8 and Sun's Forte 6.2 compiler
with GNU make:

gmake[3]: *** No rule to make target `../../libmysql/get_password.o', needed by 
`liboptions.a'.  Stop.
gmake[3]: Leaving directory `/space/mysql-5.0.18/server-tools/instance-manager'

I found that get_password.o was actually located in libmysql/.libs/

How to repeat:
LOADDIR="/opt"
STD="-D_FORTEC_ -xO4 -mt -fast -xarch=v8plusa -I/usr/local/include"
CC=cc CFLAGS="-Xa -xstrconst $STD" \
CXX=CC CXXFLAGS="-noex $STD" \
ASFLAGS="-q -xarch=v8plusa" \
LDFLAGS="-L/usr/local/lib -R/usr/local/lib" \
./configure --prefix=$LOADDIR/mysql-5.0.18 --enable-assembler --without-bench \
  --without-berkeley-db  --without-isam \
  --enable-shared --disable-static \
  --enable-thread-safe-client --with-openssl=/usr/local \
  --with-zlib=/usr/local \
  --with-charset=latin1 \
  --enable-local-infile \
  --localstatedir=/var/mysql  > configure.out 2>&1

gmake > make.out

Suggested fix:
diff server-tools/instance-manager/Makefile.am{.orig,}
41c41
< liboptions_a_LIBADD= $(top_builddir)/libmysql/get_password.$(OBJEXT)
---
> liboptions_a_LIBADD= $(top_builddir)/libmysql/.libs/get_password.$(OBJEXT)

Perhaps there is a cleverer way...but once the Makefile was convinced to look in libmysql/.libs I was
able to do a clean make and install.
[2 Apr 2006 11:12] Valeriy Kravchuk
Thank you for a bug report. I am sorry that it hang around for so long time without answer... Please, try to repeat with a newer version of MySQL server, 5.0.19, and inform about the results.
[4 Apr 2006 19:40] James Dugal
It is fixed in 5.0.19.  Thanks!
[5 Apr 2006 9:33] Valeriy Kravchuk
There is no such a bug in 5.0.19.