[Libreoffice-bugs] [Bug 97712] New: Build failure with clang++/libc++ on Linux x86_64

https://bugs.documentfoundation.org/show_bug.cgi?id=97712 Bug ID: 97712 Summary: Build failure with clang++/libc++ on Linux x86_64 Product: LibreOffice Version: 5.1.0.3 release Hardware: x86-64 (AMD64) OS: Linux (All

[Libreoffice-bugs] [Bug 95450] libreoffice-5.0.0.5 build failure on ppc64

https://bugs.documentfoundation.org/show_bug.cgi?id=95450 David Tardon changed: What|Removed |Added Status|NEW |RESOLVED

[Libreoffice-bugs] [Bug 95450] libreoffice-5.0.0.5 build failure on ppc64

https://bugs.documentfoundation.org/show_bug.cgi?id=95450 David Tardon changed: What|Removed |Added Status|UNCONFIRMED |NEW

Re: Build Failure on Ubuntu 15.10 after upgradation from 15.04

Hi Varun, On Sat, Dec 5, 2015 at 12:49 AM, Varun Dhall wrote: I am getting some errors while building the latest master on my machine. Actually I have recently upgraded from Ubuntu 15.04 to 15.10 before upgradation everything was working great (7-10 days old

Build Failure on Ubuntu 15.10 after upgradation from 15.04

hello everyone I am getting some errors while building the latest master on my machine. Actually I have recently upgraded from Ubuntu 15.04 to 15.10 before upgradation everything was working great (7-10 days old master + 15.04) with no errors. I have checked for all the dependencies and

[Libreoffice-bugs] [Bug 95450] New: libreoffice-5.0.0.5 build failure on ppc64

https://bugs.documentfoundation.org/show_bug.cgi?id=95450 Bug ID: 95450 Summary: libreoffice-5.0.0.5 build failure on ppc64 Product: cppunit Version: unspecified Hardware: PowerPC OS: Linux (All) Status

[Libreoffice-bugs] [Bug 75731] Build Failure: secutil.c:(.text+0xfdb): undefined reference to `SECITEM_ReallocItemV2'

https://bugs.documentfoundation.org/show_bug.cgi?id=75731 Adolfo Jayme f...@libreoffice.org changed: What|Removed |Added Whiteboard|NeedsDevEval|needsDevEval

Re: What to do after build failure on Gerrit submission?

On 2015-03-18 03:01 PM, Piet van Oostrum wrote: About a week ago I submitted a patch to gerrit (https://gerrit.libreoffice.org/#/c/14841/). However, the build failed on Windows, due to a unit test failing. I looked in the log file and it seems to me that the unit test failure is not related

What to do after build failure on Gerrit submission?

About a week ago I submitted a patch to gerrit (https://gerrit.libreoffice.org/#/c/14841/). However, the build failed on Windows, due to a unit test failing. I looked in the log file and it seems to me that the unit test failure is not related to my patch. So what should I do next? Shall I

[Libreoffice-bugs] [Bug 78174] Build failure: undefined reference to `non-virtual thunk to WindowListenerMultiplexer::acquire()' etc. in svx/source/fmcomp/fmgridif.cxx

https://bugs.documentfoundation.org/show_bug.cgi?id=78174 Michael Stahl mst...@redhat.com changed: What|Removed |Added Status|NEW |RESOLVED

[Libreoffice-bugs] [Bug 78174] Build failure: undefined reference to `non-virtual thunk to WindowListenerMultiplexer::acquire()' etc. in svx/source/fmcomp/fmgridif.cxx

CC||sberg...@redhat.com Resolution|INVALID |--- Summary|Build failure: undefined|Build failure: undefined |reference to acquire|reference to `non-virtual

[Libreoffice-bugs] [Bug 78174] Build failure: undefined reference to acquire

https://bugs.documentfoundation.org/show_bug.cgi?id=78174 timo.te...@iki.fi changed: What|Removed |Added CC||timo.te...@iki.fi --- Comment

[Libreoffice-bugs] [Bug 78174] Build failure: undefined reference to acquire

https://bugs.documentfoundation.org/show_bug.cgi?id=78174 --- Comment #9 from Jürg Billeter j...@bitron.ch --- (In reply to Michael Stahl from comment #7) commit bb182b47ca7362b05c03d583d3547643d9a99562 Author: Michael Stahl mst...@redhat.com AuthorDate: Thu Aug 7 21:18:56 2014 +0200

Build for Google Docs (was: Re: Build failure in 4.4 branch with --enable-ext-google-docs on Xubuntu 14.04 amd64: undefined reference to symbol 'dlclose@@GLIBC_2.2.5')

Miklos wrote: On Sun, Jan 25, 2015 at 04:27:12PM +, David Gerard dgerard at gmail.com wrote: I want to write a blog post saying how I did this - before I do so, will there be a problem putting it up with that secret (which is presumably the one in every TDF build)? Should I use another

[Libreoffice-bugs] [Bug 78174] Build failure: undefined reference to acquire

https://bugs.documentfoundation.org/show_bug.cgi?id=78174 --- Comment #8 from Björn Michaelsen bjoern.michael...@canonical.com --- (In reply to Michael Stahl from comment #7) commit bb182b47ca7362b05c03d583d3547643d9a99562 Thanks for the hint. could backport it to 4.3 if somebody says this

[Libreoffice-bugs] [Bug 78174] Build failure: undefined reference to acquire

https://bugs.documentfoundation.org/show_bug.cgi?id=78174 Michael Stahl mst...@redhat.com changed: What|Removed |Added CC|

Re: Build failure in 4.4 branch with --enable-ext-google-docs on Xubuntu 14.04 amd64: undefined reference to symbol 'dlclose@@GLIBC_2.2.5'

Le 26/01/2015 10:49, Miklos Vajna a écrit : Hi Miklos, https://wiki.documentfoundation.org/Development/ReleaseBuilds documents that the gdrive flags are also used for TDF builds, so they are available for the general public. Thanks, but that page references x86 builds for MacOSX and not

Re: Build failure in 4.4 branch with --enable-ext-google-docs on Xubuntu 14.04 amd64: undefined reference to symbol 'dlclose@@GLIBC_2.2.5'

On Mon, Jan 26, 2015 at 05:16:14PM +0100, Alexander Thurgood alex.thurg...@gmail.com wrote: Thanks, but that page references x86 builds for MacOSX and not x86_64. Is it still applicable for our 64bit OSX releases ? Norbert, am I right that just a simple x86 - 64bit rename is needed at

Re: Build failure in 4.4 branch with --enable-ext-google-docs on Xubuntu 14.04 amd64: undefined reference to symbol 'dlclose@@GLIBC_2.2.5'

On Mon, Jan 26, 2015 at 11:22 AM, Miklos Vajna vmik...@collabora.co.uk wrote: On Mon, Jan 26, 2015 at 05:16:14PM +0100, Alexander Thurgood alex.thurg...@gmail.com wrote: Thanks, but that page references x86 builds for MacOSX and not x86_64. Is it still applicable for our 64bit OSX releases ?

Re: Build failure in 4.4 branch with --enable-ext-google-docs on Xubuntu 14.04 amd64: undefined reference to symbol 'dlclose@@GLIBC_2.2.5'

On Mon, Jan 26, 2015 at 10:16 AM, Alexander Thurgood alex.thurg...@gmail.com wrote: Le 26/01/2015 10:49, Miklos Vajna a écrit : Hi Miklos, https://wiki.documentfoundation.org/Development/ReleaseBuilds documents that the gdrive flags are also used for TDF builds, so they are available for

[Libreoffice-bugs] [Bug 78174] Build failure: undefined reference to acquire

https://bugs.documentfoundation.org/show_bug.cgi?id=78174 Luke lukebe...@hotmail.com changed: What|Removed |Added See Also|

[Libreoffice-bugs] [Bug 85365] Build failure: assertion failed in CppunitTest_writerperfect_stream with clang 3.5

https://bugs.documentfoundation.org/show_bug.cgi?id=85365 Luke lukebe...@hotmail.com changed: What|Removed |Added See Also|

Re: Build failure in 4.4 branch with --enable-ext-google-docs on Xubuntu 14.04 amd64: undefined reference to symbol 'dlclose@@GLIBC_2.2.5'

Hi Alex, https://wiki.documentfoundation.org/Development/ReleaseBuilds documents that the gdrive flags are also used for TDF builds, so they are available for the general public. Regards, Miklos signature.asc Description: Digital signature ___

Re: Build failure in 4.4 branch with --enable-ext-google-docs on Xubuntu 14.04 amd64: undefined reference to symbol 'dlclose@@GLIBC_2.2.5'

Hi David, On Sun, Jan 25, 2015 at 04:27:12PM +, David Gerard dger...@gmail.com wrote: I want to write a blog post saying how I did this - before I do so, will there be a problem putting it up with that secret (which is presumably the one in every TDF build)? Should I use another one? If

Re: Build failure in 4.4 branch with --enable-ext-google-docs on Xubuntu 14.04 amd64: undefined reference to symbol 'dlclose@@GLIBC_2.2.5'

Le 26/01/2015 10:04, Miklos Vajna a écrit : Hi Miklos, See here on how to obtain your own ID: https://developers.google.com/drive/web/about-auth So, just to further my understanding of the practicalities involved, if I want to use Google Docs/Drive CMIS integration on Mac, or Linux, for

Re: Build failure in 4.4 branch with --enable-ext-google-docs on Xubuntu 14.04 amd64: undefined reference to symbol 'dlclose@@GLIBC_2.2.5'

On 17 December 2014 at 12:10, Andras Timar tima...@gmail.com wrote: On Wed, Dec 17, 2014 at 12:35 PM, David Gerard dger...@gmail.com wrote: [making LO connect to Google Drive reliably] So I need to ... literally compile my credentials into LO? How do the Windows builds of 4.3 and 4.4beta1

Build failure in 4.4 branch with --enable-ext-google-docs on Xubuntu 14.04 amd64: undefined reference to symbol 'dlclose@@GLIBC_2.2.5'

(originally filed as Bug 87293, but I was redirected here) I am attempting to build with the Google Drive connection: ./autogen.sh --enable-ext-google-docs --with-gdrive-client-secret ; make This is happening consistently for me, building latest libreoffice-4-4 from git, if I use

Re: Build failure in 4.4 branch with --enable-ext-google-docs on Xubuntu 14.04 amd64: undefined reference to symbol 'dlclose@@GLIBC_2.2.5'

Hi, On Wed, Dec 17, 2014 at 10:26 AM, David Gerard dger...@gmail.com wrote: (originally filed as Bug 87293, but I was redirected here) I am attempting to build with the Google Drive connection: ./autogen.sh --enable-ext-google-docs --with-gdrive-client-secret ; make --enable-ext-google-docs

Re: Build failure in 4.4 branch with --enable-ext-google-docs on Xubuntu 14.04 amd64: undefined reference to symbol 'dlclose@@GLIBC_2.2.5'

Andras Timar wrote: --enable-ext-google-docs enables the obsolete Google Docs extension, you don't need that. For the built-in Google Drive support via CMIS you need --with-gdrive-client-secret and --with-google-drive-client-id. Of course, you need to register with Google first, and pass

Re: Build failure in 4.4 branch with --enable-ext-google-docs on Xubuntu 14.04 amd64: undefined reference to symbol 'dlclose@@GLIBC_2.2.5'

On Wed, Dec 17, 2014 at 12:35 PM, David Gerard dger...@gmail.com wrote: Andras Timar wrote: --enable-ext-google-docs enables the obsolete Google Docs extension, you don't need that. For the built-in Google Drive support via CMIS you need --with-gdrive-client-secret and

Re: Build failure in 4.4 branch with --enable-ext-google-docs on Xubuntu 14.04 amd64: undefined reference to symbol 'dlclose@@GLIBC_2.2.5'

On 17 December 2014 at 12:10, Andras Timar tima...@gmail.com wrote: On Wed, Dec 17, 2014 at 12:35 PM, David Gerard dger...@gmail.com wrote: So I need to ... literally compile my credentials into LO? How do the Windows builds of 4.3 and 4.4beta1 work? Are you saying they have someone's

Re: Build failure in 4.4 branch with --enable-ext-google-docs on Xubuntu 14.04 amd64: undefined reference to symbol 'dlclose@@GLIBC_2.2.5'

I'll need to back port that into the 4.4 branch soon - this is something distributions that enable --as-needed by default for ld will get. In other words, only Debian based distros will see it :-) Chris On Thursday, December 18, 2014, David Gerard dger...@gmail.com wrote: On 17 December 2014

[Libreoffice-bugs] [Bug 87293] Build failure libreoffice-4-4 branch: undefined reference to symbol 'dlclose@@GLIBC_2.2.5'

https://bugs.freedesktop.org/show_bug.cgi?id=87293 Beluga todven...@suomi24.fi changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Libreoffice-bugs] [Bug 87293] New: Build failure libreoffice-4-4 branch: undefined reference to symbol 'dlclose@@GLIBC_2.2.5'

https://bugs.freedesktop.org/show_bug.cgi?id=87293 Bug ID: 87293 Summary: Build failure libreoffice-4-4 branch: undefined reference to symbol 'dlclose@@GLIBC_2.2.5' Product: LibreOffice Version: 4.4.0.0.beta1 Hardware: x86

[Libreoffice-bugs] [Bug 87293] Build failure libreoffice-4-4 branch: undefined reference to symbol 'dlclose@@GLIBC_2.2.5'

https://bugs.freedesktop.org/show_bug.cgi?id=87293 --- Comment #1 from David Gerard dger...@gmail.com --- $ git status On branch libreoffice-4-4 Your branch is up-to-date with 'origin/libreoffice-4-4'. -- You are receiving this mail because: You are the assignee for the bug.

[Libreoffice-bugs] [Bug 85365] Build failure: assertion failed in CppunitTest_writerperfect_stream with clang 3.5

https://bugs.freedesktop.org/show_bug.cgi?id=85365 Michael Stahl mst...@redhat.com changed: What|Removed |Added CC||mst...@redhat.com

[Libreoffice-bugs] [Bug 85365] Build failure: assertion failed in CppunitTest_writerperfect_stream with clang 3.5

https://bugs.freedesktop.org/show_bug.cgi?id=85365 Luke lukebe...@hotmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Libreoffice-bugs] [Bug 85365] Build failure: assertion failed in CppunitTest_writerperfect_stream with clang 3.5

https://bugs.freedesktop.org/show_bug.cgi?id=85365 David Tardon dtar...@redhat.com changed: What|Removed |Added CC||dtar...@redhat.com ---

[Libreoffice-bugs] [Bug 78174] Build failure: undefined reference to acquire

https://bugs.freedesktop.org/show_bug.cgi?id=78174 --- Comment #6 from Luke lukebe...@hotmail.com --- Michael, This is an x86 issue, as indicated by the bug's hardware category and the first line of the bug description. Were you testing with a x86-64 build of Fedora? fails with Linux x86-32 with

[Libreoffice-bugs] [Bug 85365] New: Build failure: assertion failed in CppunitTest_writerperfect_stream with clang 3.5

https://bugs.freedesktop.org/show_bug.cgi?id=85365 Bug ID: 85365 Summary: Build failure: assertion failed in CppunitTest_writerperfect_stream with clang 3.5 Product: LibreOffice Version: 4.4.0.0.alpha0+ Master Hardware

[Libreoffice-bugs] [Bug 85365] Build failure: assertion failed in CppunitTest_writerperfect_stream with clang 3.5

https://bugs.freedesktop.org/show_bug.cgi?id=85365 Joel Madero jmadero@gmail.com changed: What|Removed |Added CC||jmadero@gmail.com

[Libreoffice-bugs] [Bug 78174] Build failure: undefined reference to acquire

https://bugs.freedesktop.org/show_bug.cgi?id=78174 --- Comment #5 from Michael Stahl mst...@redhat.com --- just for the record current master builds fine on Fedora 21: gcc (GCC) 4.9.1 20140930 (Red Hat 4.9.1-11) -- You are receiving this mail because: You are the assignee for the bug.

[Libreoffice-bugs] [Bug 78174] Build failure: undefined reference to acquire

https://bugs.freedesktop.org/show_bug.cgi?id=78174 --- Comment #4 from Luke lukebe...@hotmail.com --- This is still an issue with the default compiler for Ubuntu 14.10 gcc (Ubuntu 4.9.1-16ubuntu6) 4.9.1 Has this been reported to https://gcc.gnu.org/bugzilla/ ? -- You are receiving this mail

Re: build failure in [build SAX]

On 10/13/2014 06:29 AM, Terrence Enger wrote: on debian-wheezy 64-bit. This is my first time using parameters CXXFLAGS=-std=c++11 --disable-gstreamer --enable-gstreamer-0-10. By the way, you should not need to specify CXXFLAGS=-std=c++11, configure should figure out that it needs to use

build failure in [build SAX]

Greetings, I am trying to do a clean build of master commit c967872, fetched around 2014-10-12 12:50 UTC and still current as I write this, configured: CXXFLAGS=-std=c++11 --enable-option-checking=fatal --enable-dbgutil --enable-crashdump --without-system-postgresql

[solved] Re: build failure in [build SAX]

Thanks to the good folks on IRC, my build is proceeding. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice

[Libreoffice-bugs] [Bug 78174] Build failure: undefined reference to acquire

https://bugs.freedesktop.org/show_bug.cgi?id=78174 Caolán McNamara caol...@redhat.com changed: What|Removed |Added Status|NEW |RESOLVED

[Libreoffice-bugs] [Bug 78174] Build failure: undefined reference to acquire

https://bugs.freedesktop.org/show_bug.cgi?id=78174 --- Comment #2 from Albert Hopkins freedesk...@marduk.letterboxes.org --- Ditto, except the failure occurs on an x86-64 system (gcc 4.9.1) -- You are receiving this mail because: You are the assignee for the bug.

[Libreoffice-bugs] [Bug 78174] Build failure: undefined reference to acquire

https://bugs.freedesktop.org/show_bug.cgi?id=78174 fam...@yahoo.com.br changed: What|Removed |Added CC||fam...@yahoo.com.br --- Comment #1

Disabling avmedia = build failure

Hello, just to let you know that while build with the following options, --disable-database-connectivity --disable-extensions --disable-avmedia --disable-vba --disable-odk --without-java I got this failure message :

Re: Disabling avmedia = build failure

You must have missed the Work in progress, use only if you are hacking on it. --tml ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Disabling avmedia = build failure

Thanks for the tips, I will continue to build with avmedia ;) Cheers, Michael 2014-05-26 21:25 GMT+02:00 Tor Lillqvist t...@iki.fi: You must have missed the Work in progress, use only if you are hacking on it. --tml ___ LibreOffice mailing list

