You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@openoffice.apache.org by Dave Fisher <wa...@apache.org> on 2020/08/20 17:38:23 UTC

Re: OpenSSL versions


> On Aug 20, 2020, at 10:27 AM, Matthias Seidel <ma...@hamburg.de> wrote:
> 
> Hi Don,
> 
> Am 20.08.20 um 18:35 schrieb Don Lewis:
>> 
>>> Need to look at the history of
>>> 
>>> (1) openssl
>>> (2) curl
>>> (3) and the code that uses those.
>> The version of openssl used by 4.1.7 is seriously out of date and
>> doesn't support recent versions of TLS.
> 
> Can we update openssl in 4.1.8 at least to the version we use in
> trunk/AOO42X?

Yes, please.

> 
> That version is "new" enough and has proven to be stable.

Here is the version history:

3.4: openssl-0.9.8o
4.0: openssl-0.9.8o
4.1.0: openssl-0.9.8zg
4.1.6: openssl-0.9.8zh

42X: openssl-1.0.2t

A general question as we triage the update services bug,

Have we ever used the system openssl in any of our released builds?

Regards,
Dave

> 
> Regards,
> 
>    Matthias
> 
>> 
>> 
>> ---------------------------------------------------------------------
>> 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: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]

Posted by Don Lewis <tr...@apache.org>.

On 24 Aug, Pedro Lino wrote:
> 
>> On 08/24/2020 3:18 PM Don Lewis <tr...@apache.org> wrote:
> 
>> Is this a parallel build?  Has the offuh module been built and
>> delivered?  Seems oa little dd that offuh is not listed as a dependency
>> in sax/prj/build.lst, but it is listed as a dependency of cppuhelper and 
>> cppuhelper is listed as a dependency of sax.
>> 
>> When offuh is delivered, it should put a copy of UnicodeType.hpp here:
>> solver/*/unxlngx6.pro/inc/offuh/com/sun/star/i18n/UnicodeType.hpp
> 
> I build using all cores (in this case 8). This was never a problem with 42X.
> 
> There was no offuh module...

If offuh was not built and delivered then that will break sax for sure.

With the latest set of cherry-picks, I'm seeing these modules fail:
  beanshell
  hsqldb
  saxon
  apache-commons
  rhino
  lucene
  ridljar
  jvmfwk

which are most/all java, I think.

i haven't run into the libgcc_s.so.1 issue.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org

Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]

Posted by Pedro Lino <pe...@mailbox.org>.

> On 08/24/2020 3:18 PM Don Lewis <tr...@apache.org> wrote:

> Is this a parallel build?  Has the offuh module been built and
> delivered?  Seems oa little dd that offuh is not listed as a dependency
> in sax/prj/build.lst, but it is listed as a dependency of cppuhelper and 
> cppuhelper is listed as a dependency of sax.
> 
> When offuh is delivered, it should put a copy of UnicodeType.hpp here:
> solver/*/unxlngx6.pro/inc/offuh/com/sun/star/i18n/UnicodeType.hpp

I build using all cores (in this case 8). This was never a problem with 42X.

There was no offuh module...

I'm now compiling 418 on a single thread...

Thanks!

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org

Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]

Posted by Don Lewis <tr...@apache.org>.

On 24 Aug, Don Lewis wrote:
> On 24 Aug, Pedro Lino wrote:
>> Hi Don, all
>> 
>>> On 08/24/2020 3:18 PM Don Lewis <tr...@apache.org> wrote:
>> 
>>> Is this a parallel build?
>> 
>> Switched to single thread building
>> 
>> build --all
>> 
>> when it stopped I followed the suggestion by Rigo and deleted
>> /source/openoffice/main/solver/418/unxlngx6.pro/lib/libgcc_s.so.1
>> 
>> and restarted with build --all:icu
>> 
>> Now it stopped again at
>> 
>> In file included from /source/openoffice/main/solver/418/unxlngx6.pro/inc/boost/shared_array.hpp:17:0,
>>                  from ../inc/basebmp/bitmapdevice.hxx:32,
>>                  from /source/openoffice/main/basebmp/source/bitmapdevice.cxx:28:
>> /source/openoffice/main/solver/418/unxlngx6.pro/inc/boost/smart_ptr/shared_array.hpp:177:37: warning: mangled name for ‘void boost::shared_array<T>::reset(Y*, D) [with Y = unsigned char; D = void (*)(void*) throw (); T = unsigned char]’ will change in C++17 because the exception specification is part of a function type [-Wnoexcept-type]
>>      template<class Y, class D> void reset( Y * p, D d )
>>                                      ^~~~~
>> dmake:  Error code 1, while making '../unxlngx6.pro/slo/bitmapdevice.obj'
>> 
>> 1 module(s): 
>> 	basebmp
>> need(s) to be rebuilt
>> 
>> Reason(s):
>> 
>> ERROR: error 65280 occurred while making /source/openoffice/main/basebmp/source
>> 
>> When you have fixed the errors in that module you can resume the build by running:
>> 
>> 	build --all:basebmp
>> 
>> Ideas?
> 
> basebmp fails due to a bug that I patched in trunk and AOO42X a while
> back, when clang on FreeBSD found it.  I guess that the version of gcc
> in Ubuntu 18 doesn't like it either.  It's one of the bug fixes that I
> plan to cherry-pick for AOO418 tonight.

