Re: Build --all errors on libxml2?

[Hong]

Hi Damjan,

I will paste the raw text here. The mailing list probably filtered the
attachment out.

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/Microsoft_SDKs/Windows/v7.0
--with-psdk-home=/cygdrive/c/Microsoft_SDKs/Windows/v7.0
--with-midl-path=/cygdrive/c/Microsoft_SDKs/Windows/v7.0/bin
--with-ant-home=/cygdrive/c/apacheAnt
--with-jdk-home=C:/PROGRA~2/Java/JDK18~1.0_1
--with-csc-path=C:/Windows/Microsoft.NET/Framework/v3.5
--with-cl-home=C:/PROGRA~2/MICROS~3.0/VC
--with-asm-home=C:/PROGRA~2/MICROS~3.0/VC/bin --with-dmake-url=
http://sourceforge.net/projects/oooextras.mirror/files/dmake-4.12.tar.bz2
--with-epm-url=
https://sourceforge.net/projects/oooextras.mirror/files/epm-3.7.tar.gz
--disable-pch --disable-atl --disable-activex --disable-nss-module
--disable-directx --without-junit

## - ##
## Platform. ##
## - ##

hostname = Steven-PC
uname -m = i686
uname -r = 2.6.1(0.305/5/3)
uname -s = CYGWIN_NT-6.1-WOW
uname -v = 2016-12-16 11:50

/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: /usr/local/bin
PATH: /usr/bin
PATH: /cygdrive/c/ProgramData/Oracle/Java/javapath
PATH: /cygdrive/c/Program Files/iis express/PHP/v7.0
PATH: /cygdrive/c/Windows/system32
PATH: /cygdrive/c/Windows
PATH: /cygdrive/c/Windows/System32/Wbem
PATH: /cygdrive/c/Program Files (x86)/Windows Kits/8.1/Windows Performance
Toolkit
PATH: /cygdrive/c/Program Files/Microsoft SQL Server/110/Tools/Binn
PATH: /cygdrive/c/Program Files (x86)/Microsoft SQL Server/100/Tools/Binn
PATH: /cygdrive/c/Program Files/Microsoft SQL Server/100/Tools/Binn
PATH: /cygdrive/c/Program Files/Microsoft SQL Server/100/DTS/Binn
PATH: /cygdrive/c/Program Files/Java/jdk1.8.0_11/bin
PATH: /cygdrive/c/work/android-ndk-r10
PATH: /cygdrive/c/cygwin64/bin
PATH: /cygdrive/c/Program Files (x86)/Visual Leak Detector/bin/Win32
PATH: /cygdrive/c/Program Files (x86)/Visual Leak Detector/bin/Win64
PATH: /cygdrive/c/Program Files/TortoiseSVN/bin
PATH: /cygdrive/c/PROGRA~1/DISKEE~1/DISKEE~1
PATH: /cygdrive/c/work/GOOGLETEST/depot_tools
PATH: /cygdrive/c/Program Files/Microsoft SQL Server/120/Tools/Binn
PATH: /cygdrive/c/Qt/5.4/msvc2010_opengl/include
PATH: /cygdrive/c/opencv/build/x86/vc10/bin
PATH: /cygdrive/c/GoogleTest/FXQAImage/Debug
PATH: /cygdrive/c/work/GOOGLETEST/src/out/Debug
PATH: /cygdrive/c/Steventest/pdfium/build/Debug
PATH: /cygdrive/c/program files (x86)/skype/Phone
PATH: /cygdrive/c/Program Files/Microsoft/Web Platform Installer
PATH: /cygdrive/c/Pro
PATH: /cygdrive/c/Windows/System32/WindowsPowerShell/v1.0
PATH: /cygdrive/c/Program Files (x86)/Delphi7SE/bin
PATH: /cygdrive/c/Program Files (x86)/Delphi7SE/Projects/BPL
PATH: /cygdrive/c/Program Files (x86)/Microsoft Visual
Studio/Common/Tools/WinNT
PATH: /cygdrive/c/Program Files (x86)/Microsoft Visual
Studio/Common/MSDev98/Bin
PATH: /cygdrive/c/Program Files (x86)/Microsoft Visual Studio/Common/Tools
PATH: /cygdrive/c/Program Files (x86)/Microsoft Visual Studio/VC98/bin
PATH: /cygdrive/c/Program Files (x86)/Java/jdk1.8.0_121/bin
PATH: /cygdrive/c/apacheAnt/bin
PATH: /cygdrive/c/Users/Steven/AppData/Local/atom/bin