Re: [solved] build failure, clock_gettime undefined, linking libavmedialo.so

Great, finally it is solved, on master too. Thanks guys. :) 2014-05-18 22:05 GMT+02:00 Terrence Enger ten...@iseries-guru.com: On Sun, 2014-05-18 at 12:46 +0200, David Tardon wrote: Hi, [snip] This will not work. The extra library is needed at the place(s) where collada2gltf.a is

Re: build failure, clock_gettime undefined, linking libavmedialo.so

Hi, On Fri, May 16, 2014 at 03:19:21PM +0100, Tamas Zolnai wrote: On Friday, May 16, 2014 15:00 BST, Terrence Enger ten...@iseries-guru.com wrote: My build of commit 48eccfb, fetched around 2014-05-16 00:57 UTC, is failing with messages: [build LNK] Library/libavmedialo.so

Re: [solved] build failure, clock_gettime undefined, linking libavmedialo.so

On Sun, 2014-05-18 at 12:46 +0200, David Tardon wrote: Hi, [snip] This will not work. The extra library is needed at the place(s) where collada2gltf.a is _used_. The attached patch should do that. Thank you, David. This seems to do the job. In particular, I did: (*) Applied your patch on

build failure, clock_gettime undefined, linking libavmedialo.so

Zolnai, My build of commit 48eccfb, fetched around 2014-05-16 00:57 UTC, is failing with messages: [build LNK] Library/libavmedialo.so /home/terry/lo_hacking/git/libo2/workdir/LinkTarget/StaticLibrary/libcollada2gltf.a(GLTF-Open3DGC.o): In function `o3dgc::Timer::Tic()':

Re: build failure, clock_gettime undefined, linking libavmedialo.so

On Friday, May 16, 2014 15:00 BST, Terrence Enger ten...@iseries-guru.com wrote: Zolnai, My build of commit 48eccfb, fetched around 2014-05-16 00:57 UTC, is failing with messages: [build LNK] Library/libavmedialo.so

Re: [solved] build failure, clock_gettime undefined, linking libavmedialo.so

On Fri, 2014-05-16 at 15:19 +0100, Tamas Zolnai wrote: On Friday, May 16, 2014 15:00 BST, Terrence Enger ten...@iseries-guru.com wrote: [snip] /home/terry/lo_hacking/git/libo2/workdir/UnpackedTarball/collada2gltf/dependencies/o3dgc/src/o3dgc_common_lib/inc/o3dgcTimer.h:115:

Re: [solved] build failure, clock_gettime undefined, linking libavmedialo.so

On Friday, May 16, 2014 20:38 BST, Terrence Enger ten...@iseries-guru.com wrote: On Fri, 2014-05-16 at 15:19 +0100, Tamas Zolnai wrote: On Friday, May 16, 2014 15:00 BST, Terrence Enger ten...@iseries-guru.com wrote: [snip]

Re: build failure, clock_gettime undefined, linking libavmedialo.so

On Fri, 2014-05-16 at 21:12 +0100, Tamas Zolnai wrote: On Friday, May 16, 2014 20:38 BST, Terrence Enger ten...@iseries-guru.com wrote: On Fri, 2014-05-16 at 15:19 +0100, Tamas Zolnai wrote: On Friday, May 16, 2014 15:00 BST, Terrence Enger ten...@iseries-guru.com wrote: [snip]

Re: [patch] [solved] build failure

Hi, On Tue, May 06, 2014 at 03:35:32AM -0700, julien2412 wrote: Sorry Terrence, my fault here :-( Thanks to Kohei, I could fix these at the beginning of the morning (UTC+2) It could be useful to force building in C++98 or at least put an option in autogen.input. You do not need an option

Re: [patch] [solved] build failure

Hi, On Wed, May 07, 2014 at 08:29:26AM +0200, David Tardon dtar...@redhat.com wrote: You do not need an option for that. All you need is to add CXX=g++ -std=c++98 to autogen.input. Or run Though, then e.g. SAL_OVERRIDE will evaluate to an empty macro, and you can introduce build issues

Re: [patch] [solved] build failure

Silly me, I should have waited before sending the last message. Or I should have checked commit cbd4986. On Tue, 2014-05-06 at 01:54 -0400, Terrence Enger wrote: gcc (Debian 4.7.2-5) 4.7.2 on debian-wheezy just choked on sfx2/source/control/querystatus.cxx ... And exactly similar errors with

Re: [patch] [solved] build failure

-build-failure-tp4107754p4107778.html Sent from the Dev mailing list archive at Nabble.com. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice

[patch] [solved] build failure

gcc (Debian 4.7.2-5) 4.7.2 on debian-wheezy just choked on sfx2/source/control/querystatus.cxx ... /home/terry/lo_hacking/git/libo2/sfx2/source/control/querystatus.cxx: In member function ‘virtual void SfxQueryStatus_Impl::statusChanged(const com::sun::star::frame::FeatureStateEvent)’:

[Libreoffice-bugs] [Bug 78174] New: Build failure: undefined reference to acquire

https://bugs.freedesktop.org/show_bug.cgi?id=78174 Priority: medium Bug ID: 78174 Assignee: libreoffice-bugs@lists.freedesktop.org Summary: Build failure: undefined reference to acquire Severity: major Classification: Unclassified

[Libreoffice-bugs] [Bug 75731] Build Failure: secutil.c:(.text+0xfdb): undefined reference to `SECITEM_ReallocItemV2'

