Bugzilla 22831
Hi, Marking bugs as duplicate result in losing track of the number of votes? For example bug 22831 has a couple of bugs marked as duplicate. If you add the votes for all related bugs you get 13 votes while bug 22831 only shows 6 votes. How can we make sure that bugs get the correct priority? Regards, Martin Groenescheij - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Simpler Windows builds, oowintool, and Cygwin64
I've been waiting for the dust to settle. What is the best set of instructions for doing a Windows 10 build with Cygwin 64? On 11/15/2017 7:47 AM, Matthias Seidel wrote: Hi Damjan, I added 2 trailing "/" and now it works... ;-) Maybe Patricia can confirm it? I will now start a build from trunk with Cygwin64 and put the results here: https://home.apache.org/~mseidel/AOO-builds/AOO-420-Test-Cygwin64/ Regards, Matthias Am 14.11.2017 um 03:06 schrieb Damjan Jovanovic: Please test whether the attached patch helps? Regards Damjan On Sat, Nov 11, 2017 at 8:02 PM, Matthias Seidel mailto:matthias.sei...@hamburg.de>> wrote: Hi Damjan, Am 10.11.2017 um 06:27 schrieb Damjan Jovanovic: > Hi > > I've committed a few small small fixes to oowintool, mostly for JDK 8 > detection and better logging, but I've confirmed that it already works > well, and --with-frame-home --with-psdk-home --with-midl-path > --with-jdk-home --with-csc-path and --with-cl-home options to ./configure > are all unnecessary. > > As for 64 bit Cygwin I believe the problem with oowintool is that it needs > to look under the Wow6432node subkey in the registry too, something that > should be easy to add. Is anyone available to test 64 bit Cygwin? I just installed Cygwin64 on Windows 10 and ./configure stops with: Can't find MS Visual Studio / VC++ at ./oowintool line 236. configure: error: oowintool failed to copy CRT Regards, Matthias > > Damjan > - 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: FYI: The OO 4.1.4 Mac problem
I have my Sierra MacBook and my early 2008 iMac with 10.7.5 with a replaced drive (damaged from smoke from wine country fires (it had 10.6)) ready for testing. > On Nov 15, 2017, at 1:38 PM, Jim Jagielski wrote: > > I have a 10.9/Mavericks with Xcode 6.2 VM up and running. I am > building 4.1.4 on it as we speak. Will let people know asap. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > signature.asc Description: Message signed with OpenPGP
Re: FYI: The OO 4.1.4 Mac problem
I have a 10.9/Mavericks with Xcode 6.2 VM up and running. I am building 4.1.4 on it as we speak. Will let people know asap. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Simpler Windows builds, oowintool, and Cygwin64
Great work Matthias :-). Thank you and good luck. On Wed, Nov 15, 2017 at 7:17 PM, Matthias Seidel wrote: > I just updated config.guess and config.sub to the latest version. > > See: https://www.gnu.org/software/gettext/manual/html_node/ > config_002eguess.html > > Regards, Matthias > > Am 15.11.2017 um 17:23 schrieb Matthias Seidel: > > Hi Damjan, > > Next "problem", ./bootstrap can't guess the system: > > --- > entering dmake-4.12 > checking build system type... ./config.guess: unable to guess system type > > This script, last modified 2005-07-08, has failed to recognize > the operating system you are using. It is advised that you > download the most up to date version of the config scripts from > > http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/config/ > config/config.guess > and > http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/config/ > config/config.sub > > If the version you run (./config.guess) is already up to date, please > send the following data and any information you think might be > pertinent to in order > to provide the needed > information to handle your system. > > config.guess timestamp = 2005-07-08 > > uname -m = x86_64 > uname -r = 2.9.0(0.318/5/3) > uname -s = CYGWIN_NT-10.0 > uname -v = 2017-09-12 10:18 > > /usr/bin/uname -p = unknown > /bin/uname -X = > > hostinfo = > /bin/universe = > /usr/bin/arch -k = > /bin/arch = x86_64 > /usr/bin/oslevel = > /usr/convex/getsysinfo = > > UNAME_MACHINE = x86_64 > UNAME_RELEASE = 2.9.0(0.318/5/3) > UNAME_SYSTEM = CYGWIN_NT-10.0 > UNAME_VERSION = 2017-09-12 10:18 > configure: error: cannot guess build type; you must specify one > --- > > I am wondering about the timestamp, our config.guess is from 2009-12-30. > > Regards, Matthias > > > Am 14.11.2017 um 03:06 schrieb Damjan Jovanovic: > > Please test whether the attached patch helps? > > Regards > Damjan > > On Sat, Nov 11, 2017 at 8:02 PM, Matthias Seidel < > matthias.sei...@hamburg.de> wrote: > >> Hi Damjan, >> >> Am 10.11.2017 um 06:27 schrieb Damjan Jovanovic: >> > Hi >> > >> > I've committed a few small small fixes to oowintool, mostly for JDK 8 >> > detection and better logging, but I've confirmed that it already works >> > well, and --with-frame-home --with-psdk-home --with-midl-path >> > --with-jdk-home --with-csc-path and --with-cl-home options to >> ./configure >> > are all unnecessary. >> > >> > As for 64 bit Cygwin I believe the problem with oowintool is that it >> needs >> > to look under the Wow6432node subkey in the registry too, something that >> > should be easy to add. Is anyone available to test 64 bit Cygwin? >> >> I just installed Cygwin64 on Windows 10 and ./configure stops with: >> >> Can't find MS Visual Studio / VC++ at ./oowintool line 236. >> configure: error: oowintool failed to copy CRT >> >> Regards, Matthias >> >> > >> > Damjan >> > >> >> >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > > >
Re: FYI: The OO 4.1.4 Mac problem
On 15 Nov, Jim Jagielski wrote: > Agreed. > > FWIW, I have been unable to even create a 4.1.2 build that works in > both cases, and this is via various combinations of libxml2, libxslt, Xcode > (both > 7 and 8) and selected SDKs. Look for system libraries that that we use and that link to libxml2 and/or libxslt. I suspect that is some sort of ABI difference between versions. If we bundle these libraries, some other system library breaks because it expects the system libxml2/libxslt ABI but it is linked to the bundled version. If we don't bundle these libraries, then we expect the ABI of whatever version is on the system where we do the build and break when running on a different version of Mac OS. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Simpler Windows builds, oowintool, and Cygwin64
I just updated config.guess and config.sub to the latest version. See: https://www.gnu.org/software/gettext/manual/html_node/config_002eguess.html Regards, Matthias Am 15.11.2017 um 17:23 schrieb Matthias Seidel: > > Hi Damjan, > > Next "problem", ./bootstrap can't guess the system: > > --- > entering dmake-4.12 > checking build system type... ./config.guess: unable to guess system type > > This script, last modified 2005-07-08, has failed to recognize > the operating system you are using. It is advised that you > download the most up to date version of the config scripts from > > > http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/config/config/config.guess > and > > http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/config/config/config.sub > > If the version you run (./config.guess) is already up to date, please > send the following data and any information you think might be > pertinent to in order to provide the needed > information to handle your system. > > config.guess timestamp = 2005-07-08 > > uname -m = x86_64 > uname -r = 2.9.0(0.318/5/3) > uname -s = CYGWIN_NT-10.0 > uname -v = 2017-09-12 10:18 > > /usr/bin/uname -p = unknown > /bin/uname -X = > > hostinfo = > /bin/universe = > /usr/bin/arch -k = > /bin/arch = x86_64 > /usr/bin/oslevel = > /usr/convex/getsysinfo = > > UNAME_MACHINE = x86_64 > UNAME_RELEASE = 2.9.0(0.318/5/3) > UNAME_SYSTEM = CYGWIN_NT-10.0 > UNAME_VERSION = 2017-09-12 10:18 > configure: error: cannot guess build type; you must specify one > --- > > I am wondering about the timestamp, our config.guess is from 2009-12-30. > > Regards, Matthias > > > > Am 14.11.2017 um 03:06 schrieb Damjan Jovanovic: >> Please test whether the attached patch helps? >> >> Regards >> Damjan >> >> On Sat, Nov 11, 2017 at 8:02 PM, Matthias Seidel >> mailto:matthias.sei...@hamburg.de>> wrote: >> >> Hi Damjan, >> >> Am 10.11.2017 um 06:27 schrieb Damjan Jovanovic: >> > Hi >> > >> > I've committed a few small small fixes to oowintool, mostly for >> JDK 8 >> > detection and better logging, but I've confirmed that it >> already works >> > well, and --with-frame-home --with-psdk-home --with-midl-path >> > --with-jdk-home --with-csc-path and --with-cl-home options to >> ./configure >> > are all unnecessary. >> > >> > As for 64 bit Cygwin I believe the problem with oowintool is >> that it needs >> > to look under the Wow6432node subkey in the registry too, >> something that >> > should be easy to add. Is anyone available to test 64 bit Cygwin? >> >> I just installed Cygwin64 on Windows 10 and ./configure stops with: >> >> Can't find MS Visual Studio / VC++ at ./oowintool line 236. >> configure: error: oowintool failed to copy CRT >> >> Regards, Matthias >> >> > >> > Damjan >> > >> >> >> >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: Simpler Windows builds, oowintool, and Cygwin64
Hi Damjan, Next "problem", ./bootstrap can't guess the system: --- entering dmake-4.12 checking build system type... ./config.guess: unable to guess system type This script, last modified 2005-07-08, has failed to recognize the operating system you are using. It is advised that you download the most up to date version of the config scripts from http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/config/config/config.guess and http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/config/config/config.sub If the version you run (./config.guess) is already up to date, please send the following data and any information you think might be pertinent to in order to provide the needed information to handle your system. config.guess timestamp = 2005-07-08 uname -m = x86_64 uname -r = 2.9.0(0.318/5/3) uname -s = CYGWIN_NT-10.0 uname -v = 2017-09-12 10:18 /usr/bin/uname -p = unknown /bin/uname -X = hostinfo = /bin/universe = /usr/bin/arch -k = /bin/arch = x86_64 /usr/bin/oslevel = /usr/convex/getsysinfo = UNAME_MACHINE = x86_64 UNAME_RELEASE = 2.9.0(0.318/5/3) UNAME_SYSTEM = CYGWIN_NT-10.0 UNAME_VERSION = 2017-09-12 10:18 configure: error: cannot guess build type; you must specify one --- I am wondering about the timestamp, our config.guess is from 2009-12-30. Regards, Matthias Am 14.11.2017 um 03:06 schrieb Damjan Jovanovic: > Please test whether the attached patch helps? > > Regards > Damjan > > On Sat, Nov 11, 2017 at 8:02 PM, Matthias Seidel > mailto:matthias.sei...@hamburg.de>> wrote: > > Hi Damjan, > > Am 10.11.2017 um 06:27 schrieb Damjan Jovanovic: > > Hi > > > > I've committed a few small small fixes to oowintool, mostly for > JDK 8 > > detection and better logging, but I've confirmed that it already > works > > well, and --with-frame-home --with-psdk-home --with-midl-path > > --with-jdk-home --with-csc-path and --with-cl-home options to > ./configure > > are all unnecessary. > > > > As for 64 bit Cygwin I believe the problem with oowintool is > that it needs > > to look under the Wow6432node subkey in the registry too, > something that > > should be easy to add. Is anyone available to test 64 bit Cygwin? > > I just installed Cygwin64 on Windows 10 and ./configure stops with: > > Can't find MS Visual Studio / VC++ at ./oowintool line 236. > configure: error: oowintool failed to copy CRT > > Regards, Matthias > > > > > Damjan > > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org smime.p7s Description: S/MIME Cryptographic Signature
Re: Simpler Windows builds, oowintool, and Cygwin64
Hi Damjan,
I added 2 trailing "/" and now it works... ;-)
Maybe Patricia can confirm it?
I will now start a build from trunk with Cygwin64 and put the results here:
https://home.apache.org/~mseidel/AOO-builds/AOO-420-Test-Cygwin64/
Regards, Matthias
Am 14.11.2017 um 03:06 schrieb Damjan Jovanovic:
> Please test whether the attached patch helps?
>
> Regards
> Damjan
>
> On Sat, Nov 11, 2017 at 8:02 PM, Matthias Seidel
> mailto:matthias.sei...@hamburg.de>> wrote:
>
> Hi Damjan,
>
> Am 10.11.2017 um 06:27 schrieb Damjan Jovanovic:
> > Hi
> >
> > I've committed a few small small fixes to oowintool, mostly for
> JDK 8
> > detection and better logging, but I've confirmed that it already
> works
> > well, and --with-frame-home --with-psdk-home --with-midl-path
> > --with-jdk-home --with-csc-path and --with-cl-home options to
> ./configure
> > are all unnecessary.
> >
> > As for 64 bit Cygwin I believe the problem with oowintool is
> that it needs
> > to look under the Wow6432node subkey in the registry too,
> something that
> > should be easy to add. Is anyone available to test 64 bit Cygwin?
>
> I just installed Cygwin64 on Windows 10 and ./configure stops with:
>
> Can't find MS Visual Studio / VC++ at ./oowintool line 236.
> configure: error: oowintool failed to copy CRT
>
> Regards, Matthias
>
> >
> > Damjan
> >
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
Index: oowintool
===
--- oowintool (revision 1815058)
+++ oowintool (working copy)
@@ -217,6 +217,11 @@
$ver->{'product_dir'} = $install;
return $ver;
}
+ $install = reg_get_value ("HKEY_LOCAL_MACHINE/SOFTWARE/Wow6432Node/" . $ver->{'key'});
+ if (defined $install && $install ne '') {
+ $ver->{'product_dir'} = $install;
+ return $ver;
+ }
}
die "Can't find MS Visual Studio / VC++";
}
@@ -232,6 +237,11 @@
$ver->{'product_dir'} = $install;
return $ver;
}
+ $install = reg_get_value("HKEY_LOCAL_MACHINE/SOFTWARE/Wow6432Node/" . $ver->{'key'});
+ if (defined $install && $install ne '') {
+ $ver->{'product_dir'} = $install;
+ return $ver;
+ }
}
die "Can't find MS Visual Studio / VC++";
}
smime.p7s
Description: S/MIME Cryptographic Signature
Re: FYI: The OO 4.1.4 Mac problem
Agreed. FWIW, I have been unable to even create a 4.1.2 build that works in both cases, and this is via various combinations of libxml2, libxslt, Xcode (both 7 and 8) and selected SDKs. Next step is trying to downgrade from Sierra to El Capitan or Yosemite. > On Nov 14, 2017, at 11:59 PM, Peter kovacs wrote: > > I am not sure. +1 for the release, but we should keep the other version > somehow around. Maybe offer the trade if someone asks for it. > > > Am 15. November 2017 00:12:00 MEZ schrieb Marcus : >> Am 14.11.2017 um 18:35 schrieb Dave Fisher: >>> Anyone else? >> >> yes, sounds reasonable to focus more on Calc/Chart tahn on Base. >> >> Marcus >> >> >> On Nov 12, 2017, at 12:06 PM, Dave Fisher >> wrote: +1. That makes great sense. Sent from my iPhone > On Nov 12, 2017, at 11:10 AM, Jim Jagielski >> wrote: > > Does it make sense to "release" the version that fixes the > chart problem, while we work on the one that tries to > address the table/database issue? > > I would assume that there are more people who want/need 4.1.4 > and would be affected by the chart diagram issue than those > who would be affected by the DB. >> On Nov 9, 2017, at 1:18 PM, Rory O'Farrell >> wrote: >> >> >> For information: the Mac 4.1.4 chart problem is starting to >> surface on the Forum - there have been several reports of it today. I >> explain that the fix has produced unwanted side effects and recommend >> reverting to OO 4.1.3 fir the time being. >> >> Rory >> >> -- >> Rory O'Farrell >> >> >> - >> 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 > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