## --- ##
## Core tests. ##
## --- ##

configure:5152: checking whether configure is up-to-date
configure:5159: result: yes
configure:5186: checking for grep that handles long lines and -e
configure:5244: result: /usr/bin/grep
configure:5249: checking for egrep
configure:5311: result: /usr/bin/grep -E
configure:5320: checking for gawk
configure:5350: result: no
configure:5320: checking for mawk
configure:5350: result: no
configure:5320: checking for nawk
configure:5350: result: no
configure:5320: checking for awk
configure:5336: found /usr/bin/awk
configure:5347: result: awk
configure:5360: checking for awk
configure:5378: found /usr/bin/awk
configure:5390: result: /usr/bin/awk
configure:5406: checking for sed
configure:5424: found /usr/bin/sed
configure:5436: result: /usr/bin/sed
configure:5451: checking for solenv environment
configure:5455: result: default
configure:5482: checking for custom pack.lst
configure:5496: result: no
configure:5536: checking build system type
configure:5550: result: i686-pc-cygwin
configure:5570: checking host system type
configure:5583: result: i686-pc-cygwin
configure:5603: checking target system type
configure:5616: result: i686-pc-cygwin
configure:5651: checking Cygwin version
configure:5654: result: 2.6.1(0.305/5/3)
configure:5924: checking for pkg-config
configure:5957: result: no
configure:5992: checking whether to enable crashdump feature
configure:6001: result: no

Re: AOO debugging revamp

[Damjan Jovanovic]

Thank you. I've now committed the patch with some improvements in r1781019.

On Tue, Jan 31, 2017 at 6:55 AM, Patricia Shanahan  wrote:

> I did some more testing, and it seems to be a Visual Studio weirdness. It
> was showing my breakpoint as "no symbols loaded". However, when I ran a
> test case that I know goes through that breakpoint, it turned red and
> worked.
>
>
> On 1/30/2017 8:28 PM, Damjan Jovanovic wrote:
>
>> That's unusual. It should either fix it for all gbuild modules, or none of
>> them. In the build log for main/sw, is "-DEBUG" passed to the linker?
>> Please send it through if unsure.
>>
>> I haven't had a chance to test it myself as debugging is currently broken
>> with precompiled headers, and my Windows VM doesn't have disk space for a
>> debug build anyway...
>>
>> On Tue, Jan 31, 2017 at 6:24 AM, Patricia Shanahan  wrote:
>>
>> Applying the patch fixed the vcl case, but not the one I really care
>>> about, main/sw
>>>
>>>
>>> On 1/29/2017 6:51 PM, Patricia Shanahan wrote:
>>>
>>>

 On 1/29/2017 5:59 PM, Damjan Jovanovic wrote:

 I am trying a Windows rebuild now. In the meanwhile, what debugger are
> you using? Can you debug any other modules, eg. vcl which uses gbuild,
> or sal which uses dmake?
>
>
 I'm using Visual Studio Community 2013.

 sal: Yes, at least the breakpoint stays red in the breakpoints display.
 vcl: No, "No symbols have been loaded for this document".



 It's possible that Windows also needs gb_LinkTarget_LDFLAGS += -DEBUG to
> enable debugging, as per the "ifeq ($(gb_DEBUGLEVEL),2)" part of
> solenv/gbuild/platform/windows.mk . If so, please
> try
> the attached patch which should do that.
>
>
 I'll try it.




