>> I guess somethings wrong with the gcc3.map file...
>
> Yes : the map file seems to be missing.
No, the problem is different.
During the unomacli64 life, ause removed
component_getDescription
functions and removed this symbol from map files.
Unfortunately it
was done when the unomacli64 already contained renamed map
file.
After resync of unomacli64, it was tested only on platforms
where
additional symbol in the map file doesn't matter. But it is
a problem
on Mac OS X resp. problem for our linker.
Thus the symbol had to be removed from the new map file as
well.
The evidence of this can be find also in the CWS comments of
unomacli64:
--- cut here ---
---------- Comment from pjanik Sun Jul 8 17:03:04 +0200 2007
----------
Kay: I suggest to resync it to
post-getDescriptionFunc-removal
milestone to prevent integration issues with it.
This would also help me to get it tested.
--- cut here ---
Of course you can build m221 and add unomacli64 manually,
but why to
do so, when you can just wait for the milestone with it
integrated
and test it without issues? Just waiting a bit and you have
the same
stuff without doing any kind of hacks...
--
Pavel Janík
------------------------------------------------------------
---------
To unsubscribe, e-mail: mac-unsubscribe porting.openoffice.org
For additional commands, e-mail: mac-helpporting.openoffice.org
|