https://bugs.freedesktop.org/show_bug.cgi?id=75731 Jean-Baptiste Faure jbf.fa...@sud-ouest.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Libreoffice-bugs] [Bug 75731] Build Failure: secutil.c:(.text+0xfdb): undefined reference to `SECITEM_ReallocItemV2'

https://bugs.freedesktop.org/show_bug.cgi?id=75731 Joel Madero jmadero@gmail.com changed: What|Removed |Added Whiteboard||NeedsDevEval

[Libreoffice-bugs] [Bug 75731] Build Failure: secutil.c:(.text+0xfdb): undefined reference to `SECITEM_ReallocItemV2'

https://bugs.freedesktop.org/show_bug.cgi?id=75731 --- Comment #1 from David Ronis david.ro...@mcgill.ca --- The missing symbol should be part of nss; I've got 3.4.15 installed on my system, and it doesn't contain it. LO also unloads a nss tarball and SECITEM_ReallocItemV2 doesn't appear in the

[Libreoffice-bugs] [Bug 75731] New: Build Failure: secutil.c:(.text+0xfdb): undefined reference to `SECITEM_ReallocItemV2'

https://bugs.freedesktop.org/show_bug.cgi?id=75731 Priority: medium Bug ID: 75731 Assignee: libreoffice-bugs@lists.freedesktop.org Summary: Build Failure: secutil.c:(.text+0xfdb): undefined reference to `SECITEM_ReallocItemV2

