subject:"Simpler Windows builds, oowintool, and Cygwin64"

Re: Simpler Windows builds, oowintool, and Cygwin64

2017-11-18 Thread Matthias Seidel

Hi John,

Am 16.11.2017 um 11:48 schrieb John D'Orazio:
> On Wed, Nov 15, 2017 at 6: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
>>
> Just wondering if after this update the configure script still runs fine?
> About a year or so ago when I was testing a cygwin x64 build process, I
> noticed that after updating config.guess and config.sub in the cygwin
> terminal the configure script starting choking on config.sub. Were you able
> to get past this?

Seems we ran into the same error messages... ;-)
I can confirm that the recently updated config.guess/config.sub do not
break the build and error messages are gone.
However it doesn't build with Cygwin64 because it detects
"x86_64-unknown-cygwin" I will try "--build=i686-pc-cygwin" now.

>
> Unfortunately I don't have my system set up to build ATM, unfortunately my
> "powerful" HP laptop comes with a miserly 128GB SSD as the main drive and
> Visual Studio can't be installed on a secondary drive... I'm having a heck
> of a time finding a bigger compatible SSD but I hope to resolve this soon,
> and set up my build system again...

My laptop was low on disk space too. But I could add an additional SSD
in a PCIe slot... ;-)
I run Ubuntu 16.04.3 with Windows 10 in VirtualBox.

> As these obstacles are removed the Step by step guide can be updated, I had
> opened a section about building with cywgwin x64 and I started jotting
> provisional notes down, I'd say this looks like the time to update them:
> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Testing_build_with_Cygwin_64_bit
> .

I will update the Wiki step by step now.

Regards, Matthias



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Simpler Windows builds, oowintool, and Cygwin64

2017-11-16 Thread Damjan Jovanovic

Committed now, thank you for your help:

r1815542 | damjan | 2017-11-17 04:05:43 +0200 (Fri, 17 Nov 2017) | 6 lines
Changed paths:
   M /openoffice/trunk/main/oowintool

Allow oowintool to find 32 bit VC++ in Cygwin64.

Patch by: Damjan Jovanovic and Matthias Seidel
Tested by: Matthias Seidel


On Thu, Nov 16, 2017 at 10:02 PM, Matthias Seidel <
matthias.sei...@hamburg.de> wrote:

> Hi Damjan,
>
> Do you want to commit your patch?
>
> Actually, there are still some obstacles for building with Cygwin64, but
> oowintool doesn't seem to break anything.
>
> Regards, Matthias
>
> Am 15.11.2017 um 19:55 schrieb Damjan Jovanovic:
>
> 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  
> 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: Simpler Windows builds, oowintool, and Cygwin64

2017-11-16 Thread Matthias Seidel

Hi Patricia,

Am 16.11.2017 um 00:43 schrieb Patricia Shanahan:
> 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?

Unfortunately we are only some steps closer to build with Cygwin64...

With Damjans patch applied and the updated config.guess/config.sub I get
past ./bootstrap.
Building then stops with an error in solenv. Maybe because we have to
build for 32bit in an 64 bit Cygwin now.

I use the same configuration as for 4.1.4:
https://svn.apache.org/repos/asf/openoffice/devtools/build-scripts/4.1.4/wntmsci/

Regards, Matthias

>
> 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
>>> > 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
>
>




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Simpler Windows builds, oowintool, and Cygwin64

2017-11-16 Thread Matthias Seidel

Hi Damjan,

Do you want to commit your patch?

Actually, there are still some obstacles for building with Cygwin64, but
oowintool doesn't seem to break anything.

Regards, Matthias


Am 15.11.2017 um 19:55 schrieb Damjan Jovanovic:
> 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
>>
>>
>>
>>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Simpler Windows builds, oowintool, and Cygwin64

2017-11-16 Thread John D'Orazio

