Hi Pedro,
Am 10.09.23 um 19:56 schrieb Pedro Lino:
Hi Matthias, all
On 09/10/2023 9:54 AM WEST Matthias Seidel wrote:
As I already wrote, this is just informal. They are only bootstrapped
when they are configured.
For example:
Cairo and pixman are only needed when you build with "--enab
Hi Matthias, all
> On 09/10/2023 9:54 AM WEST Matthias Seidel wrote:
> As I already wrote, this is just informal. They are only bootstrapped
> when they are configured.
>
> For example:
>
> Cairo and pixman are only needed when you build with "--enable-cairo"
> (which doesn't work [1])
>
>
Hi,
Am 09.09.23 um 20:13 schrieb Dave Fisher:
Sent from my iPhone
On Sep 9, 2023, at 10:43 AM, Pedro Lino wrote:
Hi Matthias
On 09/09/2023 10:03 AM WEST Matthias Seidel wrote:
Just to let you know that you are not the only one on this mailing list.
We are at least two! ;-)
Good to kno
Sent from my iPhone
> On Sep 9, 2023, at 10:43 AM, Pedro Lino
> wrote:
>
> Hi Matthias
>
>>> On 09/09/2023 10:03 AM WEST Matthias Seidel
>>> wrote:
>>
>> Just to let you know that you are not the only one on this mailing list.
>> We are at least two! ;-)
>
> Good to know! :) Thanks!
>
Hi Matthias
> On 09/09/2023 10:03 AM WEST Matthias Seidel
> wrote:
> Just to let you know that you are not the only one on this mailing list.
> We are at least two! ;-)
Good to know! :) Thanks!
> >> On 09/01/2023 1:54 PM WEST Pedro Lino
> >> wrote:
> >> There seems to be a kernel problem.
Hi Pedro,
Just to let you know that you are not the only one on this mailing list.
We are at least two! ;-)
Am 07.09.23 um 23:23 schrieb Pedro Lino:
Hi again
On 09/01/2023 1:54 PM WEST Pedro Lino wrote:
There seems to be a kernel problem...
False alarm. I was able to compile working binar
Hi again
> On 09/01/2023 1:54 PM WEST Pedro Lino wrote:
> There seems to be a kernel problem...
False alarm. I was able to compile working binaries for 41X under Kernel
5.4.0.162 (latest for Ubuntu 18.04) as well
> I will try building 42X later
Also managed to compile 42X under kernel 4.15 b
Hi Matthias, all
> On 08/30/2023 5:34 PM WEST Matthias Seidel wrote:
> >>> Am 29.08.23 um 00:01 schrieb Pedro Lino:
> Hi all
> I tried building our branches under Ubuntu 18.04.6 x64 (kernel 5.4)
> >> The buildbot seems to be on 4.15.0-212, so I assume the new kernel to be
> >> the
Hi Pedro,
Am 30.08.23 um 18:20 schrieb Pedro Lino:
Hi Matthias
On 08/30/2023 4:28 PM WEST Matthias Seidel wrote:
Am 29.08.23 um 00:01 schrieb Pedro Lino:
Hi all
I tried building our branches under Ubuntu 18.04.6 x64 (kernel 5.4)
The buildbot seems to be on 4.15.0-212, so I assume the ne
Hi Matthias
> On 08/30/2023 4:28 PM WEST Matthias Seidel wrote:
> > Am 29.08.23 um 00:01 schrieb Pedro Lino:
> >> Hi all
> >> I tried building our branches under Ubuntu 18.04.6 x64 (kernel 5.4)
>
> The buildbot seems to be on 4.15.0-212, so I assume the new kernel to be
> the problem...
Int
Hi again,
Am 30.08.23 um 17:23 schrieb Matthias Seidel:
Hi Pedro,
Am 29.08.23 um 00:01 schrieb Pedro Lino:
Hi all
I tried building our branches under Ubuntu 18.04.6 x64 (kernel 5.4)
The buildbot seems to be on 4.15.0-212, so I assume the new kernel to be
the problem...
Regards,
Matt
Hi Pedro,
Am 29.08.23 um 00:01 schrieb Pedro Lino:
Hi all
I tried building our branches under Ubuntu 18.04.6 x64 (kernel 5.4)
Building branch 41X failed immediately but branch 42X completed successfully. Unfortunately it will not install with error " The package lists or status file could
On 30 Sep, Dr. Michael Stehmann wrote:
> Hello Don,
>
> in configure.sh I had this line :
>
> --with-build-version="aoo42x-$(date +"%Y-%m-%d %H:%M") - `uname -sm`\n
> ${GitHash}"
>
> Because I want to have the corresponding git hash I built, I need the
> output in two lines.
Instead of \n, try
Hello Don,
in configure.sh I had this line :
--with-build-version="aoo42x-$(date +"%Y-%m-%d %H:%M") - `uname -sm`\n
${GitHash}"
Because I want to have the corresponding git hash I built, I need the
output in two lines.
Thanks for your help
Kind regards
Mechtilde
Am 30.09.20 um 08:38 schrieb
On 30 Sep, Mechtilde wrote:
> Hello,
>
> I set up a recent build environment with Debian 9.
>
> I have got the same error message again:
>
> ~/openoffice/main/instsetoo_native$ build --from cui
> build -- version: -
>
>
> =
> Building module cui
> =
>
> Entering /home/
Hello,
I set up a recent build environment with Debian 9.
I have got the same error message again:
~/openoffice/main/instsetoo_native$ build --from cui
build -- version: -
=
Building module cui
=
Entering /home/mechtilde/openoffice/main/cui/prj
cd .. && make -s -r -j1
Hi Mechtilde,
On Sun, Nov 10, 2019 at 5:23 AM Mechtilde wrote:
>
> Hello again,
>
> I did a recent git pull AOO42X and try to build it under Debian 9.
>
> It didn't build. it fails with error in main/cui/Library_cui.mk:37
>
> If I patched it as before then it builds succesfully.
>
> Either we ne
Hello again,
I did a recent git pull AOO42X and try to build it under Debian 9.
It didn't build. it fails with error in main/cui/Library_cui.mk:37
If I patched it as before then it builds succesfully.
Either we need a switch for Debian 9 and may be newer
distribution/versions or we need anothe
Hello
sorry I took the wrong branch in the vitual maschine
I will test again
Sorry
Mechtilde
Am 27.10.19 um 16:23 schrieb Mechtilde:
> Hello Ariel
>
> I uploaded a screenshot to
>
> https://imgur.com/dhGHp5Kl.png
>
> Kind regards
>
> Am 27.10.19 um 15:21 schrieb Ariel Constenla-Haile:
>>
Hello Ariel
I uploaded a screenshot to
https://imgur.com/dhGHp5Kl.png
Kind regards
Am 27.10.19 um 15:21 schrieb Ariel Constenla-Haile:
> Hello Mechtilde,
>
> On Sun, Oct 27, 2019 at 9:13 AM Mechtilde wrote:
>> I cherry-picked it in a local test branch for AOO42X too.
>>
>> Then I tried a buil
Hello Mechtilde,
On Sun, Oct 27, 2019 at 9:13 AM Mechtilde wrote:
> I cherry-picked it in a local test branch for AOO42X too.
>
> Then I tried a build
>
> I doesn't build. It looks for ../8.3.0/utility. There is only ../8/utility
Can you paste the output? (In the meantime, I started building AOO
Hello Ariel,
Am 27.10.19 um 08:20 schrieb Ariel Constenla-Haile:
> Hello Mechtilde,
>
> I committed the change in trunk and cherry-picked this and other fixes
> in AOO418, both build now with gcc 9 so I guess they should build with
> gcc 8, give it a try and let me know. (Didn't have the time to
Hello Mechtilde,
On Sun, Oct 27, 2019 at 3:54 AM Mechtilde wrote:
> > The logic in this boost header is quite broken, I guess you don't have
> > a /usr/include/c++/9.2.1.
>
> On Debian 10 (Buster) I only have /usr/include/c++/8/
>
> On the next upcomming release (Debian 11 named Bullseye) it will
Hello Ariel,
thank you for your patch.
On Debian 10 (Buster) I have gcc 8,3,0 - More information inline
Am 27.10.19 um 02:20 schrieb Ariel Constenla-Haile:
> Hi Mechtilde,
>
> On Thu, Oct 24, 2019 at 8:46 AM Mechtilde wrote:
>>
>> Hello
>>
>> I try to build AOO with Java 11 under Debian 10.
>>
Hello Ariel,
thank you for your patch.
On Debian 10 (Buster) I have gcc 8,3,0 - More information inline
Am 27.10.19 um 02:20 schrieb Ariel Constenla-Haile:
> Hi Mechtilde,
>
> On Thu, Oct 24, 2019 at 8:46 AM Mechtilde wrote:
>>
>> Hello
>>
>> I try to build AOO with Java 11 under Debian 10.
>>
Hi Mechtilde,
On Thu, Oct 24, 2019 at 8:46 AM Mechtilde wrote:
>
> Hello
>
> I try to build AOO with Java 11 under Debian 10.
>
> It stops at xml2cmp.
>
> I add a screenshot. (C&P dosn't work for me from KVM)
In file included from
/home/ariel/aoo/build/src/branch-aoo418/main/solver/418/unxlngx6.
(Bumping up th topic again)
Hi all,
One thing I noticed while building with AdoptOpenJDK are numerous
warnings regarding Javadoc.
Maybe someone with some understanding can have a look at it?
Otherwise, I have no problems when using AOO on a daily base, even with
different JREs configured.
Regar
Hi Marcus,
Am 01.10.19 um 20:20 schrieb Marcus:
> Am 01.10.19 um 10:33 schrieb Matthias Seidel:
>> Am 01.10.19 um 01:23 schrieb Marcus:
>>> Am 30.09.19 um 22:59 schrieb Matthias Seidel:
Am 30.09.19 um 22:35 schrieb Peter Kovacs:
> We had constant 7 votes on 4.1.7 and 4.1.6 release. Howeve
Am 01.10.19 um 10:33 schrieb Matthias Seidel:
Am 01.10.19 um 01:23 schrieb Marcus:
Am 30.09.19 um 22:59 schrieb Matthias Seidel:
Am 30.09.19 um 22:35 schrieb Peter Kovacs:
We had constant 7 votes on 4.1.7 and 4.1.6 release. However only 3
volunteers voted in both releases.
These numbers are lo
Hi Marcus,
Am 01.10.19 um 01:20 schrieb Marcus:
> Am 30.09.19 um 17:31 schrieb Matthias Seidel:
>> No feedback=No interest?
>>
>> Maybe I should stop providing test builds.
>> That would save me a lot of my spare time...
>
> sorry for being silent for this topic. However, Java is not really my
> f
Hi Marcus,
Am 01.10.19 um 01:23 schrieb Marcus:
> Am 30.09.19 um 22:59 schrieb Matthias Seidel:
>> Am 30.09.19 um 22:35 schrieb Peter Kovacs:
>>> We had constant 7 votes on 4.1.7 and 4.1.6 release. However only 3
>>> volunteers voted in both releases.
>>> These numbers are low in general. Maybe we
Am 30.09.19 um 22:59 schrieb Matthias Seidel:
Am 30.09.19 um 22:35 schrieb Peter Kovacs:
We had constant 7 votes on 4.1.7 and 4.1.6 release. However only 3 volunteers
voted in both releases.
These numbers are low in general. Maybe we need to organize test phases in
order to raize the numbers.
Am 30.09.19 um 17:31 schrieb Matthias Seidel:
No feedback=No interest?
Maybe I should stop providing test builds.
That would save me a lot of my spare time...
sorry for being silent for this topic. However, Java is not really my
favorite thing. ;-)
Marcus
Am 05.09.19 um 12:58 schrieb Ma
On 9/5/2019 6:58 AM, Matthias Seidel wrote:
> Hi Keith, all,
>
> Did you have time to test?
>
> Feedback is always welcome... ;-)
>
> Regards,
>
> Matthias
>
I had done successful tests on both 4.1.7 and 4.2.0. Then got
concentrating on 4.1.7 release and forgot to get back here to report.
Hi Peter,
Am 30.09.19 um 22:35 schrieb Peter Kovacs:
> We had constant 7 votes on 4.1.7 and 4.1.6 release. However only 3 volunteers
> voted in both releases.
> These numbers are low in general. Maybe we need to organize test phases in
> order to raize the numbers. This will still not raise tes
We had constant 7 votes on 4.1.7 and 4.1.6 release. However only 3 volunteers
voted in both releases.
These numbers are low in general. Maybe we need to organize test phases in
order to raize the numbers. This will still not raise test attendance for a
single feature.
How about we schedule a
Hi Dave,
Am 30.09.19 um 18:53 schrieb Dave Fisher:
> Hi Matthias,
>
> I think that it is likely people were focused on 4.1.7 testing.
Where have all these people been when we voted for release? ;-)
> My personal opinion is that if switching does not require users to switch and
> they can use th
Hi Matthias,
I think that it is likely people were focused on 4.1.7 testing.
My personal opinion is that if switching does not require users to switch and
they can use the Oracle JRE if that is what they have then the change make
sense.
Regards,
Dave
> On Sep 30, 2019, at 8:31 AM, Matthias Se
No feedback=No interest?
Maybe I should stop providing test builds.
That would save me a lot of my spare time...
Regards,
Matthias
Am 05.09.19 um 12:58 schrieb Matthias Seidel:
> Hi Keith, all,
>
> Did you have time to test?
>
> Feedback is always welcome... ;-)
>
> Regards,
>
> Matthias
Hi Keith, all,
Did you have time to test?
Feedback is always welcome... ;-)
Regards,
Matthias
Am 01.09.19 um 18:23 schrieb Matthias Seidel:
> Hi all,
>
> Am 31.08.19 um 18:45 schrieb Matthias Seidel:
>> Hi Keith,
>>
>> Am 31.08.19 um 15:37 schrieb Keith N. McKenna:
>>> On 8/31/2019 4:23 AM,
Hi all,
Am 31.08.19 um 18:45 schrieb Matthias Seidel:
> Hi Keith,
>
> Am 31.08.19 um 15:37 schrieb Keith N. McKenna:
>> On 8/31/2019 4:23 AM, Matthias Seidel wrote:
>>> Hi all,
>>>
>>> At the moment I am doing my test builds (trunk and 42X) for Windows with
>>> the latest Oracle JDK (8u221).
>>> I
Hi Keith,
Am 31.08.19 um 15:37 schrieb Keith N. McKenna:
> On 8/31/2019 4:23 AM, Matthias Seidel wrote:
>> Hi all,
>>
>> At the moment I am doing my test builds (trunk and 42X) for Windows with
>> the latest Oracle JDK (8u221).
>> I am still able to download, but Oracle changed its licensing. I am
> Why move away?
>
> https://www.java.com -> The new license permits certain uses, such as
> personal use and development use, at no cost.
Nobody says that Oracle JVM is removed.
Just you can choose what you need.
-
To unsubscr
Hi Josef,
Am 31.08.19 um 16:02 schrieb Josef Latt:
> Hi,
>
> Am 31.08.19 um 10:23 schrieb Matthias Seidel:
>> Hi all,
>>
>> At the moment I am doing my test builds (trunk and 42X) for Windows with
>> the latest Oracle JDK (8u221).
>> I am still able to download, but Oracle changed its licensing. I
Hi,
Am 31.08.19 um 10:23 schrieb Matthias Seidel:
Hi all,
At the moment I am doing my test builds (trunk and 42X) for Windows with
the latest Oracle JDK (8u221).
I am still able to download, but Oracle changed its licensing. I am not
a lawyer and would prefer to move away from it.
Why move aw
On 8/31/2019 4:23 AM, Matthias Seidel wrote:
> Hi all,
>
> At the moment I am doing my test builds (trunk and 42X) for Windows with
> the latest Oracle JDK (8u221).
> I am still able to download, but Oracle changed its licensing. I am not
> a lawyer and would prefer to move away from it.
>
> Damj
Hi Mechtilde,
Am 29.07.19 um 18:31 schrieb Mechtilde:
> Hello developers,
>
> I'm extending my build environment to build a AOO version close to the
> release build.
>
> I took the configure script published in SVN.
>
> Then I stumble about not be able to download e.g.
> README_silgraphite-2.3.1.t
Hi Mechtilde,
The file
/home/mechtilde/aoo42x/main/cui/Library_cui.mk
describes the build instruction for gcc.
In this files in line 37 is an issue (
/home/mechtilde/aoo42x/main/cui/Library_cui.mk:37
)
now check in the file the given line for a single $ and replace it with
$$. then try again.
Or
Hello,
Am 28.07.19 um 07:36 schrieb Damjan Jovanovic:
> ifneq ($(BUILD_VER_STRING),)
> $(eval $(call
> gb_Library_add_defs,cui,-DBUILD_VER_STRING="$(BUILD_VER_STRING)"))
> endif
>
> Please try fiddle with that middle line. Maybe you need $$ instead of $
> and/or {} instead of (), for the BUILD_V
ifneq ($(BUILD_VER_STRING),)
$(eval $(call
gb_Library_add_defs,cui,-DBUILD_VER_STRING="$(BUILD_VER_STRING)"))
endif
Please try fiddle with that middle line. Maybe you need $$ instead of $
and/or {} instead of (), for the BUILD_VER_STRING variable.
Regards
Damjan
On Sun, Jul 28, 2019 at 6:24 AM M
Hello,
now the resault.
With the epm version 4.4.2 Jim pubkished under
https://github.com/jimjag/epm
I can build DEBs and RPMs at Centos 7 but not at Debian 9.
Redundant argument in sprintf at
/home/mechtilde/aoo42x/main/solenv/bin/modules/installer/logger.pm line 192.
... creating epm list file
Am 24.01.19 um 13:50 schrieb Jim Jagielski:
> This looks like it's because the EPM was not built patched for AOO...
>
> Did you use 4.4.2? And add --enable-aoo ?
I use 4.4.1 with --enable-aoo. This was the link you gave me.
I will try it with 4.4.2 this evening.
Kind regards
--
Mechtilde St
This looks like it's because the EPM was not built patched for AOO...
Did you use 4.4.2? And add --enable-aoo ?
> On Jan 24, 2019, at 1:41 AM, Mechtilde wrote:
>
> Hello,
>
> Now I built on CentOS 7 again with out success.
>
> I used the recent epm version as mentioned in the wiki and a recen
Hello,
Now I built on CentOS 7 again with out success.
I used the recent epm version as mentioned in the wiki and a recent
checkout from aoo42x branch.
I get the message:
ERROR: ERROR: Did not find file: RPMS/openoffice-draw.spec
in function: prepare_packages
dmake: Error code 255, while makin
Hello Jim,
Am 23.01.19 um 15:53 schrieb Jim Jagielski:
> What does 'epm --version' say on both systems?
>
>> On Jan 23, 2019, at 8:50 AM, Mechtilde wrote:
>>
>> Hello,
>>
>> I did it now under Debian 8 again. Tere it works as expected and builds
>> DEBs and RPMs.
Here epm is the ship version 3.
What does 'epm --version' say on both systems?
> On Jan 23, 2019, at 8:50 AM, Mechtilde wrote:
>
> Hello,
>
> I did it now under Debian 8 again. Tere it works as expected and builds
> DEBs and RPMs.
>
> Kind regards
>
> Am 23.01.19 um 07:40 schrieb Mechtilde:
>> Hello,
>>
>> to document the
Hello,
I did it now under Debian 8 again. Tere it works as expected and builds
DEBs and RPMs.
Kind regards
Am 23.01.19 um 07:40 schrieb Mechtilde:
> Hello,
>
> to document the problems I found I start a new thread.
>
> First I did a clean build on Debian 9 with system epm. It builds neither
>
Am 19.01.19 um 09:45 schrieb Peter Kovacs:
> have you tried
>
> rm -r
> /home/mechtilde/aoo42x/main/instsetoo_native/unxlngx6.pro/Apache_OpenOffice/deb/install/de_inprogress/DEBS
>
> as a solution?
There isn't a directory
~/aoo42x/main/instsetoo_native/unxlngx6.pro/Apache_OpenOffice/deb/insta
have you tried
rm -r
/home/mechtilde/aoo42x/main/instsetoo_native/unxlngx6.pro/Apache_OpenOffice/deb/install/de_inprogress/DEBS
as a solution?
On 19.01.19 07:24, Mechtilde wrote:
> Hello Jim,
>
> Am 17.01.19 um 15:44 schrieb Jim Jagielski:
>> Well, the error I was hitting is fixed, yeah.
>>
>>
Hello Jim,
Am 17.01.19 um 15:44 schrieb Jim Jagielski:
> Well, the error I was hitting is fixed, yeah.
>
> You may need to blow away main/instsetoo_native/unxlngx6.pro/* and rebuild
Yes I did so.
I do a and then there were no unxlngx6.pro/* in
main/instsetoo_native. But it doesn't work. I get
Well, the error I was hitting is fixed, yeah.
You may need to blow away main/instsetoo_native/unxlngx6.pro/* and rebuild
> On Jan 17, 2019, at 9:32 AM, Mechtilde wrote:
>
> Hello,
>
> Am 15.01.19 um 19:42 schrieb Jim Jagielski:
>> As a reminder, w/ AOO 4.2.0, our Productname is now "Apache_Ope
Hello,
Am 15.01.19 um 19:42 schrieb Jim Jagielski:
> As a reminder, w/ AOO 4.2.0, our Productname is now "Apache_OpenOffice"
>
> Notice the "_" :(
>
> I am guessing that's a dpg/deb restriction??
Does it mean it should build now?
I get with r1851505 from aoo42x branch:
. /usr/bin/fakeroot /us
As a reminder, w/ AOO 4.2.0, our Productname is now "Apache_OpenOffice"
Notice the "_" :(
I am guessing that's a dpg/deb restriction??
OK... here are the pertinent sections of the log... Of particular note, look at
the "Product names should only contain letters and numbers!" error.
12.189364 : lang : ##
12.189396 : lang : epm call for openoffice-en-US-calc
12.189425 :
Am 15. Januar 2019 18:27:27 MEZ schrieb Damjan Jovanovic :
>Does 4.1.x build on Debian 9?
I never test it.
>> >Mechtilde Stehmann
>> >## Apache OpenOffice
>> >## Freie Office Suite für Linux, MacOSX, Windows
>> >## Debian Developer
>> >## PGP encryption welcome
>> >## F0E3 7F3D C87A 4998 2899
Does 4.1.x build on Debian 9?
On Tue, Jan 15, 2019 at 1:17 PM Stehmann wrote:
> it does't build with epm 4.2 too. As I described before it works under
> Debian 8. So I habe no idea where to start with bisect.
>
> Mechtilde
>
> Am 15. Januar 2019 08:13:50 MEZ schrieb Mechtilde :
> >the same revis
> On Jan 15, 2019, at 8:13 AM, Jim Jagielski wrote:
>
>
>
>> On Jan 15, 2019, at 2:36 AM, Peter Kovacs wrote:
>>
>> Maybe it is a good point to ask infra to switch to git?
>>
>
> Or maybe encourage people to use git-svn?
>
There is this... never tried it though:
https://github.com
> On Jan 15, 2019, at 2:36 AM, Peter Kovacs wrote:
>
> Maybe it is a good point to ask infra to switch to git?
>
Or maybe encourage people to use git-svn?
Let me do another build (verbose) and really dig thru the logs
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
it does't build with epm 4.2 too. As I described before it works under Debian
8. So I habe no idea where to start with bisect.
Mechtilde
Am 15. Januar 2019 08:13:50 MEZ schrieb Mechtilde :
>the same revision buids under Debian 8 with epm version 3.7 which is
>shipped in the source code.
>
>but
Maybe it is a good point to ask infra to switch to git?
On 15.01.19 08:13, Mechtilde wrote:
> the same revision buids under Debian 8 with epm version 3.7 which is
> shipped in the source code.
>
> but this doesn't work with Debian 9 and CentOS 7.
>
> Now I run it with system epm 4.2 on Debian 9. I
the same revision buids under Debian 8 with epm version 3.7 which is
shipped in the source code.
but this doesn't work with Debian 9 and CentOS 7.
Now I run it with system epm 4.2 on Debian 9. In some hours I will send
the result.
Mechtilde
Am 15.01.19 um 02:12 schrieb Damjan Jovanovic:
> I can
I can't see much in that output, and you're not going to like my suggestion.
Clone AOO from a Git repository, find an old version that could build debs,
and then do a regression test with "git bisect" to find the first commit
that broke building debs, so we can see where and how it went wrong and
Yeah... getting this on my CentOS7 builds as well...
Just on debs... rpms are fine.
> On Jan 14, 2019, at 4:37 PM, Mechtilde wrote:
>
> Hello,
>
> Am 10.01.19 um 07:01 schrieb Mechtilde:
>>
>>
>> Am 10.01.19 um 03:07 schrieb Damjan Jovanovic:
>>> Hi
>>>
>>> I am glad it worked.
>>>
>>> Sur
Hello,
Am 10.01.19 um 07:01 schrieb Mechtilde:
>
>
> Am 10.01.19 um 03:07 schrieb Damjan Jovanovic:
>> Hi
>>
>> I am glad it worked.
>>
>> Sure, patch the whole 42x branch.
>
> As I described in the other thread it breaks at building with epm.
>
> It says I had to rebuild instsetoo_native.
I
I've seen this happen sometimes.
Try "make clean" in main/sw and then build that module again.
On Fri, Jan 11, 2019 at 9:08 PM Mechtilde wrote:
> Hello,
>
> now I want to try to build 42x with my commit from trunk under Debian 8.
>
> This failed:
>
>
>
> =
> Building module sw
> =
Am 10.01.19 um 03:07 schrieb Damjan Jovanovic:
> Hi
>
> I am glad it worked.
>
> Sure, patch the whole 42x branch.
As I described in the other thread it breaks at building with epm.
It says I had to rebuild instsetoo_native.
Regards
--
Mechtilde Stehmann
## Apache OpenOffice
## Freie Offic
Hi
I am glad it worked.
Sure, patch the whole 42x branch.
Regards
Damjan
On Wed, Jan 9, 2019 at 11:54 PM Mechtilde wrote:
> Hello
>
> Now I have checkout AOO42x too
>
> I will also commit the changes in
> main/basebmp/inc/basebmp/packedpixeliterator.hxx for AOO42x.
>
> Is it ok?
>
> Regards
Hello
Now I have checkout AOO42x too
I will also commit the changes in
main/basebmp/inc/basebmp/packedpixeliterator.hxx for AOO42x.
Is it ok?
Regards
Mechtilde
Am 09.01.19 um 22:08 schrieb Mechtilde:
> Hello Damjan
>
> Am 09.01.19 um 16:28 schrieb Damjan Jovanovic:
>> Please post the output
Hello Damjan
Am 09.01.19 um 16:28 schrieb Damjan Jovanovic:
> Please post the output of your "gcc -dumpversion".
>
> Are you able to try some changes out?
> If so, on line 86 of main/basebmp/inc/basebmp/packedpixeliterator.hxx,
> change the 0 to 0u (which is used elsewhere in that file and works)
Hello Damjan
Am 09.01.19 um 16:28 schrieb Damjan Jovanovic:
> Please post the output of your "gcc -dumpversion".
My gcc version under Debian 9 is 6.3.0
>
> Are you able to try some changes out?
This takes time.
> If so, on line 86 of main/basebmp/inc/basebmp/packedpixeliterator.hxx,
> change th
Please post the output of your "gcc -dumpversion".
Are you able to try some changes out?
If so, on line 86 of main/basebmp/inc/basebmp/packedpixeliterator.hxx,
change the 0 to 0u (which is used elsewhere in that file and works).
Then try building again and report back.
Regards
Damjan
On Fri, Ja
Hello,
Am 04.01.19 um 03:00 schrieb leg...@posteo.de:
> You have to set the cxxflag g98+ or so i think.
> Also you should set some flag to switch the behaviour of binary compare. But
> i forgot wich one it is.
>
> Maybe in mails from 2016 ör 2017 you can find further hints.
I haven't enough e
You have to set the cxxflag g98+ or so i think.
Also you should set some flag to switch the behaviour of binary compare. But i
forgot wich one it is.
Maybe in mails from 2016 ör 2017 you can find further hints.
Am Donnerstag, 3. Januar 2019 schrieb Mechtilde:
> Hello,
>
> for the translation P
Am 14.10.2017 um 17:28 schrieb Jim Jagielski:
On Oct 14, 2017, at 11:28 AM, Jim Jagielski wrote:
I found the problem... It looked to be a cut/paste error where the
build system was looking in:
solver/420/unxmaccx.pro/xml/components
instead of:
solver/420/unxmaccx.pro/xml/components
Oo
> On Oct 14, 2017, at 11:28 AM, Jim Jagielski wrote:
>
> I found the problem... It looked to be a cut/paste error where the
> build system was looking in:
>
> solver/420/unxmaccx.pro/xml/components
>
> instead of:
>
> solver/420/unxmaccx.pro/xml/components
>
Oops. Should be:
solver/4
I found the problem... It looked to be a cut/paste error where the
build system was looking in:
solver/420/unxmaccx.pro/xml/components
instead of:
solver/420/unxmaccx.pro/xml/components
It looks like a number of things in 4.2.0 related to
macOS haven't been tested/built yet so I'm running
On 13/10/2017 Jim Jagielski wrote:
I've gotten pretty far in building 4.2.0 but the below error is
a puzzler for me... Any ideas or hints would be appreciated.
It looks like a build dependency, somewhere
How many parallel jobs do you run?
I usually build "4x4", i.e.
$ build --all -P4 -- -P4
(w
Thx. Yeah, I've tried that but haven't had luck so far.
> On Oct 13, 2017, at 6:02 PM, Marcus wrote:
>
> Am 13.10.2017 um 22:46 schrieb Jim Jagielski:
>> I've gotten pretty far in building 4.2.0 but the below error is
>> a puzzler for me... Any ideas or hints would be appreciated.
>> It looks lik
Am 13.10.2017 um 22:46 schrieb Jim Jagielski:
I've gotten pretty far in building 4.2.0 but the below error is
a puzzler for me... Any ideas or hints would be appreciated.
It looks like a build dependency, somewhere:
as a not so skilled builder, sometimes it helps me to:
- just restart a new bu
Hmmm. For some reason, either the build system isn't specifying
-L./solver/420/unxmaccx.pro/lib or else it's wanting to
link when it doesn't need to.
> On Oct 9, 2017, at 10:48 AM, Jim Jagielski wrote:
>
> I'm trying to build AOO 4.2.0 on macOS 10.12.6 and
> I'm getting this error:
>
> ld: lib
I think I did? ;-)
https://home.apache.org/~mseidel/AOO-builds/AOO-414-Test/ReadMe.txt
https://home.apache.org/~mseidel/AOO-builds/AOO-414-Experimental/ReadMe.txt
Kind regards, Matthias
Am 22.06.2017 um 15:40 schrieb FR web forum:
>> Meanwhile, you can test my first Windows builds:
>> https://h
>Meanwhile, you can test my first Windows builds:
>https://home.apache.org/~mseidel/AOO-builds/
Thanks Matthias
Could you explain to me difference between "test" and "experimental"?
-
To unsubscribe, e-mail: dev-unsubscr...@op
Am 21.06.2017 um 14:12 schrieb Raphael Bircher:
> Hi Matthias
>
> Am .06.2017, 13:20 Uhr, schrieb Matthias Seidel
> :
>
>> Hi at all!
>>
>> Has anyone tried to build AOO with "Bash on Ubuntu on Windows" instead
>> of cygwin?
>> It is a full Ubuntu 16.04.2 LTS command line interface running as
>> su
Hi Matthias
Am .06.2017, 13:20 Uhr, schrieb Matthias Seidel
:
Hi at all!
Has anyone tried to build AOO with "Bash on Ubuntu on Windows" instead
of cygwin?
It is a full Ubuntu 16.04.2 LTS command line interface running as
subsystem on Windows 10.
I am doing a SVN checkout at the moment, so
Hi Dany,
Are you behind a corporate firewall?
If you use the address in your web browser do you see the directory
listings?
Does the svn process work if you replace https with http?
Thanks,
Carl
On 08/09/2016 05:28 AM, Kirsten S wrote:
Hello Together,
thanks or your help so far. Unfortuna
Hello Together,
thanks or your help so far. Unfortunately I wasn`t sucesfull in building
it yet. The period in the link above posted by me was an accident.
When I execute the svn co statement it seems like the process starts
shortly but after round about 10 seconds it finishes without any result
On 08/07/2016 08:35 AM, Kirsten S wrote:
Hello together,
I am new to this list and new to the AOO-Project. I've been trying to build
AOO and to get the source code since yesterday. I followed the step by step
guide in this link: https://wiki.openoffice.org/wiki/Documentation/
Building_Guide_AOO/
The instructions need clarifying - I'll look into it later.
The final argument "aoo-trunk" is the destination folder for the
checkout. If you want to checkout into a folder called "aoo-trunk" do a
"mkdir aoo-trunk" first. If you want a different destination, replace
"aoo-trunk" with the folder
ARM chips are not Intel compatible the way AMD chips for PCs and Macintosh are.
As far as I can tell, AOO has never been targeted to ARM, whether running
Linux, Android, iOS, or Windows 10. It should not build and it certainly
should not install.
It is interesting that EricB is trying it. He
1 - 100 of 111 matches
Mail list logo