[Libreoffice-bugs] [Bug 75092] New: Other: Build failure with multi language version

https://bugs.freedesktop.org/show_bug.cgi?id=75092 Priority: medium Bug ID: 75092 Assignee: libreoffice-bugs@lists.freedesktop.org Summary: Other: Build failure with multi language version Severity: normal Classification: Unclassified

[Libreoffice-bugs] [Bug 75092] Other: Build failure with multi language version

https://bugs.freedesktop.org/show_bug.cgi?id=75092 --- Comment #1 from Mohamed-Ali medalibenmans...@gmail.com --- Created attachment 94203 -- https://bugs.freedesktop.org/attachment.cgi?id=94203action=edit Non-existent description files -- You are receiving this mail because: You are the

[Libreoffice-bugs] [Bug 75092] Other: Build failure with multi language version

https://bugs.freedesktop.org/show_bug.cgi?id=75092 sophie gautier.sop...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Libreoffice-bugs] [Bug 75092] Other: Build failure with multi language version

https://bugs.freedesktop.org/show_bug.cgi?id=75092 --- Comment #3 from Mohamed-Ali medalibenmans...@gmail.com --- Yes indeed.This is not a bug ! However we need to precise to developers that a clean is essential before switching to a multi-language version to generate all description files. =

OSX build failure on master in ucpp

