chmod .. no such user or directory

[Pocketbook]

I'm trying to install mod_auth_mysql on a FreeBSD 6.0, Apache 2.0.55, MySQL 5 setup.

I compiles fine with:

/usr/local/apache/bin/apxs -c -L/usr/local/mysql/lib/mysql -I/usr/local/mysql/include/mysql -lmysqlclient -lm -lz mod_auth_mysql.c

but when i do:

# /usr/local/apache/bin/apxs -i mod_auth_mysql.la                         

I get:

/usr/local/apache/build/instdso.sh SH_LIBTOOL='/usr/local/apache/build/libtool' mod_auth_mysql.la /usr/local/apache/modules
/usr/local/apache/build/libtool --mode=install cp mod_auth_mysql.la /usr/local/apache/modules/
cp .libs/mod_auth_mysql.lai /usr/local/apache/modules/mod_auth_mysql.la
cp .libs/mod_auth_mysql.a /usr/local/apache/modules/mod_auth_mysql.a
ranlib /usr/local/apache/modules/mod_auth_mysql.a
chmod 644 /usr/local/apache/modules/mod_auth_mysql.a
----------------------------------------------------------------------
Libraries have been installed in:
   /usr/local/apache/modules

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
     during execution
   - add LIBDIR to the `LD_RUN_PATH' environment variable
     during linking
   - use the `-Wl,--rpath -Wl,LIBDIR' linker flag

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
Warning!  dlname not found in /usr/local/apache/modules/mod_auth_mysql.la.
Assuming installing a .so rather than a libtool archive.
chmod 755 /usr/local/apache/modules/mod_auth_mysql.so
chmod: /usr/local/apache/modules/mod_auth_mysql.so: No such file or directory
apxs:Error: Command failed with rc=65536

What gives?

[Jerry Stuckle]

This is a problem we've seen occasionally, but haven't been able to nail down.  It could be a problem with a specific version of apxs, libtool, compiler or about anything.

One thing I do know is that apxs has a tendency at times to hide important messages.

My suggestion to start would be to run the apxs command - but then pay attention to the commands it generates.

Then run each of these commands from the command line, in order.  This will let you see the "real" output from each command. 

In the past this procedure has provided error messages which then allowed the user to resolve the problem.