Here is where the error occurs:

awk: fatal: can't open source file `C:/Cygwin-installationc:/Cygwin-installatio
/openoffice-4.0/openoffice/main/solenv/gbuild/processdeps.awk' for reading (No
uch file or directory)

It appears that C:/Cygwin-installation is appended to the path twice.  Not too 
sure why it is happening.  Is there a quick fix for this?

Regards,

Brett

-----Original Message-----
From: Brett Grentell [mailto:[email protected]] 
Sent: Saturday, December 12, 2015 7:34 PM
To: [email protected]
Subject: Re: Compiler Error

Ah ok,   I know what you mean.   ( there may be some more output above the 
error.)


Sent from Samsung Mobile

<div>-------- Original message --------</div><div>From: Damjan Jovanovic 
<[email protected]> </div><div>Date:12/12/2015  5:09 PM  (GMT+10:00) 
</div><div>To: Apache OO <[email protected]> </div><div>Subject: Re: 
Compiler Error </div><div> </div>Hi

When you compile with -P4, the output from gtest often appears mixed with 
output from the other 3 build jobs. Leave out -P4, and you should be able to 
see more.

Damjan

On Sat, Dec 12, 2015 at 7:55 AM, Brett Grentell <[email protected]>
wrote:

> Hi I am trying to compile open office from source so that I can learn 
> how it all works. I've attempted to compile from scratch a couple of 
> times but each time I come to the same error. (1 module(s): gtest 
> need(s) to be rebuilt).
>
> Ok - I understand that something is wrong with gtest, but there is no 
> indication of what that is. Also there's a message saying that error 
> 65280 occurred while making gtest.
>
> I followed the instructions given on this page ->
>
> https://mail-archives.apache.org/mod_mbox/openoffice-dev/201409.mbox/%
> 3CCALc 
> [email protected]%3E. The 
> parameters were exactly the same.
>
> If someone could help me that would be great.
>
> OpenOffice 4.1 on Windows 10
>
>
>
> Regards,
>
>
>
> Brett Grentell
>
>
>
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to