I justt did that, but there is another change that I need to cherry-pick
for the patch to bundled boost before we are ready for the -std=gnu++98
fix for Linux.  The ancient version of boost that we bundle doesn't
really understand the features of modern gcc.  I can get away with the
-std=gnu++98 setting the FreeBSD port of 4.1.7 because it uses system
boost, which is more modern.  I need to do some more testing before I'm
ready for this.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org

Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]

Posted by Don Lewis <tr...@apache.org>.

On 25 Aug, Pedro Lino wrote:
> Hi Don
> 
>> On 08/25/2020 10:59 AM Don Lewis <tr...@apache.org> wrote:
> 
>> With the latest batch of cherry-picks that I just pushed to AOO418
>> and using OpenJDK 8, I was able to build AOO418 on Ubuntu 18.
> 
> After updating with your latest changes and hacking a bit with the
> libgcc file mentioned in the subject, compiling ended with success.
> However after installing (without errors) the program doesn't run...
> 
> Did you install (or execute the binaries)? If they work can you share
> the tar.gz file?

I haven't had a chance to install it.  Once it built, I declared victory
and went to sleep.

I didn't run into the libgcc_s.so.1 problem.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org

Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]

Posted by Pedro Lino <pe...@mailbox.org>.

Hi Don

> On 08/25/2020 8:29 PM Don Lewis <tr...@apache.org> wrote:

> For me, it goes through the registration process and then I can create
> and save a writer document.  If I exit, I can reopen the document from
> the command line.  Looks like it works.

Sounds like a good one ;)

Can you upload it somewhere and share the link?

I will compile again tomorrow after switching to OpenJDK 8

Thanks!
Pedro

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org

Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]

Posted by Don Lewis <tr...@apache.org>.

On 25 Aug, Matthias Seidel wrote:
> Hi Pedro,
> 
> Am 25.08.20 um 20:11 schrieb Pedro Lino:
>> Hi Don
>>
>>> On 08/25/2020 10:59 AM Don Lewis <tr...@apache.org> wrote:
>>> With the latest batch of cherry-picks that I just pushed to AOO418 and
>>> using OpenJDK 8, I was able to build AOO418 on Ubuntu 18.
>> After updating with your latest changes and hacking a bit with the libgcc file mentioned in the subject, compiling ended with success. However after installing (without errors) the program doesn't run...
> 
> If you start AOO in a shell with "soffice", does that give some information?

For me, it goes through the registration process and then I can create
and save a writer document.  If I exit, I can reopen the document from
the command line.  Looks like it works.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org

Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]

Posted by Don Lewis <tr...@apache.org>.

On 25 Aug, Pedro Lino wrote:
> Hi Matthias
> 
>> On 08/25/2020 8:07 PM Matthias Seidel <ma...@hamburg.de> wrote:
> 
>> If you start AOO in a shell with "soffice", does that give some information?
> 
> Didn't think about that :)
> 
> /opt/openoffice4/program/javaldx: error while loading shared libraries: /opt/openoffice4/program/libgcc_s.so.1: invalid ELF header
> /opt/openoffice4/program/soffice.bin: error while loading shared libraries: /opt/openoffice4/program/libgcc_s.so.1: invalid ELF header

I configure with --with-system-stdlibs

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org

Success!!! [Was Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]]

Posted by Pedro Lino <pe...@mailbox.org>.

Hi Don, Matthias, all

> On 08/26/2020 6:09 AM Don Lewis <tr...@apache.org> wrote:

> I just updated AOO418 with the fix.  You should be able to successfully
> build and run --without-system-stdlibs.

I have successfully compiled 418 under Ubuntu 18.04 x64 (without any system-stdlibs switch, which I assume defaults to --without)

I installed on a separate machine (also running Ubuntu 18.04 x64) and checking for updated and extensions is working flawlessly AND editing files through WebDAV is working again as expected!

Thank you very much to both for the fixes and feedback!

This is a Good Day! :)

Kind regards,
Pedro

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org

Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]

