Re: [mac] Shall we ship OOo with internal python on Mac?

[Christian Lohmaier]

Hi Stephan, *,

On Tue, Aug 24, 2010 at 10:16 AM, Stephan Bergmann
 wrote:
> On 05/19/10 18:55, Christian Lohmaier wrote:
> [...]
> I just experienced the problem to get pyuno working on Mac OS X 10.6, too.
>  At least for me (trying to run the tests in
> testtools/source/bridgetest/pyuno/), it clearly is a problem of system
> python being executed as 64 bit, while OOo's pyuno.so is 32 bit (see below).

For that, there is an environment variable:
VERSIONER_PYTHON_PREFER_32_BIT=yes (but as mentioned earlier, I didn't
manage to get it running, no matter what variables I tried - while
then the architecture matches, the python version itself makes it
fail)

> Christian, did you already file an issue to use internal python on Mac
> (which apparently is the outcome of this thread)?

Outcome of this thread is that apparently  almost nobody seems to care
:-( Just 10 People bothered to reply at all...

But yes, filed issue(s) with patches. Meta issue:
http://qa.openoffice.org/issues/show_bug.cgi?id=111496

scp2 parts are already integrated/applied to some cws, but
unfortunately the other patches did not receive any comment yet :-(

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

Re: [mac] Re: 3.2.1 for PowerMac

[Christian Lohmaier]

Hi Larry, Drechsel, *;

On Thu, Jul 29, 2010 at 10:34 AM, Larry Gusaas  wrote:
>
> http://ooopackages.good-day.net/pub/OpenOffice.org/contrib/

The URL changed, that is right, but the following might be a little
misleading, so I'd like to add/clarify on that:

> There is an official release in US English and a few other languages at
> http://download.openoffice.org/other.html

All the official PPC releases come from ooopackges.good-day.net (Maho
prepares them and uploads them to the good-day.net server)

A release will be released as "official release" once a corresponding
QA-Team did approve it. (native-language projects run the tests and
then approve it (or not if there are serious problems with the build).
When it is approved, the RC (release candidate) from good-day.net is
simply renamed and pushed to the main mirror network.
(This process is the same for other builds as well, the RC that is
approved is renamed and then put on the main mirror network) The thing
with PPC is just that other builds are provided by Sun/Oracle and they
do QA for en-US, thus en-US version for other operating systems is
immediately released/available, while the other languages have to be
approved by the corresponding native-lang teams first (that sometimes
leads to delays for some languages/operating systems. Especially Mac
for PPC version lacks testers/feedback, so Mac/PPC version is always
amongst the last to be approved/amongst those who will always stick
with RC status just because nobody did test and approve that specific
version)

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

Re: [mac] Re: Shall we ship OOo with internal python on Mac?

[Christian Lohmaier]

Hi *,

2010/6/24 Darabos Dániel :
> +1 for system Python.

As to Mac's support for older python runtimes, see the other post: It
is not complete. I'd even say it is totally broken. It is only for
binary-applications that link against older python runtimes, but not
for shell-use. (and that is what is needed to use pyuno from outside
OOo)

> [...] The only downside I saw is that it can get vry
> outdated because it won't break :). Actually Apple forcing
> OpenOffice.org to upgrade to a newer Python every once in a while is a
> good thing for the user even if it's more work for developers.

Oh, 2.3 is not vry outdated already?
Or otherwise put: Do you really expect that there will be a
python-update by Apple for Mac OSX 10.4?

And getting outdated: Well, then it would be the same on all operating
systems, especially windows as those come with OOo's python by
default.

> The difference is most meaningful for extensions. If we stick with one
> version, OpenOffice.org will become a less appealing platform for
> developers over time, as they are already used to Python 4.6 and we
> are still on 2.3.

Well, I'd say the contrary is true. With Mac OSX you're tied to python
2.3, I don't think there will ever by an update for python by Apple
for 10.4

And as OOo for other operating systems ship with OOo's python, I don't
see this as a problem. If there is need/demand for a newer python from
the side of extension developers, the python version that is included
with OOo will be updated.

> Thanks for working on this Christian! I'm not working on
> OpenOffice.org at the moment and I cannot offer any help, but even
> moreso it's good to see you have an interest in this!

Well in case this isn't clear:
The work is done already. Patches are attached to the issue(s). What
is left is just to integrate the patches into the official codeline
(for the most part done already) and of course decide on what should
the user get.

The decision I demand here is not a technical one. It is a "political" one.

I.e. what should configure default to. OOo's own python (as is the
case for windows and linux by default), or system python.

Those who build OOo by themselves will be able to just use
--with[out]-system-python, but only very, very few Mac users will
build their own copy of OOo. Thus it is important to decide on the
default, what the installsets offered from www.openoffice.org will
include (or not include)

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

Re: [mac] Re: Shall we ship OOo with internal python on Mac?

[Christian Lohmaier]

Hi Florian, * (especially Martin and Dániel (or Darabos, no idea what
is First and Family name :-)

On Sat, Jun 26, 2010 at 6:04 AM, Florian Ludwig Heckl
 wrote:
> Hi Christian,
>
>> [x] OOo should continue to use system python, regardless of problems
>> accessing pyuno from outside OOo
>> [ ] OOo should use internal python, ship with its own copy of python
>> (increases download size)
>> [ ] I don't care - you should do a poll on the user-focused lists instead.
>
> The only thing that could make me switch to internal python would be if it 
> really was easier
> for external scripts to successfully "import uno" (is it?)

Well - for Mac OSX 10.6 (not sure about 10.5) using OOo-shipped python
is the *only* way for external scripts to successfully import uno.

I failed to get system python to work on 10.6, no matter what
environment variables I used.

So yes, it definitely is easier to use OOo's own python. You have to
run python from OOo's installation, and that is not in your PATH, so
you have to specify the path to the python executable (or better: the
wrapper that sets the corresponding environment variables for
bootstrapping to work, etc), but that is the only "difficult" thing
about it.

And as said: The only way to get it work from outside.

While Mac OS 10.6 indeed still ships with python 2.3 stuff (that is
what OOo builds against by default since that is the latest available
on Mac OSX 10.4, the baseline for OOo), it doesn't ship with a full
python 2.3
You can initialize a python-runtime from within your application
flags, similar to creating a JVM from your application code, but you
cannot run a python 2.3 environment from a terminal/a shell.
(At least I did not manage to do so)

> or if one of the OOo supplied extensions (what do we have here?) needed a 
> later python version.

No idea, don't think that extensions really require a newer python.

> In the early mac port times I was very much in favor of minimizing external 
> dependencies
> but if we don't gain anything then let's rather reduce download size.

s/reduce/not increase/

We gain the ability to use pyuno from outside OOo on 10.6 (and maybe 10.5)

I'd more than happy if anybody can give me a commandline to "import
uno" with system python (i.e. with OOo as you can download currently).

(again: no problem if you execute that macro from within OOo, the
problem is when you want to use it from outside, i.e. use uno to
bootstrap (=start) OOo, or attach to OOo listening on a TCP port) and
then remote-control it)

for Tools|Macros → run there is no problem (works on all versions of Mac OSX)

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

[mac] Re: Shall we ship OOo with internal python on Mac?

[Christian Lohmaier]

Hi *,

*PLEASE*: reply even if you don't care. I cannot tell whether there is
silence because nobody (apart from Florian - thanks for the reply!)
did read the question, or because just nobody really cares.

Please vote:

[ ] OOo should continue to use system python, regardless of problems
accessing pyuno from outside OOo
[ ] OOo should use internal python, ship with its own copy of python
(increases download size)
[ ] I don't care - you should do a poll on the user-focused lists instead.

For reference, the original mail in fullquote, so you don't have to
dig in archives for messagess from a month ago...

ciao
Christian
On Wed, May 19, 2010 at 12:55 PM, Christian Lohmaier
 wrote:
> Hi *,
>
> as the baseline of Mac OSX 10.4 only ships with python version 2.3,
> OOo is compiled against that version. This is not a problem when
> running python from within OOo, you can run python macros on
> 10.4/10.5/10.6 with no problem with a default installation of Mac OSX.
>
> There is a big "BUT" however:
> On never versions of Mac OSX, it is not possible to run standalone
> python with pyuno. I.e. you cannot run python from outside OOo and run
> your script. You'll get "incompatible version" style errors. (newer
> versions of Mac OSX ship with the 2.3 basic framework, but only have
> python2.5 and 2.6 launchers. I failed to get it to "import uno" on
> 10.6, no matter what tricks with environment variables I tried. Maybe
> there's some trick to get it running, but I gave up. I'm neither a
> python nor a Mac user, so there might still be a way though.
> (Again: running python macros from within OOo is not a problem, python
> loaded via OOo's library gets things right)
>
> Eric Bachard made me aware on IRC that the python in OOo's sources is
> already at 2.6.1 and made me start working on it. For some reason Eric
> cut communication after I filed the issues with patches , so I
> finished it myself.
>
> Main issue is http://qa.openoffice.org/issues/show_bug.cgi?id=111496
> Other issues with the corresponding patches can be found in the
> depending issues.
>
> The questions basically are:
> Should OOo for Mac ship with internal python? Or should it still use
> system-python?
> Anyone a python-guru/deep into Apple's Framework stuff who can tell
> how to get a "import uno" work on Mac OSX >10.4 from outside OOo?
> Anyone into python extensions and want to give internal python 2.6.1 a
> thorough test?
> Anyone for code-review?
>
> If necessary, I could provide installsets for PPC (build-OS: 10.4) and
> Intel (build-OS: 10.6).
>
> ciao
> Christian
>

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

Re: [mac] Re: powerpc oo 3.2.1 builds?

[Christian Lohmaier]

Hi Eric, *;

On Wed, Jun 9, 2010 at 3:25 AM, Eric Hoch  wrote:
> Hi Jack,
> Am Fri, 4 Jun 2010 10:50:43 -0400 schrieb Jack Howarth:
>>   I noticed that there seems to be no builds
>> on ooopackages.good-day.net for openoffice
>> 3.2.1 rc's under powerpc-apple-darwin.
>
>> Will
>> there be additional powerpc releases or is
>> that support winding down?
>
> Yes there will be an additional release and nope support isn't
> winding down, however it's getting harder to find and get PowerPC
> Macs that can build and test OOo at at significant speed or at a
> reasonable pace.

Nah, that's not really the problem.

> We're talking about automated building and testing
> here. Human tests aren't affected but when taking a look around at
> my peers nearly all the Apple users have upgraded to an Intel Mac
> and the new users often don't know that there were Pre-Intel Macs.

HUMAN tests are those that are the limiting factors. There just is
*no* feedback whatsoever from PPC users (mac users in general)

It is frustrating to see that for example PDF export was broken on PPC
for a looong time. PPC users surely did experience the problem, but
they did not report back, thus it went unnoticed (since that one did
only show up in real-life documents, not in a test-document that has
only "hello world" inside.
It's a lot easier to debug stuff if it is reported early, so you can
check recent changes for suspicious entries. But if you have to check
a whole year of changes, this takes considerably more effort.

not to mention: The release-approval is done by humans.
Unless a human says: I tested PPC on Mac, and found no severe issues
that would block the releae, it won't be put on the regular mirror
network, won't be listed on the main download pages (only under RC
downloads).

So again: Humans are the limiting factors, not the machines!

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

Re: [mac] Compiling OpenOffice on Mac OS X 10.6

[Christian Lohmaier]

Hi Tim, *,

On Fri, Jun 4, 2010 at 5:57 PM, Tim Schuermann  wrote:
> Hi Christian and list,
>
> first of all: After one day of downloading and compiling it worked at last. 
> :) I used MacPorts (something I liked to avoid) and a modified version of the 
> script from Stephan Bergmann some posts ago. (*)

macports/stuff that is not provided by Mac OSX or XCode is only needed
when you build mozilla instead of using the precompiled zips

here's what I did:
http://www.mail-archive.com/mac@porting.openoffice.org/msg03498.html
# when I prepared the precompiled mozilla, I did manually install pkconfig,
# libIDL,gettext and glib in a temporary prefix and did use that to build.

The only stuff you should install in addition is: ccache & mercurial
(for ccache have a look at
http://qa.openoffice.org/issues/show_bug.cgi?id=104567 for a small
patch)

> btw: Stephan, why are doing this:
>> mkdir OOo/pkgconfig
>> ln -s /opt/local/lib/pkgconfig/glib-2.0.pc OOo/pkgconfig/
>> ln -s /opt/local/lib/pkgconfig/libIDL-2.0.pc OOo/pkgconfig/
>> export PKG_CONFIG=/opt/local/bin/pkg-config \
>>  PKG_CONFIG_LIBDIR=$PWD/OOo/pkgconfig
>
> Is this really necessary?

No. As you don't need macports, but can install stuff manually, you
can choose to use different directories to keep stuff separated. So
no, this is not necessary.

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

Re: [mac] Compiling OpenOffice on Mac OS X 10.6

[Christian Lohmaier]

Hi Tim, *,

On Sun, May 30, 2010 at 11:08 AM, Tim Schuermann  wrote:
> Hi Laurent and list,
>
> still no luck compiling OO m78 on OS X 10.6:
>
>> > [...]
>> - http://www.openoffice.org/issues/show_bug.cgi?id=106059
>
> I thought these issues were fixed, see:

They are fixed, but not in m78 - the cws that got all the fixes was
integrated in m80
Go to http://qa.openoffice.org/issuelinks.html and copy the issue number.

→ 
http://eis.services.openoffice.org/EIS2/cws.InfoForTask?TaskId=106059&RSV_NoWait=true&SRC_Step=Search

There you see the short-info for the cws that contains the fix.
Important in this case is the "Milestone (integrated)" column. So in
this case it reads m80

The first milestone that contains the fix is m80. So when you're
trying to build m78, you need to patch the code yourself.

> http://old.nabble.com/Re%3A-Mac-OS-X-10.6-(Snow-Leopard)-build-problems-with-OOO320-p28027983.html

That one still mentions issues with the remark "not yet integrated",


> http://porting.openoffice.org/servlets/ReadMsg?listName=mac&msgNo=7818

This refers to the issue. And as such (if you need to read an issue on
how to proceed that imiplies that it doesn't work out-of-the-box,
hence you need to patch yourself)

> So do I have still to install a patch? If yes, which one? The 
> patch/workaround here:
> http://www.openoffice.org/issues/show_bug.cgi?id=106059
>
> disables the nss-module. But that doesn't work on my system. :) (in that case 
> the libs "libAppleRemotemxi.dylib" and "libuno_sal.dylib.3" can't be build).

Changing configure flags must be done from a clean shell, without
previous environment variables set. And when you change flags and have
already built parts of the code, you need to make sure to rebuild all
the modules that are affected by those flags. In doubt, start over
(dmake clean)

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

Re: [mac] Compiling OpenOffice on Mac OS X 10.6

[Christian Lohmaier]

Hi Tim, *,

On Tue, May 25, 2010 at 11:36 AM, Tim Schuermann  wrote:
> So here are the steps I did (according to 
> http://wiki.services.openoffice.org/wiki/AquaBuild):
> {...[
> 3. Downloaded DEV300_m77 (or DEV300_m78, the errors are the same) from 
> http://download.openoffice.org/next/ and untared them into my directory.

Unclear information, as that download page doesn't directly lists the sources.
As written by others: Either get the full set of sources or use the
appropriate configure switches

> 4. Downloaded prebuild Mozilla archives (MACOSXGCCIinc.zip, 
> MACOSXGCCIlib.zip, MACOSXGCCIruntime.zip) and placed them in the directory 
> "DEV300_m77/moz/zipped"

Again not very helpful, as there are two versions. You need the one
from m53 and above.

> 5. Invoke configure:
>
> ./configure \
> --with-lang="en-US de fr" \

Needs l10n tarball and en-US is always built, no need to specify it.

> --disable-odk \

speeds up build, no need to download unowinreg.dll, no SDK is built.
OK if you only want to hack on OOo itself.

> --disable-pasf \

No such configure switch.(anymore)

> --disable-gtk \

OK, was only needed to build mozilla from source on Mac

> --disable-headless \

no such switch (anymore)

> --disable-build-mozilla \

OK/needed when using precompiled mozilla

> --disable-fontconfig \

unnecessary (disabled for mac anyway)

> --without-nas \

No such switch (anymore)

> --with-use-shell=bash \

Very good, but no such switch anymore in recent versions either.

> --with-jdk-home=/System/Library/Frameworks/JavaVM.framework/Home \

Unnecessary, should be autodetected properly.

> --with-stlport=no \

Very dangerous. Quoting configure's help:

# Warning!!, disabling using --without-stlport or
# enabling using --with-stlport on a platform that
# defaults to the opposite will break ABI compatability

In other words: Leave that switch alone. As you're unexperienced, even
more reason to not add random flags that are not understood.
In this case Mac defaults to system stl anyway, thus unnecessary.

> --disable-mediawiki \

OK - optional extension. But when you disable that one, why not
disable the other ones?

> --enable-werror \

OK, OOo is wae free on Mac.

> --disable-vba

Well, default is different, and if that is what you want...

You don't specify --disable-binfilter. This however has the biggest
impact in terms of build time. So if you want to hack on OOo, I'd
suggest that flag, as binfilter code is dead code (in the sense of:
nobody touches it anymore, just for compatibility with older binary
file formats)

> 6. Start the Build-Process:
>
> ./bootstrap
> source MacOSXX86Env.Set.sh
> cd instsetoo_native
> export TMP=/tmp

No longer necessary

> export SYSTEM_OPENSSL=YES

BAD idea. Either you configure OOo properly using configure, or you
hack your own environment variables.
Especially if you're unexperienced: Don't mess with what configure creates.

Besides defaults to system_openssl on mac anyway.

I repeat: If you don't understand what a flag does: Don't use it.
If you don't know what a command is for: Don't execute it.

> build --all -P4

OK if you got a multiprocessor system, but I'd sugges build --all -P3
-- -P2 instead.

> ./configure --build=i386-Darwin-darwin

The --build type specifier is not used by OOo.

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

Re: [mac] Shall we ship OOo with internal python on Mac?

[Christian Lohmaier]

Hi Florian, *,

On Wed, May 19, 2010 at 2:34 PM, Florian Ludwig Heckl
 wrote:
>
>> The questions basically are:
>> Should OOo for Mac ship with internal python? Or should it still use
>> system-python?
>
> Does a normal "import uno" work with the thus provided python. (Users would 
> still need to adapt their PATH or launch the provided python explicitly)

With internal python, it would then work with the OOo-provided python.
They would have to call OOo's python manually, as OOo wouldn't be in
their PATH, so they'd run
/path/to/OpenOffice.org.app/Contents/MacOS/python and they're ready to
type "import uno"

That script sets the needed environment variables (PYHONPATH,
URE_BOOTSTRAP, etc) and starts the internal Python, like it would be
the case on other operating systems.

If the internal python should be run as-is, i.e. without the
OOo-specific variables, then the user could also run
path/to/OpenOffice.org.app/Contents/basis-link/program/OOoPython.framework/Versions/2.6/bin/python2.6

>> Anyone a python-guru/deep into Apple's Framework stuff who can tell
>> how to get a "import uno" work on Mac OSX >10.4 from outside OOo?

Reading it again, I wasn't very clear/that statement is very misleading.
What I really meant is: In case we stick with system-python, is there
anyone willing to dig into getting it to run from outisde OOo?
I.e. does anyone know a way on how to use python from outside OOo with
the current version of OOo that uses system python. This is no problem
on 10.4, as that comes with the used 2.3 version, but doesn't work (at
least I couldn't manage) with 10.6

This won't be a problem with internal python.

>> Anyone into python extensions and want to give internal python 2.6.1 a
>> thorough test?
>> Anyone for code-review?
>
> If we decide on a 'yes' for the main question, I can do so.

Thanks a lot,

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

[mac] Shall we ship OOo with internal python on Mac?

[Christian Lohmaier]

Hi *,

as the baseline of Mac OSX 10.4 only ships with python version 2.3,
OOo is compiled against that version. This is not a problem when
running python from within OOo, you can run python macros on
10.4/10.5/10.6 with no problem with a default installation of Mac OSX.

There is a big "BUT" however:
On never versions of Mac OSX, it is not possible to run standalone
python with pyuno. I.e. you cannot run python from outside OOo and run
your script. You'll get "incompatible version" style errors. (newer
versions of Mac OSX ship with the 2.3 basic framework, but only have
python2.5 and 2.6 launchers. I failed to get it to "import uno" on
10.6, no matter what tricks with environment variables I tried. Maybe
there's some trick to get it running, but I gave up. I'm neither a
python nor a Mac user, so there might still be a way though.
(Again: running python macros from within OOo is not a problem, python
loaded via OOo's library gets things right)

Eric Bachard made me aware on IRC that the python in OOo's sources is
already at 2.6.1 and made me start working on it. For some reason Eric
cut communication after I filed the issues with patches , so I
finished it myself.

Main issue is http://qa.openoffice.org/issues/show_bug.cgi?id=111496
Other issues with the corresponding patches can be found in the
depending issues.

The questions basically are:
Should OOo for Mac ship with internal python? Or should it still use
system-python?
Anyone a python-guru/deep into Apple's Framework stuff who can tell
how to get a "import uno" work on Mac OSX >10.4 from outside OOo?
Anyone into python extensions and want to give internal python 2.6.1 a
thorough test?
Anyone for code-review?

If necessary, I could provide installsets for PPC (build-OS: 10.4) and
Intel (build-OS: 10.6).

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

Re: [mac] Mac donations from Miyahara, Toru and Komachi, Mamoru to Nakata, Maho (two dual core 2.66GHz Xeon 4G memory, two 1T HDDs, and Snow Leopard)

[Christian Lohmaier]

Hi Maho, *;

On Mon, Feb 15, 2010 at 7:16 AM, Maho NAKATA  wrote:
>
> I'd like to announce that there were donations from
> MIYAHARA Toru, CEO of http://begi.net/ in 2009/1/27 - 29.
>  * two dual core 2.66GHz Intel Xeon based Mac (we are not sure which one :-))
>  * two 1T bytes HDD: Hitach HDT7201010SLA360

If you got multiple HDDs, then I strongly suggest to setup a RAID-0
(helps very much, esp. on Mac with its slow IO) :-)

> KOMACHI Mamoru,
>  * One license of Snow Leopard and Microsoft Office 2008 for Mac in 2009/9.
> [...]
> Many thanks for Miyahara-san and Komachi-san's donations, and many
> thanks for your good works on OpenOffice.org

Yes, thanks a lot!

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

Re: [mac] Leopard & OOo & java 1.6 32 bits

[Christian Lohmaier]

Hi Laurent, *,

On Wed, Dec 23, 2009 at 6:30 PM, Laurent Godard  wrote:
>
> first, i'm a beginner in mac os world
>
> I have an uno extension that fail to deploy due to java version under
> leopard. I need java 1.6 32 bits and only 64 bits is available under leopard

Unfortunately there's no way to select an specific JRE on Mac OSX currently.

On Mac OS X, there's one "JVM-launcher" that is used to create jvms of
all available version (while e.g. on linux there's a version specific
one)

What is done on Mac is to tell the "JVM-launcher" to create a jvm that
meets the 1.4 compliance.
http://pumbaa.ooodev.org:59145/source/xref/jvmfwk/plugins/sunmajor/pluginlib/sunjavaplugin.cxx#575

OOo doesn't have direct impact (it could be more strict about the
requirements, but the code doesn't do anything like that currently) on
what the launcher then actually choses..

> I tried this approach
> http://blog.adsdevshop.com/2008/02/26/installing-the-jdk-16-on-mac-os-x/
> It installs correctly and in a terminal , java -version is ok
>
> But, going to OOo java preferences, it says that no suitable java version is
> found in the directory, so i cannot use this 32 bits JVM

I didn't have any look at the URL above, but you can try to use the
equivalent of LD_PRELOAD to include the 1.6 libraries before the
default ones.
(DYLD_LIBRARY_PATH, see issue 88987 for an example)

Another one is to remove the 1.4 (and 1.5) versions so that the only
one left that fullfills the 1.4 compliance would be the 1.6 version.

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

Re: [mac] Intel VS PPC

[Christian Lohmaier]

Hi *,

On Sun, Oct 25, 2009 at 8:16 PM, Gallomimia  wrote:
> On Sun, Oct 25, 2009 at 4:06 AM, Christian Lohmaier
>  wrote:
>> On Sun, Oct 25, 2009 at 10:27 AM, Gallomimia  wrote:
>> [...]
>>> Why is the version 3.1.1
>>> not at release status for PPC while it is for intel?
>>
>> Because nobody did QA on them.
>> [...]
>
> Am I to understand that each and every language, on each and every
> architecture, requires a separate tester for each and every release?

Of course one person could perform the tests for multiple versions, but yes:
Every single installset requires a "passed QA, distribute it on the
mirrors"-statement from the corresponding tester.
Only then the release-candidate is promoted to the final version.

To what extent tests are performed is up to the corresponding team
(although tere are standardized testcases that can be used as basis)

>>> The requirements for the mac version on the main website are clearly
>>> wrong.
>>
>> URL please
>
> http://www.openoffice.org/dev_docs/source/sys_reqs_30.html

Thanks.

>>> I would like to volunteer my machine for any purposes needed.
>>
>> "only" your machine, but also your time?
>> In the latter case, you could do the release-tests for your language
>> (spanish?) so that the build can be officially released.
>
> Yes my time as well!

That sounds great :-)

> I sort of thought that was implied by my posting
> to this list. My language is english. I asked after spanish simply
> because it is the most spoken language in the world at roughly 1/3 the
> population. Seemed like it would be more important than French or
> German. I can see now that the reason those are the only versions
> available because of a lack of man-power having appropriate hardware.

Mac users in general are very, very bad at giving feedback unfortunately :-/

Only when you meet them in person (at exhibitions or something), they
start complaining ;-)

(My not very well founded expression gathered soley within the OOo-project)

> [...]
>
>> And for this combination, I already have one specific issue to test in mind:
>> http://qa.openoffice.org/issues/show_bug.cgi?id=92926
>
> I will be taking a look at this bug for sure.

Tthanks a lot! - Just tell me whether you need an installset or
whether you'll build your own version (i used DEV300_m61 as basis for
the patch)

> I will look into getting in contact with said devs to grant them ssh
> access.

The ones I have in mind are Herbert Dürr (hdu), Philipp Lohmann (pl)
and Stephan Bergmann (sb)
But I guess it is easier to handle it on a case-by-case basis,
shouldn't be needed that often.

> I should have plenty of bandwidth to be sending logs. I'm sure
> a 1mbps upstream is enough, shared with the rest of my house I hope it
> won't interfere. Perhaps I can cap it.

Yes, that's definitely enough, the question is mainly because of the
difference between tinderbox and buildbot, but with that bandwidth
both are possible.

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

Re: [mac] Intel VS PPC

[Christian Lohmaier]

Hi *,

On Sun, Oct 25, 2009 at 10:27 AM, Gallomimia  wrote:
>
> First of all, why are there separate versions of OOo for PPC and Intel
> macs? Can't a Universal Binary be created?

Yes. The universal binary would
* be huge to download
* very tricky to build in the first place (OOo uses a couple of
external modules and also bridges to various other languages
* building then also would be slow (as ccache doesn't allow multiple
arch in one compile.

Sum up: Not worth the effort. If the build could produce universal
builds, then probably just to extract the individual architectures to
create the installsets/to cross compile on fast intel machines for PPC
(where building is slooow)

Universal binaries are nice when the download then is 10 to 20 MB, but
not when you have to download more than 400 MB.

> Why is the version 3.1.1
> not at release status for PPC while it is for intel?

Because nobody did QA on them.

> It's been 2
> months... And the language specific builds on p2p distribution are
> french and german but not english.

Because french and german native-lang teams did QA the version and did
officially approve them for distribution on the main mirror network.

> No spanish? I digress.

Spanish language project did not approve the PPC build (very likely
because they didn't QA the build). Easy as that.

> The requirements for the mac version on the main website are clearly
> wrong.

URL please

> I downloaded a Release Candidate of 3.1.1 for PPC and installed it

Never saw this symptom on PPC here... Also no problems with printing.

> I would like to volunteer my machine for any purposes needed.

"only" your machine, but also your time?
In the latter case, you could do the release-tests for your language
(spanish?) so that the build can be officially released.

> I can
> grant ssh access, and run a tinderbox client. I can test and build,

Ah, test and build - that would be great.

> whatever's needed. I will give the machine specs.
>
> PowerMac Quicksilver
> Model Name:     Power Mac G4
> Model Identifier:       PowerMac3,5
> Processor Name: PowerPC G4  (2.1)
> Processor Speed:        800 MHz
> Number Of CPUs: 2
> L2 Cache (per CPU):     256 KB
> L3 Cache (per CPU):     2 MB
> Memory: 1.25 GB
> Bus Speed:      133 MHz
> Boot ROM Version:       4.2.5f1
>
> Running Leopard 10.5.8

And that is also nice have 10.4 on PPC.

And for this combination, I already have one specific issue to test in mind:
http://qa.openoffice.org/issues/show_bug.cgi?id=92926

The patch works on 10.4/PPC, but not on 10.[56]/Intel - having a 10.5
PPC would allow to check whether it is an intel problem or a problem
with [Snow] Leopard.
In both cases the cfrunloop is clrealy in another thread than the Java
stuff, but still it complains on the intel machines about awt and main
thread

> Developer Tools 3.1.4

> It is on 24/7 with a reboot every few days. The CPU time is roughly 75% 
> wasted.

Do you have enough bandwidth to run a buildbot (i.e. tinderbox
equivalent that can upload installsets to the botmaster when
requested? (tinderbox does only send the gzipped build log via mail,
so doesn't need much bandwidth)

ssh-access to the devs would also help - as the devs at Sun only have
intel macs at their hands and often cannot help when there's a
ppc-specific problem (fortunately doesn't happed that often, but
still...)

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

Re: [mac] Buliding OOo on Snow Leopard

[Christian Lohmaier]

Hi *,

On Tue, Sep 29, 2009 at 9:59 AM, Stephan Bergmann
 wrote:
> -Hi all,
>
> For what its worth, the below script is my (failed) attempt at building OOo
> (DEV300m60) on Mac OS X Snow Leopard (10.6).  Maybe somebody finds this
> helpful.  Some remarks:
>
> [hints/patch to compile a 10.6 version, against the 10.6 SDK]

As mentioned previously, the alternative is to use the 4.0 version of
the compiler and the 10.4u sdk (is not selected by default when
installing XCode 3.2). Then, all you need to do is to apply the patch
from issue 106059
http://qa.openoffice.org/issues/show_bug.cgi?id=106059 - I'll just
copy the text from the issue:

Building on Mac OS X 10.6 (Snow Leopard) for 10.4 requires the use of gcc-4.0
compiler and a compatible python version.

The patch adds the corresponding configure-checks
* error if gcc is not 4.0.x,
* use python2.3 from the SDK (the copy in /System/ is broken),
* default to CC/CXX for the objc/obj++ compilers,
* modify lpsolve patch to also use $CC,
* disable the use of the seperate nss (the libsqlite3.dylib conflicts with the
copy from the 10.6 system)

for the last one, issue 104832 took a different aproach (used for
HH-environment) - there it is solved by forcing the libsqlite3 from the system.

*** Don't forget to run autoconf ***

apply the patch, run autoconf, run

CC=gcc-4.0 CXX=g++-4.0 ./configure --with-use-shell=bash
[--disable-nss-module] …

and you'll get a working build. Instead of setting CC and CXX, you can of course
also use appropriate symlinks so that gcc and g++ will be the 4.0 version

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

Re: [mac] Re: Leopard build

[Christian Lohmaier]

Hi Joachim, *,

On Fri, Oct 9, 2009 at 7:55 AM, Joachim Lingner  wrote:
> Hi,
>
> A solution is to set DYLD_INSERT_LIBRARIES in our environment. For example:
>
> export DYLD_INSERT_LIBRARIES=/usr/lib/libsqlite3.dylib

No, that's not really a solution. The whole point in using the
10.4-SDK is to create a backwards-compatible build.
nss module was not part of the master, so was not included in the cloph13 cws.

The real solution is to make nss module respect the SDK, just as main
mozilla module.

Better solution for now is to disable the nss version of the libs,
unless you don't care about 10.4 compatibility...

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

[mac] Re: [tools-dev] Ant version upgrade to 1.7.1?

[Christian Lohmaier]

Hi *,

On Tue, Oct 6, 2009 at 12:56 PM, Ocke Janssen  wrote:
>
> For the newest version of hsqldb 1.9.0 I would need ant version 1.7.1 or
> later. Currently 1.6.2 is used.
> Would it be possible to do this upgrade or is there anything I have to take
> into account like configure or something special nobody never thought off.

This is very unfortunate since the latest version of XCode available
for PPC only compes with ant 1.6.5

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

Re: [mac] Buliding OOo on Snow Leopard

[Christian Lohmaier]

Hi Stephan, *,

I'm terribly sorry and try to find a stone to hide...

On Thu, Oct 1, 2009 at 9:14 AM, Stephan Bergmann
 wrote:
> On 09/30/09 16:04, Christian Lohmaier wrote:
>> On Wed, Sep 30, 2009 at 2:06 PM, Stephan Bergmann
>>  wrote:
>>> On 09/30/09 13:08, Christian Lohmaier wrote:
>>>>
>>>> You can do a full build (with compiling seamonkey) since m53 without
>>>> the need for any third-party build-stuff.
>>>
>>> What does the full configure command line look like in that case?
>>
>> I build with:
>> --with-use-shell=bash --disable-build-mozilla --enable-werror
>
> But without the --disable-build-mozilla you *do* need additional stuff.  At
> least I do, at least on some random Leopard box.  With the below script on
> that box configure fails with:
>
>> checking for seamonkey-1.1.14.source.tar.gz... not found
>> checking for seamonkey-1.1.14.source.tar.bz2... found
>> checking for pkg-config... no
>> *** The pkg-config script could not be found. Make sure it is
>> *** in your path, or set the PKG_CONFIG environment variable
>> *** to the full path to pkg-config.
>> *** Or see http://www.freedesktop.org/software/pkgconfig to get
>> pkg-config.
>> configure: error: libIDL 0.6.3 or newer is needed to build mozilla with
>> mac toolkit

Yes, you are completely right. I know remember that when I prepared
the precompiled mozilla, I did manually install pkconfig, libIDL,
gettext and glib in a temporary prefix and did use that to build.

So while I did never install fink/macports on those machines, it is
not true that you can build the full set (i.e. including building
mozilla from source) without any external stuff.

I'm very sorry for the false claim and all the confusion it might have
caused .-((

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

Re: [mac] Buliding OOo on Snow Leopard

[Christian Lohmaier]

Hi Stephan, *,

On Wed, Sep 30, 2009 at 2:06 PM, Stephan Bergmann
 wrote:
> On 09/30/09 13:08, Christian Lohmaier wrote:
>>
>> You can do a full build (with compiling seamonkey) since m53 without
>> the need for any third-party build-stuff.
>
> What does the full configure command line look like in that case?

I build with:
--with-use-shell=bash --disable-build-mozilla --enable-werror

the --disable-build-mozilla is to use precompiled zips. If you build
from source, then of course this isn't needed.

and to enable the extensions and graphite I also added
--enable-graphite --enable-minimizer --enable-presenter-console
--enable-pdfimport --enable-wiki-publisher --enable-report-builder

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

Re: [mac] Buliding OOo on Snow Leopard

[Christian Lohmaier]

Hi Stephan, *,

On Wed, Sep 30, 2009 at 9:08 AM, Stephan Bergmann
 wrote:
> On 09/29/09 20:42, Christian Lohmaier wrote:
>> On Tue, Sep 29, 2009 at 9:59 AM, Stephan Bergmann
>>  wrote:
>>>
>>>  [building on 10.6]
>>> - Similarly, MacPorts (used for the dependencies)
>>
>> What dependencies?
>> Only mozilla did depend on external stuff, because of the gtk-toolkit.
>> But since moz2seamonkey, no external libraries or similar is needed.
>>
>> So what parts does HH take from macports, and for what reason?
>
> First of all, the build I did was not in the HH setsolar environment, but a
> plain configure based one (I was apparently not clear about that).

Yes, but still there's still that gap that one doesn't really know
what the Sun-defaults are.
But ok if its a configure-based build :-)

> And, at least for me, if I "./configure --enable-werror
> --with-use-shel=bash", it fails at some point (either configure itself or
> building nss or moz---I do not remember which) unless there are external
> glib-2.0 and libIDL-2.0 available (which I bring in via PKG_CONFIG env vars
> and MacPorts glib, libidl, and pkgconfig).

The MacIntel buildbot did never see anything except XCode (and
manually installed ccache and mercurial), the MacPPC tinderbox is the
same: Only XCode (and manually installed ccache, subversion (which is
not part of the 2.4.x xcode) and mercurial).

> If there are configure switches that indeed allow to build a fully
> functional OOo with zero additional dependencies, I would be interested to
> learn that.  (And we should IMO set those switches implicitly then.)

This is already the case as mentioned above. Only mozilla did need gtk
(and thus the other libs). But in the past you could use precompiled
mozilla (that is what the bots use), and since moz2seamonkey, it no
longer needs to build the gtk-toolkit version and doesn't need those
libs anymore.

You can do a full build (with compiling seamonkey) since m53 without
the need for any third-party build-stuff.
Earlier milestones can be built without any third-party build-stuff
when using precompiled mozilla zips

>> Oh, that sounds bad. Isn't there even an option in xcode to install
>> the 10.4 sdk?
>
> Probably there is, as Florian pointed out in another response to this
> thread.  I had just been too lazy to check it out.

I already feared lots of special casing for 10.6, glad that this
apparently is not needed .-)

> [...]
> The problematic thing is the -fvisibility-hidden bug.  10.6 does come with
> multiple GCC versions, but I did not yet investigate there further.

At least on 10.4 you can switch the default with gcc_select, but
apparently it is no longer present?
It (AFAIK) only changed symlinks anyway, much like update-alternatives
on linux would do).

But explicitly setting CC/CXX should always work

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

Re: [mac] Buliding OOo on Snow Leopard

[Christian Lohmaier]

Hi Stephan, *,

On Tue, Sep 29, 2009 at 9:59 AM, Stephan Bergmann
 wrote:
>  [building on 10.6]
> - Similarly, MacPorts (used for the dependencies)

What dependencies?
Only mozilla did depend on external stuff, because of the gtk-toolkit.
But since moz2seamonkey, no external libraries or similar is needed.

So what parts does HH take from macports, and for what reason?

> - OOo is now explicitly built against the MacOSX10.4u.sdk (so that it runs
> on Tiger even if it is built on Leopard).  However, 10.6, at least by
> default, does not include the 10.4 SDK.  Worked around that for now by
> patching places that ask for MacOSX10.4u.sdk to use MacOSX10.6.sdk instead.

Oh, that sounds bad. Isn't there even an option in xcode to install
the 10.4 sdk?

Also regarding all the compiler quirks: Does it still come with 4.0.x,
so that one could switch compilers to ignore all those problems?

> [...]
> - And, finally, smoketestoo_native fails with a crashing soffice.  :( This
> needs to be debugged further...

That still sounds like lot of effort to make building on 10.6 a smooth
experience :-/

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

[mac] Dropping tcsh support for Mac (all?) / changing configure's default

[Christian Lohmaier]

Hi *,

because of 105003, own bad experience with tcsh (random build freezes,
slow performance), encouraged by the kick4nt cws I'd like to go on and
drop tcsh support at least for Mac OS X.

dropping tcsh support means: changing configure's default to bash and
issue a warning (or error) when tcsh is selected.

The default login shell for Mac OS X is bash, so it definitely is
available and it is proven to work without problems (Pavel builds with
bash for years, so do I on all systems)

So now to the reason why the d...@ooo list is adressed as well:

Is somebody opposing chaning the default to bash for all systems?

I.e. is there anybody who can give a reason why the default should
stick with tcsh (be it for non-Mac or even all)?

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

Re: [mac] Nice tool for better and faster issue reporting/description

[Christian Lohmaier]

Hi Sebastien, *,

On Wed, Sep 9, 2009 at 7:51 PM, Sebastien
Plisson wrote:
>
> I thought it could be great to describe issues by just recording a short
> screencast

Well, "no"

A screencast forces you to spend the time watching it, the real issue
probably only comes at 3 minutes into the screencast, so this time is
forced on the QA and dev persons (and not only only one person, but
multiple).

So while a screencast is a good help to further describe and
demonstrate a problem, it is in no way a replacement for a good
description and a screenshot.

Especially when then people write issues with "see the screencast"
with no other explanation, we will have a big mess.

So again: Screencast are fine in /addition/, but not as replacement.

> For more information, bookmarklet, etc you can check it at
> http://www.screenjelly.com
>
> What do you think ?

I had a look to the "how to install OOo on mac" screencast you linked
from your blog and was very, very disappointed.

First of all the screencast wouldn't even start. It showed the
buffering circle thing but didn't start off.
By chanc I tried it with one of your public screencasts, the same problem.
It did work without problem however, when switching to fullscreen
mode. (i.e. in fullscreen mode the screencast showed playing). Use the
very same screencast in the regular mode and all you get is the
"buffering" symbol without any action.

So that for the technical part.

And then to the part I tried to point out in the first part of the
post: To get to the contents you need to watch. And that costs time.
The disappointment id even bigger when you don't get what the title
suggests.
The "how to install OOo on Mac" doesn't show how you install OOo on
Mac. It shows going to the OOo-homepage and clicking on the download
link. Before OOo is downloaded, the screencast recording is stopped.
You don't even see the opening of the dmg.

I'm not sure whether it is possible to easily edit the screencast with
that software, but many users probably won't anyway, and staring at a
progress meter is not very satisfying.

Please don't get me wrong, I myself did create screencasts already as
well (with pyvnc2swf) to illustrate something, and it can help to
illustrate stuff hard to put into words. But please don't forget the
words. You cannot search for contents shown within a screencast, you
can only search for the words in the description. Keep that in mind
and it will be a great help, otherwise not.

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

Re: [mac] Re: [dev] Re: [qa-dev] Looking for QA-Rep for cws cloph13 - create backwards compatible builds for Mac by using the developer-sdk during compilation

[Christian Lohmaier]

Hi Thorsten, *,

On Thu, Sep 10, 2009 at 11:49 AM, Thorsten Ziehm wrote:
>
> what is the state of your CWS? Today I saw it in a query on EIS and do
> not see any progress documented in the CWS. Do you think it will be
> ready soon to get it integrated in OOo 3.2?

>From my part it is ready - but unfortunately only Thorsten did provide
feedback (all OK so far)

> Release Engineering planned
> only one more build before the branch - m58 is in work now and m59
> should be the version for the branch. So the CWS must be ready until
> this weekend, I think.

As nobody did report any problems, and the cws doesn't touch any
actual code, only the makefiles, I think it is OK to integrate.

I myself didn't find any either (well, that doesn't count much I guess :-))...

ciao
Chrstian

PS: The build breakers of the ubuntu and solaris bots in connectivity
are unrelated to the cws - apparently they're using wrong mozilla zips
(the ones needed for m53 and newer, but the cws is based on m52, so
you'd need the old zips.
/MNSInclude.hxx:77:35: error: nsIAbLDAPAttributeMap.h: No such file or directory

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

[mac] Re: [qa-dev] Looking for QA-Rep for cws cloph13 - create backwards compatible builds for Mac by using the developer-sdk during compilation

[Christian Lohmaier]

Hi Aaron, Thorsten, *,

thanks for your kind offers :-) - see below

On Wed, Sep 2, 2009 at 7:54 PM, Thorsten Behrens wrote:
> Christian Lohmaier wrote:
>> (i.e. if you have a MAC OSX 10.4 and can check the installset, or if
>> you can verify the code changes by themselves,...)
>
> can test-drive the installset & do the code review; likely no time
> though for a proper testtool or tcm qa though.

Great - no worries, tinderbox did just finish building the Intel-installset:

http://termite.go-oo.org/install_sets/MacIntel-3589-cloph13-install_set.zip

Please give it a spin :-)

As for code review: Feel free to directly comment in the corresponding
issue or in EIS or ping me on IRC, write a mail (you get the idea :-))

Unfortunately no PPC build machine that runs with Leopard, only Tiger.
While it can be used to check that no reqressions are introduced while
building with Tiger, it isn't quite what the issue is about.
So again the plead for help:
@all:Got a PPC with Mac OSX 10.5? Can build OOo? Great - please give
cws cloph13 a shot!
(even if you cannot perform tests yourself, having a 10.5 built
installset for PPC would help a lot)

Nevertheless I'll build one on 10.4 and upload it tomorrow/later today.

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

[mac] Looking for QA-Rep for cws cloph13 - create backwards compatible builds for Mac by using the developer-sdk during compilation

[Christian Lohmaier]

Hi *,

I'm looking for a qa-rep for cws cloph13 (mercurial based)
http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300/cloph13
http://hg.services.openoffice.org/hg/cws/cloph13/
http://qa.openoffice.org/issues/buglist.cgi?issue_id=104566+104567+104568

citing from the cws' description:
"Mac OS X build environment comes with SDKs that enable the
builder to create backwards compatible builds/define the
baseline a build should be able to run.
Currently OOo's build system doesn't make use of this (not in
a sufficient manner that is) so that builds created on Leopard
(10.5) cannot be run on Tiger (10.4)."

besides that, it also includes some minor janitorial fixup (remove
duplicated OBJCXXFLAGS definitions) and support for ccache-skip for
(-x objective-c++ that otherwise prevents caching of the result)

While the last two can easily be qa'd by code review, the
backwards-compatibility should be tested on the corresponding systems.
It has been confirmed during issue 102735 that the modifications allow
to create a backwards compatible build, only the most basic
functionality has been tested. (It was also issue 102735 that made the
problem apparent)

I explicitly wrote should since please also raise your hand when you
can only do part of the job.

(i.e. if you have a MAC OSX 10.4 and can check the installset, or if
you can verify the code changes by themselves,...)

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

Re: [mac] New Building OpenOffice.org guide on its way!

[Christian Lohmaier]

On Wed, Jul 15, 2009 at 10:14 PM, eric.bachard wrote:
> Hi,
>
> Christian Lohmaier a écrit :
>>
>> I dislike what I see.
>
> Same for me.
>
>> Building OOo is not rocket science. In fact it is rather simple.
>
> I disagree : if the build is now so easy (when people ask on IRC, I have
> some doubts though), it is firstly because some people, including me spend
> years to simplify, improve  and change things.

I remember me removing gnucp requirement, I remember me fixing
JDK-detection,... So yes, the build-experience was improved. But that
doesn't matter/is even more a reason to get rid of the duplicated
build instructions.

We need a guide for current OOo, not for OOo as it was three or four years ago.
And since you seem to agree with me that building OOo is (now) simple,
I don't understand why you disagree.

When did you last hear a question about building OOo that is not
already answered by configure's output itself? When did you hear a
question that is not already answered on the current build-guide?

Just because people ask questions, doesn't mean it is because of the
complexity of the build-system. In fact I never heard questions about
building OOo on Mac on IRC.

Mac/Aqua really is the most smiple platform to build on. Install XCode
and you got all you need. (prebuilt mozilla/unowinreg.dll, ccache, and
on older systems subversion being the only additional tools you need.
you need.

And further thing: If it really is complicated, the build system needs
work, as it has received in the past.
Ideally you should not need any configure switches (mac only needs
--with-use-shell=bash (well, not needed, but you really should use it)
--disable-build-mozilla (use prebiult zips) and that's about it.

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

Re: [mac] New Building OpenOffice.org guide on its way!

[Christian Lohmaier]

Hi Per, *,

On Wed, Jul 15, 2009 at 10:01 PM, Per
Eriksson wrote:
> Christian Lohmaier skrev:
>> On Wed, Jul 15, 2009 at 9:07 PM, Per Eriksson
>> wrote:
> [...]
>> Having a "book" on how to build OOo gives a wrong impression or is way
>> too broad to be useful as reference.
>>
>
> Think about the following:
>
> We have new developers who need to find all the information related to
> building farily quickly and easily.

Yes. I agree. But in my eyes that means: The page(s) must be short.
With only the necessary parts listed. Everything else on seperate
pages.

> We have new developers who would benefit a lot to see the similarities
> between the platforms in the building process.

Exactly why it is so similar, the page needs to be small and the
os-specific parts left out.

> [...]
> For the Windows platform etc. there are several ways of building the
> software, and the instructions in its most compact form seem to take up at
> least 5-6 pages.

For community builders, there is only one way. Namely using cygwin
(and 4nt is going to be obsoleted/removed completely) anyway. And
virtually any newcomer will build using the personal-edition of the
MS-compiler (available free of charge). And the walkthrough page
(Building OOo on Windows with cygwin) is good for the prerequisites,
but the actual building (running configure and everything afterwards)
should not be part of the actual build instructions. Neither is the
(details of) OOo's source-code management.

Most developers wouldn't mind installing linux for developing OOo
anyway (compiling on linux is way faster than compiling on windows)

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

Re: [mac] New Building OpenOffice.org guide on its way!

[Christian Lohmaier]

Hi Per, *,

On Wed, Jul 15, 2009 at 9:07 PM, Per Eriksson wrote:
>
> I of course want the Mac instructions to be there as well, and will be
> copying the content from these pages in to the guide:
>
> http://wiki.services.openoffice.org/wiki/Mac_OS_X_Build_Instructions_%28X11%29

Don't even  bother with this one. If somebody really wants to build an
X11 version, that documentation is more than suitabel.

> http://wiki.services.openoffice.org/wiki/AquaBuild
>
> Are there any other pages that you think should be in the Building Guide?

No. I think there are already way too many build-instructions with way
too much duplication.

> Please let me know!
>
> The current version is here:
> http://wiki.services.openoffice.org/wiki/Development/OpenOffice.org_Building_Guide

I dislike what I see.

Why not taking the one guide that is there and point out what those
instructions are lacking/create pages to fill the missing parts.

Building OOo is not rocket science. In fact it is rather simple.
(compared to building mozilla for example). And even more so on Mac
OSX.

Having a "book" on how to build OOo gives a wrong impression or is way
too broad to be useful as reference.

my 2 cents.

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

Re: [mac] Java download for Mac

[Christian Lohmaier]

Hi again :-)

On Sun, May 31, 2009 at 8:57 PM, Per Eriksson
 wrote:
> Christian Lohmaier skrev:
>
> One more thing, does the user have to select Tools > Options and select the
> JRE after installation, or does it work out of the box?

It does work out of the box, and in fact that option doesn't actually
allow you to choose a different version of the JRE due to the way the
JVM is created on Mac.
See http://qa.openoffice.org/issues/show_bug.cgi?id=88987#desc27 for details

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

Re: [mac] Java download for Mac

[Christian Lohmaier]

Hi Per, *,

On Sun, May 31, 2009 at 8:49 PM, Per Eriksson
 wrote:
>
> We are working on the Setup Guide under the documentation project, and I
> wonder the following:
>
> What is the best download binaries for JRE for Mac OS X, Intel and PPC
> versions?
>
> http://www.apple.com/support/downloads/
> or
> http://www.java.com/
>
> Are there any differences, or benefits using the Mac binaries?

Java is already part of the default installation of Mac OSX, and it
also is updated via Mac's System Update. There is no need to point the
user (especially a Mac user) to www.java.com, (and no reason to point
to the apple site either)

ciao
Chritsian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

[mac] Languagepacks for Mac, pleast test & give feedback

[Christian Lohmaier]

Hi *,

to get things going again, I uploaded a new set of languagepacks for testing.

Please test and give feedback, either on the list, or on the spec-page:

http://wiki.services.openoffice.org/wiki/Mac_OS_X_languagepacks

torrents available here:

http://izbot.dyndns.org:6969/

The languagepacks are based on DEV300_m40 (wrt. localization status),
but should basically work on any OOo 3.x version

ciao
Christian

-
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org

Re: [mac] Instruction Memory Synchronization [was: no MacOSX PPC version of DEV300 m33/m34 ?]

[Christian Lohmaier]

Hi *,

On Thu, Nov 27, 2008 at 11:40 AM, Christian Lohmaier
<[EMAIL PROTECTED]> wrote:
> [...]
> Anyway: I'm tempted to confirm that the i18npool breakers are gone.
> Not 100% sure yet, but at least 5 builds in a row now built fine,
> without any breaker.

None of the builds with the patch did break in i18npool (and didn't
break at other points except when there are errors in the cws), so I
from my part am now also conviced that the problem is really solved
and not only occuring less often :-)

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Instruction Memory Synchronization [was: no MacOSX PPC version of DEV300 m33/m34 ?]

[Christian Lohmaier]

Hi *,

On Thu, Nov 27, 2008 at 11:40 AM, Christian Lohmaier
<[EMAIL PROTECTED]> wrote:
> On Thu, Nov 27, 2008 at 9:48 AM, Stephan Bergmann
> <[EMAIL PROTECTED]> wrote:
>
>> Is there a relevant issue and/or CWS through which we should integrate the
>> patch (also for the gcc_linux_powerpc bridge, I would say)?  If not, let me
>> know, and I will take care.
>
> My understanding is that the gcc_linux_powerpc one is enough to fix
> both problems, and the "don't strip executables" is not necessary (but
> I could be wrong on that)

Sorry, misread that - you mention linux ppc :-)

