Re: failed to build aoo420 dev on win32

Hi Damjan, I've attached a possible patch for this, but won't be able to test it for a while. Does it work for you? yes, seems to work i added 2 issues for the remaining build breaks: windows build ./bootstrap fails downloading

Re: failed to build aoo420 dev on win32

Hi Damjan, >> and a new one in module "extensions", source/activex/main >> C:\build_tmp\trunk\main\solver\420\wntmsci12\inc\osl/endian.h(160) : fatal error C1189: #error : undetermined endianness >> dmake: Error code 2, while making '../../../wntmsci12/slo/x64/so_activex.obj' i think this

Re: failed to build aoo420 dev on win32

Hi Damjan, i will start with a clean debug build including your "formula" patch. just noticed, one of the "external_sources" is missing: -> c813c065dd53d7bd0a560a870ddd0af5-openssl-0.9.8zh.tar.gz failed (404 Not Found) i downloaded the package manually from:

Re: failed to build aoo420 dev on win32

On Fri, Jun 10, 2016 at 10:03 PM, Oliver Brinzing wrote: > Hi Damjan, > > thanks for fixing the two build breakers. i started a debug build 3 hours > ago > i have 2 errors till now: > Hi Oliver > >> windows build breaks in module formula > >>

Re: failed to build aoo420 dev on win32

Hi Damjan, thanks for fixing the two build breakers. i started a debug build 3 hours ago i have 2 errors till now: >> windows build breaks in module formula >> https://bz.apache.org/ooo/show_bug.cgi?id=126916 and a new one in module "extensions", source/activex/main

Re: failed to build aoo420 dev on win32

The "assertion failed" messageboxes problem (#i126918#) is fixed in trunk now. You no longer need --disable-unit-tests, and are better off with the unit tests enabled. Regards Damjan On Sun, Apr 10, 2016 at 2:28 PM, Oliver Brinzing wrote: > Hi Patricia, > > thanks for

Re: failed to build aoo420 dev on win32

I just completed a successful debug compile! Thanks. On 6/8/2016 12:33 PM, Damjan Jovanovic wrote: Hi Patricia, with that patch, you were going in the right direction by moving the declaration of OSQLParser_Data to the publicly visible inc/connectivity/sqlparse.hxx, but since that header

Re: failed to build aoo420 dev on win32

That is the sort of problem that should be expected when trying to revive my C++ skills - I last used it extensively before "namespace" became popular. I know in theory how it works, but that is not the same as having worked for a few years with a feature. On 6/8/2016 12:33 PM, Damjan

Re: failed to build aoo420 dev on win32

Hi Patricia, with that patch, you were going in the right direction by moving the declaration of OSQLParser_Data to the publicly visible inc/connectivity/sqlparse.hxx, but since that header doesn't (and shouldn't?) have "using namespace ::com::sun::star::...", this needed changing: -

Blocked from AOO work: Re: failed to build aoo420 dev on win32

I can no longer build debug versions of AOO due to this issue, making further AOO work difficult to impossible. Because of other commitments, I don't expect to do anything further on it until the end of June. Is there any chance someone with less rusty C++ could look into this before then?

Re: failed to build aoo420 dev on win32

I decided to try to fix the underlying error/warning, by making the header file declaration complete. Unfortunately, I think my C++ rustiness is getting in the way. I get an error suggesting a constructor is being treated as a function. I've attached a diff in the hope that someone else can

Re: failed to build aoo420 dev on win32

> My previous, successful, debug compile was revision 1734822, March 13th 2016, so the problem has to > be something that has changed since then. i checked output from pro an debug build: debug creates an error C4150 while pro will continue with a warning the different compiler setting are:

Re: failed to build aoo420 dev on win32

On 4/25/2016 9:07 AM, Oliver Brinzing wrote: I checked out the latest, and tried to build it. My debug build also failed on sqliterator.cxx. I used exactly the same configure parameters as on previous successful debug builds. thanks for testing, hopefully i will find some time to do further

Re: failed to build aoo420 dev on win32

> I checked out the latest, and tried to build it. My debug build also failed on sqliterator.cxx. I > used exactly the same configure parameters as on previous successful debug builds. thanks for testing, hopefully i will find some time to do further investigation. Oliver

Re: failed to build aoo420 dev on win32

I checked out the latest, and tried to build it. My debug build also failed on sqliterator.cxx. I used exactly the same configure parameters as on previous successful debug builds. Patricia On 4/17/2016 12:34 PM, Oliver Brinzing wrote: Hi, this weekend i tried again and was able to build

Re: failed to build aoo420 dev on win32

Hi, this weekend i tried again and was able to build current aoo420 (product) i had only one build break: C:/build/cygwin/bin/perl checkdeliver.pl -l ../wntmsci12.pro/misc/checkdeliver_log.txt && C:/build/cygwin/bin/touch.exe ../wntmsci12.pro/misc/checkdeliver.done checkdeliver.pl - checking

Re: failed to build aoo420 dev on win32

On 4/10/2016 5:28 AM, Oliver Brinzing wrote: Hi Patricia, thanks for your build settings. Did you manage to build aoo420 debug version? I am building off the current Trunk. Is that a00420? yesterday i started a new aoo412 debug build with my settings. after 5 hours the build finished

Re: failed to build aoo420 dev on win32

Hi Patricia, thanks for your build settings. Did you manage to build aoo420 debug version? yesterday i started a new aoo412 debug build with my settings. after 5 hours the build finished without any problems. i tried again with rev 1738357 and failed again... added 4 issues: windows build

Re: failed to build aoo420 dev on win32

For comparison, here is the debug version of my configure parameters: $ more run_configure.sh SDK_PATH="/cygdrive/c/Program Files/Microsoft SDKs/Windows/v7.0" ./configure \ --enable-dbgutil \ --enable-symbols \ --disable-unit-tests \ --with-frame-home="$SDK_PATH" \

Re: failed to build aoo420 dev on win32

Hi Patricia > How are you specifying debug? Any differences between what you are doing and https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Windows_7.2C_Windows_8.1? I have been doing Windows 8.1 debug builds without any problems. I manually 'make debug=true' the

Re: failed to build aoo420 dev on win32

How are you specifying debug? Any differences between what you are doing and https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Windows_7.2C_Windows_8.1? I have been doing Windows 8.1 debug builds without any problems. I manually 'make debug=true' the gmake