that even if I change to -m32, I get the same build failure at exactly the same spot. The failure point seems to be in this block : #include rtl/ustring.hxx SAL_DEPRECATED( replace s1.compareToAscii(s2, strlen(s2)) == 0 with s1.startsWith(s2)) sal_Int32 compareToAscii( const sal_Char

Re: OSX build failure on master in ucpp

Probably not a good idea to pass a CC environment variable but not a CXX one. (Do you try to build C code as 64-bit, but not C++ code?;)) And actually, one should not pass CC and CXX at all unless one knows *exactly* what one is doing. The configure script is supposed to figure out what compiler

Re: OSX build failure on master in ucpp

Le 21/08/13 11:12, Tor Lillqvist a écrit : Hi Tor, Probably not a good idea to pass a CC environment variable but not a CXX one. (Do you try to build C code as 64-bit, but not C++ code?;)) And actually, one should not pass CC and CXX at all unless one knows *exactly* what one is doing.

Re: OSX build failure on master in ucpp

Le 21/08/13 11:12, Tor Lillqvist a écrit : Hmm, replacing those switches with --enable-64-bit gives me a configuration error : Running ./configure with '--enable-64-bit' '--with-max-jobs=4' '--with-num-cpus=2' '--disable-ccache' '--with-macosx-sdk=10.8' '--enable-epm' '--with-epm=internal'

