You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Pedro Giffuni <pf...@apache.org> on 2012/02/24 18:53:16 UTC
Build broken on FreeBSD.
Hi;
Just FYI
______
...
... analyzing files ...
ERROR: The following files could not be found:
ERROR: File not found: libapr-1.so.0.4.5
ERROR: File not found: libaprutil-1.so.0.4.1
ERROR: File not found: libserf-1.so.0.0.0
... cleaning the output tree ...
... removing directory /tmp/ooopackaging/i_713701330104152 ...
...
___________
The naming scheme is completely inappropriate for FreeBSD:
ls /usr/local/lib/libapr*
/usr/local/lib/libapr-1.a /usr/local/lib/libaprutil-1.a
/usr/local/lib/libapr-1.la /usr/local/lib/libaprutil-1.la
/usr/local/lib/libapr-1.so /usr/local/lib/libaprutil-1.so
/usr/local/lib/libapr-1.so.4 /usr/local/lib/libaprutil-1.so.3
cheers,
Pedro.
Re: Build broken on FreeBSD.
Posted by Pedro Giffuni <pf...@apache.org>.
On 02/26/12 22:18, Maho NAKATA wrote:
> From: Pedro Giffuni<pf...@apache.org>
> Subject: Re: Build broken on FreeBSD.
> Date: Sun, 26 Feb 2012 21:16:41 -0500
>
>> I think I prefer the first option: the sysv/linux versioning doesn't
>> really fit for FreeBSD and I expect we will be using the
>> prepackaged version of apr and serf as soon as that option is
>> available.
>>
>> Patching ltmain.sh is something we can probably manage for
>> coinmp but if we have to do the same for apr, serf, and whatever
>> new library IBM or someone else brings in the future I don't think
>> that will scale well.
> No, both doesn't scale, and I prefer patching ltmain.sh.
> In the former solution, we have to patch files in scp2
> almost everywhere and introduce additioan IF DEF for each shared lib.
> We also patch prj/d.lst as well. This is much more tedious than expected.
>
> I understand Linux style versioning won't fit for FreeBSD,
> but if you don't like it, just use external libs.
Yes, that's the plan indeed.
Pedro.
Re: Build broken on FreeBSD.
Posted by Maho NAKATA <ch...@mac.com>.
From: Pedro Giffuni <pf...@apache.org>
Subject: Re: Build broken on FreeBSD.
Date: Sun, 26 Feb 2012 21:16:41 -0500
> I think I prefer the first option: the sysv/linux versioning doesn't
> really fit for FreeBSD and I expect we will be using the
> prepackaged version of apr and serf as soon as that option is
> available.
>
> Patching ltmain.sh is something we can probably manage for
> coinmp but if we have to do the same for apr, serf, and whatever
> new library IBM or someone else brings in the future I don't think
> that will scale well.
No, both doesn't scale, and I prefer patching ltmain.sh.
In the former solution, we have to patch files in scp2
almost everywhere and introduce additioan IF DEF for each shared lib.
We also patch prj/d.lst as well. This is much more tedious than expected.
I understand Linux style versioning won't fit for FreeBSD,
but if you don't like it, just use external libs.
Thanks
-- Nakata Maho http://accc.riken.jp/maho/ , JA OOO http://ja.openoffice.org/
http://blog.goo.ne.jp/nakatamaho/ ,GPG: http://accc.riken.jp/maho/maho.pgp.txt
Re: Build broken on FreeBSD.
Posted by Pedro Giffuni <pf...@apache.org>.
Maho-san!
Sorry that I haven't been working on OpenOffice at all
lately.
--- Mar 28/2/12, Maho NAKATA <ma...@apache.org> ha scritto:
...
> Hi Pedro,
>
> I have just committed a fix.
> http://www.freebsd.org/cgi/cvsweb.cgi/ports/editors/openoffice-3-devel/files/patch-apr
> http://www.freebsd.org/cgi/cvsweb.cgi/ports/editors/openoffice-3-devel/files/patch-aprutil
> http://www.freebsd.org/cgi/cvsweb.cgi/ports/editors/openoffice-3-devel/files/patch-scp2
> http://www.freebsd.org/cgi/cvsweb.cgi/ports/editors/openoffice-3-devel/files/patch-serf
>
This looks very good, you didn't end up editing ltmain.sh
and it doesn't affect linux at all.
Pedro.
Re: Build broken on FreeBSD.
Posted by Maho NAKATA <ma...@apache.org>.
Hi Pedro,
I have just committed a fix.
http://www.freebsd.org/cgi/cvsweb.cgi/ports/editors/openoffice-3-devel/files/patch-apr
http://www.freebsd.org/cgi/cvsweb.cgi/ports/editors/openoffice-3-devel/files/patch-aprutil
http://www.freebsd.org/cgi/cvsweb.cgi/ports/editors/openoffice-3-devel/files/patch-scp2
http://www.freebsd.org/cgi/cvsweb.cgi/ports/editors/openoffice-3-devel/files/patch-serf
In your case, somehow your build system picked up system apr aprutil and serf,
then build proceeded, finally build was broken.
* to deliver to solver correctly we must modify prj/d.lst in apr, aprutil and serf.
* to make installation set, we must add in scp2.
thanks
Nakata Maho
From: Pedro Giffuni <pf...@apache.org>
Subject: Re: Build broken on FreeBSD.
Date: Sun, 26 Feb 2012 21:16:41 -0500
> Hello Maho;
>
>
> On 02/26/12 20:24, Maho NAKATA wrote:
>> Hi Pedro,
>>
>> From: Pedro Giffuni<pf...@apache.org>
>> Subject: Re: Build broken on FreeBSD.
>> Date: Sat, 25 Feb 2012 17:37:49 -0500
>>
>>> Hi Maho;
>>>
>>> On 02/25/12 16:35, Maho NAKATA wrote:
>>>> Hi Pedro
>>>>
>>>>> The naming scheme is completely inappropriate for FreeBSD:
>>>> I think this is right, but again, this is libtool (version numbering
>>>> scheme difference between Linux and FreeBSD). Patching agianist
>>>> ltmain.sh would solve that type of problem.
>>> I haven't had time to investigate it but I think the problem lies in
>>> those version.mk files. OpenOffice simply imposes ignores libedit
>>> and the native build system and tries to impose the linux
>>> numbering everywhere.
>> yes. in scp2 project we speficy the version number for shared lib.
>>
>> quoting from scp2/source/ooo/file_library_ooo.scp for example as
>> follows:
>>
>> File gid_File_Lib_Serf
>> #ifdef WNT
>> Name = SPECIAL_NAME(serf);
>> #else
>> // Looks like the major version number is part of the name, not
>> // part of the suffix. An error?
>> #ifdef MACOSX
>> Name =
>> STRING(CONCAT6(libserf-1,.0.,SERF_MINOR,.,SERF_MICRO,UNXSUFFIX));
>> #else
>> Name =
>> STRING(CONCAT6(libserf-1,UNXSUFFIX,.0.,SERF_MINOR,.,SERF_MICRO));
>> #endif
>> #endif
>> PACKED_LIB_FILE_BODY;
>> End
>> . There are a lot of such kind of things. So we must compromise.
>> if we change version number in scp2, we have to take care of all
>> stuffs.
>> if we change version number in each internal library, we usually have
>> to
>> patch ltmail.sh
> Nice find, thank you.
>
> I think I prefer the first option: the sysv/linux versioning doesn't
> really fit for FreeBSD and I expect we will be using the
> prepackaged version of apr and serf as soon as that option is
> available.
>
> Patching ltmain.sh is something we can probably manage for
> coinmp but if we have to do the same for apr, serf, and whatever
> new library IBM or someone else brings in the future I don't think
> that will scale well.
>
> Pedro.
>
>>>> Could you please tell me which svn revision and configure line...
>>> I am using your port but with Revision 1293349, but any post-neon
>>> replacement should exhibit the same error.
>>>
>>> Pedro.
>>>
>>>> From: Pedro Giffuni<pf...@apache.org>
>>>> Subject: Build broken on FreeBSD.
>>>> Date: Fri, 24 Feb 2012 12:53:16 -0500
>>>>
>>>>> Hi;
>>>>>
>>>>> Just FYI
>>>>> ______
>>>>> ...
>>>>> ... analyzing files ...
>>>>> ERROR: The following files could not be found:
>>>>> ERROR: File not found: libapr-1.so.0.4.5
>>>>> ERROR: File not found: libaprutil-1.so.0.4.1
>>>>> ERROR: File not found: libserf-1.so.0.0.0
>>>>> ... cleaning the output tree ...
>>>>> ... removing directory /tmp/ooopackaging/i_713701330104152 ...
>>>>> ...
>>>>> ___________
>>>>>
>>>>> The naming scheme is completely inappropriate for FreeBSD:
>>>>>
>>>>> ls /usr/local/lib/libapr*
>>>>> /usr/local/lib/libapr-1.a /usr/local/lib/libaprutil-1.a
>>>>> /usr/local/lib/libapr-1.la /usr/local/lib/libaprutil-1.la
>>>>> /usr/local/lib/libapr-1.so /usr/local/lib/libaprutil-1.so
>>>>> /usr/local/lib/libapr-1.so.4 /usr/local/lib/libaprutil-1.so.3
>>>>>
>>>>> cheers,
>>>>>
>>>>> Pedro.
>>>>>
>
Re: Build broken on FreeBSD.
Posted by Pedro Giffuni <pf...@apache.org>.
Hello Maho;
On 02/26/12 20:24, Maho NAKATA wrote:
> Hi Pedro,
>
> From: Pedro Giffuni<pf...@apache.org>
> Subject: Re: Build broken on FreeBSD.
> Date: Sat, 25 Feb 2012 17:37:49 -0500
>
>> Hi Maho;
>>
>> On 02/25/12 16:35, Maho NAKATA wrote:
>>> Hi Pedro
>>>
>>>> The naming scheme is completely inappropriate for FreeBSD:
>>> I think this is right, but again, this is libtool (version numbering
>>> scheme difference between Linux and FreeBSD). Patching agianist
>>> ltmain.sh would solve that type of problem.
>> I haven't had time to investigate it but I think the problem lies in
>> those version.mk files. OpenOffice simply imposes ignores libedit
>> and the native build system and tries to impose the linux
>> numbering everywhere.
> yes. in scp2 project we speficy the version number for shared lib.
>
> quoting from scp2/source/ooo/file_library_ooo.scp for example as follows:
>
> File gid_File_Lib_Serf
> #ifdef WNT
> Name = SPECIAL_NAME(serf);
> #else
> // Looks like the major version number is part of the name, not
> // part of the suffix. An error?
> #ifdef MACOSX
> Name = STRING(CONCAT6(libserf-1,.0.,SERF_MINOR,.,SERF_MICRO,UNXSUFFIX));
> #else
> Name = STRING(CONCAT6(libserf-1,UNXSUFFIX,.0.,SERF_MINOR,.,SERF_MICRO));
> #endif
> #endif
> PACKED_LIB_FILE_BODY;
> End
> . There are a lot of such kind of things. So we must compromise.
> if we change version number in scp2, we have to take care of all stuffs.
> if we change version number in each internal library, we usually have to
> patch ltmail.sh
Nice find, thank you.
I think I prefer the first option: the sysv/linux versioning doesn't
really fit for FreeBSD and I expect we will be using the
prepackaged version of apr and serf as soon as that option is
available.
Patching ltmain.sh is something we can probably manage for
coinmp but if we have to do the same for apr, serf, and whatever
new library IBM or someone else brings in the future I don't think
that will scale well.
Pedro.
>>> Could you please tell me which svn revision and configure line...
>> I am using your port but with Revision 1293349, but any post-neon
>> replacement should exhibit the same error.
>>
>> Pedro.
>>
>>> From: Pedro Giffuni<pf...@apache.org>
>>> Subject: Build broken on FreeBSD.
>>> Date: Fri, 24 Feb 2012 12:53:16 -0500
>>>
>>>> Hi;
>>>>
>>>> Just FYI
>>>> ______
>>>> ...
>>>> ... analyzing files ...
>>>> ERROR: The following files could not be found:
>>>> ERROR: File not found: libapr-1.so.0.4.5
>>>> ERROR: File not found: libaprutil-1.so.0.4.1
>>>> ERROR: File not found: libserf-1.so.0.0.0
>>>> ... cleaning the output tree ...
>>>> ... removing directory /tmp/ooopackaging/i_713701330104152 ...
>>>> ...
>>>> ___________
>>>>
>>>> The naming scheme is completely inappropriate for FreeBSD:
>>>>
>>>> ls /usr/local/lib/libapr*
>>>> /usr/local/lib/libapr-1.a /usr/local/lib/libaprutil-1.a
>>>> /usr/local/lib/libapr-1.la /usr/local/lib/libaprutil-1.la
>>>> /usr/local/lib/libapr-1.so /usr/local/lib/libaprutil-1.so
>>>> /usr/local/lib/libapr-1.so.4 /usr/local/lib/libaprutil-1.so.3
>>>>
>>>> cheers,
>>>>
>>>> Pedro.
>>>>
Re: Build broken on FreeBSD.
Posted by Maho NAKATA <ch...@mac.com>.
Hi Pedro,
From: Pedro Giffuni <pf...@apache.org>
Subject: Re: Build broken on FreeBSD.
Date: Sat, 25 Feb 2012 17:37:49 -0500
> Hi Maho;
>
> On 02/25/12 16:35, Maho NAKATA wrote:
>> Hi Pedro
>>
>>> The naming scheme is completely inappropriate for FreeBSD:
>> I think this is right, but again, this is libtool (version numbering
>> scheme difference between Linux and FreeBSD). Patching agianist
>> ltmain.sh would solve that type of problem.
>
> I haven't had time to investigate it but I think the problem lies in
> those version.mk files. OpenOffice simply imposes ignores libedit
> and the native build system and tries to impose the linux
> numbering everywhere.
yes. in scp2 project we speficy the version number for shared lib.
quoting from scp2/source/ooo/file_library_ooo.scp for example as follows:
File gid_File_Lib_Serf
#ifdef WNT
Name = SPECIAL_NAME(serf);
#else
// Looks like the major version number is part of the name, not
// part of the suffix. An error?
#ifdef MACOSX
Name = STRING(CONCAT6(libserf-1,.0.,SERF_MINOR,.,SERF_MICRO,UNXSUFFIX));
#else
Name = STRING(CONCAT6(libserf-1,UNXSUFFIX,.0.,SERF_MINOR,.,SERF_MICRO));
#endif
#endif
PACKED_LIB_FILE_BODY;
End
. There are a lot of such kind of things. So we must compromise.
if we change version number in scp2, we have to take care of all stuffs.
if we change version number in each internal library, we usually have to
patch ltmail.sh
>> Could you please tell me which svn revision and configure line...
>
> I am using your port but with Revision 1293349, but any post-neon
> replacement should exhibit the same error.
>
> Pedro.
>
>>
>> From: Pedro Giffuni<pf...@apache.org>
>> Subject: Build broken on FreeBSD.
>> Date: Fri, 24 Feb 2012 12:53:16 -0500
>>
>>> Hi;
>>>
>>> Just FYI
>>> ______
>>> ...
>>> ... analyzing files ...
>>> ERROR: The following files could not be found:
>>> ERROR: File not found: libapr-1.so.0.4.5
>>> ERROR: File not found: libaprutil-1.so.0.4.1
>>> ERROR: File not found: libserf-1.so.0.0.0
>>> ... cleaning the output tree ...
>>> ... removing directory /tmp/ooopackaging/i_713701330104152 ...
>>> ...
>>> ___________
>>>
>>> The naming scheme is completely inappropriate for FreeBSD:
>>>
>>> ls /usr/local/lib/libapr*
>>> /usr/local/lib/libapr-1.a /usr/local/lib/libaprutil-1.a
>>> /usr/local/lib/libapr-1.la /usr/local/lib/libaprutil-1.la
>>> /usr/local/lib/libapr-1.so /usr/local/lib/libaprutil-1.so
>>> /usr/local/lib/libapr-1.so.4 /usr/local/lib/libaprutil-1.so.3
>>>
>>> cheers,
>>>
>>> Pedro.
>>>
>
Re: Build broken on FreeBSD.
Posted by Pedro Giffuni <pf...@apache.org>.
Hi Maho;
On 02/25/12 16:35, Maho NAKATA wrote:
> Hi Pedro
>
>> The naming scheme is completely inappropriate for FreeBSD:
> I think this is right, but again, this is libtool (version numbering
> scheme difference between Linux and FreeBSD). Patching agianist
> ltmain.sh would solve that type of problem.
I haven't had time to investigate it but I think the problem lies in
those version.mk files. OpenOffice simply imposes ignores libedit
and the native build system and tries to impose the linux
numbering everywhere.
> Could you please tell me which svn revision and configure line...
I am using your port but with Revision 1293349, but any post-neon
replacement should exhibit the same error.
Pedro.
>
> From: Pedro Giffuni<pf...@apache.org>
> Subject: Build broken on FreeBSD.
> Date: Fri, 24 Feb 2012 12:53:16 -0500
>
>> Hi;
>>
>> Just FYI
>> ______
>> ...
>> ... analyzing files ...
>> ERROR: The following files could not be found:
>> ERROR: File not found: libapr-1.so.0.4.5
>> ERROR: File not found: libaprutil-1.so.0.4.1
>> ERROR: File not found: libserf-1.so.0.0.0
>> ... cleaning the output tree ...
>> ... removing directory /tmp/ooopackaging/i_713701330104152 ...
>> ...
>> ___________
>>
>> The naming scheme is completely inappropriate for FreeBSD:
>>
>> ls /usr/local/lib/libapr*
>> /usr/local/lib/libapr-1.a /usr/local/lib/libaprutil-1.a
>> /usr/local/lib/libapr-1.la /usr/local/lib/libaprutil-1.la
>> /usr/local/lib/libapr-1.so /usr/local/lib/libaprutil-1.so
>> /usr/local/lib/libapr-1.so.4 /usr/local/lib/libaprutil-1.so.3
>>
>> cheers,
>>
>> Pedro.
>>
Re: Build broken on FreeBSD.
Posted by Maho NAKATA <ma...@apache.org>.
Hi Pedro
> The naming scheme is completely inappropriate for FreeBSD:
I think this is right, but again, this is libtool (version numbering
scheme difference between Linux and FreeBSD). Patching agianist
ltmain.sh would solve that type of problem.
Could you please tell me which svn revision and configure line...
thanks
Nakata Maho
From: Pedro Giffuni <pf...@apache.org>
Subject: Build broken on FreeBSD.
Date: Fri, 24 Feb 2012 12:53:16 -0500
> Hi;
>
> Just FYI
> ______
> ...
> ... analyzing files ...
> ERROR: The following files could not be found:
> ERROR: File not found: libapr-1.so.0.4.5
> ERROR: File not found: libaprutil-1.so.0.4.1
> ERROR: File not found: libserf-1.so.0.0.0
> ... cleaning the output tree ...
> ... removing directory /tmp/ooopackaging/i_713701330104152 ...
> ...
> ___________
>
> The naming scheme is completely inappropriate for FreeBSD:
>
> ls /usr/local/lib/libapr*
> /usr/local/lib/libapr-1.a /usr/local/lib/libaprutil-1.a
> /usr/local/lib/libapr-1.la /usr/local/lib/libaprutil-1.la
> /usr/local/lib/libapr-1.so /usr/local/lib/libaprutil-1.so
> /usr/local/lib/libapr-1.so.4 /usr/local/lib/libaprutil-1.so.3
>
> cheers,
>
> Pedro.
>
Re: Build broken on FreeBSD.
Posted by Maho NAKATA <ma...@apache.org>.
Hi Andre and Pedro
> Yes, and it does not work so well on Mac either. It does not even
> follow the Linux naming scheme (see the 0 in libapr-1.so.0.4.5? I do
> not know where that does come from.)
It came from "libtool".
Usually it is included in the tar ball, but it pick up from system's libtool
(e.g. /usr/bin/libtoo, /usr/local/bin/libtool, /sw/bin/libtool or /opt/local/bin/libtool...)
Therefore, we cannot change the version number easily.
Pedro:
In this case, we should use FreeBSD style naming for shared libs. Therefore
patching scp2 is easier and better solution...
Thanks
Nakata Maho
From: Andre Fischer <af...@a-w-f.de>
Subject: Re: Build broken on FreeBSD.
Date: Mon, 27 Feb 2012 09:42:53 +0100
> On 24.02.2012 18:53, Pedro Giffuni wrote:
>> Hi;
>>
>> Just FYI
>> ______
>> ...
>> ... analyzing files ...
>> ERROR: The following files could not be found:
>> ERROR: File not found: libapr-1.so.0.4.5
>> ERROR: File not found: libaprutil-1.so.0.4.1
>> ERROR: File not found: libserf-1.so.0.0.0
>> ... cleaning the output tree ...
>> ... removing directory /tmp/ooopackaging/i_713701330104152 ...
>> ...
>> ___________
>>
>> The naming scheme is completely inappropriate for FreeBSD:
>
> Yes, and it does not work so well on Mac either. It does not even
> follow the Linux naming scheme (see the 0 in libapr-1.so.0.4.5? I do
> not know where that does come from.) And on Windows we have a special
> makefile which uses yet another naming scheme.
>
> Welcome in multi-platform-world.
>
> Apr (and apr-util and serf) are external libraries. Our means to
> control the names of the libraries are limited. If anyone knows how
> to change that, please let me know.
>
> If that leads to problems with pre-installed libs on any platform then
> we should look for a solution that works on all platforms. The
> problem, as I understand it, is this:
>
> A - The modules apr, apr-util, and serf (and possibly coinmp) use
> their original (mostly) configure scripts to generate the library
> name.
>
> B - This name is used in scp2/ to a) include the actual library into
> the pack set and b) create some symbolic links that strip away the
> micro and minor version numbers.
>
> C - This name is not the same as the one of libraries that are already
> installed on the system. The system libraries are therefore not found
> at run-time.
>
>
> I would attempt a solution somewhere between A and B. We already have
> {library}_version.mk files in apr,apr-util, and serf that communicate
> the major, minor, and micro version numbers to scp2. Maybe we can
> rename the libraries to whatever name is appropriate on a platform at
> the time when the libraries are delivered into solver/ and then use
> the {library}_version.mk file to get the new name into scp2? For this
> we have to append the new name to the makefile before it is also
> delivered.
>
> This should be relatively simple and would require platform specific
> knowledge only in apr, apr-util, and serf.
>
> -Andre
>
>
>>
>> ls /usr/local/lib/libapr*
>> /usr/local/lib/libapr-1.a /usr/local/lib/libaprutil-1.a
>> /usr/local/lib/libapr-1.la /usr/local/lib/libaprutil-1.la
>> /usr/local/lib/libapr-1.so /usr/local/lib/libaprutil-1.so
>> /usr/local/lib/libapr-1.so.4 /usr/local/lib/libaprutil-1.so.3
>>
>> cheers,
>>
>> Pedro.
>
Re: Build broken on FreeBSD.
Posted by Andre Fischer <af...@a-w-f.de>.
On 24.02.2012 18:53, Pedro Giffuni wrote:
> Hi;
>
> Just FYI
> ______
> ...
> ... analyzing files ...
> ERROR: The following files could not be found:
> ERROR: File not found: libapr-1.so.0.4.5
> ERROR: File not found: libaprutil-1.so.0.4.1
> ERROR: File not found: libserf-1.so.0.0.0
> ... cleaning the output tree ...
> ... removing directory /tmp/ooopackaging/i_713701330104152 ...
> ...
> ___________
>
> The naming scheme is completely inappropriate for FreeBSD:
Yes, and it does not work so well on Mac either. It does not even
follow the Linux naming scheme (see the 0 in libapr-1.so.0.4.5? I do not
know where that does come from.) And on Windows we have a special
makefile which uses yet another naming scheme.
Welcome in multi-platform-world.
Apr (and apr-util and serf) are external libraries. Our means to
control the names of the libraries are limited. If anyone knows how to
change that, please let me know.
If that leads to problems with pre-installed libs on any platform then
we should look for a solution that works on all platforms. The problem,
as I understand it, is this:
A - The modules apr, apr-util, and serf (and possibly coinmp) use their
original (mostly) configure scripts to generate the library name.
B - This name is used in scp2/ to a) include the actual library into the
pack set and b) create some symbolic links that strip away the micro and
minor version numbers.
C - This name is not the same as the one of libraries that are already
installed on the system. The system libraries are therefore not found
at run-time.
I would attempt a solution somewhere between A and B. We already have
{library}_version.mk files in apr,apr-util, and serf that communicate
the major, minor, and micro version numbers to scp2. Maybe we can
rename the libraries to whatever name is appropriate on a platform at
the time when the libraries are delivered into solver/ and then use the
{library}_version.mk file to get the new name into scp2? For this we
have to append the new name to the makefile before it is also delivered.
This should be relatively simple and would require platform specific
knowledge only in apr, apr-util, and serf.
-Andre
>
> ls /usr/local/lib/libapr*
> /usr/local/lib/libapr-1.a /usr/local/lib/libaprutil-1.a
> /usr/local/lib/libapr-1.la /usr/local/lib/libaprutil-1.la
> /usr/local/lib/libapr-1.so /usr/local/lib/libaprutil-1.so
> /usr/local/lib/libapr-1.so.4 /usr/local/lib/libaprutil-1.so.3
>
> cheers,
>
> Pedro.