On 04/28/2014 03:08 PM, Torsten Förtsch wrote:
On 28/04/14 15:03, Jan Kaluža wrote:
I think we can remove that option
Please do it so.
Done in r1590627. Although r1151822 seems to do similar thing, I think
my way provides cleaner error message and has working MP_NO_THREADS=1
option.
Tor
On 28/04/14 15:03, Jan Kaluža wrote:
> I think we can remove that option
Please do it so.
Torsten
-
To unsubscribe, e-mail: dev-unsubscr...@perl.apache.org
For additional commands, e-mail: dev-h...@perl.apache.org
On 04/28/2014 03:03 PM, Jan Kaluža wrote:
On 04/28/2014 02:57 PM, Torsten Förtsch wrote:
Hi Jan,
On 28/04/14 13:22, Jan Kaluža wrote:
On 04/23/2014 03:04 PM, Torsten Förtsch wrote:
On 23/04/14 13:21, Jan Kaluža wrote:
Thanks for that summary Torsten. As I understand it right now, we
should
b
On 04/28/2014 02:57 PM, Torsten Förtsch wrote:
Hi Jan,
On 28/04/14 13:22, Jan Kaluža wrote:
On 04/23/2014 03:04 PM, Torsten Förtsch wrote:
On 23/04/14 13:21, Jan Kaluža wrote:
Thanks for that summary Torsten. As I understand it right now, we should
build mod_perl with httpd-2.4 with "-Duseith
Hi Jan,
On 28/04/14 13:22, Jan Kaluža wrote:
> On 04/23/2014 03:04 PM, Torsten Förtsch wrote:
>> On 23/04/14 13:21, Jan Kaluža wrote:
>>> Thanks for that summary Torsten. As I understand it right now, we should
>>> build mod_perl with httpd-2.4 with "-Duseithreads -Dusemultiplicity" and
>>> allow
On 04/23/2014 03:04 PM, Torsten Förtsch wrote:
On 23/04/14 13:21, Jan Kaluža wrote:
Thanks for that summary Torsten. As I understand it right now, we should
build mod_perl with httpd-2.4 with "-Duseithreads -Dusemultiplicity" and
allow building with other combination if user explicitly wants it
On Apr 23, 2014, at 7:13 PM, Fred Moyer wrote:
> +1 to this. Looks like most system perls come built with
> ithreads/multiplicity. Perls that I usually build with perlbrew have
> both disabled.
The default configuration for FreeBSD ports shows that multiplicity is off, but
threads are on. I per
On Wed, Apr 23, 2014 at 6:04 AM, Torsten Förtsch
wrote:
> On 23/04/14 13:21, Jan Kaluža wrote:
>> Thanks for that summary Torsten. As I understand it right now, we should
>> build mod_perl with httpd-2.4 with "-Duseithreads -Dusemultiplicity" and
>> allow building with other combination if user ex
On 23/04/14 13:21, Jan Kaluža wrote:
> Thanks for that summary Torsten. As I understand it right now, we should
> build mod_perl with httpd-2.4 with "-Duseithreads -Dusemultiplicity" and
> allow building with other combination if user explicitly wants it (set
> some command line parameter during bu
On 04/18/2014 12:20 PM, Torsten Förtsch wrote:
On 18/04/14 11:50, Jan Kaluza wrote:
Hm, do you know why mod_perl needs to know that during compilation? If
it's really used for something, we will have to remove those
MPM-specific #ifdefs and use normal conditionals instead for httpd-2.4.
Perl c
On 18/04/14 11:50, Jan Kaluza wrote:
> Hm, do you know why mod_perl needs to know that during compilation? If
> it's really used for something, we will have to remove those
> MPM-specific #ifdefs and use normal conditionals instead for httpd-2.4.
Perl can be built in 3 different ways:
1) with glo
On 03/05/2014 08:56 PM, Fred Moyer wrote:
Recent testing on the 2.4 threading branch has uncovered the issue
where the httpd worker type cannot be determined in Apache2::Build for
the reason that MPM_NAME is no longer included in the output of apxs
-q:
fredmoyer@aiko ~/dev $ ./httpd24/bin/apxs -
On 6 March 2014 00:44, Andy Colson wrote:
> On 03/05/2014 01:56 PM, Fred Moyer wrote:
>>
>> Recent testing on the 2.4 threading branch has uncovered the issue
>> where the httpd worker type cannot be determined in Apache2::Build for
>> the reason that MPM_NAME is no longer included in the output o
On 03/05/2014 01:56 PM, Fred Moyer wrote:
Recent testing on the 2.4 threading branch has uncovered the issue
where the httpd worker type cannot be determined in Apache2::Build for
the reason that MPM_NAME is no longer included in the output of apxs
-q:
fredmoyer@aiko ~/dev $ ./httpd24/bin/apxs -
14 matches
Mail list logo
