RE: [HELP NEEDED] old Solaris related build issues
+1 to the suggestions from Marcus > -Original Message- > From: Marcus [mailto:marcus.m...@wtnet.de] > Sent: Tuesday, April 5, 2016 09:18 > To: dev@openoffice.apache.org > Subject: Re: [HELP NEEDED] old Solaris related build issues > > Am 04/05/2016 01:51 AM, schrieb Patricia Shanahan: > > On 4/4/2016 2:59 PM, Marcus wrote: > >> Am 04/04/2016 11:30 PM, schrieb Kay Schenk: > > ... > >>> In any case, since we don't currently have "official" > >>> distros for Solaris -- I would be content changing all these > >>> issues to ENHANCEMENT rather than DEFECT. > >>> > >>> Thoughts? > >> > >> I think this wouldn't change the actual problem: Somebody has to do > the > >> change in the code. We have neglected this platform and this is IMHO > >> also one reason that we don't offer any builds anymore. > >> > >> Let's see what Patricia will say about the effort she sees. > > ... > > > > I think Apostolos Syropoulos makes a strong case for using gcc in > > preference to SunStudio. > > > > A lot depends on whether the changes suggested in the article > > https://asyropoulos.wordpress.com/2014/02/05/compiling-openoffice4/ > > still work. It was last modified in 2014. I can't determine that very > > easily without experimenting. > > should be easy for him to tell us. ;-) > > > If the rest of the PMC wants me to make the effort, I would request a > > Of course it's your decision. But if it's not that much effort IMHO it > is worth to do the compiler change. > > > Solaris ssh account from Adfinis, check out the current trunk there, > > check/apply all available Solaris patches, including the switch to > gcc, > > and attempt a build. If the patches work, and pass inspection, I would > > commit them to svn. > > OK, sounds good. > > > If that all works, I could continue to review, test, and check in > > patches suggested by people working on Solaris. Would I need AOO > > BugZilla issues supporting my changes? > > I suggest to use a BZ issue for the initial work. On the the basis of > the coming patches and the documentation of the work alone it makes > sense to do the little extra step. For other things after that we have > to see again. > > Marcus > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [HELP NEEDED] old Solaris related build issues
Am 04/05/2016 01:51 AM, schrieb Patricia Shanahan: On 4/4/2016 2:59 PM, Marcus wrote: Am 04/04/2016 11:30 PM, schrieb Kay Schenk: ... In any case, since we don't currently have "official" distros for Solaris -- I would be content changing all these issues to ENHANCEMENT rather than DEFECT. Thoughts? I think this wouldn't change the actual problem: Somebody has to do the change in the code. We have neglected this platform and this is IMHO also one reason that we don't offer any builds anymore. Let's see what Patricia will say about the effort she sees. ... I think Apostolos Syropoulos makes a strong case for using gcc in preference to SunStudio. A lot depends on whether the changes suggested in the article https://asyropoulos.wordpress.com/2014/02/05/compiling-openoffice4/ still work. It was last modified in 2014. I can't determine that very easily without experimenting. should be easy for him to tell us. ;-) If the rest of the PMC wants me to make the effort, I would request a Of course it's your decision. But if it's not that much effort IMHO it is worth to do the compiler change. Solaris ssh account from Adfinis, check out the current trunk there, check/apply all available Solaris patches, including the switch to gcc, and attempt a build. If the patches work, and pass inspection, I would commit them to svn. OK, sounds good. If that all works, I could continue to review, test, and check in patches suggested by people working on Solaris. Would I need AOO BugZilla issues supporting my changes? I suggest to use a BZ issue for the initial work. On the the basis of the coming patches and the documentation of the work alone it makes sense to do the little extra step. For other things after that we have to see again. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [HELP NEEDED] old Solaris related build issues
On 4/4/2016 2:59 PM, Marcus wrote: Am 04/04/2016 11:30 PM, schrieb Kay Schenk: ... In any case, since we don't currently have "official" distros for Solaris -- I would be content changing all these issues to ENHANCEMENT rather than DEFECT. Thoughts? I think this wouldn't change the actual problem: Somebody has to do the change in the code. We have neglected this platform and this is IMHO also one reason that we don't offer any builds anymore. Let's see what Patricia will say about the effort she sees. ... I think Apostolos Syropoulos makes a strong case for using gcc in preference to SunStudio. A lot depends on whether the changes suggested in the article https://asyropoulos.wordpress.com/2014/02/05/compiling-openoffice4/ still work. It was last modified in 2014. I can't determine that very easily without experimenting. If the rest of the PMC wants me to make the effort, I would request a Solaris ssh account from Adfinis, check out the current trunk there, check/apply all available Solaris patches, including the switch to gcc, and attempt a build. If the patches work, and pass inspection, I would commit them to svn. If that all works, I could continue to review, test, and check in patches suggested by people working on Solaris. Would I need AOO BugZilla issues supporting my changes? Patricia - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [HELP NEEDED] old Solaris related build issues
Am 04/04/2016 11:30 PM, schrieb Kay Schenk: On 04/04/2016 08:00 AM, Marcus wrote: Am 04/04/2016 12:11 PM, schrieb Απόστολος Συρόπουλος: yes, that's nice. But you shouldn't commit fixes without a possibility to test if it was good. Would you? ;-) First I did this in the past. Please see https://asyropoulos.wordpress.com/2014/02/05/compiling-openoffice4/ interesting. Thanks for the link. At that time I was sure the patches would find their way to source tree, but apparently they have been ignored... Nobody has said we don't do it and they are not more open-minded. I said that they are more open-minded! And I based this on my own personal experience. Not to mention that since you got the code from a company that produces Solaris, out of courtesy you should ensure the suite compiles under Solaris... We made the opposite experience. So, sorry that I've a different opinion. It's simply a fact that we have no experts for Solaris and no testing hardware. Hardware? We are not talking about SPARC machines. Nobody I didn't know that it's not about SPARC. This changes indeed the problem a bit. ;-) More in my answer to Patricia's mail. Marcus In any case, since we don't currently have "official" distros for Solaris -- I would be content changing all these issues to ENHANCEMENT rather than DEFECT. Thoughts? I think this wouldn't change the actual problem: Somebody has to do the change in the code. We have neglected this platform and this is IMHO also one reason that we don't offer any builds anymore. Let's see what Patricia will say about the effort she sees. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [HELP NEEDED] old Solaris related build issues
On 04/04/2016 08:00 AM, Marcus wrote: > Am 04/04/2016 12:11 PM, schrieb Απόστολος Συρόπουλος: >>> >>> yes, that's nice. But you shouldn't commit fixes without >>> a possibility >>> to test if it was good. Would you? ;-) >>> >> >> First I did this in the past. Please see >> >> https://asyropoulos.wordpress.com/2014/02/05/compiling-openoffice4/ >> > > interesting. Thanks for the link. > >> At that time I was sure the patches would find their way >> to source tree, >> but apparently they have been ignored... >> >>> Nobody has said we don't do it and they are not more >>> open-minded. >> >> I said that they are more open-minded! And I based this on >> my own >> personal experience. Not to mention that since you got the >> code >> from a company that produces Solaris, out of courtesy you >> should >> ensure the suite compiles under Solaris... > > We made the opposite experience. So, sorry that I've a > different opinion. > >>> It's simply a fact that we have no experts for Solaris >>> and no testing >>> hardware. >> >> Hardware? We are not talking about SPARC machines. Nobody > > I didn't know that it's not about SPARC. This changes indeed > the problem a bit. ;-) > > More in my answer to Patricia's mail. > > Marcus In any case, since we don't currently have "official" distros for Solaris -- I would be content changing all these issues to ENHANCEMENT rather than DEFECT. Thoughts? -- MzK "Time spent with cats is never wasted." -- Sigmund Freud - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [HELP NEEDED] old Solaris related build issues
Am 04/04/2016 12:11 PM, schrieb Απόστολος Συρόπουλος: yes, that's nice. But you shouldn't commit fixes without a possibility to test if it was good. Would you? ;-) First I did this in the past. Please see https://asyropoulos.wordpress.com/2014/02/05/compiling-openoffice4/ interesting. Thanks for the link. At that time I was sure the patches would find their way to source tree, but apparently they have been ignored... Nobody has said we don't do it and they are not more open-minded. I said that they are more open-minded! And I based this on my own personal experience. Not to mention that since you got the code from a company that produces Solaris, out of courtesy you should ensure the suite compiles under Solaris... We made the opposite experience. So, sorry that I've a different opinion. It's simply a fact that we have no experts for Solaris and no testing hardware. Hardware? We are not talking about SPARC machines. Nobody I didn't know that it's not about SPARC. This changes indeed the problem a bit. ;-) More in my answer to Patricia's mail. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [HELP NEEDED] old Solaris related build issues
Hi Marcus, * :) On Thu, 2016-03-31 at 00:41 +0200, Marcus wrote: [...] > @Nicolas: > AFAIK your company (Adfinis SyGroup AG) is managing the ports for > Solaris Sparc and x86. Is it possbile to get help from you for this case? Thanks for keeping me in the loop! Unfortunately we do not have enough resources to have a look at this in a reasonable time frame. We spent a huge amount of time trying to get 4.x working on Solaris, but after fighting with many different issues we gave up at some point (compilation went through roughly 1/3 of the code base). We still habe the boxes ready, up and running - if someone would like to have a look at it, feel free to contact us on a...@adfinis-sygroup.ch an we'll gladly provide you with an SSH account so you can get your hand dirty ;) Have a nice day! Kind regards, Nicolas -- Adfinis SyGroup AG Nicolas Christener, Bereichsleiter Services, GPG KeyID: 557DD2D6 Keltenstrasse 98 | CH-3018 Bern Tel. +41 31 550 31 11 | Direkt +41 31 550 31 13 signature.asc Description: This is a digitally signed message part
Re: [HELP NEEDED] old Solaris related build issues
On 4/4/2016 2:28 AM, Marcus wrote: ... It's simply a fact that we have no experts for Solaris and no testing hardware. ... Solaris runs on Intel PC hardware, so no need for special testing hardware. From the late 1980's to 2002, I was a system performance analyst and architect for servers that ran Solaris, while working for FPS Computing, Cray Research Superservers, and Sun Microsystems. During that time, I used it as the operating system on the workstation in my office. I was involved in helping the Solaris developers make the changes to get it to run well on 64 processor servers. I have used kadb to look at Solaris internals, while debugging hardware. I last used Solaris well over ten years ago, and don't know whether I would qualify as an "expert" for this purpose, but I could probably remember enough to be able to help a bit. There is a real resource limit. I have a finite amount of time to spend on AOO, and any time I spend on Solaris will be time I don't spend on other subprojects. Patricia - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: [HELP NEEDED] old Solaris related build issues
> > yes, that's nice. But you shouldn't commit fixes without a possibility > to test if it was good. Would you? ;-) > First I did this in the past. Please see https://asyropoulos.wordpress.com/2014/02/05/compiling-openoffice4/ At that time I was sure the patches would find their way to source tree, but apparently they have been ignored... > > Nobody has said we don't do it and they are not more open-minded. > I said that they are more open-minded! And I based this on my own personal experience. Not to mention that since you got the code from a company that produces Solaris, out of courtesy you should ensure the suite compiles under Solaris... > It's simply a fact that we have no experts for Solaris and no testing > hardware. > Hardware? We are not talking about SPARC machines. Nobody cares about these machines anymore. We are talking about "ordinary" computers with Intel or Intel-like processors. Second you do not need experts. You only need people that know Unix. After all, we are not takling about driver porting here... > If we would have it, then we would build and test the code. Or if > someone else is taking this over. So, maybe you want to help us? We are > open for this. :-) > I am sure the whole OpenIndiana community would like to help provided you do a few simple things: abandon SunStudio for Solaris and change the MAKE files according to our suggestions. A.S. -- Apostolos Syropoulos Xanthi, Greece
Re: [HELP NEEDED] old Solaris related build issues
Am 04/04/2016 11:14 AM, schrieb Απόστολος Συρόπουλος: one problem of integrating patches is that you need to test them if the trunk builds are still OK or if some adjustments are necessary. However, AFAIK no developer has a Solaris machine under the desk and therefore it's not a good idea to commit fixes when you don't know what the results are. ;-) Look the people of LibreOffice have abandoned SunStudio and have included such patches in their source tree and now LibreOffice compiles just fine. In fact, OpenIndiana has a LibreOffice package. yes, that's nice. But you shouldn't commit fixes without a possibility to test if it was good. Would you? ;-) That's also the reason why the build environment still uses Sun Studio and nothing else - instead or additional. When I tried to compile with SunStudio I realized that the building tools require a really ancient version of the compiler that has no provision for language constructs, etc., that are included in the code. For example, the template library is ancient and does not include things that the source code expects. So practically it is next to impossible to compile OpenOffice with SunStudio. Since you are not going to change your mind, better remove all Solaris bits so the make the code cleaner. Fortunately, the LibreOffice people are more open-minded... Nobody has said we don't do it and they are not more open-minded. It's simply a fact that we have no experts for Solaris and no testing hardware. If we would have it, then we would build and test the code. Or if someone else is taking this over. So, maybe you want to help us? We are open for this. :-) Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: [HELP NEEDED] old Solaris related build issues
> > one problem of integrating patches is that you need to test them if the > trunk builds are still OK or if some adjustments are necessary. However, > AFAIK no developer has a Solaris machine under the desk and therefore > it's not a good idea to commit fixes when you don't know what the > results are. ;-) > Look the people of LibreOffice have abandoned SunStudio and have included such patches in their source tree and now LibreOffice compiles just fine. In fact, OpenIndiana has a LibreOffice package. > That's also the reason why the build environment still uses Sun Studio > and nothing else - instead or additional. When I tried to compile with SunStudio I realized that the building tools require a really ancient version of the compiler that has no provision for language constructs, etc., that are included in the code. For example, the template library is ancient and does not include things that the source code expects. So practically it is next to impossible to compile OpenOffice with SunStudio. Since you are not going to change your mind, better remove all Solaris bits so the make the code cleaner. Fortunately, the LibreOffice people are more open-minded... A.S. -- Apostolos Syropoulos Xanthi, Greece
Re: [HELP NEEDED] old Solaris related build issues
Am 04/03/2016 06:56 PM, schrieb Απόστολος Συρόπουλος: We have a number of old Solaris related build issues that could use some testing. https://bz.apache.org/ooo/show_bug.cgi?id=125361 https://bz.apache.org/ooo/show_bug.cgi?id=125362 https://bz.apache.org/ooo/show_bug.cgi?id=125364 https://bz.apache.org/ooo/show_bug.cgi?id=125365 The main problem of OpenOffice on Solaris is that it still assumes that one will use SunStudio to compile it. I think OpenOffice should drop completely its support for this compiler in favor for GCC. Once, I compiled OpenOffice with GCC but for some reason it was failing to open zipped formats (.docx etc). Also, I published all my pathces and some of them were included in the source tree. Some of the pacthes mentioned on the links above are based on the patches I made. Unfortunately, no one carred to update the code... one problem of integrating patches is that you need to test them if the trunk builds are still OK or if some adjustments are necessary. However, AFAIK no developer has a Solaris machine under the desk and therefore it's not a good idea to commit fixes when you don't know what the results are. ;-) That's also the reason why the build environment still uses Sun Studio and nothing else - instead or additional. But when you can help us here with builds that would be great. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: [HELP NEEDED] old Solaris related build issues
> > We have a number of old Solaris related build issues that > > could use some testing. > > > > https://bz.apache.org/ooo/show_bug.cgi?id=125361 > > https://bz.apache.org/ooo/show_bug.cgi?id=125362 > > https://bz.apache.org/ooo/show_bug.cgi?id=125364 > > https://bz.apache.org/ooo/show_bug.cgi?id=125365 > > The main problem of OpenOffice on Solaris is that it still assumes that one will use SunStudio to compile it. I think OpenOffice should drop completely its support for this compiler in favor for GCC. Once, I compiled OpenOffice with GCC but for some reason it was failing to open zipped formats (.docx etc). Also, I published all my pathces and some of them were included in the source tree. Some of the pacthes mentioned on the links above are based on the patches I made. Unfortunately, no one carred to update the code... A.S. -- Apostolos Syropoulos Xanthi, Greece
Re: [HELP NEEDED] old Solaris related build issues
Am 03/31/2016 12:02 AM, schrieb Kay Schenk: We have a number of old Solaris related build issues that could use some testing. https://bz.apache.org/ooo/show_bug.cgi?id=125361 https://bz.apache.org/ooo/show_bug.cgi?id=125362 https://bz.apache.org/ooo/show_bug.cgi?id=125364 https://bz.apache.org/ooo/show_bug.cgi?id=125365 The fixes pertain to configure.in which has been replaced by configure.ac. TSince we've made a number of changes to configure.ac since these were submitted, the patches probably can not be directly applied. We don't formally distribute a Solaris build any more, but we do have an active port of Apache OpenOffice on Solaris see: http://www.openoffice.org/porting/index.html It would be great if we could get some gcc on Solaris builders to test these patches. @Nicolas: AFAIK your company (Adfinis SyGroup AG) is managing the ports for Solaris Sparc and x86. Is it possbile to get help from you for this case? Thanks in advance Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