>
> On Sun, Jan 29, 2017 at 10:34 PM, Patricia Shanahan  > wrote:
>
> On 1/25/2017 9:35 AM, Damjan Jovanovic wrote:
>
> Hi
>
> For a while I've noticed how gbuild modules don't have debug
> symbols unless
> built with the maximum debug level ("./configure
> --enable-debug"
> globally
> or "build debug=true" per module) which also produces oceans
> of log
> messages we usually don't want.
>
> In r1780246, I've finally changed debugging in gbuild to match
> how dmake
> works: --enable-symbols and --enable-crashdump now also add
> debug symbols
> to gbuild modules like they do to dmake modules, and the
> --enable-symbols=small option is also implemented for GCC and
> Clang (sorry
> Windows developers, MSVC doesn't seem to have it). The only
> extra benefit
> of --enable-debug on top of this now, is that it disables
> compiler
> optimizations - should we disable them for --enable-symbols
> too?
>
> In r1780248 I've also made Java's .class files get full
> debugging info
> whenever C++ does.
>
> This should vastly improve running AOO under a debugger, as we
> get nice
> line numbers and variable names for absolutely everything :-).
>
>
> I compiled with the attached configure parameters, and breakpoints
> are not working in main/sw/source/ui/app/docsh.cx
> x, "No symbols have been loaded for this
> document".
> What should I change?
>
>
> 
> -
> 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
>>>
>>>
>>>
>>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

Re: AOO debugging revamp

[Patricia Shanahan]

I did some more testing, and it seems to be a Visual Studio weirdness. 
It was showing my breakpoint as "no symbols loaded". However, when I ran 
a test case that I know goes through that breakpoint, it turned red and 
worked.


On 1/30/2017 8:28 PM, Damjan Jovanovic wrote:

That's unusual. It should either fix it for all gbuild modules, or none of
them. In the build log for main/sw, is "-DEBUG" passed to the linker?
Please send it through if unsure.

I haven't had a chance to test it myself as debugging is currently broken
with precompiled headers, and my Windows VM doesn't have disk space for a
debug build anyway...

On Tue, Jan 31, 2017 at 6:24 AM, Patricia Shanahan  wrote:


Applying the patch fixed the vcl case, but not the one I really care
about, main/sw


On 1/29/2017 6:51 PM, Patricia Shanahan wrote:




On 1/29/2017 5:59 PM, Damjan Jovanovic wrote:


I am trying a Windows rebuild now. In the meanwhile, what debugger are
you using? Can you debug any other modules, eg. vcl which uses gbuild,
or sal which uses dmake?



I'm using Visual Studio Community 2013.

sal: Yes, at least the breakpoint stays red in the breakpoints display.
vcl: No, "No symbols have been loaded for this document".




It's possible that Windows also needs gb_LinkTarget_LDFLAGS += -DEBUG to
enable debugging, as per the "ifeq ($(gb_DEBUGLEVEL),2)" part of
solenv/gbuild/platform/windows.mk . If so, please try
the attached patch which should do that.



I'll try it.






On Sun, Jan 29, 2017 at 10:34 PM, Patricia Shanahan > wrote:

On 1/25/2017 9:35 AM, Damjan Jovanovic wrote:

Hi

For a while I've noticed how gbuild modules don't have debug
symbols unless
built with the maximum debug level ("./configure --enable-debug"
globally
or "build debug=true" per module) which also produces oceans
of log
messages we usually don't want.

In r1780246, I've finally changed debugging in gbuild to match
how dmake
works: --enable-symbols and --enable-crashdump now also add
debug symbols
to gbuild modules like they do to dmake modules, and the
--enable-symbols=small option is also implemented for GCC and
Clang (sorry
Windows developers, MSVC doesn't seem to have it). The only
extra benefit
of --enable-debug on top of this now, is that it disables
compiler
optimizations - should we disable them for --enable-symbols too?

In r1780248 I've also made Java's .class files get full
debugging info
whenever C++ does.

This should vastly improve running AOO under a debugger, as we
get nice
line numbers and variable names for absolutely everything :-).


I compiled with the attached configure parameters, and breakpoints
are not working in main/sw/source/ui/app/docsh.cx
x, "No symbols have been loaded for this document".
What should I change?



-
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






-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: AOO debugging revamp

[Damjan Jovanovic]

That's unusual. It should either fix it for all gbuild modules, or none of
them. In the build log for main/sw, is "-DEBUG" passed to the linker?
Please send it through if unsure.

I haven't had a chance to test it myself as debugging is currently broken
with precompiled headers, and my Windows VM doesn't have disk space for a
debug build anyway...