Re: OSX build failure on master in ucpp

Hmm, the xcrun: command not found are interesting. There should be a /usr/bin/xcrun. Did you not install / update the Command-line Tools in Xcode's Preferences? --tml ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org

Re: OSX build failure on master in ucpp

Le 21/08/13 11:42, Tor Lillqvist a écrit : Hmm, the xcrun: command not found are interesting. There should be a /usr/bin/xcrun. Did you not install / update the Command-line Tools in Xcode's Preferences? It says they are installed under the Preferences / Components tab. Just looked for an

Re: OSX build failure on master in ucpp

So there is no /usr/bin/xcrun for you? Weird. Unfortunately the configure script assumes there is one. I have accepted all Xcode updates, too, and do have a /usr/bin/xcrun. pkgutil --file-info /usr/bin/xcrun says: pkgid: com.apple.pkg.Essentials pkg-version: 10.8.0.1.1.1306847324

Re: OSX build failure on master in ucpp

Le 21/08/13 12:03, Tor Lillqvist a écrit : Not sure what is going on... In the meantime, I have added a symlink in /usr/bin to the XCode xcrun and at least now the configure with --enable-64-bit seems to complete, but I'm seeing some weird Couldn't infer developer directory from our own

Re: OSX build failure on master in ucpp

Hi Tor, *, On Wed, Aug 21, 2013 at 11:12 AM, Tor Lillqvist t...@iki.fi wrote: Probably not a good idea to pass a CC environment variable but not a CXX one. Passing CC or CXX is a bad idea on MacOSX anyway, as configure does add necessary compiler flags only when CC or CXX is not set. If you

