> Am 24.01.2018 um 17:12 schrieb Yann Ylavic <[email protected]>: > > On Wed, Jan 24, 2018 at 4:46 PM, Stefan Eissing > <[email protected]> wrote: >> Had done the buildconf before, added the distclean + buildconf also, same >> result: > > OK, it could have been a remainder of the previous ap_queue* functions > from mpm/event/ which collided, but no.. > >> >> The content of server/.libs/libmain.a is surprising: >> rw-r--r-- 0/0 238176 Jan 1 01:00 1970 config.o >> rw-r--r-- 0/0 179672 Jan 1 01:00 1970 log.o >> rw-r--r-- 0/0 101360 Jan 1 01:00 1970 main.o >> rw-r--r-- 0/0 88232 Jan 1 01:00 1970 vhost.o >> rw-r--r-- 0/0 235112 Jan 1 01:00 1970 util.o >> rw-r--r-- 0/0 41792 Jan 1 01:00 1970 util_fcgi.o >> rw-r--r-- 0/0 104360 Jan 1 01:00 1970 util_script.o >> rw-r--r-- 0/0 16040 Jan 1 01:00 1970 util_md5.o >> .... > > No "mpm_fdqueue.o" there? > >> >> That's no library! How did that happen? > > What do you mean by "no library"? > libmain.[l]a is used for linking statically the httpd binary, no ".so" > expected. > >>> rm server/.libs/libmain.* server/libmain.la >>> make >> >> There again. >:| > > Yes, libmain.la is declared in "server/Makefile.in", and required by > the root "Makefile.in". > Still no idea why it does not work for you :/
Hmm, I have not really crawled down that rabbit hole in our build system. And, honestly, would like to avoid that. Just thought you'd have a clue as there had been the recent move... -Stefan