On Tue, Jan 31, 2017 at 6:24 AM, Patricia Shanahan  wrote:

> Applying the patch fixed the vcl case, but not the one I really care
> about, main/sw
>
>
> On 1/29/2017 6:51 PM, Patricia Shanahan wrote:
>
>>
>>
>> On 1/29/2017 5:59 PM, Damjan Jovanovic wrote:
>>
>>> I am trying a Windows rebuild now. In the meanwhile, what debugger are
>>> you using? Can you debug any other modules, eg. vcl which uses gbuild,
>>> or sal which uses dmake?
>>>
>>
>> I'm using Visual Studio Community 2013.
>>
>> sal: Yes, at least the breakpoint stays red in the breakpoints display.
>> vcl: No, "No symbols have been loaded for this document".
>>
>>
>>
>>> It's possible that Windows also needs gb_LinkTarget_LDFLAGS += -DEBUG to
>>> enable debugging, as per the "ifeq ($(gb_DEBUGLEVEL),2)" part of
>>> solenv/gbuild/platform/windows.mk . If so, please try
>>> the attached patch which should do that.
>>>
>>
>> I'll try it.
>>
>>
>>
>>>
>>>
>>> On Sun, Jan 29, 2017 at 10:34 PM, Patricia Shanahan >> > wrote:
>>>
>>> On 1/25/2017 9:35 AM, Damjan Jovanovic wrote:
>>>
>>> Hi
>>>
>>> For a while I've noticed how gbuild modules don't have debug
>>> symbols unless
>>> built with the maximum debug level ("./configure --enable-debug"
>>> globally
>>> or "build debug=true" per module) which also produces oceans
>>> of log
>>> messages we usually don't want.
>>>
>>> In r1780246, I've finally changed debugging in gbuild to match
>>> how dmake
>>> works: --enable-symbols and --enable-crashdump now also add
>>> debug symbols
>>> to gbuild modules like they do to dmake modules, and the
>>> --enable-symbols=small option is also implemented for GCC and
>>> Clang (sorry
>>> Windows developers, MSVC doesn't seem to have it). The only
>>> extra benefit
>>> of --enable-debug on top of this now, is that it disables
>>> compiler
>>> optimizations - should we disable them for --enable-symbols too?
>>>
>>> In r1780248 I've also made Java's .class files get full
>>> debugging info
>>> whenever C++ does.
>>>
>>> This should vastly improve running AOO under a debugger, as we
>>> get nice
>>> line numbers and variable names for absolutely everything :-).
>>>
>>>
>>> I compiled with the attached configure parameters, and breakpoints
>>> are not working in main/sw/source/ui/app/docsh.cx
>>> x, "No symbols have been loaded for this document".
>>> What should I change?
>>>
>>>
>>> 
>>> -
>>> 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
>
>

Re: AOO debugging revamp

[Patricia Shanahan]

Applying the patch fixed the vcl case, but not the one I really care 
about, main/sw


On 1/29/2017 6:51 PM, Patricia Shanahan wrote:



On 1/29/2017 5:59 PM, Damjan Jovanovic wrote:

I am trying a Windows rebuild now. In the meanwhile, what debugger are
you using? Can you debug any other modules, eg. vcl which uses gbuild,
or sal which uses dmake?


I'm using Visual Studio Community 2013.

sal: Yes, at least the breakpoint stays red in the breakpoints display.
vcl: No, "No symbols have been loaded for this document".




It's possible that Windows also needs gb_LinkTarget_LDFLAGS += -DEBUG to
enable debugging, as per the "ifeq ($(gb_DEBUGLEVEL),2)" part of
solenv/gbuild/platform/windows.mk . If so, please try
the attached patch which should do that.


I'll try it.






On Sun, Jan 29, 2017 at 10:34 PM, Patricia Shanahan > wrote:

On 1/25/2017 9:35 AM, Damjan Jovanovic wrote:

Hi

For a while I've noticed how gbuild modules don't have debug
symbols unless
built with the maximum debug level ("./configure --enable-debug"
globally
or "build debug=true" per module) which also produces oceans
of log
messages we usually don't want.