I think linux x64 is not 100% correct either,  since I often get
regcomp failures in testtools (running build often enough helps)
But I guess this is related to gcj/gij
regcomp -register [...]
"error (RuntimeException): [jni_uno bridge error] UNO calling Java
method initialize: non-UNO exception occurred:
java.lang.NullPointerException"
e.g.
http://tinderbox.go-oo.org/gunzip.cgi?tree=DEV300_m35&brief-log=1227726602.22207#err117

ciao
Christian

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Instruction Memory Synchronization [was: no MacOSX PPC version of DEV300 m33/m34 ?]

[Christian Lohmaier]

Hi Stephan, *,

On Thu, Nov 27, 2008 at 9:48 AM, Stephan Bergmann
<[EMAIL PROTECTED]> wrote:
> Maho NAKATA wrote:
>>
>> Hi Stefan, and *
>> I could provide DEV300_m33 with Stefan's patch. Very stable.
>> No hack for regcomp anymore.
>> Thank you very much,
>> -- Nakata Maho http://accc.riken.jp/maho/
>
> This news really makes me happy.  :)
>
> Is there a relevant issue and/or CWS through which we should integrate the
> patch (also for the gcc_linux_powerpc bridge, I would say)?  If not, let me
> know, and I will take care.

My understanding is that the gcc_linux_powerpc one is enough to fix
both problems, and the "don't strip executables" is not necessary (but
I could be wrong on that)