Posted by Don Lewis <tr...@apache.org>.

On 25 Aug, Don Lewis wrote:
> On 25 Aug, Don Lewis wrote:
>> On 25 Aug, Pedro Lino wrote:
>>> 
>>>> On 08/25/2020 8:35 PM Don Lewis <tr...@apache.org> wrote:
>>> 
>>>> Try deleting /opt/openoffice4/program/libgcc_s.so.1
>>>> For some reason that bogus file is getting packaged by your build.
>>> 
>>> Yep. That fixed it. It doesn't make any sense to me that an extra file
>>> prevents the program from working... Maybe this is part of some
>>> forgotten/abandoned code?
>> 
>> That file is in the shared library search path.  When you try to start a
>> program, it is being found instead of the correct shared library file
>> under /lib, causing the runtime linker to blow a gasket.
>> 
>>> But the file is checked during compiling. If the file is not present,
>>> building "postprocess" will fail...
>>> 
>>> I will try building with --with-system-stdlibs
>>> 
>>> Thank you for the tips and fixes!
> 
> I dug into this a bit more.  It turns out that the bogus copy of
> libgcc_s.so.1 is a linker script and not a shared library.   Linker 
> scripts are a failrly new thing, which is why we haven't run into this
> before.  The build code that is grabbing this file was removed from
> trunk and AOO42X a few years ago, which is why you didn't see the
> problem with those versions.  I've cherry-picked the fix and will push
> it to AOO418 after I've had a chance to test it.

I just updated AOO418 with the fix.  You should be able to successfully
build and run --without-system-stdlibs.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org

Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]

Posted by Don Lewis <tr...@apache.org>.

On 27 Aug, Matthias Seidel wrote:
> Hi Don,
> 
> Am 26.08.20 um 03:55 schrieb Don Lewis:
>> On 25 Aug, Don Lewis wrote:
>>> On 25 Aug, Pedro Lino wrote:
>>>>> On 08/25/2020 8:35 PM Don Lewis <tr...@apache.org> wrote:
>>>>> Try deleting /opt/openoffice4/program/libgcc_s.so.1
>>>>> For some reason that bogus file is getting packaged by your build.
>>>> Yep. That fixed it. It doesn't make any sense to me that an extra file
>>>> prevents the program from working... Maybe this is part of some
>>>> forgotten/abandoned code?
>>> That file is in the shared library search path.  When you try to start a
>>> program, it is being found instead of the correct shared library file
>>> under /lib, causing the runtime linker to blow a gasket.
>>>
>>>> But the file is checked during compiling. If the file is not present,
>>>> building "postprocess" will fail...
>>>>
>>>> I will try building with --with-system-stdlibs
>>>>
>>>> Thank you for the tips and fixes!
>> I dug into this a bit more.  It turns out that the bogus copy of
>> libgcc_s.so.1 is a linker script and not a shared library.   Linker 
>> scripts are a failrly new thing, which is why we haven't run into this
>> before.  The build code that is grabbing this file was removed from
>> trunk and AOO42X a few years ago, which is why you didn't see the
>> problem with those versions.  I've cherry-picked the fix and will push
>> it to AOO418 after I've had a chance to test it.
> 
> Great!
> 
> Then we can set this issue (i104495 - libstdc++ removal) to
> resolved/fixed now?

I guess so, though I haven't tested the KDE bits.
 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org

Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]

Posted by Matthias Seidel <ma...@hamburg.de>.

Hi Don,

Am 26.08.20 um 03:55 schrieb Don Lewis:
> On 25 Aug, Don Lewis wrote:
>> On 25 Aug, Pedro Lino wrote:
>>>> On 08/25/2020 8:35 PM Don Lewis <tr...@apache.org> wrote:
>>>> Try deleting /opt/openoffice4/program/libgcc_s.so.1
>>>> For some reason that bogus file is getting packaged by your build.
>>> Yep. That fixed it. It doesn't make any sense to me that an extra file
>>> prevents the program from working... Maybe this is part of some
>>> forgotten/abandoned code?
>> That file is in the shared library search path.  When you try to start a
>> program, it is being found instead of the correct shared library file
>> under /lib, causing the runtime linker to blow a gasket.
>>
>>> But the file is checked during compiling. If the file is not present,
>>> building "postprocess" will fail...
>>>
>>> I will try building with --with-system-stdlibs
>>>
>>> Thank you for the tips and fixes!
> I dug into this a bit more.  It turns out that the bogus copy of
> libgcc_s.so.1 is a linker script and not a shared library.   Linker 
> scripts are a failrly new thing, which is why we haven't run into this
> before.  The build code that is grabbing this file was removed from
> trunk and AOO42X a few years ago, which is why you didn't see the
> problem with those versions.  I've cherry-picked the fix and will push
> it to AOO418 after I've had a chance to test it.