In r1780246, I've finally changed debugging in gbuild to match
how dmake
works: --enable-symbols and --enable-crashdump now also add
debug symbols
to gbuild modules like they do to dmake modules, and the
--enable-symbols=small option is also implemented for GCC and
Clang (sorry
Windows developers, MSVC doesn't seem to have it). The only
extra benefit
of --enable-debug on top of this now, is that it disables
compiler
optimizations - should we disable them for --enable-symbols too?

In r1780248 I've also made Java's .class files get full
debugging info
whenever C++ does.

This should vastly improve running AOO under a debugger, as we
get nice
line numbers and variable names for absolutely everything :-).


I compiled with the attached configure parameters, and breakpoints
are not working in main/sw/source/ui/app/docsh.cx
x, "No symbols have been loaded for this document".
What should I change?


-
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

Re: Build --all errors on libxml2?

[Damjan Jovanovic]

I don't see any attachments.

On Tue, Jan 31, 2017 at 5:04 AM, Hong  wrote:

> Hi Damjan,
>
> I attached config.log. Can you please take a look? Thanks.
>
> On Thu, Jan 26, 2017 at 12:02 PM, Damjan Jovanovic 
> wrote:
>
>> I suspect a wrong version of MSVC. Attach your config.log.
>>
>> On Thu, Jan 26, 2017 at 8:56 PM, Hong  wrote:
>>
>> > Hi,
>> >
>> > I encountered a bunch of link errors of missing symbol
>> ___security_cookie.
>> >
>> > Does anybody know what could be the problem?
>> >
>> > link.exe /nologo /VERSION:2.9 /LIBPATH:bin.msvc /LIBPATH:.\lib /DLL
>> >  /IMPLIB:bin.msvc\libxml2.lib /OUT:bin.msvc\libxml2.dll int.msvc\buf.obj
>> > int.msvc\c14n.obj int.msvc\catalog.obj int.msvc\chvalid.obj
>> > int.msvc\debugXML.obj int.msvc\dict.obj int.msvc\DOCBparser.obj
>> > int.msvc\encoding.obj int.msvc\entities.obj int.msvc\error.obj
>> > int.msvc\globals.obj int.msvc\hash.obj int.msvc\HTMLparser.obj
>> > int.msvc\HTMLtree.obj int.msvc\legacy.obj int.msvc\list.obj
>> > int.msvc\nanoftp.obj int.msvc\nanohttp.obj int.msvc\parser.obj
>> > int.msvc\parserInternals.obj int.msvc\pattern.obj int.msvc\relaxng.obj
>> > int.msvc\SAX2.obj int.msvc\SAX.obj int.msvc\schematron.obj
>> > int.msvc\threads.obj int.msvc\tree.obj int.msvc\uri.obj
>> int.msvc\valid.obj
>> > int.msvc\xinclude.obj int.msvc\xlink.obj int.msvc\xmlIO.obj
>> > int.msvc\xmlmemory.obj int.msvc\xmlreader.obj int.msvc\xmlregexp.obj
>> > int.msvc\xmlmodule.obj int.msvc\xmlsave.obj int.msvc\xmlschemas.obj
>> > int.msvc\xmlschemastypes.obj int.msvc\xmlunicode.obj
>> int.msvc\xmlwriter.obj
>> > int.msvc\xpath.obj int.msvc\xpointer.obj int.msvc\xmlstring.obj
>> >  wsock32.lib ws2_32.lib kernel32.lib
>> >Creating library bin.msvc\libxml2.lib and object bin.msvc\libxml2.exp
>> > xmlsave.obj : error LNK2019: unresolved external symbol
>> ___security_cookie
>> > referenced in function _xhtmlNodeListDumpOutput
>> > xmlschemas.obj : error LNK2001: unresolved external symbol
>> > ___security_cookie
>> > xmlschemastypes.obj : error LNK2001: unresolved external symbol
>> > ___security_cookie
>> > xpath.obj : error LNK2001: unresolved external symbol ___security_cookie
>> > valid.obj : error LNK2001: unresolved external symbol ___security_cookie
>> > xlink.obj : error LNK2001: unresolved external symbol ___security_cookie
>> > xmlIO.obj : error LNK2001: unresolved external symbol ___security_cookie
>> > xmlregexp.obj : error LNK2001: unresolved external symbol
>> > ___security_cookie
>> > SAX2.obj : error LNK2001: unresolved external symbol ___security_cookie
>> > schematron.obj : error LNK2001: unresolved external symbol
>> > ___security_cookie
>> > tree.obj : error LNK2001: unresolved external symbol ___security_cookie
>> > uri.obj : error LNK2001: unresolved external symbol ___security_cookie
>> > nanohttp.obj : error LNK2001: unresolved external symbol
>> ___security_cookie
>> > parser.obj : error LNK2001: unresolved external symbol
>> ___security_cookie
>> > parserInternals.obj : error LNK2001: unresolved external symbol
>> > ___security_cookie
>> > relaxng.obj : error LNK2001: unresolved external symbol
>> ___security_cookie
>> > error.obj : error LNK2001: unresolved external symbol ___security_cookie
>> > HTMLparser.obj : error LNK2001: unresolved external symbol
>> > ___security_cookie
>> > HTMLtree.obj : error LNK2001: unresolved external symbol
>> ___security_cookie
>> > nanoftp.obj : error LNK2001: unresolved external symbol
>> ___security_cookie
>> > catalog.obj : error LNK2001: unresolved external symbol
>> ___security_cookie
>> > debugXML.obj : error LNK2001: unresolved external symbol
>> ___security_cookie
>> > encoding.obj : error LNK2001: unresolved external symbol
>> ___security_cookie
>> > entities.obj : error LNK2001: unresolved external symbol
>> ___security_cookie
>> > xmlsave.obj : error LNK2001: unresolved external symbol
>> > @__security_check_cookie@4
>> > xmlschemas.obj : error LNK2019: unresolved external symbol
>> > @__security_check_cookie@4 referenced in function
>> > _xmlSchemaFormatNodeForError
>> > xmlschemastypes.obj : error LNK2001: unresolved external symbol
>> > @__security_check_cookie@4
>> > xpath.obj : error LNK2001: unresolved external symbol
>> > @__security_check_cookie@4
>> > valid.obj : error LNK2001: unresolved external symbol
>> > @__security_check_cookie@4
>> > xlink.obj : error LNK2001: unresolved external symbol
>> > @__security_check_cookie@4
>> > xmlIO.obj : error LNK2001: unresolved external symbol
>> > @__security_check_cookie@4
>> > xmlregexp.obj : error LNK2001: unresolved external symbol
>> > @__security_check_cookie@4
>> > SAX2.obj : error LNK2001: unresolved external symbol
>> > @__security_check_cookie@4
>> > schematron.obj : error LNK2001: unresolved external symbol
>> > @__security_check_cookie@4
>> > tree.obj : error LNK2001: unresolved external symbol
>> > @__security_check_cookie@4
>> > uri.obj : error LNK2001: unresolved external symbol