Anyway: I'm tempted to confirm that the i18npool breakers are gone.
Not 100% sure yet, but at least 5 builds in a row now built fine,
without any breaker.

> However, if anybody happens to know whether Mac OS X offers a function to do
> instruction memory synchronization,[...]

Sorry, no clue

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] no MacOSX PPC version of DEV300 m33/m34 ?

[Christian Lohmaier]

Hi *,

On Tue, Nov 25, 2008 at 1:25 PM, Stephan Bergmann
<[EMAIL PROTECTED]> wrote:
> On 11/25/08 11:03, Christian Lohmaier wrote:
>>
>> But did you have any problems in i18npool? That's another candidate
>> where builds often fail (running build often enough gets the module
>> built). Here, saxparser crashes IIRC.. If not stripping excecutables
>> would solve this problem as well... Would be great.
>
> Had no problem building i18npool.

Unfortunately didn't avoid the i18npool breaker. building cppu with
debug seems to be the only way to avoid the breaker here...

> (But remember, that was for just one
> build, and I still am not confident that the stripping issue is really
> causing the problem, and not only making it less likely that the problem
> will pop up---similar to the prior attempts at building certain files with
> different optimization levels.)

Still worth a try.

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] no MacOSX PPC version of DEV300 m33/m34 ?

[Christian Lohmaier]

