You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Nick Edwards <ni...@gmail.com> on 2012/01/17 01:25:37 UTC
[users@httpd] 2.4.0 fails
Hello,
I was not sure if I should subscribe to dev list to send this, but, I
guess here is better?
Trying out 2.4.0 from 2.2.21
Well, the config file from 2.2.21 is not going to work, fine, I'll
deal with that in time, obviously things that were defaulted to under
some IFs are no longer so a full rewrite of config is going to be
needed, I mean User/Group clearly are options but apparently not for
me LOL.. but anyway the more pressing thing is the build...
I liked the earlier method where when using:
--enable-so --enable-modules=all --disable-dav --enable-suexec ..snip..
Would statically build my modules leaving only httpd.exp libphp5.so
(yes, from php) in modules/ just like in 2.2.x, but not so, I'm left
with 100 .so's in modules/
and 100 loadmodule options in config file to scratch my head at what
ones I need to return too to get back to the old behaviour
then I found new option --enable-mods-static which I assumed would
revert back to how it used to be, but alas build now fails:
modules/dav/lock/.libs/libmod_dav_lock.a(locks.o): In function
`dav_generic_dbm_new_error':
/usr/local/src/httpd-2.4.0/modules/dav/lock/locks.c:226: undefined
reference to `dav_new_error'
modules/dav/lock/.libs/libmod_dav_lock.a(locks.o): In function
`dav_generic_really_open_lockdb':
/usr/local/src/httpd-2.4.0/modules/dav/lock/locks.c:328: undefined
reference to `dav_push_error'
modules/dav/lock/.libs/libmod_dav_lock.a(locks.o): In function
`dav_generic_save_lock_record':
/usr/local/src/httpd-2.4.0/modules/dav/lock/locks.c:447: undefined
reference to `dav_new_error'
/usr/local/src/httpd-2.4.0/modules/dav/lock/locks.c:531: undefined
reference to `dav_push_error'
modules/dav/lock/.libs/libmod_dav_lock.a(locks.o): In function
`dav_generic_load_lock_record':
/usr/local/src/httpd-2.4.0/modules/dav/lock/locks.c:664: undefined
reference to `dav_new_error'
modules/dav/lock/.libs/libmod_dav_lock.a(locks.o): In function
`dav_generic_resolve':
/usr/local/src/httpd-2.4.0/modules/dav/lock/locks.c:721: undefined
reference to `dav_new_error'
modules/dav/lock/.libs/libmod_dav_lock.a(locks.o): In function
`dav_generic_get_locks':
/usr/local/src/httpd-2.4.0/modules/dav/lock/locks.c:798: undefined
reference to `dav_new_error'
modules/dav/lock/.libs/libmod_dav_lock.a(locks.o): In function
`dav_generic_open_lockdb':
/usr/local/src/httpd-2.4.0/modules/dav/lock/locks.c:363: undefined
reference to `dav_new_error'
modules/dav/lock/.libs/libmod_dav_lock.a(locks.o): In function
`dav_generic_parse_locktoken':
/usr/local/src/httpd-2.4.0/modules/dav/lock/locks.c:264: undefined
reference to `dav_new_error'
modules/dav/lock/.libs/libmod_dav_lock.a(locks.o):/usr/local/src/httpd-2.4.0/modules/dav/lock/locks.c:273:
more undefined references to `dav_new_error' follow
collect2: ld returned 1 exit status
make[1]: *** [httpd] Error 1
make[1]: Leaving directory `/usr/local/src/httpd-2.4.0'
make: *** [all-recursive] Error 1
any suggestions?
I must also say, that 2.4.0 documentation leaves a lot to be desired
for those upgrading, like no mention we also now need to separately
get the -deps file as well.
the CHANGES file does not include any stand out gotyas either for
those using major upgrades, from 2.2 to 2.4, and that's going to be a
lot.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] 2.4.0 fails
Posted by Rainer Jung <ra...@kippdata.de>.
On 17.01.2012 01:25, Nick Edwards wrote:
> Hello,
>
> I was not sure if I should subscribe to dev list to send this, but, I
> guess here is better?
> Trying out 2.4.0 from 2.2.21
>
> Well, the config file from 2.2.21 is not going to work, fine, I'll
> deal with that in time, obviously things that were defaulted to under
> some IFs are no longer so a full rewrite of config is going to be
> needed, I mean User/Group clearly are options but apparently not for
> me LOL.. but anyway the more pressing thing is the build...
>
> I liked the earlier method where when using:
>
> --enable-so --enable-modules=all --disable-dav --enable-suexec ..snip..
> Would statically build my modules leaving only httpd.exp libphp5.so
> (yes, from php) in modules/ just like in 2.2.x, but not so, I'm left
> with 100 .so's in modules/
> and 100 loadmodule options in config file to scratch my head at what
> ones I need to return too to get back to the old behaviour
>
> then I found new option --enable-mods-static which I assumed would
> revert back to how it used to be, but alas build now fails:
Which should work. Can you please post your complete configure line? Not
sure how you merged your first attempt with the static switch.
Regards,
Rainer
> modules/dav/lock/.libs/libmod_dav_lock.a(locks.o): In function
> `dav_generic_dbm_new_error':
> /usr/local/src/httpd-2.4.0/modules/dav/lock/locks.c:226: undefined
> reference to `dav_new_error'
> modules/dav/lock/.libs/libmod_dav_lock.a(locks.o): In function
> `dav_generic_really_open_lockdb':
> /usr/local/src/httpd-2.4.0/modules/dav/lock/locks.c:328: undefined
> reference to `dav_push_error'
> modules/dav/lock/.libs/libmod_dav_lock.a(locks.o): In function
> `dav_generic_save_lock_record':
> /usr/local/src/httpd-2.4.0/modules/dav/lock/locks.c:447: undefined
> reference to `dav_new_error'
> /usr/local/src/httpd-2.4.0/modules/dav/lock/locks.c:531: undefined
> reference to `dav_push_error'
> modules/dav/lock/.libs/libmod_dav_lock.a(locks.o): In function
> `dav_generic_load_lock_record':
> /usr/local/src/httpd-2.4.0/modules/dav/lock/locks.c:664: undefined
> reference to `dav_new_error'
> modules/dav/lock/.libs/libmod_dav_lock.a(locks.o): In function
> `dav_generic_resolve':
> /usr/local/src/httpd-2.4.0/modules/dav/lock/locks.c:721: undefined
> reference to `dav_new_error'
> modules/dav/lock/.libs/libmod_dav_lock.a(locks.o): In function
> `dav_generic_get_locks':
> /usr/local/src/httpd-2.4.0/modules/dav/lock/locks.c:798: undefined
> reference to `dav_new_error'
> modules/dav/lock/.libs/libmod_dav_lock.a(locks.o): In function
> `dav_generic_open_lockdb':
> /usr/local/src/httpd-2.4.0/modules/dav/lock/locks.c:363: undefined
> reference to `dav_new_error'
> modules/dav/lock/.libs/libmod_dav_lock.a(locks.o): In function
> `dav_generic_parse_locktoken':
> /usr/local/src/httpd-2.4.0/modules/dav/lock/locks.c:264: undefined
> reference to `dav_new_error'
> modules/dav/lock/.libs/libmod_dav_lock.a(locks.o):/usr/local/src/httpd-2.4.0/modules/dav/lock/locks.c:273:
> more undefined references to `dav_new_error' follow
> collect2: ld returned 1 exit status
> make[1]: *** [httpd] Error 1
> make[1]: Leaving directory `/usr/local/src/httpd-2.4.0'
> make: *** [all-recursive] Error 1
>
>
> any suggestions?
>
>
> I must also say, that 2.4.0 documentation leaves a lot to be desired
> for those upgrading, like no mention we also now need to separately
> get the -deps file as well.
>
> the CHANGES file does not include any stand out gotyas either for
> those using major upgrades, from 2.2 to 2.4, and that's going to be a
> lot.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org