Great!

Then we can set this issue (i104495 - libstdc++ removal) to
resolved/fixed now?

Regards,

   Matthias

>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>

Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]

Posted by Don Lewis <tr...@apache.org>.

On 25 Aug, Don Lewis wrote:
> On 25 Aug, Pedro Lino wrote:
>> 
>>> On 08/25/2020 8:35 PM Don Lewis <tr...@apache.org> wrote:
>> 
>>> Try deleting /opt/openoffice4/program/libgcc_s.so.1
>>> For some reason that bogus file is getting packaged by your build.
>> 
>> Yep. That fixed it. It doesn't make any sense to me that an extra file
>> prevents the program from working... Maybe this is part of some
>> forgotten/abandoned code?
> 
> That file is in the shared library search path.  When you try to start a
> program, it is being found instead of the correct shared library file
> under /lib, causing the runtime linker to blow a gasket.
> 
>> But the file is checked during compiling. If the file is not present,
>> building "postprocess" will fail...
>> 
>> I will try building with --with-system-stdlibs
>> 
>> Thank you for the tips and fixes!

I dug into this a bit more.  It turns out that the bogus copy of
libgcc_s.so.1 is a linker script and not a shared library.   Linker 
scripts are a failrly new thing, which is why we haven't run into this
before.  The build code that is grabbing this file was removed from
trunk and AOO42X a few years ago, which is why you didn't see the
problem with those versions.  I've cherry-picked the fix and will push
it to AOO418 after I've had a chance to test it.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org

Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]

Posted by Don Lewis <tr...@apache.org>.

On 25 Aug, Pedro Lino wrote:
> 
>> On 08/25/2020 8:35 PM Don Lewis <tr...@apache.org> wrote:
> 
>> Try deleting /opt/openoffice4/program/libgcc_s.so.1
>> For some reason that bogus file is getting packaged by your build.
> 
> Yep. That fixed it. It doesn't make any sense to me that an extra file
> prevents the program from working... Maybe this is part of some
> forgotten/abandoned code?

That file is in the shared library search path.  When you try to start a
program, it is being found instead of the correct shared library file
under /lib, causing the runtime linker to blow a gasket.

> But the file is checked during compiling. If the file is not present,
> building "postprocess" will fail...
> 
> I will try building with --with-system-stdlibs
> 
> Thank you for the tips and fixes!
> 
> Best,
> Pedro
> 
> ---------------------------------------------------------------------
> 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: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]

Posted by Pedro Lino <pe...@mailbox.org>.

> On 08/25/2020 8:35 PM Don Lewis <tr...@apache.org> wrote:

> Try deleting /opt/openoffice4/program/libgcc_s.so.1
> For some reason that bogus file is getting packaged by your build.

Yep. That fixed it. It doesn't make any sense to me that an extra file prevents the program from working... Maybe this is part of some forgotten/abandoned code?

But the file is checked during compiling. If the file is not present, building "postprocess" will fail...

I will try building with --with-system-stdlibs

Thank you for the tips and fixes!

Best,
Pedro

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org

Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]

Posted by Don Lewis <tr...@apache.org>.

On 25 Aug, Pedro Lino wrote:
> Hi Matthias
> 
>> On 08/25/2020 8:07 PM Matthias Seidel <ma...@hamburg.de> wrote:
> 
>> If you start AOO in a shell with "soffice", does that give some information?
> 
> Didn't think about that :)
> 
> /opt/openoffice4/program/javaldx: error while loading shared libraries: /opt/openoffice4/program/libgcc_s.so.1: invalid ELF header
> /opt/openoffice4/program/soffice.bin: error while loading shared libraries: /opt/openoffice4/program/libgcc_s.so.1: invalid ELF header

Try deleting /opt/openoffice4/program/libgcc_s.so.1
For some reason that bogus file is getting packaged by your build.  I'm
not seeing that happen here:
$ ls /opt/openoffice4/program/libg*
/opt/openoffice4/program/libgcc3_uno.so
/opt/openoffice4/program/libguesslang.so


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org

Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]

Posted by Pedro Lino <pe...@mailbox.org>.

Hi Matthias

> On 08/25/2020 8:07 PM Matthias Seidel <ma...@hamburg.de> wrote:

> If you start AOO in a shell with "soffice", does that give some information?

Didn't think about that :)

/opt/openoffice4/program/javaldx: error while loading shared libraries: /opt/openoffice4/program/libgcc_s.so.1: invalid ELF header
/opt/openoffice4/program/soffice.bin: error while loading shared libraries: /opt/openoffice4/program/libgcc_s.so.1: invalid ELF header