Hi Stephan, *,

On Tue, Nov 25, 2008 at 10:06 AM, Stephan Bergmann
<[EMAIL PROTECTED]> wrote:
> On 11/18/08 02:49, Maho NAKATA wrote:
> [Stephan did have a look at the regcomp problems on the Mac (PPC]
> Anyway, the attached Build.sh worked for me (the build did not fail in
> testtools),

Sounds great! Will try the patch as well. Tinderbox doesn't always
fail in testtools, so might need a bit of time to check whether it
really solves the problem or whether it just makes the error less
likely to happen.

> but unfortunately the build failed in moz ("libIDL 0.6.3 or
> higher is required," which I do not know how to work around on that machine)

This is a bug in fink (repository system for external libraries) -
easiest "workaround" is to use precompiled mozilla-packages from
tools.openoffice.org (link/rename the universal binaries to the
architecture dependent name that configure expects (s/UB/P/)
http://tools.openoffice.org/moz_prebuild/680/index.html

> so that none of moz, connectivity, svx, basctl, binfilter, chart2, dbaccess,
> desktop, extensions, filter, forms, libxmlsec, sc, sd, sdext, starmath, sw,
> writerfilter, xmlsecurity, postprocess, packimages, instsetoo_native,
> smoketestoo_native were build yet.

from all of those, instsetoo_native would be the most interesting :-)
The others never did show problems here...

But did you have any problems in i18npool? That's another candidate
where builds often fail (running build often enough gets the module
built). Here, saxparser crashes IIRC.. If not stripping excecutables
would solve this problem as well... Would be great.

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] mac + moz project with fink and "--with-mozilla-toolkit=xlib" is now preferable

[Christian Lohmaier]

Hi *,

On Thu, Oct 23, 2008 at 8:24 AM, Stephan Bergmann
<[EMAIL PROTECTED]> wrote:
> Just in case it is of interest to anyone, the below is an excerpt from [...]

Just for completion:

Of course you can also use the prebuilt archives that are available here:
http://tools.openoffice.org/moz_prebuild/680/
(You only need to either rename or link the "UB" ones (universal
binaries) to the "I" or "P" ones.

or create your own prebuilt binaries to save some buildtime
http://wiki.services.openoffice.org/wiki/Building_OpenOffice.org#create_prebuilt_mozilla_and_use_that_instead_of_recompiling_everytime

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] More HDD on Good-Day server!

[Christian Lohmaier]

Hi *,e

On Tue, Oct 14, 2008 at 10:37 AM, Uwe Altmann <[EMAIL PROTECTED]> wrote:
> Maho NAKATA schrieb:
>> I asked Maeda-san and Nishiyamasa of Good-Day to add more HDD capacity.
>> They are really kind, and immedately said ok for me. Really appreciated.
>
> This is indeed very generous of them and so we all are really
> appreciated of that.
> Thank you for your reliable work on mac port and for asking them - and
> thank to Maeda-san and Nishiyamasa to be so gracious to the mac port
> over all these years and now again.

Yes, much appreciated! Thanks a lot to you & the sponsors :-)

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] openoffice 3,0 for ppc?

[Christian Lohmaier]

Hi *,

On Tue, Oct 14, 2008 at 11:16 AM, Uwe Altmann <[EMAIL PROTECTED]> wrote:
>
> Provincia San Benedetto di Don Orione schrieb:
>
>>> thank you for the answer! Are there differences between rc4 and the
>>> official one?
>
> no. except version string of course :-)

To clarify: Only the filename of the dmg is different, everything in
the package is the same.

And the mirror that hosts all the builds is up and running:
http://ooopackages.good-day.net/pub/OpenOffice.org/MacOSX/3.0.0rc4/
ftp://ooopackages.good-day.net/pub/OpenOffice.org/MacOSX/3.0.0rc4/

(It is located in japan, so transfer speeds from Asia/Japan to your
country might not be the best)

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] New mirror is empty (was: Re: [mac] Re: [releases] More HDD on Good-Day server!)

[Christian Lohmaier]

Hi Eric, *,

On Tue, Oct 14, 2008 at 10:26 AM, Eric Hoch <[EMAIL PROTECTED]> wrote:
> Hi Maho,
> Am Sat, 11 Oct 2008 06:48:26 +0900 (JST) schrieb Maho NAKATA:
>> From: Maho NAKATA <[EMAIL PROTECTED]>
>> Subject: [releases] More HDD on Good-Day server!
>> Date: Fri, 10 Oct 2008 10:16:25 +0900 (JST)
>>> If you access via
>>> ftp://ooopackages.good-day.net/pub/OpenOffice.org/MacOSXod
>>> you can see as a symbolic link.
>
>> Now via http, we can follow the link. So everthing works fine now!
>> thank you very much!!
>
> This directory is as of today 14/10/2008 10:24 (CEST) emtpy

Either it is fixed already, or you looked at the wrong spot.
both
ftp://ooopackages.good-day.net/pub/OpenOffice.org/MacOSX/3.0.0rc4/
and
http://ooopackages.good-day.net/pub/OpenOffice.org/MacOSX/3.0.0rc4/
have all the Intel an PPC versions...

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] macleofix4x11 needs a QA resp

[Christian Lohmaier]

Hi James, *,

On Thu, Oct 9, 2008 at 5:41 PM, James Mckenzie
<[EMAIL PROTECTED]> wrote:
> Christian Lohmaier <[EMAIL PROTECTED]> at Oct 9, 2008 8:26 AM wrote about Re: 
> [mac] macleofix4x11 needs a QA resp
>>On Thu, Oct 9, 2008 at 5:22 PM, James Mckenzie
>><[EMAIL PROTECTED]> wrote:
>> [...]
>>Doing QA for a CWS and "doing QA for MacOSX American English versions"
>>is not related to each other and more importnat: not mutually
>>exclusive.
> [...]
> The other thing is that I don't like duplicating someone else's work and feel 
> that SUN is much better at QA than I am.

Maybe this is a misconception here: Doing QA for a CWS is not
duplicating somebody else's work.
Nobody else will do QA on that same cws in addition.

>  Since the Mac OS X AQUA version is now offical and they are conducting QA of 
> the 3.0 releases and may conduct QA of the 2.4.2 version, I will not be 
> conducting QA of them unless SUN is not.

But they won't do QA work on each an every cws. That is exactly the
point where the community can make a big difference!
The biggest problem in contributing code has always been to find
somebody who is willing (and able to) QA your code.

The bottleneck is not integration into the master or the actual coding
itself - it is finding somebody who has the time and knowledge to flag
the cws as "approved by QA" - the rest doesn't add much delay to it.

Don't get me wrong, I'm not trying to talk you into doing stuff you
don't want to do. It is perfectly fine to say: No, thanks, I have
other plans for my time.
I'm just trying to clarify that your assumption (doing QA on a cws is
waste of time, since Sun will be doing it anyway) is wrong.
Sun is happy if other people will do QA (since then, Sun's
QA-engineers can work on Sun's own cws or do other tasks).

Qualified QA for a cws is always welcome, and I cannot state this
often enough: QA for a cws makes the difference whether a CWS can be
integrated next week, or in two months.
(next week: there is QA available, can work on the cws and approve it,
two months: need to wait until a Sun-Engineer finds the time to do it)
QA by a non-Sun-community-member for a cws is not duplicating somebody
else's (Sun's) work.

>  Simple, my efforts can be better spent working on other things (like riding 
> 50KM per day up some hills we have here.)

I understand that you have other priorities than doing work on OOo -
but your reasoning should not be based on wrong assumptions.

ciao
Christain

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] macleofix4x11 needs a QA resp

[Christian Lohmaier]

Hi James,

On Thu, Oct 9, 2008 at 5:22 PM, James Mckenzie
<[EMAIL PROTECTED]> wrote:
>
> I had originally responded to the 'other' CWS you had set up, but I am no 
> longer available to do QA on this.
>
> Since SUN has taken over QA of the official releases of the MacOSX American 
> English versions, I will be moving to the background and will no longer be 
> conducting QA of these builds.

Doing QA for a CWS and "doing QA for MacOSX American English versions"
is not related to each other and more importnat: not mutually
exclusive.

But well, your decision.

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Re: Mac OS X 10.5.5 sabotages X11 (and pdf files too it seems)

[Christian Lohmaier]

On Sun, Sep 28, 2008 at 5:09 PM, eric b <[EMAIL PROTECTED]> wrote:
> Le 28 sept. 08 à 16:12, Christian Lohmaier a écrit :
>
>>> Mind you with
>>> the time that I've spent on it so far, I probably should have spent the
>>> half/full day required to get it sorted.
>>
>> You should have spent two minutes filing an issue of type "Patch".
>
> Sure, provide a patch is two minutes, indeed.  But the bottleneck are QA and
> code integration process : just discouraging people to provide code.

That is missing the point.

Did providing a solution in a blogpost solve the problem?
No.

Will RE or some other contributor look in blogs for patches?
No.

Will somebody, even after being told: Look, somebody posted some code
on his blog just grab it and take it?
Hell no, especially when there are no statements wrt.
copyright/licencing in that blog. (Of course the patch we're talking
about is small, but just to make my point more clear)

Will somebody working on a cws, and being pointed to an issue with an
attached patch include that patch in his open cws?
Very likely if the patch is straightforward and if it touches a module
already part of that cws.

Will someone providing builds apply patches from a blog?
Very unlikely.
Will someone providing builds apply patches from IssueZilla?
less unlikely, esp. if it is an annoying thing that gets fixed (so
that you don't want to wait for the next (or second next) milestone
with a cws that fixes the problem.

And wrt. delays and such: There were enough open mac-related cws
lately, so no need to create a cws just for that patch. And if you
hook up to an existing cws by somebody else, you don't have to deal
with all the administrativa. (that btw. is not that much. The only
hard part is finding someone who is willing to do QA, but if you ask
on the Mailinglist, you'll get some help anyway).
If you got QA, then you're set. Code-Integration nowadays is fast when
the cws is approved/nominated (and when there's not a version control
system migration at the same time)

Hope my point of view is now understandable/more clear.

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Re: Mac OS X 10.5.5 sabotages X11 (and pdf files too it seems)

[Christian Lohmaier]

Hi Rainer, *,

On Sun, Sep 28, 2008 at 5:00 PM, Rainer Schuetz
<[EMAIL PROTECTED]> wrote:
> At first sight the issue-tracker of OO is intimidating and looks over
> complex (exposes too much of its data-structure) - I can understand if users
> turn away from it.

Shaun is not just any random user. He has experience wrt IZ and OOo,
and he is Lead of the Mac porting project after all.

And we're not talking about some random problem report, but filing a patch.

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Re: Mac OS X 10.5.5 sabotages X11 (and pdf files too it seems)

[Christian Lohmaier]

On Sun, Sep 28, 2008 at 3:54 PM, Shaun McDonald
<[EMAIL PROTECTED]> wrote:
> On 28 Sep 2008, at 13:48, Christian Lohmaier wrote:
>> On Sun, Sep 28, 2008 at 11:58 AM, Shaun McDonald
>> <[EMAIL PROTECTED]> wrote:
>>>
>>> [...]
>>> I have just tested OOo 2.4.1 on Mac OS X 10.5.5, without having ever
>>> installed some other X11 software. I also applied my patch at
>>>
>>> http://blog.shaunmcdonald.me.uk/2008/03/ooo-possible-fix-for-the-command-timed-out-error-on-leopard/
>>> and have absolutely _no_ problems whatsoever starting OpenOffice.org X11!
>>
>> Why don't you attach the patch to an issue or commit it to  a cws? I
>> bet the problem would have been solved a long time ago.
>
> I was intending on creating or commiting this to a CWS, however I find it
> far too difficult to create and commit a tiny patch like that.

Attaching a patch to an issue doesn't involve creating a cws.

> Mind you with
> the time that I've spent on it so far, I probably should have spent the
> half/full day required to get it sorted.

You should have spent two minutes filing an issue of type "Patch".

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Re: Mac OS X 10.5.5 sabotages X11 (and pdf files too it seems)

[Christian Lohmaier]

On Sun, Sep 28, 2008 at 2:52 PM, Eric Hoch <[EMAIL PROTECTED]> wrote:
> Am Sun, 28 Sep 2008 14:48:43 +0200 schrieb Christian Lohmaier:
>> On Sun, Sep 28, 2008 at 11:58 AM, Shaun McDonald
>> <[EMAIL PROTECTED]> wrote:
>>> [...]
>>> I have just tested OOo 2.4.1 on Mac OS X 10.5.5, without having ever
>>> installed some other X11 software. I also applied my patch at
>>>
> http://blog.shaunmcdonald.me.uk/2008/03/ooo-possible-fix-for-the-command-timed-out-error-on-leopard/
>>> and have absolutely _no_ problems whatsoever starting OpenOffice.org X11!
>>
>> Why don't you attach the patch to an issue or commit it to  a cws? I
>> bet the problem would have been solved a long time ago.
>
> I already had a showstopper issue dealing with it for 2.4.1 but
> someone deleted for whatever reason from the list of potential
> showstoppers and so it got lost.

I don't mean to mention some blogpost in some issue, but to actually
add the patch as an attachment.

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Re: Mac OS X 10.5.5 sabotages X11 (and pdf files too it seems)

[Christian Lohmaier]

Hi Shaun,

On Sun, Sep 28, 2008 at 11:58 AM, Shaun McDonald
<[EMAIL PROTECTED]> wrote:
> [...]
> I have just tested OOo 2.4.1 on Mac OS X 10.5.5, without having ever
> installed some other X11 software. I also applied my patch at
> http://blog.shaunmcdonald.me.uk/2008/03/ooo-possible-fix-for-the-command-timed-out-error-on-leopard/
> and have absolutely _no_ problems whatsoever starting OpenOffice.org X11!

Why don't you attach the patch to an issue or commit it to  a cws? I
bet the problem would have been solved a long time ago.

> [...]

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Looking for QA-Rep for cws cloph11 (removing no-longer used build-defines, minor code-cleanup)

[Christian Lohmaier]

Hi Jason, *,

On Wed, Sep 10, 2008 at 6:41 PM, Jason Stephenson <[EMAIL PROTECTED]> wrote:
> Christian Lohmaier wrote:
>> On Wed, Sep 3, 2008 at 1:17 AM, Jason Stephenson <[EMAIL PROTECTED]>
>> wrote:
>>>
>>> I know this is not an official QA response,
>>
>> But I was looking for a QA-Rep, not only for comments.
>> Why do you think it is not an official "QA response"/what is missing
>> in your opinion?
>
> Well, I see how to add myself as a QA-Rep in EIS, but I don't see my ID on
> the list, so I hesitate to just type myself in.

Well - if you tell me your OOo-login/address I can type you in. Don't
hesitate to add yourself (although I don't know whether it is possible
to set oneself as QA of a cws one doesn't own - just try and we'll
see)

> It does look good to me, and if you need someone to sign off on it, and if I
> am considered qualified, then I'll gladly put my name in as QA-Rep.  Thing
> is, I only built it on Leopard Intel, so I can't say if there would be
> problems on another arch.

Well - I did announce the cws here, mentioned it on the IRC channel a
few times, people had a chance to have a look :-)
And as the cws is not critical in any way (I mean it only removes
per-facto dead code: It is Mac OSX only and nobody uses Mac OSX 10.2
to build anymore, the aqua version requires 10.4 as baseline anyway)
so there shouldn't be any effects on other operating systems - and I
have the PPC tinderbox here that doesn't have any problems with it
either..

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Looking for QA-Rep for cws cloph11 (removing no-longer used build-defines, minor code-cleanup)

[Christian Lohmaier]

Hi Jason, *,

On Wed, Sep 3, 2008 at 1:17 AM, Jason Stephenson <[EMAIL PROTECTED]> wrote:
>
> I know this is not an official QA response,

But I was looking for a QA-Rep, not only for comments.
Why do you think it is not an official "QA response"/what is missing
in your opinion?

> but the changes in
> cws_dev300_cloph11 look good to me, and it builds just fine.

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] unopkg fails on PowerPC

