You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Don Lewis <tr...@apache.org> on 2016/08/15 20:16:39 UTC
upgrading bundled openssl
I started working on upgrading the bundled version of openssl to 1.0.2h.
So far I've discovered that building in on Windows requires nasm. That
will need to be documented in the build requirements / procedures. I
think I need to add a check to configure to look for it and bail out if
nasm isn't installed, but I haven't gotten that far yet. The Windows
buildbot will need to have nasm installed.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: upgrading bundled openssl
Posted by Andrea Pescetti <pe...@apache.org>.
On 22/08/2016 Don Lewis wrote:
> On 21 Aug, Andrea Pescetti wrote:
>> https://bz.apache.org/ooo/show_bug.cgi?id=126312 is the reference issue
>> for the serf upgrade and I know there was more than what is written in
>> the issue, so you can ask for clarifications directly there in the comments.
> I think I'm going to attempt to build with scons. Windows is likely to
> be the most problematic, but even there it it looks like it could be
> feasible.
Plan looks good. It is mostly the approach from
https://bz.apache.org/ooo/show_bug.cgi?id=126312#c1 "if there is
availability of python natively, and the build is native, just install
python (min vers is 2.7) and install SCons (min ver is 2.3.0)" but with
the nice trick of using the Python we already build anyway.
The patch contributed by Giuseppe and left out of 4.1.2 worked on
Windows (reportedly) but not on Mac.
Still, whichever alternate approach you choose, I feel that a brief
preliminary description in the issue itself could be useful.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: upgrading bundled openssl
Posted by Don Lewis <tr...@apache.org>.
On 21 Aug, Andrea Pescetti wrote:
> On 19/08/2016 Don Lewis wrote:
>> The upcoming serf upgrade also has a new dependency issue. It has
>> changed to using scons as its build system, which has its own
>> dependencies, python and m4. I haven't yet decided what to do about
>> that.
>
> I may have already given this information elsewhere, but
> https://bz.apache.org/ooo/show_bug.cgi?id=126312 is the reference issue
> for the serf upgrade and I know there was more than what is written in
> the issue, so you can ask for clarifications directly there in the comments.
>
> Also, since serf is an Apache project and OpenOffice is a prominent user
> of serf, the serf project may be able to advise on a possible
> "lightweight" build process - even though I don't think there is one
> different from scons.
I think I'm going to attempt to build with scons. Windows is likely to
be the most problematic, but even there it it looks like it could be
feasible. Cygwin comes with m4 and we build a bundled version of
python. We wouldn't be able to build scons as part of bootstrap like we
do with dmake, but we should be able to build it as part of the main
build between python and serf. On the other platforms, we could use the
system scons if it is available, or build it like in the Windows port,
but with either system python or bundled python. We would just add m4
as a prerequisite and have configure check for its presence.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: upgrading bundled openssl
Posted by Andrea Pescetti <pe...@apache.org>.
On 19/08/2016 Don Lewis wrote:
> The upcoming serf upgrade also has a new dependency issue. It has
> changed to using scons as its build system, which has its own
> dependencies, python and m4. I haven't yet decided what to do about
> that.
I may have already given this information elsewhere, but
https://bz.apache.org/ooo/show_bug.cgi?id=126312 is the reference issue
for the serf upgrade and I know there was more than what is written in
the issue, so you can ask for clarifications directly there in the comments.
Also, since serf is an Apache project and OpenOffice is a prominent user
of serf, the serf project may be able to advise on a possible
"lightweight" build process - even though I don't think there is one
different from scons.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: upgrading bundled openssl
Posted by Don Lewis <tr...@apache.org>.
On 15 Aug, Marcus wrote:
> Am 08/15/2016 10:16 PM, schrieb Don Lewis:
>> I started working on upgrading the bundled version of openssl to 1.0.2h.
>> So far I've discovered that building in on Windows requires nasm. That
>> will need to be documented in the build requirements / procedures. I
>> think I need to add a check to configure to look for it and bail out if
>> nasm isn't installed, but I haven't gotten that far yet. The Windows
>> buildbot will need to have nasm installed.
>
> puh, so many dependencis and it's still increasing. ;-)
>
> Thanks for working this out.
I figured out how to make nasm an optional dependency, so the openssl
update commit I just made won't immediately break our Windows buildbot.
The upcoming serf upgrade also has a new dependency issue. It has
changed to using scons as its build system, which has its own
dependencies, python and m4. I haven't yet decided what to do about
that.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: upgrading bundled openssl
Posted by Marcus <ma...@wtnet.de>.
Am 08/15/2016 10:16 PM, schrieb Don Lewis:
> I started working on upgrading the bundled version of openssl to 1.0.2h.
> So far I've discovered that building in on Windows requires nasm. That
> will need to be documented in the build requirements / procedures. I
> think I need to add a check to configure to look for it and bail out if
> nasm isn't installed, but I haven't gotten that far yet. The Windows
> buildbot will need to have nasm installed.
puh, so many dependencis and it's still increasing. ;-)
Thanks for working this out.
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org