Re: Build --all errors on libxml2?

[Hong]

Hi Damjan,

I attached config.log. Can you please take a look? Thanks.

On Thu, Jan 26, 2017 at 12:02 PM, Damjan Jovanovic 
wrote:

> I suspect a wrong version of MSVC. Attach your config.log.
>
> On Thu, Jan 26, 2017 at 8:56 PM, Hong  wrote:
>
> > Hi,
> >
> > I encountered a bunch of link errors of missing symbol
> ___security_cookie.
> >
> > Does anybody know what could be the problem?
> >
> > link.exe /nologo /VERSION:2.9 /LIBPATH:bin.msvc /LIBPATH:.\lib /DLL
> >  /IMPLIB:bin.msvc\libxml2.lib /OUT:bin.msvc\libxml2.dll int.msvc\buf.obj
> > int.msvc\c14n.obj int.msvc\catalog.obj int.msvc\chvalid.obj
> > int.msvc\debugXML.obj int.msvc\dict.obj int.msvc\DOCBparser.obj
> > int.msvc\encoding.obj int.msvc\entities.obj int.msvc\error.obj
> > int.msvc\globals.obj int.msvc\hash.obj int.msvc\HTMLparser.obj
> > int.msvc\HTMLtree.obj int.msvc\legacy.obj int.msvc\list.obj
> > int.msvc\nanoftp.obj int.msvc\nanohttp.obj int.msvc\parser.obj
> > int.msvc\parserInternals.obj int.msvc\pattern.obj int.msvc\relaxng.obj
> > int.msvc\SAX2.obj int.msvc\SAX.obj int.msvc\schematron.obj
> > int.msvc\threads.obj int.msvc\tree.obj int.msvc\uri.obj
> int.msvc\valid.obj
> > int.msvc\xinclude.obj int.msvc\xlink.obj int.msvc\xmlIO.obj
> > int.msvc\xmlmemory.obj int.msvc\xmlreader.obj int.msvc\xmlregexp.obj
> > int.msvc\xmlmodule.obj int.msvc\xmlsave.obj int.msvc\xmlschemas.obj
> > int.msvc\xmlschemastypes.obj int.msvc\xmlunicode.obj
> int.msvc\xmlwriter.obj
> > int.msvc\xpath.obj int.msvc\xpointer.obj int.msvc\xmlstring.obj
> >  wsock32.lib ws2_32.lib kernel32.lib
> >Creating library bin.msvc\libxml2.lib and object bin.msvc\libxml2.exp
> > xmlsave.obj : error LNK2019: unresolved external symbol
> ___security_cookie
> > referenced in function _xhtmlNodeListDumpOutput
> > xmlschemas.obj : error LNK2001: unresolved external symbol
> > ___security_cookie
> > xmlschemastypes.obj : error LNK2001: unresolved external symbol
> > ___security_cookie
> > xpath.obj : error LNK2001: unresolved external symbol ___security_cookie
> > valid.obj : error LNK2001: unresolved external symbol ___security_cookie
> > xlink.obj : error LNK2001: unresolved external symbol ___security_cookie
> > xmlIO.obj : error LNK2001: unresolved external symbol ___security_cookie
> > xmlregexp.obj : error LNK2001: unresolved external symbol
> > ___security_cookie
> > SAX2.obj : error LNK2001: unresolved external symbol ___security_cookie
> > schematron.obj : error LNK2001: unresolved external symbol
> > ___security_cookie
> > tree.obj : error LNK2001: unresolved external symbol ___security_cookie
> > uri.obj : error LNK2001: unresolved external symbol ___security_cookie
> > nanohttp.obj : error LNK2001: unresolved external symbol
> ___security_cookie
> > parser.obj : error LNK2001: unresolved external symbol ___security_cookie
> > parserInternals.obj : error LNK2001: unresolved external symbol
> > ___security_cookie
> > relaxng.obj : error LNK2001: unresolved external symbol
> ___security_cookie
> > error.obj : error LNK2001: unresolved external symbol ___security_cookie
> > HTMLparser.obj : error LNK2001: unresolved external symbol
> > ___security_cookie
> > HTMLtree.obj : error LNK2001: unresolved external symbol
> ___security_cookie
> > nanoftp.obj : error LNK2001: unresolved external symbol
> ___security_cookie
> > catalog.obj : error LNK2001: unresolved external symbol
> ___security_cookie
> > debugXML.obj : error LNK2001: unresolved external symbol
> ___security_cookie
> > encoding.obj : error LNK2001: unresolved external symbol
> ___security_cookie
> > entities.obj : error LNK2001: unresolved external symbol
> ___security_cookie
> > xmlsave.obj : error LNK2001: unresolved external symbol
> > @__security_check_cookie@4
> > xmlschemas.obj : error LNK2019: unresolved external symbol
> > @__security_check_cookie@4 referenced in function
> > _xmlSchemaFormatNodeForError
> > xmlschemastypes.obj : error LNK2001: unresolved external symbol
> > @__security_check_cookie@4
> > xpath.obj : error LNK2001: unresolved external symbol
> > @__security_check_cookie@4
> > valid.obj : error LNK2001: unresolved external symbol
> > @__security_check_cookie@4
> > xlink.obj : error LNK2001: unresolved external symbol
> > @__security_check_cookie@4
> > xmlIO.obj : error LNK2001: unresolved external symbol
> > @__security_check_cookie@4
> > xmlregexp.obj : error LNK2001: unresolved external symbol
> > @__security_check_cookie@4
> > SAX2.obj : error LNK2001: unresolved external symbol
> > @__security_check_cookie@4
> > schematron.obj : error LNK2001: unresolved external symbol
> > @__security_check_cookie@4
> > tree.obj : error LNK2001: unresolved external symbol
> > @__security_check_cookie@4
> > uri.obj : error LNK2001: unresolved external symbol
> > @__security_check_cookie@4
> > nanohttp.obj : error LNK2001: unresolved external symbol
> > @__security_check_cookie@4
> > parser.obj : error LNK2001: unresolved external symbol
> > 