[Christian Lohmaier]

Hi Maho, *,

On Wed, Sep 10, 2008 at 4:19 AM, Maho NAKATA <[EMAIL PROTECTED]> wrote:
> From: Maho NAKATA <[EMAIL PROTECTED]>
> Subject: [mac] unopkg fails on PowerPC (Re: [mac] unopkg waiting for Enter or 
> so?)
> Date: Wed, 10 Sep 2008 10:58:17 +0900 (JST)
>
>> It seems I'm facing a different issue.
>> I've got bunch of errors while making install sets on PPC
>> since DEV300_m20.
>>
>> % grep ERROR 
>> /Volumes/ooo-dev/Tiger/work.DEV300_m31.AQUA/DEV300_m31/instsetoo_native/unxmacxp.pro/OpenOffice/dmg/logging/ar/log_DEV300_ar.log
>> ERROR: Could not execute "unopkg add --shared --verbose 
>> ../share/extension/install/dict-es.oxt -env:UserInstallation=file:// 2>&1 |"!
>> ERROR: unopkg add --shared --verbose ../share/extension/install/dict-es.oxt 
>> -env:UserInstallation=file:// 2>&1 | failed!

I also build on Tiger/PPC - and builds based on DEV300_m30 or
OOO300_m2 and newer are aqua builds as well on the tinderbox. I don't
build additional languages though.

> Why on PPC
> UserInstallation=file://

I can confirm Stephan's comment - it uses the TMP environmentvariable
here (with the ooopackaging added).

> and on Intel
> UserInstallation=file:///tmp/ooopackaging/i_61220963120/unxmacxi.pro
> ?
>
> BTW: If one do many tries, build progress without error:
> Success: Executed "unopkg add --shared --verbose 
> ../share/extension/install/dict-af.oxt -env:UserInstallation=file:// 2>&1 |" 
> successfully!

I can only guess that it is related to cppu. More or less every build
on the PPC stops in i18npool here.
To bypass that problem, I rebuild cppu with debug=true, then i18npool
finishes without problem. Maybe that is why it doesn't break here. Or
maybe it just fails less often here

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Looking for QA-Rep for cws cloph11 (removing no-longer used build-defines, minor code-cleanup)

[Christian Lohmaier]

Hi Jason,

On Wed, Aug 27, 2008 at 12:28 AM, Jason Stephenson <[EMAIL PROTECTED]> wrote:
>
> I just need a refresher on how to chekcout a CWS into an existing CVS
> checkout, unless I find my notes first.

Does this help:
http://wiki.services.openoffice.org/wiki/Building_OpenOffice.org#Building_a_CWS

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[mac] Looking for QA-Rep for cws cloph11 (removing no-longer used build-defines, minor code-cleanup)

[Christian Lohmaier]

Hi *,

I'm looking for a QA-Rep for cws cloph11:
http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300/cloph11
http://www.openoffice.org/issues/buglist.cgi?issue_id=91352+92913+92922

It is a rather small-scope cws, and basically is Mac-only (hence this list)

QA in that case is mainly code-review, since nothing (should :-) )
change in the resulting Office Suite.

If you're willing to do so, either post to this list, talk to me on
IRC, add a comment to EIS,...

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Error building DEV300_m28

[Christian Lohmaier]

Hi Michel,

On Thu, Aug 7, 2008 at 1:46 PM, michel RENON <[EMAIL PROTECTED]> wrote:
> Le 7 août 08 à 13:32, Christian Lohmaier a écrit :
>> it is in module cppunit.
>
> in DEV300_m28, there are folders "cppu", "cppuhelper", "cpputools", but no
> "cppunit"...
>>
>>> Did i forgot to apply a patch ?
>>
>> Your checkout is incomplete - how did yuo check it out?
>
> i just followed indications in
> http://wiki.services.openoffice.org/wiki/AquaBuild (and even i did a
> copy/paste from browser to the terminal) :
> export CVSROOT=":pserver:[EMAIL PROTECTED]:/cvs"
> cvs login  (password is 'anoncvs' )  + Enter
> cvs -z3 co -r DEV300_m28 OpenOffice3 swext apache-commons tomcat hyphen

OpenOffice3 is wrong. That alias has not been
approved/announced/declared as ready.

Use OpenOffice2 - and for the other ones: Use Extensions3
i.e. do
cvs co -r DEV300_m28 OpenOffice2
cvs co -r DEV300_m28 Extensions3

But for your case I think it is enough to checkout cppunit.

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Error building DEV300_m28

[Christian Lohmaier]

Hi Michel,

On Thu, Aug 7, 2008 at 12:00 PM, michel RENON <[EMAIL PROTECTED]> wrote:

> Well, i try to make the first build, as indicated in the aquabuild page in
> the wiki : DEV300_m28
> But i got an error while compiling file "testshl2/source/getopt.cxx" : he
> tries to include "testshl/getopt.hxx" that doesn't exists, anywhere,

it is in module cppunit.

> Did i forgot to apply a patch ?

Your checkout is incomplete - how did yuo check it out?

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Can't unsubscribe

[Christian Lohmaier]

Hi Alex, *,

On Fri, Aug 1, 2008 at 1:16 PM, Alex Zachopoulos
<[EMAIL PROTECTED]> wrote:
> Is it possible to unsubscribe from the list?
> I have, and got all the confirmation from ezlm whatever, but the mssgs keep
> on coming.

You need to reply to the /request/ for confirmation ezmlm sends you.
It basically asks: Is it really OK unsubscribe you?
By replying, you answer: Yes, unsubscribe me. Only after that reply
you're really unsubscribed.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Any marketing wrt Beta2?

[Christian Lohmaier]

Hi Maho, *,

On Fri, Jul 11, 2008 at 3:02 AM, Maho NAKATA <[EMAIL PROTECTED]> wrote:
>
> I provided all localized packages both for Intel and PPC.
> I think some of Intel builds are redundant, though.

IIRC beta2 still misses one of the essential mac-specific cws, so
maybe make a big announcement for third beta. (key combo and maybe
"crash on close when help was used")

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] DEV300_m21 has been provided Re: [mac] [Intel] [Leopard] Frequent crashes

[Christian Lohmaier]

Hi Eric, *,

On Mon, Jun 30, 2008 at 2:01 PM, eric b <[EMAIL PROTECTED]> wrote:
> Le 30 juin 08 à 13:08, Christian Lohmaier a écrit :
> [...]
> No, that's not my idea, but just a fact: people (not me) believe Maho's
> builds are "releases". Here is the problem.

That might indeed the problem. But your solution is wrong. Not
providing milestone builds surely is not a solution to a communication
problem.

> Read (in the thread) my answer to Philipp, where I wrote "We all agree the
> only reason to provide such milestones is for QA. "

Ok, so we're clear on that.

> [...] but the fact is, people who are not aware of QA are
> downloading them.

So: Fix that! Make it clear to people that the builds are for QA/testing only.

Again: Not providing builds is not a solution to that problem.

> I think Jason mails is a good summary of what I think.

But he doesn't mention the root cause either:

Why do people think that the builds are releases.
Obviously linux and windows users have no problem in understanding
that Pavel builds are snapshots/testing builds. Are Mac users more
stupid that linux/windows users? I don't think so.

>> He did never announce them to "users", he announces availability of
>> the builds on developer lists.
>> So everyone who downloads the builds should know that those are only
>> snapshots, not "releases".
>
> The reality is different. Here is the problem.

Why do (in your opinion) people think that the builds are "releases"
(i.e. ready for personal use as opposed to testing only/use at your
own risk)?

>>> So, I ask to find a solution, to prevent such issues in the future.
>>
>> What issue? That stupid users download non-released software?
>
> "That stupid users downloading non-released software " as you wrote, will
> propagate a bad image of the mac port.
>
> And we don't need that at all.

Well, the feedback I notice from the german project's lists, form IRC
that people rather are impressed by the progress of the port than
complain about a quirk here or there. Maybe that is because in
german-lang the communication is clear about those snapshots, maybe
because the users who give feedback already use OOo for some time and
few new users try the snapshots (maybe again because people know that
those are snapshots).

And now comes a "weired" theory:
Maybe people download the snapshots, because there just are too few
"official" testing-releases?

The port makes so much progress, that a snapshot that is a couple of
months old just doesn't reflect the current status.
I go further: Such an old status can even be worse than a crash in a
newer version, when the rest of the system feels snappier, feels more
integrated/more impressive.


>> Then
>> yes: Do something about it.
>
> Indeed:  that's why I proposed to not provide all the milestones.

And I (and others say): Buying a louder horn or driving at low speed
will not fix your breaks.

> [...]
>> It is true that some builds have problems. These faults are a problem with
>> QA. (of the cws that are about to be integrated, or just because the
>> milestones/the combination of the cws
>> is not tested as well as it should).
>> This is not Maho's fault as QA is not his job.
>
> Just about the job, isn't it Maho who does manage QA ?

of course everywhere I wrote "Maho doesn't do QA" or "Maho's job is
not QA" I was refering to his status against the build he provides. He
is not responsible for doing Mac-Teams's QA work, he is not
responsible for testing every build he provides.

> [...]
>> He spends his time and ressources on doing builds, not development, not
>> QA.
>
> As QA lead, this is not the best example  :-)

being QA-lead doesn't mean one has to do QA on everything himself
(more the contrary, do the administrative stuff, give guidance, but
not do the QA itself)

>>[...]
> Sure but when a bug leading to instant and random crashes is well known, and
> needs time before the fix to be integrated, it sounds reasonable to stop
> providing public milestones in meantime, at least until the fix has been
> integrated.

Might be true, but then just ask Maho to not provide builds until
them, ask him to add a big, fat disclaimer, or ask him to include the
patch in his builds.
Don't ask him to generally not provide builds.

>> That's why it is even more important that people do find those bugs.
>
> That's what we did: I announced the crashes on IRC before WWDC.  And there a
> bit after .. and just now, some people seems to discover the issue.

Announcing on IRC doesn't help making Maho aware of the problem.

>> It also shows that communication of the Mac 

Re: [mac] DEV300_m21 has been provided Re: [mac] [Intel] [Leopard] Frequent crashes

[Christian Lohmaier]

Hi Eric, *,

On Mon, Jun 30, 2008 at 1:40 PM, eric b <[EMAIL PROTECTED]> wrote:
> Le 30 juin 08 à 13:13, Christian Lohmaier a écrit :
>>> [...]
>>> Eric's point is that having unstable code available to the general public
>> [...]
> A lot of people are subscribed/read the lists (they are public, and often
> listed on gmane),

People who read the lists should know what the builds are about.

> and publy the links on their blogs or whatever other way
> of communication.

And when people do that, then having a seperate server for the regular
snapshots won't help.
Since those people would publish the links from the other server as well.

> [...]
> Again -> the only protection (for the image of the port) would be to use
> another server QA dedicated, and reserve only known-to-be-working builds on
> good-day, as "snapshots".

Well, this sounds a lot different from your initial demand.

But I still don't see it as the "only" protection, and by far not the
most efficient one to prevent this.

One needs to put the efforts to the very bottom of the queue, not at
the top of it.
beware - a car-related analogy will follow - as such it will always
have weak points, but I'll try to make my point clear:
If your car doesn't stop when you hit the break, what will you do:
* Buy a louder horn, so that you can alarm people to get out of your way
* Only drive at 10 km/h, so when you hit stuff, you won't break much
* Fix your breaking system

So I think fixing the breaking system is the best solution (work
towards milestones being what the milestone rules suggest: Always
building, always in a state in such no new problems are introduced)
Of course, driving slowly can help to prevent causes of an accident -
but this doesn't work when running downhill (when a release is near,
you cannot work up all the work that should have been done during the
milestone tests)

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] DEV300_m21 has been provided Re: [mac] [Intel] [Leopard] Frequent crashes

[Christian Lohmaier]

Hi Jason, *,

On Mon, Jun 30, 2008 at 12:36 PM, Jason Stephenson <[EMAIL PROTECTED]> wrote:
>
> Certainly, *we* expect that the builds could be unstable, but what about J.
> Random Blogger who downloads the latest snapshot (more or less at random) to
> look at the native Aqua of OO.o 3.0 beta and sees these apparently random
> crashes?

Just answer: How did J. Random Blogger know that there are snapshot
builds available at all?
Where did he get the download URL from?
/*That*/ is the point where you need to improve communication, not at
the lower end, the milestone builds themselves.

(And I'm really curious to getting an answer on the question, since
that is really a point where one can easily improve things)

> [...]
> Eric's point is that having unstable code available to the general public

Sure, but just answer the above. Maho's build are not announced to the
general public (at least not by Maho himself) - so how could it be the
fault of the milestone builds themselves?

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] DEV300_m21 has been provided Re: [mac] [Intel] [Leopard] Frequent crashes

[Christian Lohmaier]

Hi Eric, *,

Disclaimer: This is a post about the facts/about the situation, not
about persons.
It doesn't matter whether Maho does the builds or some other person.
It doesn't matter who demands that no/not all milestone builds are
provided. So always take this into account. Don't take this
personally.

On Mon, Jun 30, 2008 at 8:43 AM, eric b <[EMAIL PROTECTED]> wrote:
> Le 30 juin 08 à 03:13, James McKenzie a écrit :
>
>> eric.bachard wrote:
>> Eric, Maho has NEVER tested his builds to my knowledge.
>
> I know  :-/

OK, so we all agree on this /fact/.

>> That is what the QA testing team is here for.
>
> Then something must be improved, because there is obviously a problem.

So no disagreement here either: QA for Mac could be improved.

Wrong conclusion: Maho must do QA.

>> Maho fixes problems he encounters with the build process.
>
> That's not true: there are PowerPC builds provided by Maho, and including
> jvmfwk fix. afaik, this fix is in aquavcl08, not yet integrated.

You blame Maho for not following the list, but why don't you follow
the list (more on that at the end of the post)?

> So ?

Right: That doesn't really matter.

> [...]
> Yet another reason to select good milestones, and not provide all.

Again you're basing all your argumentation on a wrong starting point.
Your idea is that Maho's build are "releases" for the public. This is
just not the case.

Maho's builds are milestone builds for interested users/developers/QA-folks.

He did never announce them to "users", he announces availability of
the builds on developer lists.
So everyone who downloads the builds should know that those are only
snapshots, not "releases".

> [...]
> Here is development mailing list.

So agreement that this is is a development list. And I'm pretty sure
there's no doubt that [EMAIL PROTECTED] is a development list as
well.

> When the milestones are unusable, no need
> to provide them, and better wait for the integration of the fix.
>
> That's all.
>
> What happens here:  developers said "hey, there is a problem ..."   .. and
> nobody did care.

Correct fact.

> Result: unusable milestone have repeatably being provided.

Correct fact (albeit "unusable" differs in perception, unusable
regarding a specific functionality, well, doesn't matter - there
definietely were "not-perfect" builds)

Wrong conclusion: It is Maho's fault and Maho should not provide
milestone builds.

> So, I ask to find a solution, to prevent such issues in the future.

What issue? That stupid users download non-released software? Then
yes: Do something about it.

Wrong conclusion: "forbid" Maho to publish milestone builds.

