Re: [Mac OS X] Very close with OOo 2.0 build on Jaguar

At 9:32 AM +0200 5/21/05, eric.bachard wrote:
>Hi Terry,
>
>Terry Teague a écrit :
>> Dear Folks,
>>
>> Over the past week or so, off and on, I have been trying to build OOo 2.0
>> (more specifically 1.9m97) in Mac OS X 10.2.x Jaguar.
>>
>> I have had to make a few fixes, and a couple of hack workarounds for the
>
>Which one ?
>
>> moment, but it finished building today.
>
>I'm very intersted with your changes, can you please give us the issues
>numbers ?
>Thank's in advance  :-)


Since I don't know how to proceed with the last remaining error (as per my
previous EMail), there may not be a Jaguar version of OOo 2.0 anytime soon.
I also don't have any time at the moment to work on it.

If you really want me to write up issues I can (but since I haven't signed
the JCA, any patches will be rejected).

Actually you are probably one of the people in a position to be able to
come up with good patches rather than my workarounds.

Here is a summary of the problems I ran into (so far) :

1) I had to install Perl 5.8.6 (through CPAN) to be able to successfully
install the Archive::Zip CPAN module - this took a while to get right
(initially 'dmake' crashed because of a Perl library mismatch), and I was
concerned it would break my existing Perl installation (it didn't appear to
do so). There is a web page I found that described the Perl 5.8.x
installation process on Jaguar (I don't have the URL handy), that helped a
lot.

2) "configure" failed in the check for PackageMaker on Mac OS X - the check
works for Panther/Tiger, but not for Jaguar, because of the location of
PackageMaker changed for Panther. I did a quick workaround by making a copy
of PackageMaker in the expected place.

3) The "sal" module failed to build. I then discovered that "set_soenv"
wasn't setting the BUILD_OS_MAJOR, BUILD_OS_MINOR, BUILD_OS_REV environment
variables. This is because the "set_soenv" check for Mac OS X was changed
from the original check that worked - the new check is cleaner code, but it
only works on Panther/Tiger.

The fix (in "soenv.in") is probably fairly simple, except I can't do it
because I am not a Perl programmer - the fix is to parse the full output of
"sw_vers" rather than trying to make "sw_vers" do the work with an option
that is only available in the Panther/Tiger versions of "sw_vers".

I worked around the problem by just manually setting the environment
variables (I modified my copy of the MacosxEnv scripts).

4) The "jvmfwk" module failed to build. This is because of a missing
"libxml2" library (even though the "libxml2" module had been built). I
hacked around this problem for a while (there are the sort of circular
references to dylibs that we have seen in Panther builds), but in the end,
I just copied the built "libxml2" to /usr/local/lib (and created the
appropriate symlinks). Of course it might not work at runtime if I get that
far.

5) The "odk" module failed to build. A new file
"odk.source/unoapploader/unx/unoapploader.c" uses some "dl_info" stuff,
which the comments in the file suggest are Linux specific. I think the
problem is that the "dlcompat" stuff that was in OOo 1.1.x seems to have
been removed from OOo 2.0, because it is no longer required for
Panther/Tiger.

I hacked around this by conditionally #ifdefing the code for Mac OS X (does
nothing at present on Mac OS X).

6) The "vcl" module failed to build. This was easy - this is a well known
bug with (I don't have the IZ # handy) where there is an extra #include
<sys/poll.h> in "vcl/unx/source/app/sm.cxx".

7) The "insetoo_native" module failed to build. This is the one I am stuck
on - it could not register the Python UNO components.


>Regards,
>eric bachard


Regards, Terry