Re: Building on Windows
According to http://stackoverflow.com/questions/19641685/java-jni-jawt-error-unresolved-external-symbol-imp-jawt-getawt8 you're using a 64 bit JDK instead of a 32 bit one. On Tue, Feb 2, 2016 at 9:40 AM, Patricia Shanahan wrote: > After checking out with Cygwin's svn rather than TortoiseSVN, my build > failed in "Building module bean" with the following message: > >Creating library ../../wntmsci12.pro/lib/iofficebean_t1.lib and object > ../../wntmsci12.pro/lib/iofficebean_t1.exp > officebean.lib(com_sun_star_comp_beans_LocalOfficeWindow.obj) : error > LNK2019: unresolved external symbol __imp__JAWT_GetAWT@8 referenced in > function _Java_com_sun_star_comp_beans_LocalOfficeWindow_getNativeWindow@8 > ../../wntmsci12.pro/bin/officebean.dll : fatal error LNK1120: 1 > unresolved externals > dmake: Error code 96, while making '../../ > wntmsci12.pro/bin/officebean.dll' > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: Building on Windows
After checking out with Cygwin's svn rather than TortoiseSVN, my build failed in "Building module bean" with the following message: Creating library ../../wntmsci12.pro/lib/iofficebean_t1.lib and object ../../wntmsci12.pro/lib/iofficebean_t1.exp officebean.lib(com_sun_star_comp_beans_LocalOfficeWindow.obj) : error LNK2019: unresolved external symbol __imp__JAWT_GetAWT@8 referenced in function _Java_com_sun_star_comp_beans_LocalOfficeWindow_getNativeWindow@8 ../../wntmsci12.pro/bin/officebean.dll : fatal error LNK1120: 1 unresolved externals dmake: Error code 96, while making '../../wntmsci12.pro/bin/officebean.dll' - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Let's fix the Windows build bots
On Mon, Feb 1, 2016 at 2:43 AM, j.nitsc...@ok.de wrote: > On Sun, 31 Jan 2016 10:07:33 -0800 Kay Schenk wrote: > > On Fri, Jan 29, 2016 at 10:04 PM, Damjan Jovanovic > > wrote: > > >> I think the latter is true: it's re-entering them because they broke the > >> build. > >> > >> Yesterday jpeg failed to download and broke the build, and today nss > failed > >> to download and also broke the build. Why are downloads often failing > >> during ./bootstrap? Can we get a local mirror or cache external > >> dependencies somehow? Also, why does ./bootstrap seem to return an exit > >> code of 0 when needed dependencies can't be downloaded, and why is > >> haltOnFailure=False for the Windows buildbots but True for other > platforms? > >> > > No idea about this setting. You might look at the svn logs for our > config > > to see if there's any information there. Otherwise, just change it if you > > feel inclined. > Not sure if you are talking about a global setting or just for the > 'build.pl --all' step. > But a global haltOnFailure would stop the build at 'svn info' step. > > I meant just for the ./bootstrap step. > About the 'svn info' step, this one stopped working between 27.07.2015 > and 03.08.2015 as one can see in the snapshot builds #7 and #8 which run > exact the same command but later fails. > https://ci.apache.org/builders/aoo-w7snap/builds/7 > https://ci.apache.org/builders/aoo-w7snap/builds/8 > > The error on https://ci.apache.org/builders/aoo-win7/builds/159/steps/svn%20info/logs/stdio is: 'svn' is not recognized as an internal or external command, operable program or batch file. As of r979234 I started running "svn info" under Cygwin like is already done for "svn co". Let's see if it helps. Is there some way to request an immediate rebuild?
Re: Let's fix the Windows build bots
On Sat, Jan 30, 2016 at 8:04 AM, Damjan Jovanovic wrote: > > > On Fri, Jan 29, 2016 at 7:25 PM, Kay Schenk wrote: > >> On Thu, Jan 28, 2016 at 11:18 PM, Damjan Jovanovic >> wrote: >> >> > >> > Our build page https://ci.apache.org/projects/openoffice/index.html is >> > also >> > messed up - eg. "Windows Nightly Build Logs" is listed under "FreeBSD >> > nightly Install Packages". How do we edit it? >> > >> >> Ok, yeah, it's a bit of odd formatting. I understand what you're saying. >> Look at the other areas and you'll see that the HRs come under the Build >> Logs headings. So this is not just a Windows anomaly. >> >> We can definitely change this. >> >> Here is the svn info for this page if you want to change things: >> >> >> https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/public_html/projects/openoffice >> >> Have fun. >> >> > I made several changes, but they aren't being applied. When/how does the > create-ooo-snapshots-index.sh script create the webpage? > > This still isn't working: I've changed https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/public_html/projects/openoffice/create-ooo-snapshots-index.sh but https://ci.apache.org/projects/openoffice/index.html hasn't changed in days. Please help? Damjan
Re: Building on Windows
On 2/1/2016 7:00 AM, Damjan Jovanovic wrote: On Mon, Feb 1, 2016 at 4:46 PM, Patricia Shanahan wrote: On 2/1/2016 4:34 AM, Regina Henschel wrote: Hi Patricia, Patricia Shanahan schrieb: Now I'm stuck. I got through configure, with warnings. Can you please be more specific about the warnings? Are you sure, you start building in instsetoo_native ? I've posted a message in this thread with config.log attached. Here is the prompt, including current directory, from my attempt to run build. I did my SVN checkout into /cygdrive/c/OpenOfficeDev/Trunk Patricia@Jan2014Desktop /cygdrive/c/OpenOfficeDev/Trunk/main/instsetoo_native $ build --all Thanks, Patricia Windows is probably the worst platform to build on: it's the slowest and apparently the most problematic :-(. 64-bit Windows is one of the commonest platforms that can be used for software development. The problems with building AOO on it may discourage a lot of potential developers. Nothing seems obviously wrong so far. That perl file your build breaks on wasn't changed since 2012. Later I will compare your ./configure options with my own that works. In the meanwhile please post the entire sequence of commands you ran, from autoconf onwards. You could also "dmake clean" after you "source winenv...", then start again from ./configure. Thanks for looking into it. It appears to probably be, ultimately, an issue with TortoiseSVN mangling line endings. I am redoing the checkout using Cygwin's command line svn. Once that is done, I'll copy over a few things from the old tree, and try again from autoconf on. Patricia - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Building on Windows
On 2/1/2016 2:41 PM, j.nitsc...@ok.de wrote:
On Mon, 1 Feb 2016 14:08:06 -0800 Patricia Shanahan wrote:
On 2/1/2016 12:04 PM, Patricia Shanahan wrote:
On 1/31/2016 6:36 PM, Patricia Shanahan wrote:
Now I'm stuck. I got through configure, with warnings. My build attempt
failed with:
$ build --all
build -- version: 275224
=
Building module solenv
=
Entering /cygdrive/c/OpenOfficeDev/Trunk/main/solenv
/cygdrive/c/OpenOfficeDev/Trunk/main/solenv/bin/mkout.pl: line 1:
$':\r': command not found
mkout -- version: 1.8
The perl module mkout.pl starts with:
:
eval 'exec perl -wS $0 ${1+"$@"}'
if 0;
My Perl is very rusty. Can anyone translate? Especially, the initial
line with just a ":" confuses both me and the build.
I took my problem to StackOverflow. See
http://stackoverflow.com/a/35140265/1798593
I worked around it by setting igncr in my Cygwin bash SHELLOPTS, and
the build is now building.
Patricia
interesting, how did you checkout the source?
I remember TortoiseSVN converted unix line endings to windows style
unless told otherwise. The original git-scm asks on installation how to
treat line endings. No idea how the cygwin subverion and git packages
behave.
You might run into other unexpected problems due line endings. (e.g.
scripts replacing \n with \r\n for windows)
I would checkout the source again.
Thanks. I did use TortoiseSVN, so that is probably the problem.
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Building on Windows
On Mon, 1 Feb 2016 14:08:06 -0800 Patricia Shanahan wrote:
>
>
> On 2/1/2016 12:04 PM, Patricia Shanahan wrote:
>>
>>
>> On 1/31/2016 6:36 PM, Patricia Shanahan wrote:
>>> Now I'm stuck. I got through configure, with warnings. My build attempt
>>> failed with:
>>>
>>> $ build --all
>>> build -- version: 275224
>>>
>>>
>>> =
>>> Building module solenv
>>> =
>>>
>>> Entering /cygdrive/c/OpenOfficeDev/Trunk/main/solenv
>>>
>>> /cygdrive/c/OpenOfficeDev/Trunk/main/solenv/bin/mkout.pl: line 1:
>>> $':\r': command not found
>>> mkout -- version: 1.8
>>
>> The perl module mkout.pl starts with:
>>
>> :
>> eval 'exec perl -wS $0 ${1+"$@"}'
>> if 0;
>>
>>
>> My Perl is very rusty. Can anyone translate? Especially, the initial
>> line with just a ":" confuses both me and the build.
>
> I took my problem to StackOverflow. See
> http://stackoverflow.com/a/35140265/1798593
>
> I worked around it by setting igncr in my Cygwin bash SHELLOPTS, and
> the build is now building.
>
> Patricia
interesting, how did you checkout the source?
I remember TortoiseSVN converted unix line endings to windows style
unless told otherwise. The original git-scm asks on installation how to
treat line endings. No idea how the cygwin subverion and git packages
behave.
You might run into other unexpected problems due line endings. (e.g.
scripts replacing \n with \r\n for windows)
I would checkout the source again.
signature.asc
Description: OpenPGP digital signature
Re: Building on Windows
On 2/1/2016 12:04 PM, Patricia Shanahan wrote:
On 1/31/2016 6:36 PM, Patricia Shanahan wrote:
Now I'm stuck. I got through configure, with warnings. My build attempt
failed with:
$ build --all
build -- version: 275224
=
Building module solenv
=
Entering /cygdrive/c/OpenOfficeDev/Trunk/main/solenv
/cygdrive/c/OpenOfficeDev/Trunk/main/solenv/bin/mkout.pl: line 1:
$':\r': command not found
mkout -- version: 1.8
The perl module mkout.pl starts with:
:
eval 'exec perl -wS $0 ${1+"$@"}'
if 0;
My Perl is very rusty. Can anyone translate? Especially, the initial
line with just a ":" confuses both me and the build.
I took my problem to StackOverflow. See
http://stackoverflow.com/a/35140265/1798593
I worked around it by setting igncr in my Cygwin bash SHELLOPTS, and the
build is now building.
Patricia
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Building on Windows
On 1/31/2016 6:36 PM, Patricia Shanahan wrote:
Now I'm stuck. I got through configure, with warnings. My build attempt
failed with:
$ build --all
build -- version: 275224
=
Building module solenv
=
Entering /cygdrive/c/OpenOfficeDev/Trunk/main/solenv
/cygdrive/c/OpenOfficeDev/Trunk/main/solenv/bin/mkout.pl: line 1:
$':\r': command not found
mkout -- version: 1.8
The perl module mkout.pl starts with:
:
eval 'exec perl -wS $0 ${1+"$@"}'
if 0;
My Perl is very rusty. Can anyone translate? Especially, the initial
line with just a ":" confuses both me and the build.
Patricia
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Possible difference between RPM and DEB OO instaals
On Mon, 01 Feb 2016 19:37:24 +0100 Andrea Pescetti wrote: > Rory O'Farrell wrote: > > A thread on en-Forum suggests that there may be a difference, perhaps even > > a bug, between the RPM and DEB linux installs. > > We don't have different packaging in this respect, I think. Anyway in > 4.1.2 RPM I can successfully switch between OpenOffice dialogues and > system (GNOME 3) dialogues. > > > Can list members with appropriate machines confirm this difference before > > we post it to Bugzilla? > > I guess this may be an environment issue. I would definitely like to > know more on this, but this is not a packaging issue. > > Regards, >Andrea. Thanks, Andrea. I'll pass that on. acknak can be relied upon to supply any required information. -- Rory O'Farrell - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Possible difference between RPM and DEB OO instaals
Rory O'Farrell wrote: A thread on en-Forum suggests that there may be a difference, perhaps even a bug, between the RPM and DEB linux installs. We don't have different packaging in this respect, I think. Anyway in 4.1.2 RPM I can successfully switch between OpenOffice dialogues and system (GNOME 3) dialogues. Can list members with appropriate machines confirm this difference before we post it to Bugzilla? I guess this may be an environment issue. I would definitely like to know more on this, but this is not a packaging issue. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Possible difference between RPM and DEB OO instaals
A thread on en-Forum suggests that there may be a difference, perhaps even a bug, between the RPM and DEB linux installs. In /Tools /Options /OpenOffice : General, there is an option to switch between OO file dialogues and O.S. file dialogues. In this thread https://forum.openoffice.org/en/forum/viewtopic.php?f=6&t=81618 the OP posts a screenshot to show he has not that option running on CentOS 7.1. acknak, a Forum Administrator, has the option running on Fedora 23, but indicates that it doesn't work. Both of these are RPM installs. It does work for me running on Xubuntu 15.10 (DEB file install) Can list members with appropriate machines confirm this difference before we post it to Bugzilla? -- Rory O'Farrell - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Building on Windows
On 2/1/2016 8:34 AM, Damjan Jovanovic wrote: On Mon, Feb 1, 2016 at 1:49 PM, Patricia Shanahan wrote: On 1/31/2016 11:59 PM, Damjan Jovanovic wrote: On Mon, Feb 1, 2016 at 4:36 AM, Patricia Shanahan wrote: Now I'm stuck. I got through configure, with warnings. My build attempt failed with: $ build --all build -- version: 275224 = Building module solenv = Entering /cygdrive/c/OpenOfficeDev/Trunk/main/solenv /cygdrive/c/OpenOfficeDev/Trunk/main/solenv/bin/mkout.pl: line 1: $':\r': command not found mkout -- version: 1.8 /usr/bin/bash: C:/OpenOfficeDev/Trunk/main/solenv/ wntmsci12.pro/inc/myworld.mk: No such file or directory dmake: Error code 1, while making '/cygdrive/C/OpenOfficeDev/Trunk/main/solenv/ wntmsci12.pro/inc/myworld.mk' 1 module(s): solenv need(s) to be rebuilt Reason(s): ERROR: error 65280 occurred while making /cygdrive/c/OpenOfficeDev/Trunk/main/solenv When you have fixed the errors in that module you can resume the build by running: build --all:solenv Any advice on e.g. configure warnings that are likely to be significant? A Perl problem of some kind? Please post your main/config.log and see if the "perl" command works. A perl "hello, world" runs in the Cygwin terminal window I used for the build attempt. I am attaching my config.log. The call was: SDK_PATH="/cygdrive/c/Program Files/Microsoft SDKs/Windows/v7.0" ./configure \ --with-frame-home="$SDK_PATH" \ --with-psdk-home="$SDK_PATH" \ --with-midl-path="$SDK_PATH/bin" \ --with-directx-home="C:/Program Files (x86)/Microsoft DirectX SDK (June 2010)" \ --with-ant-home="/cygdrive/c/ant" \ --with-dmake-url=" http://dmake.apache-extras.org.codespot.com/files/dmake-4.12.tar.bz2"; \ --with-epm-url="http://www.msweet.org/files/project2/epm-3.7-source.tar.gz"; \ --enable-pch \ --disable-atl \ --disable-activex \ --without-junit \ --with-jdk-home="/cygdrive/c/Program Files/Java/jdk1.7.0_67" Thanks for any advice, Patricia Why do you have both PROGRA~1 and PROGRA~2 paths (I presume these are "Program Files" and "Program Files (x86)")? Are you building on Win64? We don't have a Win64 version of AOO, so it's possible (I'm not sure) that AOO doesn't even compile on Win64. PATH: /cygdrive/c/PROGRA~1/Java/JDK18~1.0_7/bin PATH: /cygdrive/c/PROGRA~2/MICROS~1.0/VC/bin PATH: /cygdrive/c/PROGRA~2/MICROS~1.0/Common7/IDE PATH: /cygdrive/c/PROGRA~1/MICROS~2/Windows/v7.0/bin PATH: /cygdrive/c/Windows/MICROS~1.NET/FRAMEW~1/V20~1.507 PATH: /cygdrive/c/PROGRA~2/MICROS~1.0/VC/bin Otherwise my own ./configure options differ from yours as follows: * Build is done in a 32 bit virtual machine * I used --disable-directx instead of your --with-directx-home=... * I also had --with-cl-home=/cygdrive/c/Program Files/Microsoft Visual Studio 9.0/VC * I also had --with-csc-path=/cygdrive/c/Windows/Microsoft.NET/Framework/v3.5 Damjan I don't have a working 32-bit machine. When is AOO going to catch up with current memory sizes? I've already had to downgrade to 32-bit Cygwin. I'll try the rest of the changes first, but having to go virtual to build would probably kill my attempts to do AOO development on Windows. I might try to do some work on one of my Linux boxes instead, but it would affect my productivity. They only have small screens, relatively small memories (still too big for a 32 bit OS), and don't support Carbonite for backup. Also, I would like to be able to look at equation display on Windows, and for that I need to do Windows builds. Thanks, Patricia - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Building on Windows
On Mon, Feb 1, 2016 at 1:49 PM, Patricia Shanahan wrote: > > > On 1/31/2016 11:59 PM, Damjan Jovanovic wrote: > >> On Mon, Feb 1, 2016 at 4:36 AM, Patricia Shanahan wrote: >> >> Now I'm stuck. I got through configure, with warnings. My build attempt >>> failed with: >>> >>> $ build --all >>> build -- version: 275224 >>> >>> >>> = >>> Building module solenv >>> = >>> >>> Entering /cygdrive/c/OpenOfficeDev/Trunk/main/solenv >>> >>> /cygdrive/c/OpenOfficeDev/Trunk/main/solenv/bin/mkout.pl: line 1: >>> $':\r': >>> command not found >>> mkout -- version: 1.8 >>> /usr/bin/bash: C:/OpenOfficeDev/Trunk/main/solenv/ >>> wntmsci12.pro/inc/myworld.mk: No such file or directory >>> dmake: Error code 1, while making >>> '/cygdrive/C/OpenOfficeDev/Trunk/main/solenv/ >>> wntmsci12.pro/inc/myworld.mk' >>> >>> 1 module(s): >>> solenv >>> need(s) to be rebuilt >>> >>> Reason(s): >>> >>> ERROR: error 65280 occurred while making >>> /cygdrive/c/OpenOfficeDev/Trunk/main/solenv >>> >>> When you have fixed the errors in that module you can resume the build by >>> running: >>> >>> build --all:solenv >>> >>> Any advice on e.g. configure warnings that are likely to be significant? >>> >>> >>> A Perl problem of some kind? >> >> Please post your main/config.log and see if the "perl" command works. >> > > A perl "hello, world" runs in the Cygwin terminal window I used for the > build attempt. I am attaching my config.log. The call was: > > SDK_PATH="/cygdrive/c/Program Files/Microsoft SDKs/Windows/v7.0" > ./configure \ > --with-frame-home="$SDK_PATH" \ > --with-psdk-home="$SDK_PATH" \ > --with-midl-path="$SDK_PATH/bin" \ > --with-directx-home="C:/Program Files (x86)/Microsoft DirectX SDK > (June 2010)" \ > --with-ant-home="/cygdrive/c/ant" \ > > --with-dmake-url=" > http://dmake.apache-extras.org.codespot.com/files/dmake-4.12.tar.bz2"; \ > > --with-epm-url="http://www.msweet.org/files/project2/epm-3.7-source.tar.gz"; > \ > --enable-pch \ > --disable-atl \ > --disable-activex \ > --without-junit \ > --with-jdk-home="/cygdrive/c/Program Files/Java/jdk1.7.0_67" > > Thanks for any advice, > > Patricia > > Why do you have both PROGRA~1 and PROGRA~2 paths (I presume these are "Program Files" and "Program Files (x86)")? Are you building on Win64? We don't have a Win64 version of AOO, so it's possible (I'm not sure) that AOO doesn't even compile on Win64. PATH: /cygdrive/c/PROGRA~1/Java/JDK18~1.0_7/bin PATH: /cygdrive/c/PROGRA~2/MICROS~1.0/VC/bin PATH: /cygdrive/c/PROGRA~2/MICROS~1.0/Common7/IDE PATH: /cygdrive/c/PROGRA~1/MICROS~2/Windows/v7.0/bin PATH: /cygdrive/c/Windows/MICROS~1.NET/FRAMEW~1/V20~1.507 PATH: /cygdrive/c/PROGRA~2/MICROS~1.0/VC/bin Otherwise my own ./configure options differ from yours as follows: * Build is done in a 32 bit virtual machine * I used --disable-directx instead of your --with-directx-home=... * I also had --with-cl-home=/cygdrive/c/Program Files/Microsoft Visual Studio 9.0/VC * I also had --with-csc-path=/cygdrive/c/Windows/Microsoft.NET/Framework/v3.5 Damjan
Re: Building on Windows
On Mon, Feb 1, 2016 at 4:46 PM, Patricia Shanahan wrote: > On 2/1/2016 4:34 AM, Regina Henschel wrote: > >> Hi Patricia, >> >> Patricia Shanahan schrieb: >> >>> Now I'm stuck. I got through configure, with warnings. >>> >> >> Can you please be more specific about the warnings? >> >> Are you sure, you start building in instsetoo_native ? >> > > I've posted a message in this thread with config.log attached. Here is the > prompt, including current directory, from my attempt to run build. I did my > SVN checkout into /cygdrive/c/OpenOfficeDev/Trunk > > Patricia@Jan2014Desktop > /cygdrive/c/OpenOfficeDev/Trunk/main/instsetoo_native > $ build --all > > Thanks, > > Patricia > > Windows is probably the worst platform to build on: it's the slowest and apparently the most problematic :-(. Nothing seems obviously wrong so far. That perl file your build breaks on wasn't changed since 2012. Later I will compare your ./configure options with my own that works. In the meanwhile please post the entire sequence of commands you ran, from autoconf onwards. You could also "dmake clean" after you "source winenv...", then start again from ./configure. Thank you Damjan
Re: Norwegian translation for website
Any news on this? I see now a “hello” web page up for http://www.openoffice.org/no-test/ -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com > 25. jan. 2016 kl. 23.06 skrev Marcus : > > Thanks for testing. I've ping'ed Daniel again for help. Let's see if he can > help us also with this. > > Marcus > > > > Am 01/25/2016 11:01 PM, schrieb Andrea Pescetti: >> On 23/01/2016 Marcus wrote: >>> However, the new dir "no-test/" is not going to staging [1]. I can do >>> changes in my CMS working directory or from the command line from my >>> local PC but it's not going to the staging build - or the production >>> build [2]. >>> The same when committing changes in already existing files and dirs. >> >> I remember that I had problems also last time the CMS was restored. >> Namely, I had updated the logo but it wouldn't show up. And I had to >> manually change it again for the CMS to pick up the update. It seems you >> have already done so though. >> >> I have just tried a forced republish and then I tried adding the >> templates under templates/; after doing this, I republished but with no >> results. >> >> On the other side, I confirm that my previous changes to >> http://www.openoffice.org/eu/ (where I uploaded the new Basque >> translation) are not shown either. So this looks more a general CMS >> problem than something specific to the no-test directory. > > - > 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: Really?!
On Mon, 1 Feb 2016 08:53:57 -0500 chrispy...@aol.com wrote: > YOUR WEBSITE SUCKS...NO HELP AT ALLI HAVE SPENT HOURS UPON HOURS TRYING > TO GET HELPI CAN NOT AFFORD TO PAY FOR THE HELP, I AM PRESENTLY > UNEMPLOYED. I AM S DISAPPOINTED IN THE LACK OF HELP PROVIDED. I AM > READY > TO GO CHARGE THE COST OF MICROSOFT OFFICE. AT LEAST THEY PROVIDE HELP!! > I WILL NEVER EVER RECOMMEND APACHE TO ANYONE I KNOW. EVEN THE FORUMS > STATE HOW HARD IT IS TO GET HELP...AGAIN YOUR CUSTOMER SERVICE SUCKS! The OpenOffice project is available for free. The Website and Forum , as also this mailing list, are manned by volunteers on a pro bono basis. If you told us what your problems are, we might be able to help. By the way, the shift key on your keyboard seems to be stuck. -- Rory O'Farrell - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Building on Windows
On 2/1/2016 4:34 AM, Regina Henschel wrote: Hi Patricia, Patricia Shanahan schrieb: Now I'm stuck. I got through configure, with warnings. Can you please be more specific about the warnings? Are you sure, you start building in instsetoo_native ? I've posted a message in this thread with config.log attached. Here is the prompt, including current directory, from my attempt to run build. I did my SVN checkout into /cygdrive/c/OpenOfficeDev/Trunk Patricia@Jan2014Desktop /cygdrive/c/OpenOfficeDev/Trunk/main/instsetoo_native $ build --all Thanks, Patricia - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Really?!
YOUR WEBSITE SUCKS...NO HELP AT ALLI HAVE SPENT HOURS UPON HOURS TRYING TO GET HELPI CAN NOT AFFORD TO PAY FOR THE HELP, I AM PRESENTLY UNEMPLOYED. I AM S DISAPPOINTED IN THE LACK OF HELP PROVIDED. I AM READY TO GO CHARGE THE COST OF MICROSOFT OFFICE. AT LEAST THEY PROVIDE HELP!! I WILL NEVER EVER RECOMMEND APACHE TO ANYONE I KNOW. EVEN THE FORUMS STATE HOW HARD IT IS TO GET HELP...AGAIN YOUR CUSTOMER SERVICE SUCKS!
Re: Building on Windows
Hi Patricia, Patricia Shanahan schrieb: Now I'm stuck. I got through configure, with warnings. Can you please be more specific about the warnings? Are you sure, you start building in instsetoo_native ? Kind regards Regina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Building on Windows
On 1/31/2016 11:59 PM, Damjan Jovanovic wrote: On Mon, Feb 1, 2016 at 4:36 AM, Patricia Shanahan wrote: Now I'm stuck. I got through configure, with warnings. My build attempt failed with: $ build --all build -- version: 275224 = Building module solenv = Entering /cygdrive/c/OpenOfficeDev/Trunk/main/solenv /cygdrive/c/OpenOfficeDev/Trunk/main/solenv/bin/mkout.pl: line 1: $':\r': command not found mkout -- version: 1.8 /usr/bin/bash: C:/OpenOfficeDev/Trunk/main/solenv/ wntmsci12.pro/inc/myworld.mk: No such file or directory dmake: Error code 1, while making '/cygdrive/C/OpenOfficeDev/Trunk/main/solenv/wntmsci12.pro/inc/myworld.mk' 1 module(s): solenv need(s) to be rebuilt Reason(s): ERROR: error 65280 occurred while making /cygdrive/c/OpenOfficeDev/Trunk/main/solenv When you have fixed the errors in that module you can resume the build by running: build --all:solenv Any advice on e.g. configure warnings that are likely to be significant? A Perl problem of some kind? Please post your main/config.log and see if the "perl" command works. A perl "hello, world" runs in the Cygwin terminal window I used for the build attempt. I am attaching my config.log. The call was: SDK_PATH="/cygdrive/c/Program Files/Microsoft SDKs/Windows/v7.0" ./configure \ --with-frame-home="$SDK_PATH" \ --with-psdk-home="$SDK_PATH" \ --with-midl-path="$SDK_PATH/bin" \ --with-directx-home="C:/Program Files (x86)/Microsoft DirectX SDK (June 2010)" \ --with-ant-home="/cygdrive/c/ant" \ --with-dmake-url="http://dmake.apache-extras.org.codespot.com/files/dmake-4.12.tar.bz2"; \ --with-epm-url="http://www.msweet.org/files/project2/epm-3.7-source.tar.gz"; \ --enable-pch \ --disable-atl \ --disable-activex \ --without-junit \ --with-jdk-home="/cygdrive/c/Program Files/Java/jdk1.7.0_67" Thanks for any advice, Patricia This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by configure, which was generated by GNU Autoconf 2.69. Invocation command line was $ ./configure --with-frame-home=/cygdrive/c/Program Files/Microsoft SDKs/Windows/v7.0 --with-psdk-home=/cygdrive/c/Program Files/Microsoft SDKs/Windows/v7.0 --with-midl-path=/cygdrive/c/Program Files/Microsoft SDKs/Windows/v7.0/bin --with-directx-home=C:/Program Files (x86)/Microsoft DirectX SDK (June 2010) --with-ant-home=/cygdrive/c/ant --with-dmake-url=http://dmake.apache-extras.org.codespot.com/files/dmake-4.12.tar.bz2 --with-epm-url=http://www.msweet.org/files/project2/epm-3.7-source.tar.gz --enable-pch --disable-atl --disable-activex --without-junit --with-jdk-home=/cygdrive/c/Program Files/Java/jdk1.7.0_67 ## - ## ## Platform. ## ## - ## hostname = Jan2014Desktop uname -m = i686 uname -r = 2.4.1(0.293/5/3) uname -s = CYGWIN_NT-6.3-WOW uname -v = 2016-01-24 11:24 /usr/bin/uname -p = unknown /bin/uname -X = unknown /bin/arch = i686 /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: . PATH: /cygdrive/c/OpenOfficeDev/Trunk/main/solenv/bin PATH: /cygdrive/c/OpenOfficeDev/Trunk/main/solenv/wntmsci12.pro/bin PATH: /cygdrive/c/PROGRA~1/Java/JDK18~1.0_7/bin PATH: /cygdrive/c/PROGRA~2/MICROS~1.0/VC/bin PATH: /cygdrive/c/PROGRA~2/MICROS~1.0/Common7/IDE PATH: /cygdrive/c/PROGRA~1/MICROS~2/Windows/v7.0/bin PATH: /cygdrive/c/Windows/MICROS~1.NET/FRAMEW~1/V20~1.507 PATH: /cygdrive/c/PROGRA~2/MICROS~1.0/VC/bin PATH: /usr/bin PATH: /cygdrive/c/PROGRA~2/NSIS PATH: /usr/local/bin PATH: /cygdrive/c/ProgramData/Oracle/Java/javapath PATH: /cygdrive/c/Program Files (x86)/Intel/iCLS Client PATH: /cygdrive/c/Program Files/Intel/iCLS Client PATH: /cygdrive/c/Program Files (x86)/NVIDIA Corporation/PhysX/Common PATH: /cygdrive/c/WINDOWS/system32 PATH: /cygdrive/c/WINDOWS PATH: /cygdrive/c/WINDOWS/System32/Wbem PATH: /cygdrive/c/WINDOWS/System32/WindowsPowerShell/v1.0 PATH: /cygdrive/c/Program Files/Intel/Intel(R) Management Engine Components/DAL PATH: /cygdrive/c/Program Files/Intel/Intel(R) Management Engine Components/IPT PATH: /cygdrive/c/Program Files (x86)/Intel/Intel(R) Management Engine Components/DAL PATH: /cygdrive/c/Program Files (x86)/Intel/Intel(R) Management Engine Components/IPT PATH: /cygdrive/c/Program Files (x86)/Windows Live/Shared PATH: /cygdrive/c/Program Files/Intel/WiFi/bin PATH: /cygdrive/c/Program Files/Common Files/Intel/WirelessCommon PATH: /cygdrive/c/Program Files/TortoiseSVN/bin PATH: /cygdrive/c/MinGW/bin PATH: /cygdrive/c/MinGW/msys/1.0/bin PATH: /cygdrive/c/WINDOWS/system32/config/systemprofile/.dnx/bin PATH: /cygdrive/c/Program Files/Microsoft DNX/Dnvm PATH: /usr/lib/lapack PATH: /usr/openwin/bin ## --- ## ## Core tests. ## ## --- ## configure:5146: checking whet
Re: Building on Windows
On Mon, Feb 1, 2016 at 4:36 AM, Patricia Shanahan wrote: > Now I'm stuck. I got through configure, with warnings. My build attempt > failed with: > > $ build --all > build -- version: 275224 > > > = > Building module solenv > = > > Entering /cygdrive/c/OpenOfficeDev/Trunk/main/solenv > > /cygdrive/c/OpenOfficeDev/Trunk/main/solenv/bin/mkout.pl: line 1: $':\r': > command not found > mkout -- version: 1.8 > /usr/bin/bash: C:/OpenOfficeDev/Trunk/main/solenv/ > wntmsci12.pro/inc/myworld.mk: No such file or directory > dmake: Error code 1, while making > '/cygdrive/C/OpenOfficeDev/Trunk/main/solenv/wntmsci12.pro/inc/myworld.mk' > > 1 module(s): > solenv > need(s) to be rebuilt > > Reason(s): > > ERROR: error 65280 occurred while making > /cygdrive/c/OpenOfficeDev/Trunk/main/solenv > > When you have fixed the errors in that module you can resume the build by > running: > > build --all:solenv > > Any advice on e.g. configure warnings that are likely to be significant? > > A Perl problem of some kind? Please post your main/config.log and see if the "perl" command works. Damjan