(correct: Educate the users about the fact, write big letters that
those are un-QA'd builds or something)

> I don't want to support my own builds. I'm only interested with code
> understanding, and provide builds including new code for some testers, to
> have the faster feedback.

But how does that conflict with providing milestone builds? Those
offer build including new code for some testers, to have faster
feedback.
With the additional point that those code is already integrated. Bugs
found there are already in the code and needs to be fixed.
In "hacky" builds noone can be sure what really ends up in the
product, so the results may or may not be useful in the end.

Wrong conclusion of the above statement: You are not allowed to
provide cws builds.

>> Otherwise, Maho is doing what he said he would do and I, for one, would
>> not want him to stop.

Me neither.

So to sum up:

Maho just builds every milestone and uploads every milestone (if time permits).

(Sun would do the same if they could do it by a snap of their
fingers/if they had the ressources, so any argument telling "Sun skips
build as well" is plain wrong. Since if the reason for skipping would
be "the master has problems", then the integration process of the cws
would have been seriously flawed. The rule for a milestone is: No
known additional issues. There might be *rare* exceptions to this rule
though)

It is true that some builds have problems.
These faults are a problem with QA. (of the cws that are about to be
integrated, or just because the milestones/the combination of the cws
is not tested as well as it should).
This is not Maho's fault as QA is not his job. He is a provider of
builds. He spends his time and ressources on doing builds, not
development, not QA.

It is true that users use development builds (the milestones or beta)
and find bugs.
See above: This is a problem with QA. Those problems should not have
been introduced in the milestone in the first place. (but this is only
theory, you cannot test each and every feature in all environments to
catch all bugs).
That's why it is even more important that people do find those bugs.
It shows that they care, it shows that there is a problem with the
code. If the problem is already known: The better, shows that the
developers did work quickly for a fix.
If the problem is known for a long time, for a co

Re: [mac] Broken link

[Christian Lohmaier]

Hi Larry, *,

On Tue, Jun 24, 2008 at 8:13 AM, Larry Gusaas <[EMAIL PROTECTED]> wrote:
> The link for OO.o 3Beta for PPC on the Mac porting page
> (http://porting.openoffice.org/mac/download/aqua-PPC.html) is broken. I
> gives a not found message.

Cannot reproduce. the link point to
http://ooopackages.good-day.net/pub/OpenOffice.org/MacOSX/3.0.0beta/
and that contains the builds.
Probably already fixed in the meantime.

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] [Fwd: [porting-cvs] CVS update [hdu_aqua2008-04]: /porting/www/mac/index.html]

[Christian Lohmaier]

On Fri, Apr 11, 2008 at 12:15:47PM +0200, Shaun McDonald wrote:
> cloph,
> 
> This has been done intentionally as a tag, so that we can confirm the  
> changes before making them live. If anyone sees errors, please make  
> the relevant changes, or comment on them.

It shows that most of the time the poster didn't take the time to read
the post.

:> Why does top-posting suck big time? 

> On 11 Apr 2008, at 12:19, Christian Lohmaier wrote:
> > [...]
> >It is unusual to use a tag for webpages. The webpages will only serve
> >HEAD. But as this is labeled "work in progress", this is intentional..
^^^
ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] [Fwd: [porting-cvs] CVS update [hdu_aqua2008-04]: /porting/www/mac/index.html]

[Christian Lohmaier]

Hi James, *,

On Thu, Apr 10, 2008 at 08:14:54PM -0700, James McKenzie wrote:
> Is this viewable anywhere?  The pages on the OpenOffice.org web site 
> still point to the old versions.

Usually, you only need to do a force refresh in your browser. OOo's
pages are served by a proxy-cache. But...

> I would like to point out that there are several typographical errors in 
> them and attempt to fix them before the public can view them.

Once it is in cvs, it is available to the public...

> Tag: hdu_aqua2008-04

It is unusual to use a tag for webpages. The webpages will only serve
HEAD. But as this is labeled "work in progress", this is intentional..
(and probably fits your idea with "before the public can view them")

But there you have it how to grab the file and fix the typos:
Check it out with the tag hdu_aqua2008-04

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] DEV300_m4 breaks in helpcontent2 (PPC/Tiger)

[Christian Lohmaier]

Hi Stephan, *,

On Thu, Apr 03, 2008 at 06:37:44PM +0200, Stephan Bergmann wrote:
> Christian Lohmaier wrote:
> >I tried to build --with-stlport=yes to force OOo's copy, but this
> >doesn't work anymore. It breaks in stlport.
> 
> Yes, this configuration no longer works.  Ideally, it should no longer 
> be possible to create such a configuration with config_office/configure, 
> but nobody bothered to adapt configure accordingly (at least I didn't). 
>  Is this seen as a problem worth addressing?

No, I don't think it is worth adressing - I only tried to use it to see
whether helpcontent then still would break.

But as the reason for the failure is now known (and a fix is available)
that should be enough.

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] DEV300_m4 breaks in helpcontent2 (PPC/Tiger)

[Christian Lohmaier]

Hi *,

On Tue, Mar 25, 2008 at 03:39:27PM +0100, Stephan Bergmann wrote:
> eric b wrote:
> >Le 25 mars 08 à 10:08, Stephan Bergmann a écrit :
> >>
> >>Smells like , 
> >>right?
> >
> >
> >That's what I believed at the beginning, but in fact I had to create a 
> >new issue, on ab behalf :
> >
> >http://qa.openoffice.org/issues/show_bug.cgi?id=84145
> >
> >IMHO, the issue is there since weuse system stl, not sb83
> 
> using system stl became the default with sb83, which would explain 
> cloph's problems starting with sb83...

I tried to build --with-stlport=yes to force OOo's copy, but this
doesn't work anymore. It breaks in stlport.

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] DEV300_m4 breaks in helpcontent2 (PPC/Tiger)

[Christian Lohmaier]

Hi Stephan,

On Wed, Mar 26, 2008 at 09:33:34AM +0100, Stephan Bergmann wrote:
> eric b wrote:
> >Le 25 mars 08 à 10:08, Stephan Bergmann a écrit :
> >>
> >>Smells like , 
> >>right?
> >>
> >
> >
> >That's what I believed at the beginning, but in fact I had to create a 
> >new issue, on ab behalf :
> >
> >http://qa.openoffice.org/issues/show_bug.cgi?id=84145
> 
> Hi Eric,
> 
> Since you say you can reproduce it (and I have no ppc box available): 
> Maybe it would help if you apply the below simple patch in xmlhelp, 
> rebuild xmlhelp (without -debug=x), and build helpcontent2 to failure 
> and make available the resulting output.

Here's what I get with the patch applied:

/Users/buildslave/compile/300m4/helpcontent2/util/sbasic
--
-
HelpLinker @/tmp/mkimcH0I
orig was file:///tmp/yuHHtS
final is file:///tmp/yuHHtS/sbasic.ht
native_file_string is /tmp/yuHHtS/sbasic.ht
orig was file:///tmp/yuHHtS
final is file:///tmp/yuHHtS/sbasic.db
native_file_string is /tmp/yuHHtS/sbasic.db
orig was file:///tmp/yuHHtS
final is file:///tmp/yuHHtS/sbasic.key
native_file_string is /tmp/yuHHtS/sbasic.key
orig was file:///tmp/yuHHtS
final is file:///tmp/yuHHtS/sbasic.idx
indexDir is native_file_string is /tmp/yuHHtS/sbasic.idx
/tmp/yuHHtS/sbasic.idx
orig was file:///tmp/yuHHtS
final is file:///tmp/yuHHtS/default.xsl
native_file_string is /tmp/yuHHtS/default.xsl
native_file_string is 
/Users/buildslave/compile/300m4/helpcontent2/unxmacxp.pro/bin/sbasic_en-US.zip
Making 
/Users/buildslave/compile/300m4/helpcontent2/unxmacxp.pro/bin/sbasic_en-US.zip 
from 1183 input files
.before compile of 
../../unxmacxp.pro/misc/en-US/text/sbasic/guide/control_properties.xhp
after compile of 
../../unxmacxp.pro/misc/en-US/text/sbasic/guide/control_properties.xhp
HelpLinker::addBookmark text/sbasic/guide/control_properties.xhp 
text/sbasic/guide/control_properties.xhp  sbasic.jar Changing the Properties of 
Controls in the Dialog Editor
native_file_string is 
/Users/buildslave/compile/300m4/helpcontent2/source/auxiliary/index.xsl
orig was file:///tmp/yuHHtS
final is file:///tmp/yuHHtS/index.xsl
native_file_string is /tmp/yuHHtS/index.xsl
orig was file:///tmp/yuHHtS/sbasic.idx
final is file:///tmp/yuHHtS/sbasic.idx/SCHEMA
native_file_string is /tmp/yuHHtS/sbasic.idx/SCHEMA
orig was file:///tmp/yuHHtS/sbasic.idx
final is file:///tmp/yuHHtS/sbasic.idx/DICTIONARY
file name set to native_file_string is /tmp/yuHHtS/sbasic.idx/DICTIONARY
/tmp/yuHHtS/sbasic.idx/DICTIONARYopening native_file_string is 
/tmp/yuHHtS/sbasic.idx/DICTIONARY
/tmp/yuHHtS/sbasic.idx/DICTIONARY
native_file_string is /tmp/yuHHtS/sbasic.idx/DICTIONARY
didn't exist
native_file_string is /tmp/yuHHtS/sbasic.idx/DICTIONARY
len is 0
want to write at -1
outputting 0 in is 0
outputting 0 in is 0
outputting 0 in is 0
outputting 0 in is 0
want to write at -1
outputting 80 in is 8000
outputting 0 in is 8000
outputting 0 in is 8000
outputting 0 in is 8000
len is now 1
want to read at -1
inputting 90 ret is now 9000
inputting 90 ret is now 9090
inputting 90 ret is now 90909000
inputting 90 ret is now 90909090
want to read at -1
inputting 90 ret is now 9000
inputting 90 ret is now 9090
inputting 90 ret is now 90909000
inputting 90 ret is now 90909090
read leaf as 1
numbers are 2425393296 0
dmake:  Error code 138, while making '../../unxmacxp.pro/bin/sbasic_en-US.zip'

ERROR: Error 65280 occurred while making 
/Users/buildslave/compile/300m4/helpcontent2/util/sbasic

HTH,
ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[mac] DEV300_m4 breaks in helpcontent2 (PPC/Tiger) (was: putting the latest aqua on Apple Downloads)

[Christian Lohmaier]

Hi Eric, *,

On Fri, Mar 21, 2008 at 06:40:08PM +0100, eric b wrote:
> Le 21 mars 08 à 18:35, Christian Lohmaier a écrit :
> 
> >Here (PPC, Tiger) a build fails. While I didn't need any hacks like  
> >rebuilding i18npool or cppuhelper lately,
> >DEV300_m4 (and already sb83) now break in helpcontent2. I need to  
> >rebuild helpcontent2 with debug=true to allow it
> >to build.
> 
> Got the same breaker since a long time.
> 
> To save some time, I'd suggest you to build xmlhelp with debug=true  
> instead.

Ah, that's what I meant of course. HelpLinker must be built with
debug=true so that helpcontent2 will build.
I never tried whether building helpcontente2 with debug would solve the
problem as well.

But since when did you have that problem? The first time I hit it when I
contintued buildig sb83 after the fixes discussed here for the other
problems, and now a second time when trying to build m4 - I never got
that error before (not with helpcontent2)

ciao
Christian
-- 
NP: nichts

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Re: putting the latest aqua on Apple Downloads

[Christian Lohmaier]

Hi Maho, *,

On Fri, Mar 21, 2008 at 06:21:41AM +0900, Maho NAKATA wrote:
> When I can remove DEV300_m2 from Good-Day?

I suggest to remove SRC680_m222_cws_localisation21 and
SRC680_m241_localisation27 instead. Those are so old, I doubt those will
be useful to anybody. (all changes are already included in newer
snapshots)

> DEV300_m4 is out. I'd like to provide this as well.

Did you already build it?

Here (PPC, Tiger) a build fails. While I didn't need any hacks like rebuilding
i18npool or cppuhelper lately, DEV300_m4 (and already sb83) now break in
helpcontent2. I need to rebuild helpcontent2 with debug=true to allow it
to build.

ciao
Christian
-- 
NP: nichts

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[mac] Mac-Torrents updated (regenerated on Mike's server), if you seed, plese update the torrent

[Christian Lohmaier]

Hi *,

The torrents for the public Aqua Snapshots were regenerated by Mike's
tracker, unfortunately now the hash is different from the torrents I
initially uploaded.

If you already downloaded or started downloading via BT and now your
client tells you "torrent not authorized with this tracker", then 
please replace the .torrent you downloaded with the ones now linked from
the download-pages.

You only need to replace the .torrent, the actual installation set did
not change at all. 

If your download stopped in the middle, you can resume the download with
the new torrent without any problem.

Sorry for the inconvenience,

Note: The ja builds apparently didn't reach Mike's server yet, so those
torrents still are the originals I created (you see a comment in the
"stats" view of the torrent)
http://ooodev.org:6969/index.html?sort=1&search=0_080314

Those might be replaced by the mike's versions of the .torrent as well
(since ooodev syncs the OOo-torrents via rsync from Mike's server, and
thus the file will replaced automatically when it is available there)

I already prepared the new URLs in the HTML, so if you notice that the
ja torrents no longer work, then you know what to do :-)

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] strange tinderbox "Mac OSX gcc-4.0.1 (X11)" break

[Christian Lohmaier]

Hi Stephan, *,

On Wed, Mar 19, 2008 at 11:14:26AM +0100, Stephan Bergmann wrote:
> Christian Lohmaier wrote:
> 
> Older Mac OS X ld versions (like ld -v "Apple Computer, Inc. version 
> cctools-622.5.obj~13"; Tiger-era) seem to have a bug, that symbols from 
> archives are not taken into consideration when resolving symbol 
> references in objects later on the command line.
> [...] 
> As a workaround for the broken ld, it appears that -Wl,-all_load 
> anywhere on the command line fixes the problem, too.  (There should also 
> be -noall_load, and maybe wrapping -ludm and -lcosv in 
> -Wl,-all_load/-Wl,-noall_load would localize its effect, but at least my 
> ld complains that -noall_load is unknown...)  Thus,

Same here - it is listed in the gcc manpage, but fails nevertheless.
The ld manpage as installed on my system doesn't list it at all
http://developer.apple.com/documentation/Darwin/Reference/ManPages/man1/ld.1.html
reads: 
-noall_load
 This is the default.  This option is obsolete.
> 
> ---8<---
> Index: source/exes/adc_uni/makefile.mk
> ===
> RCS file: /cvs/tools/autodoc/source/exes/adc_uni/makefile.mk,v
> retrieving revision 1.14
> diff -u -r1.14 makefile.mk
> --- source/exes/adc_uni/makefile.mk 1.14
> +++ source/exes/adc_uni/makefile.mk
> @@ -85,7 +85,7 @@
>  APP1STDLIBS= $(LIBSTLPORT) $(COSVLIB) $(UDMLIB)
>  .ELSE
>  .IF "$(OS)"=="MACOSX"
> -APP1STDLIBS= $(LIBSTLPORT) -ludm -lcosv
> +APP1STDLIBS= $(LIBSTLPORT) -Wl,-all_load -ludm -lcosv
>  .ELSE
>  APP1STDLIBS= -lcosv -ludm
>  .ENDIF
> ---8<---
> 
> should solve this.

It does. Thanks for the digging into it.

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] strange tinderbox "Mac OSX gcc-4.0.1 (X11)" break

[Christian Lohmaier]

Hi Stephan,

On Wed, Mar 19, 2008 at 12:01:51PM +0100, Stephan Bergmann wrote:
> (There are two further breaks in that tinderbox build.  One is desktop, 
> which has been fixed on the CWS in the meantime.  The other is some 
> setlocale stuff in vcl, 
> ,
>  
> and I assume it is not related to the CWS.)
> >>>Hmm - as this as well doesn't happen in any other cws or master, this
> >>>might still be a side-effect of the cws, same with the autodoc one.
> >>Right, it is probably related to using the compiler's C++ library 
> >>instead of STLport.  I now get errors ("[Tue Mar 18 09:08:52 2008] 
> >>gunzip.cgi: tree: sb83 does not exist") when I try to access the 
> >>tinderbox status, so I have currently no idea how to address this.
> 
> This might be caused by solenv/inc/unxmacx.mk:1.22.14.6 l. 55--57
> 
> .IF "$(GUIBASE)"=="unx"
> CDEFS+= -DX_LOCALE
> .ENDIF
> 
> (whatever that is supposed to be good for). 

Was introduced here:
http://tools.openoffice.org/source/browse/tools/solenv/inc/unxmacxp.mk?r1=1.45&r2=1.45.14.1
(before the common unxmacx.mk was created) - ooo111fix2 cws with
internal issue 111934
That change is four years old. lxr didn't return any occurences of
X_LOCALE except for the makefile, grep -rI X_LOCALE * in solver & vcl didn't
return anything either. SO I wonder how that could cause a problem,
but...

> Could anybody verify that a 
> CWS sb83 based (i.e., --without-stlport), X11 (i.e., --with-x) build 
> succeeds when those three lines are dropped?

...commented-out the lines above and rebuilt vcl in the existing build tree
-> build succeeded. 
So yes, this is the cause, and since it appears to be used nowhere (?)
it should be safe to remove completely - at least from the global flags.

The only occurence I found is in /usr/include/X11/Xlocale.h
#ifndef X_LOCALE
#include 
#else

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Re: putting the latest aqua on Apple Downloads

[Christian Lohmaier]

Hi *,


On Tue, Mar 18, 2008 at 07:59:54PM +, Shaun McDonald wrote:
> 
> 
> Can you please wait until the links on the pages below have been  
> updated to include BitTorrent, and mirror network links.

FYI - the torrents for en, fr, ja, de are up:
http://ooodev.org:6969/index.html?sort=1&search=0_080314

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] strange tinderbox "Mac OSX gcc-4.0.1 (X11)" break