Re: master build failure

-build-failure-tp4067657p4068629.html Sent from the Dev mailing list archive at Nabble.com.___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: build failure in [build GAL] arrows

Hi, On 17 June 2013 03:19, Terrence Enger ten...@iseries-guru.com wrote: Hi, I have two successive failures building master, each at the step [build GAL] arrows. The first was an incremental build of commit 843735f pulled today (Sunday) around 00:45 UCT, which failed with ... ... Among

Why not to use Gerrit patch set verification? -- was build failure in [build GAL] arrows

On 17 June 2013, Matúš Kukan wrote: Indeed, sorry for this, there was missing dependency hopefully fixed with [...] it was broken for me too, while it was easy to fix with --without-galleries option, i wonder why you don't use Gerrit? Note: mmeeks knows how to schedule a build now and is

Resolved: build failure in [build GAL] arrows

On Mon, 2013-06-17 at 10:45 +0200, Matúš Kukan wrote: Hi, On 17 June 2013 03:19, Terrence Enger ten...@iseries-guru.com wrote: Hi, I have two successive failures building master, each at the step [build GAL] arrows. The first was an incremental build of commit 843735f pulled today

build failure in [build GAL] arrows

Hi, I have two successive failures building master, each at the step [build GAL] arrows. The first was an incremental build of commit 843735f pulled today (Sunday) around 00:45 UCT, which failed with ... [build GAL] arrows warn:legacy.tools:6673:1:vcl/source/app/svapp.cxx:302:

dbgutil build failure in libreoffice-4-1 and master: copy-construct of singular iterator