Regards,
Pedro

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org

Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]

Posted by Matthias Seidel <ma...@hamburg.de>.

Hi Pedro,

Am 25.08.20 um 20:11 schrieb Pedro Lino:
> Hi Don
>
>> On 08/25/2020 10:59 AM Don Lewis <tr...@apache.org> wrote:
>> With the latest batch of cherry-picks that I just pushed to AOO418 and
>> using OpenJDK 8, I was able to build AOO418 on Ubuntu 18.
> After updating with your latest changes and hacking a bit with the libgcc file mentioned in the subject, compiling ended with success. However after installing (without errors) the program doesn't run...

If you start AOO in a shell with "soffice", does that give some information?

Regards,

   Matthias

>
> Did you install (or execute the binaries)? If they work can you share the tar.gz file?
>
> Maybe setting java 8 as default solves the problem...
>
> Thanks!
> Pedro
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>

Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]

Posted by Pedro Lino <pe...@mailbox.org>.

Hi Don

> On 08/25/2020 10:59 AM Don Lewis <tr...@apache.org> wrote:

> With the latest batch of cherry-picks that I just pushed to AOO418 and
> using OpenJDK 8, I was able to build AOO418 on Ubuntu 18.

After updating with your latest changes and hacking a bit with the libgcc file mentioned in the subject, compiling ended with success. However after installing (without errors) the program doesn't run...

Did you install (or execute the binaries)? If they work can you share the tar.gz file?

Maybe setting java 8 as default solves the problem...

Thanks!
Pedro

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org

Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]

Posted by Don Lewis <tr...@apache.org>.

On 25 Aug, Pedro Lino wrote:
> 
>> On 08/25/2020 3:47 AM Don Lewis <tr...@apache.org> wrote:
> 
>> It's one of the bug fixes that I
>> plan to cherry-pick for AOO418 tonight.
> 
> Excellent! Thanks!
> 
>> What version of OpenJDK are you using?  I'm seeing a fair amount of
>> fallout from OpenJDK 11.
> 
> I have both 8 and 11
> 
> sudo update-alternatives --config java
> 
> There are 2 choices for the alternative java (providing /usr/bin/java).
> 
>   Selection    Path                                            Priority   Status
> ------------------------------------------------------------
> * 0            /usr/lib/jvm/java-11-openjdk-amd64/bin/java      1111      auto mode
>   1            /usr/lib/jvm/java-11-openjdk-amd64/bin/java      1111      manual mode
>   2            /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java   1081      manual mode
> 
> Java 11 is
> openjdk version "11.0.8" 2020-07-14
> OpenJDK Runtime Environment (build 11.0.8+10-post-Ubuntu-0ubuntu118.04.1)
> OpenJDK 64-Bit Server VM (build 11.0.8+10-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing)

With the latest batch of cherry-picks that I just pushed to AOO418 and
using OpenJDK 8, I was able to build AOO418 on Ubuntu 18.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org

Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]

Posted by Pedro Lino <pe...@mailbox.org>.

> On 08/25/2020 3:47 AM Don Lewis <tr...@apache.org> wrote:

> It's one of the bug fixes that I
> plan to cherry-pick for AOO418 tonight.

Excellent! Thanks!

> What version of OpenJDK are you using?  I'm seeing a fair amount of
> fallout from OpenJDK 11.

I have both 8 and 11

sudo update-alternatives --config java

There are 2 choices for the alternative java (providing /usr/bin/java).

  Selection    Path                                            Priority   Status
------------------------------------------------------------
* 0            /usr/lib/jvm/java-11-openjdk-amd64/bin/java      1111      auto mode
  1            /usr/lib/jvm/java-11-openjdk-amd64/bin/java      1111      manual mode
  2            /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java   1081      manual mode

Java 11 is
openjdk version "11.0.8" 2020-07-14
OpenJDK Runtime Environment (build 11.0.8+10-post-Ubuntu-0ubuntu118.04.1)
OpenJDK 64-Bit Server VM (build 11.0.8+10-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org

Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]

Posted by Don Lewis <tr...@apache.org>.