[Christian Lohmaier]

Hi Stephan,

On Tue, Mar 18, 2008 at 05:14:02PM +0100, Stephan Bergmann wrote:
> Christian Lohmaier wrote:
> >>I have not 
> >>seen this happen on any other box, and the tinderbox output is not enough 
> >>information to track this problem down. If anybody can help, I would be 
> >>grateful.
> >
> >Well, since I still have the buildtree of the breaking build lying
> >around - what should I try?
> 
> For starters, can you make the libcosv.a delivered from module cosv 
> available to me?  Maybe that already helps.

http://muenchen-surf.de/lohmaier/mac/sb83/

the lib is from the build that was done yesterday (08-03-17) 

> >>(There are two further breaks in that tinderbox build.  One is desktop, 
> >>which has been fixed on the CWS in the meantime.  The other is some 
> >>setlocale stuff in vcl, 
> >><http://tinderbox.go-oo.org/gunzip.cgi?tree=sb83&brief-log=1205767802.29103#err55>,
> >> 
> >>and I assume it is not related to the CWS.)
> >
> >Hmm - as this as well doesn't happen in any other cws or master, this
> >might still be a side-effect of the cws, same with the autodoc one.
> 
> Right, it is probably related to using the compiler's C++ library 
> instead of STLport.  I now get errors ("[Tue Mar 18 09:08:52 2008] 
> gunzip.cgi: tree: sb83 does not exist") when I try to access the 
> tinderbox status, so I have currently no idea how to address this. 

Yes - this is because the cws has been integrated already :-(

At the URL above, you'll find two gzipped logs. HTH.

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] strange tinderbox "Mac OSX gcc-4.0.1 (X11)" break

[Christian Lohmaier]

On Tue, Mar 18, 2008 at 3:03 PM, Christian Lohmaier
<[EMAIL PROTECTED]> wrote:
> Hi Stephan, *,
>
>  I'm sad to see the cws in nominated state despite the known problems
>  (that are not new to the cws)

Great. Already integrated. So what exactly were you planning to fix
this? Why did you ask if you didn't intend to fix it in the cws?
Not good style :-((

ciao
Chritain

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] strange tinderbox "Mac OSX gcc-4.0.1 (X11)" break

[Christian Lohmaier]

Hi Stephan, *,

I'm sad to see the cws in nominated state despite the known problems
(that are not new to the cws)

On Tue, Mar 18, 2008 at 09:55:23AM +0100, Stephan Bergmann wrote:
> The last build of CWS sb83 (based on DEV300m3) on tinderbox "Mac OSX 
> gcc-4.0.1 (X11)" (03/17 15:24 UTC) shows a strange break in autodoc 
^
(Yes, it does build --with-x)
> ():
>  
>  When building the autodoc executable, it links against -lcosv, but 
> complains that many (all?) of the symbols from cosv are undefined. (This is 
> not only with the latest build of that CWS on that tinderbox, but already 
> happened with previous builds of that CWS on that tinderbox.) 

...but not with any other cws or master.

> I have not 
> seen this happen on any other box, and the tinderbox output is not enough 
> information to track this problem down. If anybody can help, I would be 
> grateful.

Well, since I still have the buildtree of the breaking build lying
around - what should I try?

> (There are two further breaks in that tinderbox build.  One is desktop, 
> which has been fixed on the CWS in the meantime.  The other is some 
> setlocale stuff in vcl, 
> ,
>  
> and I assume it is not related to the CWS.)

Hmm - as this as well doesn't happen in any other cws or master, this
might still be a side-effect of the cws, same with the autodoc one.

ciao
Christian
-- 
NP: nichts

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] OOo_SRC680_m247 crashes

[Christian Lohmaier]

Hi Martin, *,

On Fri, Feb 22, 2008 at 01:16:42PM +0100, Martin Srebotnjak wrote:
> While mentioning resources, what was the decision regarding
> localization of the language packs for Mac? If there was any? Should
> we start translating? Or will this be incorporated into sdf/gsi (i.e.
> po) files?

Any translations (if there are any) will be part of the regular
translation mechanism of OOo - i.e. the strings would be put in some sdf
file and translators then can convert to po or any other format of their
choice.

But as Shaun correctly wrote: I didn't recieve any further feedback.

Last time I uploaded test-languagepacks they were only downloaded
twice, nobody add comments to the spec in the wiki either, people seem
to not care, and then there was exams season, so I didn't push it myself...

I'm still undecided what the best way to go is.

It is only clear that it won't be possible to provide a langaugepack
installer that has all translations and a string like "This is the
French/German/Japanese languagepack installer". (since that would
require all translators to translate every language name, and the
packaging process of the languagepack would have to choose different
strings for all of the languagepacks, even it the installer was only
english, it would have to be changed for each language (this is way too
much effort for such little gain)

So that leaves the following choices:
* Only english, no translations
* English and langauge of the languagepack
* only langauge of the languagepack

Not sure whether to include all languages makes sense at all, that's why
it is not listed.

For the two language options, there's the choice between
* two seperate icons/launchers
* one launcher, providing two buttons (one for english, one for
  $language)
 
But as these points are not clear yet, it doesn't make sense to start
translating.
Even if the way was clear, the english stings/the dialogs themselves
have not been approved either.

You're basically the only one who commented on the specification, the
dialogs themselves (thanks for that).

I guess I should take the lack of feedback as "it's acceptable how it is
now" and just go on with it...

ciao
Christian
-- 
NP: nichts

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Help with Aqua build on Leopard

[Christian Lohmaier]

Hi Russel,

On Mon, Jan 28, 2008 at 07:28:47AM -0600, Russell McGaha wrote:
> Well; ... the 'build' in instsetoo_native directory worked.
> 
> I also started a simple build of an almost clean tree [almost, because  
> I copied the Helpcontent2 directory from a previously completed build,  
> per Ericb's suggestion]; as I went to bed last night, and it completed  
> without ANY errors [took almost 7 hours].
> 
> I'm going to have to say that parallel builds on a PPC under Leopard  
> are seriously FLAKEY!  Whether you use -P2 or P4.

That is a wrong conclusion (unfortunately - I'd be happy if it really
was a parallel build issue, then it would be rather easy to fix), but it
is not a parallel build issue in that case.

When you specify -Px to build, it tells build to build multiple modules
(that don't depend on each other) in parallel. 

Packaging the installsets is the very last module that is to be built,
nothing is run in parallel at that stage, since the installer needs
everything else, so it doesn't matter what you specify.

Whether it breaks or not depends on solar winds or temerature or
whatever (just as the i18npool problem, this happens from time to time).

regcomp just is broken in a way that it sometimes doesn't work and will
cause those breakers. I observed that when you compile cpputools with
debug=true, the break in instsetoo_native will less likely occur (in
fact, I let the tinderbox rebuild cpputools with debug=true when the
build fails in instsetoo_native and then let it build instsetoo_native
again, before that I just let it try 5 times or so)

ciao
Christian
-- 
NP: Evanescence - Sweet Sacrifice

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Help with Aqua build on Leopard

[Christian Lohmaier]

Hi Russel, *,

On Sun, Jan 27, 2008 at 09:54:32AM -0600, Russell McGaha wrote:
> Eric H.;
>   As far as the build instr. on the wiki go; I wasn't criticizing, 
>   just  explaining.

wrt parallel builds: I currently build with -P2 -- -P2  

>   I'd already started a -P2 build [I kept clean sources THIS time].  
>   it  died in i18npool:source/localedata/data with the error:

> [...]
> dmake:  Error code 132, while making '../../../unxmacxp.pro/misc/ 
> localedata_dz_BT.cxx'
> ---* tg_merge.mk *---
> 
> is this something your familiar with;

This is unfortunately something I (and Maho) are familiar with. THis is
a problem that can be bypassed by running build multiple times.
Unfortunately this is not the only module where such "sometimes works,
sometimes fails" situation occurs.
Maho switched to the new XCode release, and wrote that those problems
now occur less frequently (not at all?) now.

http://qa.openoffice.org/issues/show_bug.cgi?id=77664

> or should I delete this tree and  

No, no need to start over. Just run

until build; do echo "another round"; done 

followed by build --deliver
then you can switch to instsetoo_native and use 
build --since i18npool 

>   And is the m243 'workspace ?' static or are changes still taking  
> place in/on it?

It is static. Master workspaces stay the same after they have been
announced as ready.

ciao
Christian
-- 
NP: Evanescence - Sweet Sacrifice

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] another request for feedback on the languagepacks

[Christian Lohmaier]

Hi Martin,

On Fri, Jan 25, 2008 at 08:10:25AM +0100, Martin Srebotnjak wrote:
> Will the strings become part of sdf file or will the translators have to
> translate the lang-packs strings separately?

If the strings get translated at all, then they will become part of the
default translation procedure, i.e. will be included in a sdf file.
Translators will not need to treat it specially.

ciao
Christian
-- 
NP: Pantera - A New Level

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] another request for feedback on the languagepacks

[Christian Lohmaier]

Hi Maho, *,

On Fri, Jan 25, 2008 at 05:18:06PM +0900, Maho NAKATA wrote:
> Great contribution!

Thanks :-)
 
> From: "Christian Lohmaier" <[EMAIL PROTECTED]>
> Subject: [mac] another request for feedback on the languagepacks (was: MacOSX 
> INTEL/PPC X11/Aqua version of SRC680_m243 have been uploaded)
> Date: Fri, 25 Jan 2008 01:44:24 +0100
> 
> > 
> > and give on of the langpacks a try and comment.
> > You can get them from here: (de, fr, ja, nl ones available)
> > http://izbot.dyndns.org:6969/
> 
> With firefox,
> > The connection was reset
> for me.

Hmm - must have been a temporary failure - maybe you were trying in the
very same moment when my connection is cut by my ISP (once every 24
hours).

> > (The languagepacks don't depend on the architecture (PPC/Intel) and
> > don't depend on the version of Mac OSX either)
> 
> Great.
> 
> BTW: did build time reduce?

No, build time itself is not reduced. But what is greatly reduced is the
time spent with building the final dmg - you can do "build --all" in
postprocess [1] and only build the full-set for english, and a langaugepack
for all the others. And packaging up a languagepack is much, much faster
than creating a full-install dmg (and of course as a sideeffect doesn't
need so much diskspace :-))
So if you include creating the dmg in build time, then yes, buildtime
was reduced (when you don't build full installsets for every language,
obviously)

ciao
Christian
[1] of course you can prevent it from building all languages by
modifying the ALLTAR/openoffice target in
instsetoo_native/util/makefile.mk to only build en-us, not not
"foralllangiso" or use a packagelist or similar as well
-- 
NP: Pantera - A New Level

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[mac] another request for feedback on the languagepacks (was: MacOSX INTEL/PPC X11/Aqua version of SRC680_m243 have been uploaded)

[Christian Lohmaier]

Hi *,

I resynced the cws that adds support for langaugepacks to m243 and
created a handful of packages for demonstrating the current state of
the cws.

The suggestions from the last time I asked for feedback are not
integrated yet, since honestly I hoped for much more feedback,
especially for the wording from native-english speakers.

So please get one of the m243 full-installsets
> URI ftp://ooopackages.good-day.net/pub/OpenOffice.org/MacOSX/SRC680_m243/
>  http://ooopackages.good-day.net/pub/OpenOffice.org/MacOSX/SRC680_m243/

and give on of the langpacks a try and comment.
You can get them from here: (de, fr, ja, nl ones available)
http://izbot.dyndns.org:6969/

(The languagepacks don't depend on the architecture (PPC/Intel) and
don't depend on the version of Mac OSX either)

Thanks a lot,

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Help with Aqua build on Leopard

[Christian Lohmaier]

Hi Eric, *,

On 1/22/08, Eric Hoch <[EMAIL PROTECTED]> wrote:
> >
> > You need to install pkg-config from Fink.  I don't know if the
> > raw pkg-config will build on the Mac platform.
>
> The raw pkg-config will build on Mac OS X but you need to build
> some dependencies first.

No, pkg-config doesn't have any dependencies. It /can/ use a system
version of glib, but it brings it own, in case there is none.

But let me stress it again: You don't need it when you build a current
milestone.

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Help with Aqua build on Leopard

[Christian Lohmaier]

Hi Mat, James, *,

On 1/22/08, James McKenzie <[EMAIL PROTECTED]> wrote:
> Mat Kramer wrote:
> >
> > I've been trying to build the Aqua OO using the Wiki instructions.
> >  I'm using OSX 10.5.1 and XCode 3.0.  I found I had to add
> > --with-jdk-home=/System/Library/Frameworks/JavaVM.framework/Home
> > to the ./configure line.  Does it make sense to add this to the Wiki
> > if this is the "standard" location?
> >
> > Now I'm running into the following error
> >
> > ...
> > checking which libssl to use... external
> > checking for pkg-config... no
> > *** The pkg-config script could not be found. Make sure it is
> > *** in your path, or set the PKG_CONFIG environment variable
> > *** to the full path to pkg-config.
> > *** Or see http://www.freedesktop.org/software/pkgconfig to get
> > pkg-config.
> > configure: error: Library requirements (openssl ) not met; consider
> > adjusting the PKG_CONFIG_PATH environment variable if your libraries
> > are in a nonstandard prefix so pkg-config can find them.
> Mat:
>
> You need to install pkg-config from Fink.  I don't know if the raw
> pkg-config will build on the Mac platform.

No. That is not true.

(Well, it is true for that milestone, but not for current ones)

The pkg-config program has only been required for a few milestones,
but is no longer required.

Nothing else besides xcode is required to build OOo (unless you want
to build mozilla from source, instead of using the precompiled
packages). Of course installing ccache is highly recommended to speed
up subsequent builds, but again let me stress this:

On Mac, you don't need any external tools or programs to build OOo.

You only need XCode.

other tools were only required for older milestones or when building
mozilla from source.

Mat should use a current milestone, not one from last year

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Xcode 2.5 and issue 82955

[Christian Lohmaier]

Hi Maho, *,

On 1/22/08, Maho NAKATA <[EMAIL PROTECTED]> wrote:
> From: "Christian Lohmaier" <[EMAIL PROTECTED]>
> Subject: [mac] Re: [releases] MacOSX INTEL X11/AQUA version of SRC680_m223 
> have been uploaded
> Date: Tue, 30 Oct 2007 19:24:49 +0100
>
> > > > Somehow my G5 builds are corrupted :(
> > > > http://www.openoffice.org/issues/show_bug.cgi?id=82955
> > > > MacOSX PPC : Build fails at instsetoo_native; regcomp fails
> > > >
> > > > Christian Lohmaier, Eric Hoch have you ever encountered this issue?
> >
> > Yes, I encounter it from time to time.  It seems to be dependent on the
> > filesystem used.
>
> Christian, do you use Xcode 2.5? I tried and it reduced such strange errors
> significantly on PPC/Intel Tiger.

No, I always used 2.4.1
What does "reduce" mean? Do they still happen, but less often, or
didn't you have any since the upgrade, but it is still to early to say
they won't occur?

I tried to find some kind of changelog of the differences between 2.5
and 2.4.1, but I couldn't find anything, except from a gdb security
bugfix and some rearranging of the directory sturcture - do you have
more details?

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[mac] Let"s make a m243 the next public aqua-snapshot (was: Scroll bar manipulation problem)

[Christian Lohmaier]

Hi *,

I've been waiting since the Systems fair in Munich for a new public
snapshot that would be "advertised" to the public. Many little or
bigger problems (amongst them the openssl disaster) prevented
providing a snapshot. But now the tree is in a buildable state again,
and a aqua-related cws is about to get integrated, this seems like a
good point of time to provide a new official snapshot.

I can provide the BitTorrent downloads again like last time and could
provide builds for PPC (built on Tiger), in case Maho can't provide
them.

I suggest to do a basic smoketest on the builds, and provide builds in
english, japanese, french and german again (possibly other langauges
on request)

What do you think?

ciao
Christian

On 1/11/08, Philipp Lohmann <[EMAIL PROTECTED]> wrote:
> eric.bachard wrote:
> > Indeed, it was issue 77549, and has been fixed in aquavcl04. The great
> > news is aquavcl04 will be integrated very soon  :-)
>
> Yes, looks like SRC680m243 and OOH680m2.

Hooray :-)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Request for feedback: Languagepacks for the Mac

[Christian Lohmaier]

Hi James, *,

On Dec 31, 2007 3:33 AM, James McKenzie <[EMAIL PROTECTED]> wrote:
> Christian Lohmaier wrote:
> >
> +1 for this process.  What will the base language be?

Base language of what? OOo itself? Well, that's whatever language the
user did install.

Langage of the installer? Well, this is either english only or in the
language of the languagepack itself.

> Remember it might
> be easier to update en-mass (as a group) the
> languages, such as all Western European languages at one time rather
> than one language at a time.

I think t hat use case (mass-installation of more than let's say three
languagepacks) is a rare usecase, and only for "power" users, not for
the regular user. For those a manual way, bypassing the installer
could be documented.
Basically "installing" is only extracting a tarball in the OOo
installation directory)

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Request for feedback: Languagepacks for the Mac

[Christian Lohmaier]

Hi Martin, *,

On Dec 31, 2007 1:23 PM, Martin Srebotnjak <[EMAIL PROTECTED]> wrote:
>
> why not use some strings that are already in the po files? Wont these
> strings end in a po file eventually?

As OOo doesn't use po files: What files are you referring to?

> Shouldn't lang pack installs feel
> similar across different platforms?

Well, "no" is the answer I guess... On linux, you install rpms, on
solaris you install pgks, on Windows you run an exe,
The installation process is different on each platform.