Re: Fwd: New Pootle Account

[Matthias Seidel]

Am 28.01.2017 um 12:10 schrieb Andrea Pescetti:
> On 27/01/2017 Matthias Seidel wrote:
>> Has this been taken care of?
>
> Not yet (not by me, at least).
>
>> We have a growing number of volunteers on l10n@ waiting for a Pootle
>> account or even an answer...
>
> I'll take a look at the queue this weekend.
>
>> This must be improved
>
> Oh yes, and actually if you have some time for helping I can give you
> the correct privileges for it (pending lazy consensus on this list);
> technically it's very easy (you just login to the web application and
> you create the user); feel free to reach out to me offlist if you are
> interested in more details.

That would be helpful.
I will write you a PM.

And I hope we meet in Brussels!?

Regards, Matthias

>
> Regards,
>   Andrea.
>
> -
> 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: Windows PCH + debug regression in r1758061 and r1758092

[Don Lewis]

On 30 Jan, Damjan Jovanovic wrote:
> Hi Don / others
> 
> As of r1758061 and/or 1758092, the 27/28 August 2016 patches that fixed a
> major performance regression on Windows with precompiled headers [thank you
> so much for that by the way :-)], building with debugging enabled broke.
> 
> In all versions after those commits, build any gbuild module that uses
> precompiled headers (eg. main/formula) with "DEBUG=t make" from the module
> directory (or use the --enable-debug configure switch for the whole build),
> and it will break: the -Fd option that gets passed to the compiler lacks a
> subsequent path. It appears that the $(PDBFILE) variable goes missing...
> 
> Can you please help?