On 24 Aug, Pedro Lino wrote:
> Hi Don, all
> 
>> On 08/24/2020 3:18 PM Don Lewis <tr...@apache.org> wrote:
> 
>> Is this a parallel build?
> 
> Switched to single thread building
> 
> build --all
> 
> when it stopped I followed the suggestion by Rigo and deleted
> /source/openoffice/main/solver/418/unxlngx6.pro/lib/libgcc_s.so.1
> 
> and restarted with build --all:icu
> 
> Now it stopped again at
> 
> In file included from /source/openoffice/main/solver/418/unxlngx6.pro/inc/boost/shared_array.hpp:17:0,
>                  from ../inc/basebmp/bitmapdevice.hxx:32,
>                  from /source/openoffice/main/basebmp/source/bitmapdevice.cxx:28:
> /source/openoffice/main/solver/418/unxlngx6.pro/inc/boost/smart_ptr/shared_array.hpp:177:37: warning: mangled name for ‘void boost::shared_array<T>::reset(Y*, D) [with Y = unsigned char; D = void (*)(void*) throw (); T = unsigned char]’ will change in C++17 because the exception specification is part of a function type [-Wnoexcept-type]
>      template<class Y, class D> void reset( Y * p, D d )
>                                      ^~~~~
> dmake:  Error code 1, while making '../unxlngx6.pro/slo/bitmapdevice.obj'
> 
> 1 module(s): 
> 	basebmp
> need(s) to be rebuilt
> 
> Reason(s):
> 
> ERROR: error 65280 occurred while making /source/openoffice/main/basebmp/source
> 
> When you have fixed the errors in that module you can resume the build by running:
> 
> 	build --all:basebmp
> 
> Ideas?

basebmp fails due to a bug that I patched in trunk and AOO42X a while
back, when clang on FreeBSD found it.  I guess that the version of gcc
in Ubuntu 18 doesn't like it either.  It's one of the bug fixes that I
plan to cherry-pick for AOO418 tonight.

What version of OpenJDK are you using?  I'm seeing a fair amount of
fallout from OpenJDK 11.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org

Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]

Posted by Pedro Lino <pe...@mailbox.org>.

Hi Don

> On 08/24/2020 4:58 PM Don Lewis <tr...@apache.org> wrote:

> The actual error should show up as "error: " in the build output.

The error messages and compiling stop at a completely different step on each run even if I do a dmake clean and repeat the exact same 3 steps.

Adding --enable-verbose did not make messages clearer

Thank you for your patience and assistance but this seems like a random task and I have no idea what I'm doing :(

Thank you anyway!

Best,
Pedro

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org

Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]

Posted by Don Lewis <tr...@apache.org>.

On 24 Aug, Pedro Lino wrote:
> Hi Don, all
> 
>> On 08/24/2020 3:18 PM Don Lewis <tr...@apache.org> wrote:
> 
>> Is this a parallel build?
> 
> Switched to single thread building
> 
> build --all
> 
> when it stopped I followed the suggestion by Rigo and deleted
> /source/openoffice/main/solver/418/unxlngx6.pro/lib/libgcc_s.so.1
> 
> and restarted with build --all:icu
> 
> Now it stopped again at
> 
> In file included from /source/openoffice/main/solver/418/unxlngx6.pro/inc/boost/shared_array.hpp:17:0,
>                  from ../inc/basebmp/bitmapdevice.hxx:32,
>                  from /source/openoffice/main/basebmp/source/bitmapdevice.cxx:28:
> /source/openoffice/main/solver/418/unxlngx6.pro/inc/boost/smart_ptr/shared_array.hpp:177:37: warning: mangled name for ‘void boost::shared_array<T>::reset(Y*, D) [with Y = unsigned char; D = void (*)(void*) throw (); T = unsigned char]’ will change in C++17 because the exception specification is part of a function type [-Wnoexcept-type]
>      template<class Y, class D> void reset( Y * p, D d )
>                                      ^~~~~
> dmake:  Error code 1, while making '../unxlngx6.pro/slo/bitmapdevice.obj'
> 
> 1 module(s): 
> 	basebmp
> need(s) to be rebuilt
> 
> Reason(s):
> 
> ERROR: error 65280 occurred while making /source/openoffice/main/basebmp/source
> 
> When you have fixed the errors in that module you can resume the build by running:
> 
> 	build --all:basebmp
> 
> Ideas?

This looks like just a warning:
77:37: warning: mangled name for ‘void boost::shared_array<T>::reset(Y*, D)
[with Y = unsigned char; D = void (*)(void*) throw (); T = unsigned char]’
will change in C++17
and from the warning it looks like the -std=gnu++98 fix isn't taking
effect.  basebmp hasn't been converted to gbuild in AOO418, so the fix
should be in solenv/inc/unxlng.mk.

The actual error should show up as "error: " in the build output.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org

Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]

Posted by Don Lewis <tr...@apache.org>.