On Wed, Nov 15, 2017 at 6: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
>
Just wondering if after this update the configure script still runs fine?
About a year or so ago when I was testing a cygwin x64 build process, I
noticed that after updating config.guess and config.sub in the cygwin
terminal the configure script starting choking on config.sub. Were you able
to get past this?

Unfortunately I don't have my system set up to build ATM, unfortunately my
"powerful" HP laptop comes with a miserly 128GB SSD as the main drive and
Visual Studio can't be installed on a secondary drive... I'm having a heck
of a time finding a bigger compatible SSD but I hope to resolve this soon,
and set up my build system again...

As these obstacles are removed the Step by step guide can be updated, I had
opened a section about building with cywgwin x64 and I started jotting
provisional notes down, I'd say this looks like the time to update them:
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Testing_build_with_Cygwin_64_bit
.

Re: Simpler Windows builds, oowintool, and Cygwin64

2017-11-15 Thread Patricia Shanahan

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 
> 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: Simpler Windows builds, oowintool, and Cygwin64

2017-11-15 Thread Damjan Jovanovic

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: Simpler Windows builds, oowintool, and Cygwin64

2017-11-15 Thread Matthias Seidel

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
>> > 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

2017-11-15 Thread 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
> > 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

2017-11-15 Thread Matthias Seidel

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
> > 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: Simpler Windows builds, oowintool, and Cygwin64

2017-11-13 Thread Damjan Jovanovic

Please test whether the attached patch helps?

Regards
Damjan

On Sat, Nov 11, 2017 at 8:02 PM, Matthias Seidel  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
> >
>
>
>
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++";
 }

-
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

2017-11-11 Thread Matthias Seidel

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
>




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Simpler Windows builds, oowintool, and Cygwin64

2017-11-10 Thread Patricia Shanahan

I have a Windows 10 computer I do not currently use for builds. I'll 
configure it with 64-bit Cygwin and JDK 8 and try this out.


On 11/10/2017 6:58 AM, Matthias Seidel 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.


Thanks!
At the time when I configured our buildbot for Windows 10 (together with
Infra) we recognized, that oowintool wasn't of great help.
Your fixes make it much easier!



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 will try to set up a machine with cygwin64.
And if I remember it correctly our buildbot has it already installed, so
I could then simply switch...

Regards, Matthias



Damjan






-
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

2017-11-10 Thread Matthias Seidel

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.

Thanks!
At the time when I configured our buildbot for Windows 10 (together with
Infra) we recognized, that oowintool wasn't of great help.
Your fixes make it much easier!

>
> 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 will try to set up a machine with cygwin64.
And if I remember it correctly our buildbot has it already installed, so
I could then simply switch...

Regards, Matthias

>
> Damjan
>




smime.p7s
Description: S/MIME Cryptographic Signature

Simpler Windows builds, oowintool, and Cygwin64

2017-11-09 Thread 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?

Damjan

Re: Simpler Windows builds, oowintool, and Cygwin64

Re: Simpler Windows builds, oowintool, and Cygwin64

Re: Simpler Windows builds, oowintool, and Cygwin64

Re: Simpler Windows builds, oowintool, and Cygwin64

Re: Simpler Windows builds, oowintool, and Cygwin64

Re: Simpler Windows builds, oowintool, and Cygwin64

Re: Simpler Windows builds, oowintool, and Cygwin64

Re: Simpler Windows builds, oowintool, and Cygwin64

Re: Simpler Windows builds, oowintool, and Cygwin64

Re: Simpler Windows builds, oowintool, and Cygwin64

Re: Simpler Windows builds, oowintool, and Cygwin64

Re: Simpler Windows builds, oowintool, and Cygwin64

Re: Simpler Windows builds, oowintool, and Cygwin64

Re: Simpler Windows builds, oowintool, and Cygwin64

Simpler Windows builds, oowintool, and Cygwin64

15 matches

Site Navigation

Mail list logo

Footer information