Thomas Fitzsimmons wrote:
> On Thu, 2006-01-19 at 17:40 -0700, Richard Megginson wrote:
>
>
>> Thomas Fitzsimmons wrote:
>>
>>
>>
>>> On Thu, 2006-01-19 at 17:16 -0700, Richard Megginson wrote:
>>>
>>>
>>>
>>>
>>>> Thomas Fitzsimmons wrote:
>>>>
>>>>
>>>>
>>>>
>>>>> On Thu, 2006-01-19 at 15:56 -0700, Richard Megginson wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> Now you can use the one step build method -
>>>>>>
http://directory.fedora.redhat.com/wiki/Building#One-Step_Build -
>>>>>> to build a debug version of the server, suitable for gdb and the
>>>>>> like. Please try it out and let us know how it works.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> I'm trying this on FC5test1 to see if I can build FDS against
gcj.
>>>>>
>>>>>
>>>>>
>>>>
>>>> Hmm - if you just want to check our java code, you might want to
>>>> just build the Java based components with gcj -
>>>>
http://directory.fedora.redhat.com/wiki/BuildingConsole and the
>>>> like. But I suppose you will want to test the console against the
>>>> server once it is compiled.
>>>>
>>>>
>>>
>>> Yeah, I'd like to compile the whole thing, if possible.
>>>
>>>
>>>
>>>
>>>
>>>>> One
>>>>> nit is the instructions:
>>>>>
>>>>> ...
>>>>> % cd to dsbuild/meta/ds
>>>>> ...
>>>>>
>>>>> should read:
>>>>>
>>>>> ...
>>>>> % cd dsbuild/meta/ds
>>>>> ...
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> Done.
>>>>
>>>>
>>>>
>>>>
>>>>> The next problem is that I can't find apr-config for FC5. All I
>>>>> have is
>>>>> apr-1-config. When I modify ds/mod_nss/Makefile's CONFIGURE_ARGS
to
>>>>> change --with-apr-config to
>>>>> --with-apr-config=/usr/bin/apr-1-config the
>>>>> build fails like this:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> Hmm - what version of Apache does FC5 use? Try
>>>> apr-1-config --version
>>>>
>>>>
>>>
>>> $ apr-1-config --version
>>> 1.2.2
>>>
>>>
>>>
>>>
>>>
>>>> and
>>>> /usr/sbin/httpd.worker -v
>>>>
>>>>
>>>
>>> $ /usr/sbin/httpd.worker -v
>>> Server version: Apache/2.2.0
>>> Server built: Jan 5 2006 06:53:51
>>>
>>>
>>>
>>
>> Ah. It looks as though there will be some porting work - darn - why
>> the heck did they have to change the include files used for modules
>> from Apache 2.0 to Apache 2.2 :-(
>>
>
>
> Joe Orton (CCed) may know; Joe is there some compatibility package I can
> install to work around 2.0 -> 2.2 header differences?
>
>
Or better yet - is there a way we can change our module code so that it
compiles with Apache 2.0 and 2.2?
The mod_nss tip does compile against either version. It hasn't been
heavily tested against 2.2 but I had no problems in my limited testing.
rob