You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Andrea Pescetti <pe...@apache.org> on 2017/12/02 22:56:01 UTC
Re: a more sane way to override optimization flags in gbuild
On 30/11/2017 Jim Jagielski wrote:
> I think for 4.2.x and later, we have deprecated CentOS5 as a supported
> build system... I ran into a LOT of issues.
Such as, for example? I think that the guide we have at
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#CentOS_5
used to be the most solid procedure to build OpenOffice, while it is
well-known that building on Windows is complex and building on Mac is
even more complex and resulted in broken builds several times.
The reason I'm asking is not because CentOS 5 is particularly relevant
(I think we have agreement that we'll switch to CentOS 6 for 4.2.x and
that the next, if any, 4.1.x releases will cover major regressions
only), but because I think that an updated version (to CentOS 6) of that
guide should be the reference for our 4.2.x builds. So if there are
issues that can be ironed out, better to do it as soon as possible.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Updating the build guide (Re: a more sane way to override
optimization flags in gbuild)
Posted by Kay Schenk <ka...@gmail.com>.
On 12/03/2017 12:30 PM, Jim Jagielski wrote:
>> On Dec 3, 2017, at 1:31 PM, Andrea Pescetti <pe...@apache.org> wrote:
>>
>> Keith N. McKenna wrote:
>>> That begs the Question should we add a section to the overall build
>>> guide for CentOS6? If yes I can add the section as a clone of the
>>> CentOS5 Guide with all the proper warnings and notes about it needing
>>> updating for the CentOS6 specifics.
>> No, this wouldn't be helpful since the CentOS 6 guide should be almost completely different from the CentOS 5 one (that section is meant to only contain the distribution-specific details, and they differ significantly between major versions of the same distribution). So this is best done by someone who actually did build on CentOS 6.
>>
> Actually, as someone who has built on both, the instructions are
> pretty much mirrors. In fact, a simple s/5/6/p almost does it :)
Ditto for me. I've been building on CentOS6 (32 bit) for at least a year
and really no major issues. I've never built on CentOS 5 so I can't say
what the differences might be.
>
> My plan is to edit https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step <https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step>
> and make the CentOS5 section AOO 4.1.x specific and, similar to what
> I did with the macOS guide, create a new CentOS6 section for 4.2.x and
> later.
>
>
--
------------------------------------------
MzK
"Don't you know that it's worth
every treasure on earth
To be young at heart."
-- song, "Young at Heart"
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Updating the build guide (Re: a more sane way to override
optimization flags in gbuild)
Posted by Jim Jagielski <ji...@jaguNET.com>.
> On Dec 3, 2017, at 1:31 PM, Andrea Pescetti <pe...@apache.org> wrote:
>
> Keith N. McKenna wrote:
>> That begs the Question should we add a section to the overall build
>> guide for CentOS6? If yes I can add the section as a clone of the
>> CentOS5 Guide with all the proper warnings and notes about it needing
>> updating for the CentOS6 specifics.
>
> No, this wouldn't be helpful since the CentOS 6 guide should be almost completely different from the CentOS 5 one (that section is meant to only contain the distribution-specific details, and they differ significantly between major versions of the same distribution). So this is best done by someone who actually did build on CentOS 6.
>
Actually, as someone who has built on both, the instructions are
pretty much mirrors. In fact, a simple s/5/6/p almost does it :)
My plan is to edit https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step <https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step>
and make the CentOS5 section AOO 4.1.x specific and, similar to what
I did with the macOS guide, create a new CentOS6 section for 4.2.x and
later.
Re: Updating the build guide (Re: a more sane way to override
optimization flags in gbuild)
Posted by "Keith N. McKenna" <ke...@comcast.net>.
On 12/3/2017 3:30 PM, Jim Jagielski wrote:
>
>> On Dec 3, 2017, at 1:31 PM, Andrea Pescetti <pe...@apache.org> wrote:
>>
>> Keith N. McKenna wrote:
>>> That begs the Question should we add a section to the overall build
>>> guide for CentOS6? If yes I can add the section as a clone of the
>>> CentOS5 Guide with all the proper warnings and notes about it needing
>>> updating for the CentOS6 specifics.
>>
>> No, this wouldn't be helpful since the CentOS 6 guide should be almost completely different from the CentOS 5 one (that section is meant to only contain the distribution-specific details, and they differ significantly between major versions of the same distribution). So this is best done by someone who actually did build on CentOS 6.
>>
>
> Actually, as someone who has built on both, the instructions are
> pretty much mirrors. In fact, a simple s/5/6/p almost does it :)
>
> My plan is to edit https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step <https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step>
> and make the CentOS5 section AOO 4.1.x specific and, similar to what
> I did with the macOS guide, create a new CentOS6 section for 4.2.x and
> later.
>
>
Jim;
I am not a Linux user, but I am very familiar with the mwiki. Any help I
can be all you have to do is ask.
Regards
Keith
Updating the build guide (Re: a more sane way to override optimization
flags in gbuild)
Posted by Andrea Pescetti <pe...@apache.org>.
Keith N. McKenna wrote:
> That begs the Question should we add a section to the overall build
> guide for CentOS6? If yes I can add the section as a clone of the
> CentOS5 Guide with all the proper warnings and notes about it needing
> updating for the CentOS6 specifics.
No, this wouldn't be helpful since the CentOS 6 guide should be almost
completely different from the CentOS 5 one (that section is meant to
only contain the distribution-specific details, and they differ
significantly between major versions of the same distribution). So this
is best done by someone who actually did build on CentOS 6.
> Also will the top level build guide at
> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO need
> updating?
Not major changes at least. It might need some minor updates, but the
process didn't change much. Still, since we do not provide a detailed
README with build instructions in the sources, it will be important to
make sure the page still applies when we are closer to a release. Thanks
for the heads-up.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: a more sane way to override optimization flags in gbuild
Posted by "Keith N. McKenna" <ke...@comcast.net>.
On 12/3/2017 4:14 AM, Andrea Pescetti wrote:
> Jim Jagielski wrote:
>>> On Dec 2, 2017, at 5:56 PM, Andrea Pescetti wrote:
>>> On 30/11/2017 Jim Jagielski wrote:
>>>> I think for 4.2.x and later, we have deprecated CentOS5 as a supported
>>>> build system... I ran into a LOT of issues.
>>> Such as, for example?
>> for starters:
>> o zip 3.0.
>> o GIO
>
> OK, I now get it. You ran into issues when you tried to build *trunk* on
> CentOS 5, not when you built 4.1.4 on CentOS 5. I had read your sentence
> above as "We should deprecate CentOS 5 since I found lots of issues
> [when building 4.1.4]".
>
>> Isn't that exactly what I'm doing???
>
> Yes, we are on the same page:
>
> - The CentOS 5 guide works well and smoothly for 4.1.x
>
> - The CentOS 5 guide does not work any longer for trunk (for the reasons
> Damjan detailed), but this is irrelevant as we'll update to CentOS 6
> anyway.
>
> Regards,
> Andrea.
That begs the Question should we add a section to the overall build
guide for CentOS6? If yes I can add the section as a clone of the
CentOS5 Guide with all the proper warnings and notes about it needing
updating for the CentOS6 specifics.
Also will the top level build guide at
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO need
updating?
Regards
Keith
Re: a more sane way to override optimization flags in gbuild
Posted by Andrea Pescetti <pe...@apache.org>.
Jim Jagielski wrote:
>> On Dec 2, 2017, at 5:56 PM, Andrea Pescetti wrote:
>> On 30/11/2017 Jim Jagielski wrote:
>>> I think for 4.2.x and later, we have deprecated CentOS5 as a supported
>>> build system... I ran into a LOT of issues.
>> Such as, for example?
> for starters:
> o zip 3.0.
> o GIO
OK, I now get it. You ran into issues when you tried to build *trunk* on
CentOS 5, not when you built 4.1.4 on CentOS 5. I had read your sentence
above as "We should deprecate CentOS 5 since I found lots of issues
[when building 4.1.4]".
> Isn't that exactly what I'm doing???
Yes, we are on the same page:
- The CentOS 5 guide works well and smoothly for 4.1.x
- The CentOS 5 guide does not work any longer for trunk (for the reasons
Damjan detailed), but this is irrelevant as we'll update to CentOS 6 anyway.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: 4.2.0: Baseline CentOS6 as reference build platform
Posted by Andrea Pescetti <pe...@apache.org>.
Jim Jagielski wrote:
> Who has write access to that?
The main OpenOffice site is in our source repository, so all committers
have access to it. But for some reason we don't post news there, even
though we have an (outdated) news archive there.
The OpenOffice blog https://blogs.apache.org/OOo/ is powered by Roller
and managed by Infra; I don't really recommend the tool for anything
more than basic text-only posts, but I have write access, like many
other PMC members (Marcus, probably Roberto, and surely many others).
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: 4.2.0: Baseline CentOS6 as reference build platform
Posted by Jim Jagielski <ji...@jaguNET.com>.
Who has write access to that?
> On Dec 4, 2017, at 8:28 AM, Damjan Jovanovic <da...@apache.org> wrote:
>
> Why don't we post that on our www.openoffice.org blog?
>
> On Mon, Dec 4, 2017 at 3:25 PM, Jim Jagielski <ji...@jagunet.com> wrote:
>
>> http://jimjag.com/imo/index.php?/archives/272-The-Path-to-
>> Apache-OpenOffice-4.2.0.html <http://jimjag.com/imo/index.
>> php?/archives/272-The-Path-to-Apache-OpenOffice-4.2.0.html>
>>
>>> On Dec 4, 2017, at 7:35 AM, Jim Jagielski <ji...@jaguNET.com> wrote:
>>>
>>> Sounds like a good topic for a blog post... Our current
>>> discussions regarding 4.2.0 and Linux.
>>>
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: 4.2.0: Baseline CentOS6 as reference build platform
Posted by Damjan Jovanovic <da...@apache.org>.
Why don't we post that on our www.openoffice.org blog?
On Mon, Dec 4, 2017 at 3:25 PM, Jim Jagielski <ji...@jagunet.com> wrote:
> http://jimjag.com/imo/index.php?/archives/272-The-Path-to-
> Apache-OpenOffice-4.2.0.html <http://jimjag.com/imo/index.
> php?/archives/272-The-Path-to-Apache-OpenOffice-4.2.0.html>
>
> > On Dec 4, 2017, at 7:35 AM, Jim Jagielski <ji...@jaguNET.com> wrote:
> >
> > Sounds like a good topic for a blog post... Our current
> > discussions regarding 4.2.0 and Linux.
> >
>
>
Re: 4.2.0: Baseline CentOS6 as reference build platform
Posted by Jim Jagielski <ji...@jaguNET.com>.
http://jimjag.com/imo/index.php?/archives/272-The-Path-to-Apache-OpenOffice-4.2.0.html <http://jimjag.com/imo/index.php?/archives/272-The-Path-to-Apache-OpenOffice-4.2.0.html>
> On Dec 4, 2017, at 7:35 AM, Jim Jagielski <ji...@jaguNET.com> wrote:
>
> Sounds like a good topic for a blog post... Our current
> discussions regarding 4.2.0 and Linux.
>
Re: 4.2.0: Baseline CentOS6 as reference build platform
Posted by Jim Jagielski <ji...@jaguNET.com>.
Sounds like a good topic for a blog post... Our current
discussions regarding 4.2.0 and Linux.
> On Dec 4, 2017, at 7:25 AM, Peter kovacs <pe...@apache.org> wrote:
>
> Are there users who want CentOS5 builds?
>
> Am 4. Dezember 2017 13:23:39 MEZ schrieb Jim Jagielski <ji...@jaguNET.com>:
>> Thx. Yeah, I got that. I also understand that GIO is, by far, the
>> recommended option.
>>
>> So our options are:
>>
>> 1. We stick w/ CentOS5 as our ref build system for 4.2.0 but force
>> Gnome VFS.
>>
>> 2. We move to CentOS6, accept the default of GIO but understand that
>> this moves CentOS5 as a non-supported OS for our community builds.
>>
>> 3. Just as we offer Linux 32 and 64bit builds, starting w/ 4.2.0
>> we offer CentOS5 community builds (w/ Gnome VFS) IN ADDITION
>> TO CentOS6 builds (w/ GIO). (i.e.: 32bit-Gnome VFS, 64bit-Gnome VFS,
>> 32bit-GIO, 64bit-GIO).
>>
>> It doesn't matter to me... I'm setup to be able to
>> do any and all options re: builds. Whatever makes most
>> sense for our end-users and community is what we should
>> do.
>>
>>> On Dec 3, 2017, at 6:43 PM, Damjan Jovanovic <da...@apache.org>
>> wrote:
>>>
>>> Sorry what I meant to say was, those flags to ./configure still let
>> you
>>> build with Gnome VFS instead of GIO.
>>>
>>> I didn't take GIO out of the build, I just switched the default VFS
>>> implementation from Gnome VFS to GIO.
>>>
>>> Damjan
>>>
>>> On Sun, Dec 3, 2017 at 4:28 PM, Jim Jagielski <ji...@jagunet.com>
>> wrote:
>>>
>>>>
>>>>> On Dec 3, 2017, at 1:16 AM, Damjan Jovanovic <da...@apache.org>
>> wrote:
>>>>>
>>>>> On Sun, Dec 3, 2017 at 2:25 AM, Jim Jagielski <ji...@jagunet.com>
>> wrote:
>>>>>
>>>>>>
>>>>>>> On Dec 2, 2017, at 5:56 PM, Andrea Pescetti <pe...@apache.org>
>>>> wrote:
>>>>>>>
>>>>>>> On 30/11/2017 Jim Jagielski wrote:
>>>>>>>> I think for 4.2.x and later, we have deprecated CentOS5 as a
>> supported
>>>>>>>> build system... I ran into a LOT of issues.
>>>>>>>
>>>>>>> Such as, for example?
>>>>>>
>>>>>> for starters:
>>>>>> o zip 3.0.
>>>>>> o GIO
>>>>>>
>>>>>>
>>>>> If you *really* need GIO, try adding --disable-gio
>> --enable-gnome-vfs to
>>>>> ./configure.
>>>>>
>>>>
>>>> The issue is that CentOS5 simply does not and can not provide GIO.
>>>> So it is, IMO at least, unsuitable for our reference community
>>>> build platform.
>>>>
>>>> This was brought up on the "AOO 4.2.0-dev builds" thread.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: 4.2.0: Baseline CentOS6 as reference build platform
Posted by Peter kovacs <pe...@apache.org>.
Are there users who want CentOS5 builds?
Am 4. Dezember 2017 13:23:39 MEZ schrieb Jim Jagielski <ji...@jaguNET.com>:
>Thx. Yeah, I got that. I also understand that GIO is, by far, the
>recommended option.
>
>So our options are:
>
> 1. We stick w/ CentOS5 as our ref build system for 4.2.0 but force
> Gnome VFS.
>
> 2. We move to CentOS6, accept the default of GIO but understand that
> this moves CentOS5 as a non-supported OS for our community builds.
>
> 3. Just as we offer Linux 32 and 64bit builds, starting w/ 4.2.0
> we offer CentOS5 community builds (w/ Gnome VFS) IN ADDITION
> TO CentOS6 builds (w/ GIO). (i.e.: 32bit-Gnome VFS, 64bit-Gnome VFS,
> 32bit-GIO, 64bit-GIO).
>
>It doesn't matter to me... I'm setup to be able to
>do any and all options re: builds. Whatever makes most
>sense for our end-users and community is what we should
>do.
>
>> On Dec 3, 2017, at 6:43 PM, Damjan Jovanovic <da...@apache.org>
>wrote:
>>
>> Sorry what I meant to say was, those flags to ./configure still let
>you
>> build with Gnome VFS instead of GIO.
>>
>> I didn't take GIO out of the build, I just switched the default VFS
>> implementation from Gnome VFS to GIO.
>>
>> Damjan
>>
>> On Sun, Dec 3, 2017 at 4:28 PM, Jim Jagielski <ji...@jagunet.com>
>wrote:
>>
>>>
>>>> On Dec 3, 2017, at 1:16 AM, Damjan Jovanovic <da...@apache.org>
>wrote:
>>>>
>>>> On Sun, Dec 3, 2017 at 2:25 AM, Jim Jagielski <ji...@jagunet.com>
>wrote:
>>>>
>>>>>
>>>>>> On Dec 2, 2017, at 5:56 PM, Andrea Pescetti <pe...@apache.org>
>>> wrote:
>>>>>>
>>>>>> On 30/11/2017 Jim Jagielski wrote:
>>>>>>> I think for 4.2.x and later, we have deprecated CentOS5 as a
>supported
>>>>>>> build system... I ran into a LOT of issues.
>>>>>>
>>>>>> Such as, for example?
>>>>>
>>>>> for starters:
>>>>> o zip 3.0.
>>>>> o GIO
>>>>>
>>>>>
>>>> If you *really* need GIO, try adding --disable-gio
>--enable-gnome-vfs to
>>>> ./configure.
>>>>
>>>
>>> The issue is that CentOS5 simply does not and can not provide GIO.
>>> So it is, IMO at least, unsuitable for our reference community
>>> build platform.
>>>
>>> This was brought up on the "AOO 4.2.0-dev builds" thread.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>For additional commands, e-mail: dev-help@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: 4.2.0: Baseline CentOS6 as reference build platform
Posted by Andrea Pescetti <pe...@apache.org>.
Jim Jagielski wrote:
> So our options are:
> 1. We stick w/ CentOS5 as our ref build system for 4.2.0 but force
> Gnome VFS.
> 2. We move to CentOS6, accept the default of GIO but understand that
> this moves CentOS5 as a non-supported OS for our community builds.
> 3. Just as we offer Linux 32 and 64bit builds, starting w/ 4.2.0
> we offer CentOS5 community builds (w/ Gnome VFS) IN ADDITION
> TO CentOS6 builds (w/ GIO). (i.e.: 32bit-Gnome VFS, 64bit-Gnome VFS,
> 32bit-GIO, 64bit-GIO).
If the post on your web space spurs a debate, we can indeed let users
choose; but if that doesn't come I guess we are simply left with the
responsibility of choosing for them, and option 3 looks the best one.
In that sense, CentOS 5 is not only old but officially dead and
unsupported. This should be taken into consideration, not only the
number of users. That said, virtually any Linux distribution released in
2011 or later (a huge period by Linux distributions standards) will be
supported if we switch to CentOS 6 for "official" builds. Bugzilla link:
https://bz.apache.org/ooo/show_bug.cgi?id=127513
It seems reasonable to believe that we can offer CentOS6 builds from the
download page and CentOS5 builds (in a "more unofficial" fashion, as we
already did once in the past; and linked from the Release Notes but not
from the download page) from a committer's home directory.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: 4.2.0: Baseline CentOS6 as reference build platform
Posted by Jim Jagielski <ji...@jaguNET.com>.
Thx. Yeah, I got that. I also understand that GIO is, by far, the
recommended option.
So our options are:
1. We stick w/ CentOS5 as our ref build system for 4.2.0 but force
Gnome VFS.
2. We move to CentOS6, accept the default of GIO but understand that
this moves CentOS5 as a non-supported OS for our community builds.
3. Just as we offer Linux 32 and 64bit builds, starting w/ 4.2.0
we offer CentOS5 community builds (w/ Gnome VFS) IN ADDITION
TO CentOS6 builds (w/ GIO). (i.e.: 32bit-Gnome VFS, 64bit-Gnome VFS,
32bit-GIO, 64bit-GIO).
It doesn't matter to me... I'm setup to be able to
do any and all options re: builds. Whatever makes most
sense for our end-users and community is what we should
do.
> On Dec 3, 2017, at 6:43 PM, Damjan Jovanovic <da...@apache.org> wrote:
>
> Sorry what I meant to say was, those flags to ./configure still let you
> build with Gnome VFS instead of GIO.
>
> I didn't take GIO out of the build, I just switched the default VFS
> implementation from Gnome VFS to GIO.
>
> Damjan
>
> On Sun, Dec 3, 2017 at 4:28 PM, Jim Jagielski <ji...@jagunet.com> wrote:
>
>>
>>> On Dec 3, 2017, at 1:16 AM, Damjan Jovanovic <da...@apache.org> wrote:
>>>
>>> On Sun, Dec 3, 2017 at 2:25 AM, Jim Jagielski <ji...@jagunet.com> wrote:
>>>
>>>>
>>>>> On Dec 2, 2017, at 5:56 PM, Andrea Pescetti <pe...@apache.org>
>> wrote:
>>>>>
>>>>> On 30/11/2017 Jim Jagielski wrote:
>>>>>> I think for 4.2.x and later, we have deprecated CentOS5 as a supported
>>>>>> build system... I ran into a LOT of issues.
>>>>>
>>>>> Such as, for example?
>>>>
>>>> for starters:
>>>> o zip 3.0.
>>>> o GIO
>>>>
>>>>
>>> If you *really* need GIO, try adding --disable-gio --enable-gnome-vfs to
>>> ./configure.
>>>
>>
>> The issue is that CentOS5 simply does not and can not provide GIO.
>> So it is, IMO at least, unsuitable for our reference community
>> build platform.
>>
>> This was brought up on the "AOO 4.2.0-dev builds" thread.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: 4.2.0: Baseline CentOS6 as reference build platform
Posted by Damjan Jovanovic <da...@apache.org>.
Sorry what I meant to say was, those flags to ./configure still let you
build with Gnome VFS instead of GIO.
I didn't take GIO out of the build, I just switched the default VFS
implementation from Gnome VFS to GIO.
Damjan
On Sun, Dec 3, 2017 at 4:28 PM, Jim Jagielski <ji...@jagunet.com> wrote:
>
> > On Dec 3, 2017, at 1:16 AM, Damjan Jovanovic <da...@apache.org> wrote:
> >
> > On Sun, Dec 3, 2017 at 2:25 AM, Jim Jagielski <ji...@jagunet.com> wrote:
> >
> >>
> >>> On Dec 2, 2017, at 5:56 PM, Andrea Pescetti <pe...@apache.org>
> wrote:
> >>>
> >>> On 30/11/2017 Jim Jagielski wrote:
> >>>> I think for 4.2.x and later, we have deprecated CentOS5 as a supported
> >>>> build system... I ran into a LOT of issues.
> >>>
> >>> Such as, for example?
> >>
> >> for starters:
> >> o zip 3.0.
> >> o GIO
> >>
> >>
> > If you *really* need GIO, try adding --disable-gio --enable-gnome-vfs to
> > ./configure.
> >
>
> The issue is that CentOS5 simply does not and can not provide GIO.
> So it is, IMO at least, unsuitable for our reference community
> build platform.
>
> This was brought up on the "AOO 4.2.0-dev builds" thread.
4.2.0: Baseline CentOS6 as reference build platform
Posted by Jim Jagielski <ji...@jaguNET.com>.
> On Dec 3, 2017, at 1:16 AM, Damjan Jovanovic <da...@apache.org> wrote:
>
> On Sun, Dec 3, 2017 at 2:25 AM, Jim Jagielski <ji...@jagunet.com> wrote:
>
>>
>>> On Dec 2, 2017, at 5:56 PM, Andrea Pescetti <pe...@apache.org> wrote:
>>>
>>> On 30/11/2017 Jim Jagielski wrote:
>>>> I think for 4.2.x and later, we have deprecated CentOS5 as a supported
>>>> build system... I ran into a LOT of issues.
>>>
>>> Such as, for example?
>>
>> for starters:
>> o zip 3.0.
>> o GIO
>>
>>
> If you *really* need GIO, try adding --disable-gio --enable-gnome-vfs to
> ./configure.
>
The issue is that CentOS5 simply does not and can not provide GIO.
So it is, IMO at least, unsuitable for our reference community
build platform.
This was brought up on the "AOO 4.2.0-dev builds" thread.
Re: a more sane way to override optimization flags in gbuild
Posted by Damjan Jovanovic <da...@apache.org>.
On Sun, Dec 3, 2017 at 2:25 AM, Jim Jagielski <ji...@jagunet.com> wrote:
>
> > On Dec 2, 2017, at 5:56 PM, Andrea Pescetti <pe...@apache.org> wrote:
> >
> > On 30/11/2017 Jim Jagielski wrote:
> >> I think for 4.2.x and later, we have deprecated CentOS5 as a supported
> >> build system... I ran into a LOT of issues.
> >
> > Such as, for example?
>
> for starters:
> o zip 3.0.
> o GIO
>
>
If you *really* need GIO, try adding --disable-gio --enable-gnome-vfs to
./configure.
The check for ZIP version 3.0 was added in revision 1755455, the gbuild
branch merge into trunk. Within that branch it was added in this commit:
r1409544 | arist | 2012-11-15 01:22:40 +0200 (Thu, 15 Nov 2012) | 9 lines
Changed paths:
M /incubator/ooo/branches/gbuild/main/configure.in
gnumake4_047_ce56f9735b9c.patch
# HG changeset patch
# User Michael Stahl <ms...@openoffice.org>
# Date 1301690824 0
# Node ID ce56f9735b9cd04f4e2724754fe7c11d9cec1ca9
# Parent e37d17b6d8d93e87a4886268f338a2d4ea2a6304
gnumake4: configure.in: require Info-ZIP 3.0
apparently around the time they were adding support for Java in gbuild.
Maybe gbuild uses a ZIP 3 feature for JAR files? This is all we do with zip
in gbuild:
$(gb_Zip_ZIPCOMMAND) -rX -FS $(call gb_Zip_get_target,$*) $(FILES) )
are -rX or -FS new?
But can we please use another thread for such issues?
Damjan
Re: a more sane way to override optimization flags in gbuild
Posted by Jim Jagielski <ji...@jaguNET.com>.
> On Dec 2, 2017, at 5:56 PM, Andrea Pescetti <pe...@apache.org> wrote:
>
> On 30/11/2017 Jim Jagielski wrote:
>> I think for 4.2.x and later, we have deprecated CentOS5 as a supported
>> build system... I ran into a LOT of issues.
>
> Such as, for example?
for starters:
o zip 3.0.
o GIO
> I think that the guide we have at
> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#CentOS_5
> used to be the most solid procedure to build OpenOffice, while it is well-known that building on Windows is complex and building on Mac is even more complex and resulted in broken builds several times.
>
> The reason I'm asking is not because CentOS 5 is particularly relevant (I think we have agreement that we'll switch to CentOS 6 for 4.2.x and that the next, if any, 4.1.x releases will cover major regressions only), but because I think that an updated version (to CentOS 6) of that guide should be the reference for our 4.2.x builds. So if there are issues that can be ironed out, better to do it as soon as possible.
Isn't that exactly what I'm doing??? Or do you have some
other point to make?