Re: [External] : Re: LibreOffice architecture support (was: Fwd: Plan to remove dead C++ UNO bridge implementations (bridges/source/cpp_uno/*))

2023-01-12 Thread Petr Sumbera 

Hi,

On 12.01.2023 10:53, John Paul Adrian Glaubitz wrote:

Hi Stephan!

On 1/12/23 10:48, Stephan Bergmann wrote:

On 10/01/2023 19:57, John Paul Adrian Glaubitz wrote:

Hi Stephan!

There are currently 27 different, per-platform C++ UNO bridge 
implementations at
bridges/source/cpp_uno/, some of which are presumably dead by now. 
And my recent


"Rudimentary support for dynamic_cast on UNO proxy objects" (which 
had to touch
each of them individually) was the latest example how even 
presumably dead ones
have ongoing maintenance cost. Therefore, I would like to remove (on 
master,

towards LO 7.6) the ones that can clearly be identified as being dead.

Below, I sorted those 27 implementations into 5 categories: Ideally, 
each active
implementation would be built regularly by Jenkins; those 9 that are 
go into category
1. Next, there are 2 additional implementations that I know are 
built for Fedora
releases; they go into category 2. Next, there are 2 additional 
implementations
that I presume are built for Debian releases (Rene, correct me if 
I'm wrong);
they go into category 3. And then there are 3 implementations that 
are presumably
in active use elsewhere (Tor, wjh-la, Sakura286, correct me if I'm 
wrong); which
go into category 4. That leaves 11 implementations that are 
presumably dead, in

category 5.



(5) Presumably dead:

[...]

* gcc3_solaris_intel
* gcc3_solaris_sparc


Oracle is still maintaining Solaris until at least 2035 and 
OpenIndiana is still maintained, too.


According to this article, LibreOffice 7.2.7 was shipped with 
OpenIndiana 2022.10:


https://urldefense.com/v3/__https://www.theregister.com/2022/12/07/new_version_of_openindiana/__;!!ACWV5N9M2RV99hQ!KXU_z2MpxVAcDc3mFSv6lVajUOw57x8kXdOz-kYNh_H6qrbrbJ_-oDGDaMyqhLSViKqpztTIkBHLPjYe5On88Xvkj9VyDQ$ 


So, I'm not sure dropping Solaris support is a good idea either.


Thanks for that link.

 From 
 it looks like at least OpenIndiana only supports x86-64, so neither gcc3_solar_intel (32-bit x86) nor gcc3_solaris_sparc (32-bit SPARC) should be relevant for it. I'm adding Andreas Wacknitz (who's the author of recent OpenIndiana announcements like ) in CC, maybe he can shed some light on this.  (Andreas, my full original email starting this thread is at  "Plan to remove dead C++ UNO bridge implementations (bridges/source/cpp_uno/*)").


I don't know if there are any other Solaris-based offerings for which 
current LO master gcc3_solaris_intel and/or gcc3_solar_sparc would 
still be relevant.  If somebody knows of any, please report back here.


I'm adding two of the Solaris maintainers at Oracle that I know to ask 
them whether

the SPARC port for LibreOffice is still relevant for them.


We don't build or bundle LibreOffice with Solaris.

I know that in past people tried to build it:
https://sfe.opencsw.org/libreoffice-on-solaris11

Generally if it works on OpenIndiana it's possible that someone tries to 
build it on Solaris too.


I expect that only 64bits and GCC build might be relevant (probably 
rather on Intel than on SPARC).


Thanks,

Petr

Re: LibreOffice architecture support (was: Fwd: Plan to remove dead C++ UNO bridge implementations (bridges/source/cpp_uno/*))

2023-01-12 Thread John Paul Adrian Glaubitz 

Hi Stephan!

On 1/12/23 10:48, Stephan Bergmann wrote:

On 10/01/2023 19:57, John Paul Adrian Glaubitz wrote:

Hi Stephan!


There are currently 27 different, per-platform C++ UNO bridge implementations at
bridges/source/cpp_uno/, some of which are presumably dead by now. And my recent

"Rudimentary support for dynamic_cast on UNO proxy objects" (which had to touch
each of them individually) was the latest example how even presumably dead ones
have ongoing maintenance cost. Therefore, I would like to remove (on master,
towards LO 7.6) the ones that can clearly be identified as being dead.

Below, I sorted those 27 implementations into 5 categories: Ideally, each active
implementation would be built regularly by Jenkins; those 9 that are go into 
category
1. Next, there are 2 additional implementations that I know are built for Fedora
releases; they go into category 2. Next, there are 2 additional implementations
that I presume are built for Debian releases (Rene, correct me if I'm wrong);
they go into category 3. And then there are 3 implementations that are 
presumably
in active use elsewhere (Tor, wjh-la, Sakura286, correct me if I'm wrong); which
go into category 4. That leaves 11 implementations that are presumably dead, in
category 5.



(5) Presumably dead:

[...]

* gcc3_solaris_intel
* gcc3_solaris_sparc


Oracle is still maintaining Solaris until at least 2035 and OpenIndiana is 
still maintained, too.

According to this article, LibreOffice 7.2.7 was shipped with OpenIndiana 
2022.10:


https://www.theregister.com/2022/12/07/new_version_of_openindiana/


So, I'm not sure dropping Solaris support is a good idea either.


Thanks for that link.

 From  it looks like at least OpenIndiana only supports 
x86-64, so neither gcc3_solar_intel (32-bit x86) nor gcc3_solaris_sparc (32-bit SPARC) should be relevant 
for it. I'm adding Andreas Wacknitz (who's the author of recent OpenIndiana announcements like 
) in CC, maybe he can 
shed some light on this.  (Andreas, my full original email starting this thread is at 
 "Plan to remove 
dead C++ UNO bridge implementations (bridges/source/cpp_uno/*)").

I don't know if there are any other Solaris-based offerings for which current 
LO master gcc3_solaris_intel and/or gcc3_solar_sparc would still be relevant.  
If somebody knows of any, please report back here.


I'm adding two of the Solaris maintainers at Oracle that I know to ask them 
whether
the SPARC port for LibreOffice is still relevant for them.

Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Re: LibreOffice architecture support (was: Fwd: Plan to remove dead C++ UNO bridge implementations (bridges/source/cpp_uno/*))

2023-01-12 Thread Stephan Bergmann 

On 10/01/2023 19:57, John Paul Adrian Glaubitz wrote:

Hi Stephan!

There are currently 27 different, per-platform C++ UNO bridge 
implementations at
bridges/source/cpp_uno/, some of which are presumably dead by now. And 
my recent


"Rudimentary support for dynamic_cast on UNO proxy objects" (which had 
to touch
each of them individually) was the latest example how even presumably 
dead ones
have ongoing maintenance cost. Therefore, I would like to remove (on 
master,

towards LO 7.6) the ones that can clearly be identified as being dead.

Below, I sorted those 27 implementations into 5 categories: Ideally, 
each active
implementation would be built regularly by Jenkins; those 9 that are 
go into category
1. Next, there are 2 additional implementations that I know are built 
for Fedora
releases; they go into category 2. Next, there are 2 additional 
implementations
that I presume are built for Debian releases (Rene, correct me if I'm 
wrong);
they go into category 3. And then there are 3 implementations that are 
presumably
in active use elsewhere (Tor, wjh-la, Sakura286, correct me if I'm 
wrong); which
go into category 4. That leaves 11 implementations that are presumably 
dead, in

category 5.



(5) Presumably dead:

[...]

* gcc3_solaris_intel
* gcc3_solaris_sparc


Oracle is still maintaining Solaris until at least 2035 and OpenIndiana 
is still maintained, too.


According to this article, LibreOffice 7.2.7 was shipped with 
OpenIndiana 2022.10:



https://www.theregister.com/2022/12/07/new_version_of_openindiana/


So, I'm not sure dropping Solaris support is a good idea either.


Thanks for that link.

From  it looks like at least 
OpenIndiana only supports x86-64, so neither gcc3_solar_intel (32-bit 
x86) nor gcc3_solaris_sparc (32-bit SPARC) should be relevant for it. 
I'm adding Andreas Wacknitz (who's the author of recent OpenIndiana 
announcements like 
) 
in CC, maybe he can shed some light on this.  (Andreas, my full original 
email starting this thread is at 
 
"Plan to remove dead C++ UNO bridge implementations 
(bridges/source/cpp_uno/*)").


I don't know if there are any other Solaris-based offerings for which 
current LO master gcc3_solaris_intel and/or gcc3_solar_sparc would still 
be relevant.  If somebody knows of any, please report back here.

Re: LibreOffice architecture support (was: Fwd: Plan to remove dead C++ UNO bridge implementations (bridges/source/cpp_uno/*))

2023-01-11 Thread John Paul Adrian Glaubitz 

Hi Stephan!

On 1/11/23 08:21, Stephan Bergmann wrote:

On 10/01/2023 19:57, John Paul Adrian Glaubitz wrote:

(5) Presumably dead:
* gcc3_linux_alpha


=> https://buildd.debian.org/status/logs.php?pkg=libreoffice&arch=alpha


Thanks for those pointers.  Just to make sure, the latest line there being


1:6.4.5-1 (sid) Buildd exposure stats alpha Maybe-Failed 2020-07-03 
06:39:28 phys 18h 37m 9.48 GB


means that that's a build of LO 6.4.5, right?  Are all those Debian Ports 
builds consistently lagging behind current LO master by N years?


No, that's not a consistent state but rather was due to various resource 
problems in the past.

I have actually started working these issues out now and as a first result, the 
latest version
of the libreoffice package was already built successfully on 32-bit PowerPC:


https://buildd.debian.org/status/package.php?p=libreoffice&suite=sid


More architectures will follow within the next weeks. I will make use of the 
freed up time to work
on these issues to get LibreOffice building.

If it helps, please add myself as a code owner for the Debian Ports 
architectures. I am willing to
keep the stuff working together with the other maintainers in Debian Ports (and 
probably Gentoo).

Thanks,
Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Re: LibreOffice architecture support (was: Fwd: Plan to remove dead C++ UNO bridge implementations (bridges/source/cpp_uno/*))

2023-01-10 Thread Stephan Bergmann 

On 10/01/2023 19:57, John Paul Adrian Glaubitz wrote:

(5) Presumably dead:
* gcc3_linux_alpha


=> https://buildd.debian.org/status/logs.php?pkg=libreoffice&arch=alpha


Thanks for those pointers.  Just to make sure, the latest line there being


1:6.4.5-1 (sid) Buildd exposure stats alpha Maybe-Failed
2020-07-03 06:39:28 phys18h 37m 9.48 GB


means that that's a build of LO 6.4.5, right?  Are all those Debian 
Ports builds consistently lagging behind current LO master by N years?

Re: LibreOffice architecture support (was: Fwd: Plan to remove dead C++ UNO bridge implementations (bridges/source/cpp_uno/*))

2023-01-10 Thread John Paul Adrian Glaubitz 

Hi Stephan!


There are currently 27 different, per-platform C++ UNO bridge implementations at
bridges/source/cpp_uno/, some of which are presumably dead by now. And my recent

"Rudimentary support for dynamic_cast on UNO proxy objects" (which had to touch
each of them individually) was the latest example how even presumably dead ones
have ongoing maintenance cost. Therefore, I would like to remove (on master,
towards LO 7.6) the ones that can clearly be identified as being dead.

Below, I sorted those 27 implementations into 5 categories: Ideally, each active
implementation would be built regularly by Jenkins; those 9 that are go into 
category
1. Next, there are 2 additional implementations that I know are built for Fedora
releases; they go into category 2. Next, there are 2 additional implementations
that I presume are built for Debian releases (Rene, correct me if I'm wrong);
they go into category 3. And then there are 3 implementations that are 
presumably
in active use elsewhere (Tor, wjh-la, Sakura286, correct me if I'm wrong); which
go into category 4. That leaves 11 implementations that are presumably dead, in
category 5.



(5) Presumably dead:
* gcc3_linux_alpha


=> https://buildd.debian.org/status/logs.php?pkg=libreoffice&arch=alpha


* gcc3_linux_hppa


=> https://buildd.debian.org/status/logs.php?pkg=libreoffice&arch=hppa


* gcc3_linux_ia64


=> https://buildd.debian.org/status/logs.php?pkg=libreoffice&arch=ia64


* gcc3_linux_m68k


=> https://buildd.debian.org/status/logs.php?pkg=libreoffice&arch=m68k


* gcc3_linux_powerpc


=> https://buildd.debian.org/status/logs.php?pkg=libreoffice&arch=powerpc


* gcc3_linux_sparc64


=> https://buildd.debian.org/status/logs.php?pkg=libreoffice&arch=sparc64

We're still maintaining these in Debian Ports. I have added the build logs for 
the latest builds above.

New builds will be triggered soonish when I have worked through the queue of 
package
dependencies that need to be fixed.


* gcc3_solaris_intel
* gcc3_solaris_sparc


Oracle is still maintaining Solaris until at least 2035 and OpenIndiana is 
still maintained, too.

According to this article, LibreOffice 7.2.7 was shipped with OpenIndiana 
2022.10:


https://www.theregister.com/2022/12/07/new_version_of_openindiana/


So, I'm not sure dropping Solaris support is a good idea either.


* gcc3_linux_sparc


32-bit SPARC is still supported by Gentoo, see:


https://www.gentoo.org/downloads/


Let me know if I can be of any help.

PS: I'm subscribed to this list, but I don't receive any mail.

Thanks,
Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913