Re: Broken trunk build
On Oct 30, 2008, at 7:08 PM, William A. Rowe, Jr. wrote: Jim Jagielski wrote: Still semi-broken if trying the simple MPM due to both mod_unixd and unixd being built: I presume this isn't about simple mpm - that mod_unixd is going to be modularized for all unix mpm's? Yeppers... that was what I didn't understand at first.
Re: Broken trunk build
William A. Rowe, Jr. wrote: Jim Jagielski wrote: Still semi-broken if trying the simple MPM due to both mod_unixd and unixd being built: I presume this isn't about simple mpm - that mod_unixd is going to be modularized for all unix mpm's? That's the idea, yes. Plus a decision over whether everything goes into the module, or some stuff remains in the old unixd. Just about to look at Paul's update to that. Simple MPM was just a good cue to actually do something. When simple told me the "User" directive in httpd.conf was unrecognised -- Nick Kew
Re: Broken trunk build
Jim Jagielski wrote: > > Still semi-broken if trying the simple MPM due to both mod_unixd and unixd > being built: I presume this isn't about simple mpm - that mod_unixd is going to be modularized for all unix mpm's?
Re: Broken trunk build
On Oct 30, 2008, at 4:19 PM, Paul Querna wrote: Jim Jagielski wrote: On Oct 30, 2008, at 3:00 PM, Tim Bray wrote: On Oct 29, 2008, at 6:21 AM, Nick Kew wrote: When svn up breaks a source file, at least you get a meaningful error message pointing to exactly what needs fixing. This m4 is nasty! If /usr/bin/m4 were by arbitrary fiat deleted from all unix-like systems world-wide, there would be considerable temporary breakage, but the world would on balance be a better place thereafter. -Tim Still semi-broken if trying the simple MPM due to both mod_unixd and unixd being built: ld: duplicate symbol _unixd_set_user in os/unix/.libs/ libos.a(unixd.o) and modules/arch/unix/.libs/ libmod_unixd.a(mod_unixd.o) collect2: ld returned 1 exit status Plus, we need to get a mod_unixd.h file which exports those functions... currently have a *nasty* cruft just to get the bugger compiled to play around with it :) no, mod_unixd should not need to export any functions like current unixd does Hmmm... must have misunderstood the intent of the module... Looking into it, and rereading Nick's email, I got it now. I'll rename them so there aren't any symbol conflicts, but they should all be static anyways inside mod_unixd.c. +1
Re: Broken trunk build
Jim Jagielski wrote: On Oct 30, 2008, at 3:00 PM, Tim Bray wrote: On Oct 29, 2008, at 6:21 AM, Nick Kew wrote: When svn up breaks a source file, at least you get a meaningful error message pointing to exactly what needs fixing. This m4 is nasty! If /usr/bin/m4 were by arbitrary fiat deleted from all unix-like systems world-wide, there would be considerable temporary breakage, but the world would on balance be a better place thereafter. -Tim Still semi-broken if trying the simple MPM due to both mod_unixd and unixd being built: ld: duplicate symbol _unixd_set_user in os/unix/.libs/libos.a(unixd.o) and modules/arch/unix/.libs/libmod_unixd.a(mod_unixd.o) collect2: ld returned 1 exit status Plus, we need to get a mod_unixd.h file which exports those functions... currently have a *nasty* cruft just to get the bugger compiled to play around with it :) no, mod_unixd should not need to export any functions like current unixd does I'll rename them so there aren't any symbol conflicts, but they should all be static anyways inside mod_unixd.c. -Paul
Re: Broken trunk build
Tim Bray wrote: On Oct 29, 2008, at 6:21 AM, Nick Kew wrote: When svn up breaks a source file, at least you get a meaningful error message pointing to exactly what needs fixing. This m4 is nasty! If /usr/bin/m4 were by arbitrary fiat deleted from all unix-like systems world-wide, there would be considerable temporary breakage, but the world would on balance be a better place thereafter. -Tim scons. -Paul
Re: Broken trunk build
On Oct 30, 2008, at 3:00 PM, Tim Bray wrote: On Oct 29, 2008, at 6:21 AM, Nick Kew wrote: When svn up breaks a source file, at least you get a meaningful error message pointing to exactly what needs fixing. This m4 is nasty! If /usr/bin/m4 were by arbitrary fiat deleted from all unix-like systems world-wide, there would be considerable temporary breakage, but the world would on balance be a better place thereafter. -Tim Still semi-broken if trying the simple MPM due to both mod_unixd and unixd being built: ld: duplicate symbol _unixd_set_user in os/unix/.libs/libos.a(unixd.o) and modules/arch/unix/.libs/libmod_unixd.a(mod_unixd.o) collect2: ld returned 1 exit status Plus, we need to get a mod_unixd.h file which exports those functions... currently have a *nasty* cruft just to get the bugger compiled to play around with it :)
Re: Broken trunk build
On Oct 29, 2008, at 6:21 AM, Nick Kew wrote: When svn up breaks a source file, at least you get a meaningful error message pointing to exactly what needs fixing. This m4 is nasty! If /usr/bin/m4 were by arbitrary fiat deleted from all unix-like systems world-wide, there would be considerable temporary breakage, but the world would on balance be a better place thereafter. -Tim
Re: Broken trunk build
Nick Kew wrote: > Plüm, Rüdiger, VF-Group wrote: > [SNIP] ... > This m4 is nasty! +1 on that
Re: Broken trunk build
Plüm, Rüdiger, VF-Group wrote: Any clues for hunting down the cause of this? Hm. I cannot reproduce this. Did you issue a 'make extraclean' before? Well, I wasnt looking for you to reproduce it; rather for hints on chasing it down. But thanks for trying. Anyway, I´ve got it, and it was local to me. I had a modified server/mpm/config.m4 which I´d used for my own MPM. ¨svn up¨ with Paul´s changes broke it. When svn up breaks a source file, at least you get a meaningful error message pointing to exactly what needs fixing. This m4 is nasty! -- Nick Kew
Re: Broken trunk build
> -Ursprüngliche Nachricht- > Von: [EMAIL PROTECTED] > Auftrag von Nick Kew > Gesendet: Mittwoch, 29. Oktober 2008 12:18 > An: dev@httpd.apache.org > Betreff: Broken trunk build > > I've just tried a clean trunk build, to play with Paul's simple MPM. > Unfortunately buildconf fails around autoheader and autoconf: > > > rebuilding include/ap_config_auto.h.in > > NONE:0: m4: ERROR: EOF in string > > autom4te: m4 failed with exit status: 1 > > autoheader: autom4te failed with exit status: 1 > > rebuilding configure > > NONE:0: m4: ERROR: EOF in string > > autom4te: m4 failed with exit status: 1 > > A bit of googling suggests the culprit may be unbalanced > brackets or quotes somewhere in the M4, but I'm struggling > to find out where to look. > > Any clues for hunting down the cause of this? Hm. I cannot reproduce this. Did you issue a 'make extraclean' before? Regards Rüdiger
Broken trunk build
I've just tried a clean trunk build, to play with Paul's simple MPM. Unfortunately buildconf fails around autoheader and autoconf: rebuilding include/ap_config_auto.h.in NONE:0: m4: ERROR: EOF in string autom4te: m4 failed with exit status: 1 autoheader: autom4te failed with exit status: 1 rebuilding configure NONE:0: m4: ERROR: EOF in string autom4te: m4 failed with exit status: 1 A bit of googling suggests the culprit may be unbalanced brackets or quotes somewhere in the M4, but I'm struggling to find out where to look. Any clues for hunting down the cause of this? -- Nick Kew