> That way these language packs can be
> properly localized - which they will have to be eventually. Of course, if
> those strings apply to the Mac installation process.
>
> I believe (windows/linux) language-pack strings are currently in (not sure
> if in all of those):
> scp2/source/lingu.po
> scp2/source/ooo.po
> svx/source/dialog.po

You're not looking at a vanilla repository. (OOo doesn't use po files)
But even if it would mean the sdf files: As the installation on Mac is
different from the installation on other platforms, there are no
matching strings yet. (for the button labels maybe, but that doesn't
really count :-)

> I would suggest not to use system strings like "Yes", "No", "OK", "Cancel",
> "Abort", "Continue" etc., because OSX interface is not translated to many
> languages (in fact it is localized in a very small number of languages, much
> less than OpenOffice.org). So all these strings for the langpack installer
> should, IMHO, be taken out of the OpenOffice.org po files as well.

In fact, I'm not using default strings already, but set them to OK,
Cancel manually already.

> As far as your English strings are concerned, they probably need some native
> English speaker tweaking, but you could do that by adding them to po files
> and asking OOo/Sun teams to check them. Here are just my 2 cents, although I
> am also not a native English speaker:
>
> 1st Window
> "Welcome to the OpenOffice.org Languagepack Installer" -> "Languagepack" or
> "Language Pack"? Shouldn't the language be explicitly stated on this first
> window? Like "French" or "Slovenian"?

Hmm - the language is included in the filename of the dmg like
OpenOffice.org-langpack-2.3.0_fr.dmg

> One could download the wrong pack and
> only find out later that it's impossible to use the interface and that the
> process must be repeated and that the wrong ui langpack must be removed :)

See above - you don't download the script alone, but the dmg
containing the script :-)
And the languagepack installer doesn't switch the UI language by
itself. The user would have to manually switch the language in
Tools|Options→Languages, so he won't be presented with an
incomprehensible UI in that case either :-)

(the language will only switch if the langaugepack matches the
langauge of your Mac-Settings and the base version doesn't since OOo
defaults to "default" - so when you have a french version of Mac OSX,
an english base version of OOo and then install the french
languagepack, OOo will launch with french UI, since "default" means
langauge of the operating system - but if you use Mac OSX in that
language, I'm sure you'll understan OOo in that langauge, so no
problem here...)

> [I snip all the full-stop missing ones for brevity]
> "This might take a moment" -> [...] why is
> this sentence in a new line? Maybe it should follow the previous sentence in
> the same paragraph. If you want it in a separate paragraph, I suggest you
> add spacing between both paragraphs.

Well, I just added a newline, no real thought put in this - that's why
I ask for feedback here :-))

> 2nd Window
> "Choose the installation for which you want to install the languagepack" ->
> "language pack" [...] I think
> there are word order problems here, so I suggest: "Choose the installation
> to install the language pack for:" or something like that?

Well, I'm open to suggestions, it could be a totally different wording as well.
But maybe a native-english speaker could jump in and make a proposal?

> 3rd Window
> "Click OK to start the installation" [...]
> "(installation might take a minute...)" -> "Installation might take a
> minute, please wait." or "please be patient" :)
>
> 4th Window
> "Installation is completed - you should now be able to switch the UI
> language" -> [...] does a newbie user know, what UI is? +

Hmm - not sure, but how would you call it then?

> "should be able" - arent we sure?

Well, you never know bugs beforehand :-) - and users are creative when
it comes to finding a way to break things :-)
But seriously: When that dialog appears, the installation is complete
and "we are sure".

> + "completed"? -> here is my suggestion to
> make it a bit easier for novice users:
> "Installation is complete.\n\nYou can switch the user interface language
> with $menu-path." where $menu-path would be the menu path to change the ui
> language, I don't know it, so it should be like "Tools - Language - Change
> ..." or whatever it truly is.

Thanks

> Don't forg

Re: [mac] Request for feedback: Languagepacks for the Mac

[Christian Lohmaier]

Hi Eric, *,

On Dec 31, 2007 11:30 AM, eric b <[EMAIL PROTECTED]> wrote:
> Le 31 déc. 07 à 02:49, Christian Lohmaier a écrit :
> >
> > unfortunately nobody reacted to the previous request for
> > comments/contribution to the specification of the languagepack
> > install process.
>
> You mean nobody reacted to your mail ? On IRC, we discussed a lot
> about them, and the testswe did.

No, I didn't mean testing of the installation process itself, that was
tested (thanks for that) - I meant nobody contributed to the
specification, told what messages should be printed to the user.
The test-languagepacks were full of debug-statements/preliminary
dialogs with bad wording and lots of typos. Suitable to test whether
they work or not, but nothing to present to a user.

>   From my side I already tested your language packs, and I confirm
> they work fine. You did a great work !

Thanks again :-)

> Sure: imho your work is already fully usable ( I verified a lot it
> works).

Yes, but that is not what needs to be done to finish it up. Of course
it is the most basic requirement that it actually works, but to
integrate it/to flag it as ready, the UI, the dialogs should be in a
state that it can be presented to the end-user, not to developers :-)

> > I have
> > completed the specification in the wiki with the status/behaviour I
> > have implemented.
>
> I'm volunteer, and I added my name, but I'm not sure it is a correct
> place in "author" ( of the spec ? )

Yes, the author of the spec is OK, (as would be User
Experience-contact if you want to focus on that part, or QA)

> > So please check out
> > http://wiki.services.openoffice.org/wiki/
> > Mac_OS_X_languagepacks#Detailed_Specification
>
> Thanks for the link. See my changes and tell me if you agree, or
> remove them if I'm wrong :)

Well, the installation part of the whole OOo is out of scope of the
cws, and the specification. That (multi-language installs) is not what
I intended to implement, neither is a big download size something I
want to achieve.
That part is more suited for an extra specification, one to revamp the
complete installation process (but again, I /personally/ wouldn't want
it to go this way)

I'll change it to future considerations, but this is nothing I would
like to add in that cws.
The cws/the specification is only about installing one additional
languagepack. (or course you can install multiple languagepacks by
downloading multiple dmgs and installing them seperately)

> > And if you got a nice icon for the installer and/or a nice background
> > for the dmg, then please post it as well.
>
> What about use the icon Florian Ponson provided ?
>
> See : http://eric.bachard.free.fr/news/2007/11/be-mac-like-1.html

That doesn't look like it would launch an installer... It looks like
it would open a text-processing application. I'm more looking fore
something that says "launch me to install an additional language" or
only "launch/run me to install"

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[mac] Request for feedback: Languagepacks for the Mac

[Christian Lohmaier]

Hi *,

unfortunately nobody reacted to the previous request for
comments/contribution to the specification of the languagepack install
process.

But I know that it is always easier to comment on stuff that is
already there, than to think of something from scratch, I have
completed the specification in the wiki with the status/behaviour I
have implemented.

So please check out

http://wiki.services.openoffice.org/wiki/Mac_OS_X_languagepacks#Detailed_Specification

and don't hesitate to post your comments (either to the wiki page
itself, to the discussion page or here on the mailinlist)

And if you got a nice icon for the installer and/or a nice background
for the dmg, then please post it as well.

As you might notice, I'm not a native english speaker, so I'd very
much welcome polished versions of the strings. And I'm not a real Mac
user either (I'm using linux mostly) - so if you got remarks in that
regard, don't hesitate either...

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Build issue woes

[Christian Lohmaier]

Hi Alex, *,

On Nov 23, 2007 12:10 PM, eric.bachard <[EMAIL PROTECTED]> wrote:
> Alex Thurgood a écrit :
>
> > Sorry, I made a typo there, I checked out just using  :
> >>cvs -z3 co -r SRC680 OpenOffice2
>
> Then you are building HEAD ?  ( SRC680_m237 is really mandatory )

I suggest using m236, m237 is one of the exceptions I mentioned.
m237 did introduce a new module, and that is very likely to break
if you don't take special care...

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Build issue woes

[Christian Lohmaier]

Hi Alex,*,

On Nov 23, 2007 11:46 AM, Alex Thurgood <[EMAIL PROTECTED]> wrote:
> Christian Lohmaier a écrit :
> >
> > What milestone is that?
>
> I don't know, just took the sources from what I assumed was head without
> specifying any particular version.

That's probably the biggest mistake. HEAD or branches like SRC680 are
not in a defined state, not guaranteed to build at all.
OOo's model is to have milestones that are the basis for everything else.
Only those masters have the label "buildable" (well, always with a few
exceptions naturally)
So use a milestone like SRC680_m236 (SRC680 is the development
codeline, leading to the next minor release), or OOG680_m9 (OOG680 is
the codeline for the micro releases for the stable versions)

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Build issue woes

[Christian Lohmaier]

Hi Alex, *,

On Nov 23, 2007 11:41 AM, Alex Thurgood <[EMAIL PROTECTED]> wrote:
> Christian Lohmaier a écrit :
>
> > Did you clean the build-tree after changing configure flags or did you
> > just try to continue with the changed configure values?
>
> No, just re-executed the .config command with changed flags, this is how
> I compile my ports on FreeBSD. Do you have to clean everything out each
> time ? If so, then how ?

configure alone absolutely is not enough.
at the bare minimum you need to take care of the following:
1) Reexcecute configure in a clean environment, a new terminal/shell
(otherwise the values from the previous build will interfere with your options,
in some cases just ignoring the new values)
2) resource the environment variable configure creates. Unless you
re-read the MacOSXPPC_env.sh (or whatever it is called :-) the options you
did choose at configure time will have no effect.

I suggest doing a dmake clean before rerunning a build, because it could
be that modules were already compiled with flags only suitable for the old
configure line, and that could cause problems later on.
If the configure switch only affects one single module, you could use
build --prepare
to clean the buildtree since that module, but doing a dmake clean is easier
most of the time.

> If a build goes wrong, is it best to clean it out with a make clean,
> before starting again ?

If you change configure options: Probably.
If you change the current module only (the one where it breaks): then no.
If you need to change a module up high in the dependency chain: then probably
yes.

>
> Well I downloaded the binaries, and put them in the download folder of
> the moz directory, but then the config command complained that it
> couldn't find the moz libraries and that I needed to download the
> tarball sources !!!

You need to copy the precompiled zips into the moz/zipped folder, not directly
into the moz directory.
And you would still need to specify --disable-build-mozilla (note the
build in the
middle, this is a different option than --disable-mozilla)

> It's a good job I'm used to building other stuff on FreeBSD, else I'd
> have lost patience by now :-))

:-)
ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Build issue woes

[Christian Lohmaier]

Hi Alex, *,

On Nov 23, 2007 12:53 AM, Alex Thurgood <[EMAIL PROTECTED]> wrote:
> Le Thursday 22 November 2007 14:18:26 eric.bachard, vous avez écrit:
>
> I'll have to go and look them up since I'm sending this from another machine.
> I know I've disabled mozilla, took out GTK, but the rest is pretty much what
> is in the how-to.

Did you clean the build-tree after changing configure flags or did you
just try to continue with the changed configure values?

> > Other question: did you vanilla build or modified sources (means
> > including some cws) ?
>
> Took the vanilla sources from CVS, no other added code apart from that
> suggested in the how-to. Originally tried building with mozilla, but gave
> that up when I hit some gObject/GDKpixbuf errors that I couldn't understand /
> resolve.

Building mozilla from source requires GTK-development and other libraries
like glib. Those in turn probably require other tools like pango, ... So
when you want to compile mozilla yourself instead of using the precompiled
packages, then I suggest using fink or some other package manager
to get the prerequisites.
But building mozilla more than once (to create prebuilt mozilla packages) does
not make much sense, since it only wastes time.. But as there are precompiled
mozilla packages already, you could of course just download those..

ciao
Christian
>
> Alex
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Build issue woes

[Christian Lohmaier]

Hi Alex, *,

On Nov 22, 2007 3:02 PM, Alex Thurgood <[EMAIL PROTECTED]> wrote:
> Hi again,
> Well I didn't really expect things to go smoothly the first time around, so
> here's the first build problem I've encountered :
>
> Making: ../unxmacxi.pro/lib/libuno_sal.dylib.3
> g++ -Wl,-multiply_defined,suppress -Wl -Wl,-exported_symbols_list
> ../unxmacxi.pro/misc/sal_uno_sal.map -dynamiclib -single_module
> -install_name @executable_path/libuno_sal.dylib.3 -L../unxmacxi.pro/lib
> -L/Users/AJT/680/build/source/solver/680/unxmacxi.pro/lib -L/usr/lib
> -L/usr/X11R6/lib -o ../unxmacxi.pro/lib/libuno_sal.dylib.3 -framework
> CoreFoundation -framework Carbon -lpthread -lstdc++ -lm -filelist
> ../unxmacxi.pro/misc/libuno_sal.dylib.list
> ld: symbols names listed in -exported_symbols_list:
> ../unxmacxi.pro/misc/sal_uno_sal.map not in linked objects
> _osl_createDirectoryPath
> _osl_getFileSize
> /usr/bin/libtool: internal link edit command failed
> dmake: Error code 1, while making '../unxmacxi.pro/lib/libuno_sal.dylib.3'
> ---* tg_merge.mk *---
>
>
> Any ideas ?

What milestone is that?
I wonder why it fails for you, since the mac tinderbox has a vanilla Mac OSX
setup and does not fail.

And are these vanilla sources or did you apply some patches or even use
ooo-build?

My PPC Mac has Mac OSX 10.4.11 + XCode + a manually installed ccache,
no third party packages like fink or else.

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Re: [releases] MacOSX INTEL X11/AQUA version of SRC680_m223 have been uploaded

[Christian Lohmaier]

Hi Maho, *,

On Nov 20, 2007 9:34 AM, Maho NAKATA <[EMAIL PROTECTED]> wrote:
> From: Eric Hoch <[EMAIL PROTECTED]>
> Subject: Re: [mac] Re: [releases] MacOSX INTEL X11/AQUA version of 
> SRC680_m223 have been uploaded
> Date: Tue, 20 Nov 2007 08:46:41 +0100
>
> > I always turn off screensaver and all the other little tools like
> > MenuMeters etc that I have running.
> Yes, MenuMeters is running. But I don't know about it.

What is MenuMeters?
I have activity monitor running (cpu usage history in the dock-symbol)

> > I only allow the screen to go to sleep after five minutes.
> Maybe this is correct setting. BTW I don't have a display. Just connetcting
> via VNC :)

/me too :-)
OSXVnc (now named Vino Server) runs on the Mac, no real monitor attached
except for reinstalling/debugging

screen saver is set to "enable: never" (but OSXVnc has "display dimming" and
"enable screensaver" enabled.

> > > I have serious breakage with MacOSX OOo 2.3.1 RC1 PPC build
> > > and if I turned off screen saver turned off, now it build is progressing
> > > until NS language. I suspect CPU power is sucked into screen
> > > saver, and sometimes
> > > hdiutil or screensaver eats up all CPU time, then regcomp fails.
> >
> > Is it necessary for you to let hdiutil run while you compile OOo?
>
> No, but while creating packages, dmake runs hdiutil. Sometimes hdiutil
> doesn't exit and eats up CPU. Then build fails. Still I'm not sure
> the connections between build failure and high CPU occupation.

I don't blame the CPU-usage, but disk-IO - I down don't have the partition
as filled up as it used to be. And I again can only speculate whether that
has something to do with it or not, but my feeling is that this helps as well
to avoid the breaker. At least when building only one language (en-US), the
tinderbox doesn't really hit the problem anymore.

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] ADC donation from Mr. Miyahara Toru

[Christian Lohmaier]

Hi *,

On 11/2/07, Maho NAKATA <[EMAIL PROTECTED]> wrote:
> Dear Mac porting team,
>
> My ADC account will be expired in 2007/11/1, and Mr.
> Miyahara Toru,
> CEO of Begi.Net (http://begi.net/ )
> and CEO of Virtual Tech JP ( http://virtualtech.jp/ )
> has donated ADC Software Seed Key for me. I installed Leopard on
> my iMac.
>
> I thank him very much.

I do so to with my first-lesson japanese :-)

どもうありがとうございます

ではまた
クリスティアン

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Sun building milestones for Mac/Intel

[Christian Lohmaier]

Hi James, *,

On 10/27/07, James Mckenzie <[EMAIL PROTECTED]> wrote:
> >
> +1.  And I have a PowerBook G4 that is doing nothing right now but consuming
> power as it is plugged in.  If I had a full time Internet connection, it
> could be a buildbot or tinderbox for PPC builds.

Only buildbot requires a steady connection, tinderbox doesn't.

tinderbox only needs a connection to fetch the files from cvs and to send
the buildlog via mail. During the build itself, no connection is needed.

> I could also use it to
> QA PPC builds.  And it runs Tiger, 10.4.10.

Doing QA is even more important I think - since that doesn't only require
a machine doing things on its own, but a human operator that evaluates
the results - so this is a more challenging (and more time-consuming) task.
So anybody who does systematic QA on PPC is more than welcome.

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [mac] Sun building milestones for Mac/Intel

[Christian Lohmaier]

Hi Laurent, Alex, *,

On 10/25/07, Laurent Godard <[EMAIL PROTECTED]> wrote:
>
> > Don't worry, I'll provide PPC packages as usual. Until my motivation
> > will be lost.
> >
> > My G5 is too slow and I'm sometimes busy so that there will
> > be some (lot of) delays or even without providing packages...
>
> would it be usefull to provide remote access to some other PPC ?

It surely would be interesting to try out build's distributed build feature

(See
http://www.mail-archive.com/[EMAIL PROTECTED]/msg00720.html
for a short introduction of that feature)

ciao
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]