The gbuild stuff is pretty inscrutable ...

After looking at the r1758092 changes to
main/solenv/gbuild/LinkTarget.mk, I wonder if the two instances of this
in solenv/gbuild/platform/windows.mk:

$(call gb_LinkTarget_get_target,$(2)) \
$(call gb_LinkTarget_get_headers_target,$(2)) : PDBFILE = $(call 
gb_LinkTarget_get_pdbfile,$(2))

should be:

$(call gb_LinkTarget_get_headers_target,$(2)) \
$(call gb_LinkTarget_get_target,$(2)) : PDBFILE = $(call 
gb_LinkTarget_get_pdbfile,$(2))


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

option development suggestion

[Valery Sivakov]

Dear Friends,

thanks a lot for you brilliant products.
Nevertheless I  ask you to think about involving speech recognition tool in
OO writer.
I have learned, when one is writing his brain operates in focus mode. That
makes to type on keyboard and keep idea quite a difficult thing. So speech
recognition tool could significantly assist to write down ideas and convert
notebook or PC into typewriter secretary. I believe all necessary
technology already exist, but are not brought together in a right place. OO
writer is a right place. Entering big text via typing is wasting a time,
especially when most of the people use mobile phones. Lett do old thinks in
a mordern style.

Best regards,
Valery

Windows PCH + debug regression in r1758061 and r1758092

[Damjan Jovanovic]

Hi Don / others

As of r1758061 and/or 1758092, the 27/28 August 2016 patches that fixed a
major performance regression on Windows with precompiled headers [thank you
so much for that by the way :-)], building with debugging enabled broke.

In all versions after those commits, build any gbuild module that uses
precompiled headers (eg. main/formula) with "DEBUG=t make" from the module
directory (or use the --enable-debug configure switch for the whole build),
and it will break: the -Fd option that gets passed to the compiler lacks a
subsequent path. It appears that the $(PDBFILE) variable goes missing...

Can you please help?

Thank you
Damjan