On 24 Aug, Pedro Lino wrote:
> Hi Don, all
> 
>> On 08/24/2020 3:18 PM Don Lewis <tr...@apache.org> wrote:
> 
>> Is this a parallel build?
> 
> Switched to single thread building
> 
> build --all
> 
> when it stopped I followed the suggestion by Rigo and deleted
> /source/openoffice/main/solver/418/unxlngx6.pro/lib/libgcc_s.so.1
> 
> and restarted with build --all:icu
> 
> Now it stopped again at
> 
> In file included from /source/openoffice/main/solver/418/unxlngx6.pro/inc/boost/shared_array.hpp:17:0,
>                  from ../inc/basebmp/bitmapdevice.hxx:32,
>                  from /source/openoffice/main/basebmp/source/bitmapdevice.cxx:28:
> /source/openoffice/main/solver/418/unxlngx6.pro/inc/boost/smart_ptr/shared_array.hpp:177:37: warning: mangled name for ‘void boost::shared_array<T>::reset(Y*, D) [with Y = unsigned char; D = void (*)(void*) throw (); T = unsigned char]’ will change in C++17 because the exception specification is part of a function type [-Wnoexcept-type]
>      template<class Y, class D> void reset( Y * p, D d )
>                                      ^~~~~
> dmake:  Error code 1, while making '../unxlngx6.pro/slo/bitmapdevice.obj'
> 
> 1 module(s): 
> 	basebmp
> need(s) to be rebuilt
> 
> Reason(s):
> 
> ERROR: error 65280 occurred while making /source/openoffice/main/basebmp/source
> 
> When you have fixed the errors in that module you can resume the build by running:
> 
> 	build --all:basebmp
> 
> Ideas?

You might want to configure with --enable-verbose so that you can see
the compiler command line as each file is compiled.  That will show all
the options passed to the compiler.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org

Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]

Posted by Pedro Lino <pe...@mailbox.org>.

Hi Don, all

> On 08/24/2020 3:18 PM Don Lewis <tr...@apache.org> wrote:

> Is this a parallel build?

Switched to single thread building

build --all

when it stopped I followed the suggestion by Rigo and deleted
/source/openoffice/main/solver/418/unxlngx6.pro/lib/libgcc_s.so.1

and restarted with build --all:icu

Now it stopped again at

In file included from /source/openoffice/main/solver/418/unxlngx6.pro/inc/boost/shared_array.hpp:17:0,
                 from ../inc/basebmp/bitmapdevice.hxx:32,
                 from /source/openoffice/main/basebmp/source/bitmapdevice.cxx:28:
/source/openoffice/main/solver/418/unxlngx6.pro/inc/boost/smart_ptr/shared_array.hpp:177:37: warning: mangled name for ‘void boost::shared_array<T>::reset(Y*, D) [with Y = unsigned char; D = void (*)(void*) throw (); T = unsigned char]’ will change in C++17 because the exception specification is part of a function type [-Wnoexcept-type]
     template<class Y, class D> void reset( Y * p, D d )
                                     ^~~~~
dmake:  Error code 1, while making '../unxlngx6.pro/slo/bitmapdevice.obj'

1 module(s): 
	basebmp
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /source/openoffice/main/basebmp/source

When you have fixed the errors in that module you can resume the build by running:

	build --all:basebmp

Ideas?

Thanks!
Pedro

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org

Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]

Posted by Don Lewis <tr...@apache.org>.

On 24 Aug, Pedro Lino wrote:
> Ciao Rigo
> 
>> > /source/openoffice/main/solver/418/unxlngx6.pro/lib/libgcc_s.so.1: invalid ELF header
>> > 
> 
> Now it stopped at expat, but the issue was the same: libgcc_s.so.1: invalid ELF header
> 
>> > I'm wondering why there is a copy of libgcc_s.so.1 here.  That should be
>> > a system library.
>> 
>> I also bumped into this very strange error.
>> 
>> The file was indeed not an ELF, but it contained a number (like "42")
>> or something like that. I cannot remember exactly.
> 
> If the file contained 42 that would be correct because 42 is the answer to everything! ;)
> 
> https://duckduckgo.com/?q=the+answer+to+life+the+universe+everything
> 
>> If I recall correctly, deleting that spurious file was enough to let
>> the build proceed further.
>> 
>> Once the build succeeded, I was not able to reproduce the problem any
>> more, therefore I did not report it.
>> 
>> I hope this helps,
> 
> Yes, it did help to move one step further! Thank you for the suggestion!
> 
> Now it fails at
> 
> =============
> Building module sax
> =============
> 
> Entering /source/openoffice/main/sax/source/tools
> 
> mkout -- version: 1.8
> Making:    all_sax.dpslo
> Compiling: sax/unxlngx6.pro/misc/sax_version.c
> Compiling: sax/source/tools/converter.cxx
> /source/openoffice/main/sax/source/tools/converter.cxx:25:10: fatal error: com/sun/star/i18n/UnicodeType.hpp: No such file or directory
>  #include <com/sun/star/i18n/UnicodeType.hpp>
>           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> compilation terminated.
> dmake:  Error code 1, while making '../../unxlngx6.pro/slo/converter.obj'
> 
> Any ideas?