Hi, For several days straight now, I've been unable to build master or libreoffice-4-1, because several unittests fail with something like the below. Anybody else getting that / any clue what is going on? $ gcc --version gcc (Debian 4.7.2-5) 4.7.2 $ dpkg -l libstdc++6-4.7-dev ii

dbgutil build failure with system mdds in lo-4-1 and master: copy-construct of singular iterator

On Sun, Jun 02, 2013 at 12:16:44PM +0200, Lionel Elie Mamane wrote: For several days straight now, I've been unable to build master or libreoffice-4-1, because several unittests fail with something like the below. /usr/include/c++/4.7/debug/safe_iterator.h:187:error: attempt to copy-

Re: Master build failure on OSX 10.8 with 10.6 SDK in libwpftdrawlo

Le 30/05/2013 18:03, Stephan Bergmann a écrit : Hi Stephan, So the relevant libs appear to be built just as archives in your case, too. But since the -Wl,-fatal_warnings got meanwhile removed again anyway with

Re: Master build failure on OSX 10.8 with 10.6 SDK in libwpftdrawlo

On 05/29/2013 09:06 PM, Stephan Bergmann wrote: On 05/29/2013 07:01 PM, Tor Lillqvist wrote: I build on OS X 10.8, but with the 10.7 SDK. I guess what makes the difference is that --with-macosx-sdk=10.7/8 uses Clang and HAVE_GCC_VISIBILITY_FEATURE=FALSE, whereas --with-macsox-sdk=10.6 uses

Re: Master build failure on OSX 10.8 with 10.6 SDK in libwpftdrawlo

Le 30/05/13 10:20, Stephan Bergmann a écrit : Hi Stephan, Alex, can you please provide the output of ls solver/*/lib from your build? ns1:core alex$ ls solver/*/lib/ solver/unxmacxi.pro/lib/: JREProperties.class libneon.dylib SunPresentationMinimizer.uno.dylib

Re: Master build failure on OSX 10.8 with 10.6 SDK in libwpftdrawlo

On 05/30/2013 04:34 PM, Alexander Thurgood wrote: Le 30/05/13 10:20, Stephan Bergmann a écrit : Alex, can you please provide the output of ls solver/*/lib from your build? So the relevant libs appear to be built just as archives in your case, too. But since the -Wl,-fatal_warnings got

Master build failure on OSX 10.8 with 10.6 SDK in libwpftdrawlo

Hi all, Since about May 24th/25th, I have been getting build failures with master on OSX in libwpftdrawlo : [build LNK] Library/libwpftdrawlo.dylib [build CXX] scripting/source/basprov/baslibnode.cxx [build CXX] scripting/source/basprov/basmethnode.cxx [build CXX]

Re: Master build failure on OSX 10.8 with 10.6 SDK in libwpftdrawlo

On 05/29/2013 06:17 PM, Alexander Thurgood wrote: Since about May 24th/25th, I have been getting build failures with master on OSX in libwpftdrawlo : [build LNK] Library/libwpftdrawlo.dylib [build CXX] scripting/source/basprov/baslibnode.cxx [build CXX] scripting/source/basprov/basmethnode.cxx

Re: Master build failure on OSX 10.8 with 10.6 SDK in libwpftdrawlo

On 05/29/2013 06:41 PM, Stephan Bergmann wrote: Odd that this doesn't show up with my build (on Mac OS X 10.7). What are the details of your build? Yeah, forget it; I hadn't read the subject... Stephan ___ LibreOffice mailing list

Re: Master build failure on OSX 10.8 with 10.6 SDK in libwpftdrawlo

Le 29/05/13 18:43, Stephan Bergmann a écrit : Hi Stephan, On 05/29/2013 06:41 PM, Stephan Bergmann wrote: Odd that this doesn't show up with my build (on Mac OS X 10.7). What are the details of your build? Yeah, forget it; I hadn't read the subject... LOL, but there must be others

Re: Master build failure on OSX 10.8 with 10.6 SDK in libwpftdrawlo

I build on OS X 10.8, but with the 10.7 SDK. --tml ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Master build failure on OSX 10.8 with 10.6 SDK in libwpftdrawlo

On 05/29/2013 07:01 PM, Tor Lillqvist wrote: I build on OS X 10.8, but with the 10.7 SDK. I guess what makes the difference is that --with-macosx-sdk=10.7/8 uses Clang and HAVE_GCC_VISIBILITY_FEATURE=FALSE, whereas --with-macsox-sdk=10.6 uses GCC and HAVE_GCC_VISIBILITY_FEATURE=TRUE (I'd

<    1   2   3   4   5   6   7   >