Is this a parallel build?  Has the offuh module been built and
delivered?  Seems oa little dd that offuh is not listed as a dependency
in sax/prj/build.lst, but it is listed as a dependency of cppuhelper and 
cppuhelper is listed as a dependency of sax.

When offuh is delivered, it should put a copy of UnicodeType.hpp here:
solver/*/unxlngx6.pro/inc/offuh/com/sun/star/i18n/UnicodeType.hpp

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org

Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]

Posted by Pedro Lino <pe...@mailbox.org>.

Ciao Rigo

> > /source/openoffice/main/solver/418/unxlngx6.pro/lib/libgcc_s.so.1: invalid ELF header
> > 

Now it stopped at expat, but the issue was the same: libgcc_s.so.1: invalid ELF header

> > I'm wondering why there is a copy of libgcc_s.so.1 here.  That should be
> > a system library.
> 
> I also bumped into this very strange error.
> 
> The file was indeed not an ELF, but it contained a number (like "42")
> or something like that. I cannot remember exactly.

If the file contained 42 that would be correct because 42 is the answer to everything! ;)

https://duckduckgo.com/?q=the+answer+to+life+the+universe+everything

> If I recall correctly, deleting that spurious file was enough to let
> the build proceed further.
> 
> Once the build succeeded, I was not able to reproduce the problem any
> more, therefore I did not report it.
> 
> I hope this helps,

Yes, it did help to move one step further! Thank you for the suggestion!

Now it fails at

=============
Building module sax
=============

Entering /source/openoffice/main/sax/source/tools

mkout -- version: 1.8
Making:    all_sax.dpslo
Compiling: sax/unxlngx6.pro/misc/sax_version.c
Compiling: sax/source/tools/converter.cxx
/source/openoffice/main/sax/source/tools/converter.cxx:25:10: fatal error: com/sun/star/i18n/UnicodeType.hpp: No such file or directory
 #include <com/sun/star/i18n/UnicodeType.hpp>
          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
dmake:  Error code 1, while making '../../unxlngx6.pro/slo/converter.obj'

Any ideas?

Thanks!
Pedro

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org

Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]

Posted by Arrigo Marchiori <ar...@yahoo.it.INVALID>.

Hello All,

On Fri, Aug 21, 2020 at 12:13:49PM -0700, Don Lewis wrote:

> On 21 Aug, Pedro Lino wrote:
> > Hi Don
> > 
> >> Hmn, I don't know about the extras failure, but all of the other errors
> >> are failures to build various third party packages that we bundle. This
> >> should be independent of the CXXFLAGS issue.  More of the output of
> >>   build --from python
> >> might be informative.
> > 
> > Did a Dmake clean and the problem now starts on icu so here is the output below
> > 
> > #######
> > 
> > build --from icu
> > build -- version: 275224

[...]

> > LD_LIBRARY_PATH=../lib:../stubdata:../tools/ctestfw:$LD_LIBRARY_PATH  ../bin/icupkg -d ./out/build/icudt40l --list -x \* ./in/icudt40l.dat > out/tmp/icudata.lst
> > ../bin/icupkg: error while loading shared libraries: /source/openoffice/main/solver/418/unxlngx6.pro/lib/libgcc_s.so.1: invalid ELF header
> > Makefile:350: recipe for target 'out/tmp/icudata.lst' failed
> > make[1]: *** [out/tmp/icudata.lst] Error 127
> > make[1]: Leaving directory '/source/openoffice/main/icu/unxlngx6.pro/misc/build/icu/source/data'
> > Makefile:103: recipe for target 'all-recursive' failed
> > make: *** [all-recursive] Error 2
> > dmake:  Error code 2, while making './unxlngx6.pro/misc/build/so_built_so_icu'

[...]

> /source/openoffice/main/solver/418/unxlngx6.pro/lib/libgcc_s.so.1: invalid ELF header
> 
> I'm wondering why there is a copy of libgcc_s.so.1 here.  That should be
> a system library.

I also bumped into this very strange error.

The file was indeed not an ELF, but it contained a number (like "42")
or something like that. I cannot remember exactly.

If I recall correctly, deleting that spurious file was enough to let
the build proceed further.

Once the build succeeded, I was not able to reproduce the problem any
more, therefore I did not report it.

I hope this helps,
-- 
rigo

http://rigo.altervista.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org