Fwd: Question about Apache projects and Kickstarter-like campaigns
Information to those that do not follow the community list. It seems crowdfunding is slowly becomming more accepted and funding is possible for opensource projects. Something to think about, if we want a bigger task done. rgds jan I. -- Forwarded message -- From: Thiago H de Paula Figueiredo Date: 10 December 2013 02:58 Subject: Re: Question about Apache projects and Kickstarter-like campaigns To: "d...@community.apache.org" Hi! The campaign has just been funded: http://www.indiegogo.com/ projects/a-month-of-apache-tapestry-5 :D Thanks everybody for your comments and feedback! They really improved my campaign and helped me getting it funded the right way. :) Cheers! -- Thiago H. de Paula Figueiredo Tapestry, Java and Hibernate consultant and developer http://machina.com.br
Bug 119006 - Restore windows problem on Mac OS X
Bug 119006 - Restore windows problem on Mac OS X - Reopen?? It seem this bug is not fixed as reported. There are still people reporting the problem on the forum and on the mailing list. Several of them say they are using AOO 4.0.1. I got a new Mac a month ago with OS X version 10.9 (Mavericks). Using AOO 4.0.1 I had the Restore Windows once. I had previously been using OS X 10.6.8 so hadn't personally experienced the problem before. -- _ Larry I. Gusaas Moose Jaw, Saskatchewan Canada Website: http://larry-gusaas.com "An artist is never ahead of his time but most people are far behind theirs." - Edgard Varese - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Incompatibility between OpenOffice version of libxml2 and libarchive?
To follow up on this, the problem persists even when using a version of openoffice compiled locally. On Fri, Dec 6, 2013 at 4:58 PM, Marcin Tustin wrote: > I moved the OO version of libxml, and it only fixes the error messages > about libxml. OO still crashes with the same other errors. > > > On Fri, Dec 6, 2013 at 4:19 PM, Marcin Tustin wrote: > >> Hi All, >> >> I'm using a version of openoffice compiled by me, albeit on another >> machine, under linux. I run openoffice as an uno listener with the command >> below. When I connect to it using python, I get the stack trace below. This >> happens whether or not I use the openoffice version of python. I have all >> of the environment variables set up such that the python side works to talk >> to the openoffice listener. >> >> The command, and error (triggered by the python connection) are below. I >> would appreciate any insight into possible solutions. >> >> $ openoffice/opt/openoffice4/program/soffice.bin -headless -invisible >> -nocrashreport -nodefault -nologo -nofirststartwizard -norestore >> -accept=pipe,name=`pwd`/../tmp/oo.sock;urp;StarOffice.ComponentContext >> terminate called after throwing an instance of >> 'com::sun::star::uno::RuntimeException' >> Application Error >> >> Fatal exception: Signal 6 >> Stack: >> >> /home/marcintustin/oneclickrep/oneclickcosvirt/oneclickcos/openoffice/opt/openoffice4/program/libuno_sal.so.3(+0x37b9a)[0x7f4b92cfab9a] >> >> /home/marcintustin/oneclickrep/oneclickcosvirt/oneclickcos/openoffice/opt/openoffice4/program/libuno_sal.so.3(+0x37ccc)[0x7f4b92cfaccc] >> >> /home/marcintustin/oneclickrep/oneclickcosvirt/oneclickcos/openoffice/opt/openoffice4/program/libuno_sal.so.3(+0x37d69)[0x7f4b92cfad69] >> /lib64/libc.so.6[0x3e518359b0] >> /lib64/libc.so.6(gsignal+0x35)[0x3e51835935] >> /lib64/libc.so.6(abort+0x148)[0x3e518370e8] >> >> /home/marcintustin/oneclickrep/oneclickcosvirt/oneclickcos/openoffice/opt/openoffice4/program/libvcl.so(+0x1544a9)[0x7f4b8f6ef4a9] >> >> /home/marcintustin/oneclickrep/oneclickcosvirt/oneclickcos/openoffice/opt/openoffice4/program/libsofficeapp.so(+0x2352b)[0x7f4b92a5a52b] >> >> /home/marcintustin/oneclickrep/oneclickcosvirt/oneclickcos/openoffice/opt/openoffice4/program/libvcl.so(+0x17eab0)[0x7f4b8f719ab0] >> >> /home/marcintustin/oneclickrep/oneclickcosvirt/oneclickcos/openoffice/opt/openoffice4/program/libuno_sal.so.3(+0x36962)[0x7f4b92cf9962] >> >> /home/marcintustin/oneclickrep/oneclickcosvirt/oneclickcos/openoffice/opt/openoffice4/program/libuno_sal.so.3(+0x37d4a)[0x7f4b92cfad4a] >> /lib64/libc.so.6[0x3e518359b0] >> /lib64/libc.so.6(gsignal+0x35)[0x3e51835935] >> /lib64/libc.so.6(abort+0x148)[0x3e518370e8] >> >> /lib64/libstdc++.so.6(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x11d)[0x3e5b860dad] >> /lib64/libstdc++.so.6[0x3e5b85eea6] >> /lib64/libstdc++.so.6[0x3e5b85dfb9] >> /lib64/libstdc++.so.6(__gxx_personality_v0+0x481)[0x3e5b85eaf1] >> /lib64/libgcc_s.so.1[0x3e5500f8bb] >> /lib64/libgcc_s.so.1(_Unwind_Resume+0x68)[0x3e5500fd18] >> >> /home/marcintustin/oneclickrep/oneclickcosvirt/oneclickcos/openoffice/opt/openoffice4/program/libsfx.so(_ZN9SfxMediumD1Ev+0x140)[0x7f4b916d0634] >> >> /home/marcintustin/oneclickrep/oneclickcosvirt/oneclickcos/openoffice/opt/openoffice4/program/../program/libsdd.so(+0x85cb)[0x7f4b7c0a85cb] >> >> /home/marcintustin/oneclickrep/oneclickcosvirt/oneclickcos/openoffice/opt/openoffice4/program/../program/libfilterconfig1.so(+0x3a300)[0x7f4b7c532300] >> >> /home/marcintustin/oneclickrep/oneclickcosvirt/oneclickcos/openoffice/opt/openoffice4/program/../program/libfilterconfig1.so(+0x3b708)[0x7f4b7c533708] >> >> /home/marcintustin/oneclickrep/oneclickcosvirt/oneclickcos/openoffice/opt/openoffice4/program/../program/libfilterconfig1.so(+0x3c406)[0x7f4b7c534406] >> >> /home/marcintustin/oneclickrep/oneclickcosvirt/oneclickcos/openoffice/opt/openoffice4/program/libfwk.so(+0xe2ada)[0x7f4b8b3b2ada] >> >> /home/marcintustin/oneclickrep/oneclickcosvirt/oneclickcos/openoffice/opt/openoffice4/program/libfwk.so(+0xe3062)[0x7f4b8b3b3062] >> >> /home/marcintustin/oneclickrep/oneclickcosvirt/oneclickcos/openoffice/opt/openoffice4/program/libfwk.so(+0xe4178)[0x7f4b8b3b4178] >> >> /home/marcintustin/oneclickrep/oneclickcosvirt/oneclickcos/openoffice/opt/openoffice4/program/libfwk.so(+0x102742)[0x7f4b8b3d2742] >> >> /home/marcintustin/oneclickrep/oneclickcosvirt/oneclickcos/openoffice/opt/openoffice4/program/libgcc3_uno.so(+0x78cd)[0x7f4b81d008cd] >> >> /home/marcintustin/oneclickrep/oneclickcosvirt/oneclickcos/openoffice/opt/openoffice4/program/libgcc3_uno.so(+0x7ee2)[0x7f4b81d00ee2] >> >> /home/marcintustin/oneclickrep/oneclickcosvirt/oneclickcos/openoffice/opt/openoffice4/program/libgcc3_uno.so(+0x8c20)[0x7f4b81d01c20] >> >> /home/marcintustin/oneclickrep/oneclickcosvirt/oneclickcos/openoffice/opt/openoffice4/program/ >> binaryurp.uno.so(+0x112e6)[0x7f4b7e08d2e6] >> >> /home/marcintustin/oneclickrep/oneclickcosvirt/oneclickcos/openoffice/opt/openoffice4/program/ >> bin
Re: Reporting a problem with the OpenOffice website
On 2013-12-09, 3:32 PM Tyson Charlson wrote: I am having issues with my Open Office program. A Restore Windows window pops up and won't let me close out (see attachment). I've tried a reinstall but that didn't work. Thanks and have a great day. You need to delete the file "org.openoffice.script.savedState". It is in the "Saved Application State" folder in your User/Library. See this post on the user forum for detailed instructions: https://forum.openoffice.org/en/forum/viewtopic.php?f=17&t=55755#p244931 -- As a courtesy I have sent a copy of this reply to you as well as to the mailing list. Since you are not subscribed to this list you may not see all the replies to your query.To subscribe Apache OpenOffice mailing lists go to http://openoffice.apache.org/mailing-lists.html For user support you can also use The OpenOffice.org Community Forum http://user.services.openoffice.org/en/forum/ _ Larry I. Gusaas Moose Jaw, Saskatchewan Canada Website: http://larry-gusaas.com "An artist is never ahead of his time but most people are far behind theirs." - Edgard Varese
Re: OpenOffice subreddit?
Reddit is generally a good platform for discussions. I'll tell the admins about this message. On Sun, Dec 8, 2013 at 1:18 PM, Rob Weir wrote: > Anyone familiar with this? http://www.reddit.com/r/openoffice/ Does > anyone know who the owner "citronix09" is? Is it worth making more > use of reddit? > > -Rob > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > -- Marcin Tustin Tel: +44 (0) 7773 787 105 (UK) +1 917 553 3974 (US)
Reporting a problem with the OpenOffice website
I am having issues with my Open Office program. A Restore Windows window pops up and won't let me close out (see attachment). I've tried a reinstall but that didn't work. Thanks and have a great day. Tyson CharlsonArt DirectorPurple DaneO: 254.297.8621C: 254.315.0330F: 254.755.7006ty...@purpledane.comPurpleDane.com
Build error
Hello, I am having problem with the build, I have been getting this error during the building process: ERROR: ERROR: More than one new package in directory /home/efi/AOO/aoo-trunk/main/instsetoo_native/unxlngi6.pro/Apache_OpenOffice/deb/install/en-US_inprogress/DEBS ( /home/efi/AOO/aoo-trunk/main/instsetoo_native/unxlngi6.pro/Apache_OpenOffice/deb/install/en-US_inprogress/DEBS/openoffice-ure-4.1.0-1-linux-3.8-intel.deb /home/efi/AOO/aoo-trunk/main/instsetoo_native/unxlngi6.pro/Apache_OpenOffice/deb/install/en-US_inprogress/DEBS/openoffice-ure-4.1.0-1-linux-3.8-intel) in function: determine_new_packagename (packagepool) ** in function: determine_new_packagename (packagepool)stopping log at Mon Dec 9 21:37:52 2013 dmake: Error code 255, while making 'openoffice_en-US.deb' 1 module(s): instsetoo_native need(s) to be rebuilt I searched the mailing lists and I found the same one,the solution suggested configuring with the --with-epm-url=http://www.msweet.org/files/project2/epm-3.7-source.tar.gz which was what i used in the first place. I tried moving to different revisions before and after the 1546570 which is the revision I first got the error. I use ubuntu 12.04 and my building steps are: sudo apt-get install subversion svn co https://svn.apache.org/repos/asf/openoffice/trunk aoo-trunk cd aoo-trunk/main sudo apt-get install g++ gcc bison flex libarchive-zip-perl libcups2-dev libpam0g-dev gperf libfreetype6-dev libxaw7-dev libfontconfig1-dev libxrandr-dev patch libgconf2-dev libgnomevfs2-dev ant libgtk2.0-dev junit junit4 libidl-dev liborbit2-dev openjdk-6-jdk libwww-perl libxml-parser-perl autoconf libssl-dev ./configure --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-category-b --enable-bundled-dictionaries ./bootstrap source LinuxX86Env.Set.sh cd instsetoo_native build --all Does anyone know how to solve this? Regards Efi - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [RELEASE]: proposal for our next release AOO 4.1
On Fri, Dec 6, 2013 at 3:41 AM, Jürgen Schmidt wrote: > Hi, > > some time ago we have discussed a language only release on base of > 4.0.1. And even a language release requires a lot of work. Until today I > see 3 potential languages ready which is not enough from my perspective. +1 > But on the other side we have some nice stuff in place that should be > released asap, for example the iAccessibility support which is a great > step forward and will help a lot of people. > +1 > I would like to propose a new release AOO 4.1 early next year and as > soon as possible. Taking into account that Christmas and the related > holidays in many countries will slow down all the activities a little > bit I can think of the following: > > Jan 10, 2014features freeze > Jan 13, 2014translation freeze for beta I'm not sure what "freeze for beta" means? Will more languages be permitted after beta? Or only bug fixes to the languages that made it into beta? The purpose of a beta is to help assure quality, so it might be reasonable to have all new features, including new languages in the beta. But I could also see an argument for letting more languages come after beta. > Jan 20, 2014feature FVT finish > Jan 21, 20144.1 beta candidate, with major features and languages > Jan 27, 20144.1 beta release for public review > Jan 27 - ? full regression testing and bug fixing I assume we would produce further snapshot builds for testing, by QA volunteers in the project, while the beta is ongoing. > ? RC1 Feb 28, or later? A one-month beta would take us to February 28th. Next steps would depend on the feedback from the beta, how many serious issues are found, how many have already been fixed, etc. We would assume that the most spectacular bugs will be found in the first couple of days of the beta, not in the last week. But if things go well then the beta naturally leads into a RC for 4.1. > GA ? > > > I really would like to see the iAccessibility improvements publicly > available as soon as possible because from my perspective it is a > further huge milestone for AOO. And I would like to support the new > languages as soon as possible and hopefully we can have a few more. Some > are very close to be ready. > > Opinions and feedback is welcome and I hope may of you can share my view. > It sounds good to me! Regards, -Rob > Juergen > > - > 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: Open Office
Hallo Herr Gruberbauer, w. gruberbauer schrieb: Sehr geehrte Damen und Herren, Ich verwende noch immer “Star-Office 9” und möchte gerne auf “Open Office” umsteigen. Frage: werden nach der Installation meine vorhandenen Dokumente etc. von Star-Office auf Open-Office konvertiert? Nur sehr alte Dokumente, die beispielsweise mit StarOffice 5.2 geschrieben wurden, lassen sich mit Apache OpenOffice 4 nicht lesen. Die Dateiendung für diese alten Formate sind sdw, sdc u.ä. Falls Sie solche Dokumente haben, können Sie diese mit StarOffice 9 konvertieren oder eine portable Version von OpenOffice.org 3 zusammen mit solchen Dokumenten aufbewahren. Alle anderen Dateiformate werden von Apache OpenOffice 4 gelesen. Sie können Apache OpenOffice auch parallel zu StarOffice installieren. Mit freundlichen Grüßen Regina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: ADD TO CONSULTANT LIST
On Sat, Dec 7, 2013 at 3:59 PM, Ramon Sole wrote: > Hello, > > Our company has been providing services for OpenOffice in Spain since 2004 > and we would like to be listed in the consultant page of the project. > > http://www.openoffice.org/bizdev/consultants.html > > We're providing the requested info in the xml format for your convenience > and submiting it to the list for review by the Project Management Committee. > > Don't hesitate in contacting with me if you need any additional > information or you prefer other format for the data. > > Thanks in advance. > > Best Regards, > > Ramon Sole > OPS Consulting > > --- > > > OPS Consulting > ES > Deployment > Support > Development > Training > Other > OPS Consulting is located in Barcelona, Spain. We've been > providing consulting and training services to help organizations to deploy > OpenOffice since 2004. > > http://www.opscons.com/soluciones/migracion/ > ofimatica/servicios-de-migracion > i...@opscons.com > +34 93 451 40 46 > > > -- > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > Thank you for contacting OpenOffice and for your submission. If there are no objections to your listing, we will publish it by the end of the work week and let you know. -- - MzK "Cats do not have to be shown how to have a good time, for they are unfailing ingenious in that respect." -- James Mason
RE: soltools need(s) to be rebuilt
> > Speaking of symbol visibility on unxsogi platforms there is an > interesting comment in > main/solenv/inc/unxsogi.mk > regarding that topic. In > main/sal/inc/sal/types.h > In that file there is some magic going on with that visibility and I'm > quite sure that the Solaris+gcc specific checks need to be updated to > work with newer versions of these tools. > Hello, I have noticed that visibility does not work in Solaris with gcc. The compiler complains that it is not defined or available to this platform. Since I have compiled gcc myself chances are that I did something wrong... However, I have compiled Qt with this compiler, the TeX distribution and many many other things and all work as expected... > > The manual interventions are good to experiment with different solution > approaches. When the experiments provided a clearer picture the solenv > makefiles for the "unxsogi" platform should be updated so all that could > work out of the box. We have so many libraries that it would be quite > painful if one had to do many of them manually. > I totally agree! But I keep notes of what I do so I hope these notes would be useful when I will hopefully finish. All the best, A.S. -- Apostols Syropoulos Xanthi, Greece
Re: Using system boost 1.54 (was Re: EXTERNAL: Re: Building comphelper)
On Mon, Dec 9, 2013 at 5:29 AM, Herbert Duerr wrote: > On 08.12.2013 19:26, Kay Schenk wrote: > >> [...] >> >> short story -- I couldn't get things to work with 1.49, so I decided to >> try >> 1.54. Errors, but different. At first I WAS using 1.49. >> > > Ok. That 1.49 didn't work is an interesting data point. > > > Is it OK to use this newer version because I'm getting errors [...] >>> > There should be no general problem, but boost 1.49 wasn't regularly used > for building AOO, so the AOO may need some adaptions to work with boost > 1.49. > > > The 1.54 boost version you are using is much newer than the AOO internal >>> version, which is version still at 1.48. We should upgrade our codebase >>> to work with the newer version and update the internal boost then. This >>> could solve many compile warnings that are spewed out for 1.48 and fix >>> some hard problems like the one with the Solaris compilers. >>> >>> But as you saw such support for newer boost versions is more than just a >>> recompile. Making AOO build with newer boost versions may be an >>> interesting topic for a volunteer. One could leverage the experience of >>> the very popular boost library to dive into many corners of the AOO >>> codebase. >>> >> >> >> I'm not sure what some of this statement really means... but definitely a >> worthwhile project for a volunteer! >> > > By the way I created an enhancement issue [1] for upgrading to the latest > boost version. I also developed a patch that already works with my systems > and attached it to that issue. > > [1] https://issues.apache.org/ooo/show_bug.cgi?id=123817 > > It would be interesting to know if that experimental patch to support the > new boost version works better for e.g. our Solaris ports? Please test. > Maybe upgrading to boost 1.55 is a good idea for the AOO 4.1 release. > > > Herbert > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > OK, good...I'll have a look soonish. -- - MzK "Cats do not have to be shown how to have a good time, for they are unfailing ingenious in that respect." -- James Mason
Re: [RELEASE]: proposal for our next release AOO 4.1
On Fri, Dec 6, 2013 at 12:41 AM, Jürgen Schmidt wrote: > Hi, > > some time ago we have discussed a language only release on base of > 4.0.1. And even a language release requires a lot of work. Until today I > see 3 potential languages ready which is not enough from my perspective. > But on the other side we have some nice stuff in place that should be > released asap, for example the iAccessibility support which is a great > step forward and will help a lot of people. > > I would like to propose a new release AOO 4.1 early next year and as > soon as possible. Taking into account that Christmas and the related > holidays in many countries will slow down all the activities a little > bit I can think of the following: > > Jan 10, 2014features freeze > Jan 13, 2014translation freeze for beta > Jan 20, 2014feature FVT finish > Jan 21, 20144.1 beta candidate, with major features and languages > Jan 27, 20144.1 beta release for public review > Jan 27 - ? full regression testing and bug fixing > ? RC1 Feb 28, or later? > GA ? > > > I really would like to see the iAccessibility improvements publicly > available as soon as possible because from my perspective it is a > further huge milestone for AOO. And I would like to support the new > languages as soon as possible and hopefully we can have a few more. Some > are very close to be ready. > > Opinions and feedback is welcome and I hope may of you can share my view. > > Juergen > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > I haven't yet installed the linux snapshot containing these changes or reviewed current bugs *in a while* but the proposed schedule looks like a good goal to me. The public beta will be an interesting aspect for us. -- - MzK "Cats do not have to be shown how to have a good time, for they are unfailing ingenious in that respect." -- James Mason
Re: Open Office
Guten Abend Herr Gruberbauer, das dürfte überhaupt kein Problem sein. StarOffice 9 basierte auf OpenOffice 3 und verwendet daher die gleichen Dateiformate wie Openoffice. Dem Umstieg auf OpenOffice steht also nichts im Wege. Beachten Sie aber bitte, dass Sie das OpenOffice nur von der offiziellen Webseite www.openoffice.org herunter laden. Anderenorts könnten Sie ggf. unerwünschte Zusatzsoftware mit dazu bekommen. Alles Gute Max Merbald Am 09.12.2013 17:17, schrieb w. gruberbauer: Sehr geehrte Damen und Herren, Ich verwende noch immer “Star-Office 9” und möchte gerne auf “Open Office” umsteigen. Frage: werden nach der Installation meine vorhandenen Dokumente etc. von Star-Office auf Open-Office konvertiert? Vielen Dank für Ihre Hilfe Mit freundlichen Grüßen Werner Gruberbauer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Checked out revision 1547453 Build problem on Windows 7
Hello Herbert,
Commented:
//namespace _STL
//{
///** @internal */
//template
//inline ::rtl::Allocator & __stl_alloc_rebind (::rtl::Allocator
& a, U const *)
//{
//return (::rtl::Allocator&)(a);
//}
//}
in C:\source\aoo-trunk\main\sal\inc\rtl\allocator.hxx
*The next problem is with undeclared identifiers:*
Entering /cygdrive/c/source/aoo-trunk/main/sal/osl/all
Compiling: sal/osl/all/debugbase.cxx
C:/PROGRA~2/MICROS~1.0/VC/include\../../VC/include/unordered_set(64) :
error C2065: '_Hash_compare' : undeclared identifier
C:/PROGRA~2/MICROS~1.0/VC/include\../../VC/include/unordered_set(183)
: see reference to class template instantiation
'std::tr1::unordered_set<_Kty,_Hasher,_Keyeq,_Alloc>' being
compiled
C:/PROGRA~2/MICROS~1.0/VC/include\../../VC/include/unordered_set(64) :
error C2974: 'std::tr1::_Uset_traits' : invalid template
argument for '_Tr', type expected
C:/PROGRA~2/MICROS~1.0/VC/include\../../VC/include/unordered_set(20) :
see declaration of 'std::tr1::_Uset_traits'
C:/PROGRA~2/MICROS~1.0/VC/include\../../VC/include/unordered_set(64) :
error C2975: 'std::tr1::_Uset_traits' : invalid template
argument for '_Mfl', expected compile-time constant expression
C:/PROGRA~2/MICROS~1.0/VC/include\../../VC/include/unordered_set(20) :
see declaration of 'std::tr1::_Uset_traits'
C:/PROGRA~2/MICROS~1.0/VC/include\../../VC/include/unordered_set(64) :
error C2977: 'stdext::_Hash' : too many template arguments
C:/PROGRA~2/MICROS~1.0/VC/include\xhash(147) : see declaration of
'stdext::_Hash'
C:/PROGRA~2/MICROS~1.0/VC/include\../../VC/include/unordered_set(64) :
error C2955: 'stdext::_Hash' : use of class template requires
template argument list
C:/PROGRA~2/MICROS~1.0/VC/include\xhash(147) : see declaration of
'stdext::_Hash'
C:/PROGRA~2/MICROS~1.0/VC/include\../../VC/include/unordered_set(64) :
error C2143: syntax error : missing ',' before '>'
C:/PROGRA~2/MICROS~1.0/VC/include\../../VC/include/unordered_set(67) :
error C2143: syntax error : missing ';' before '<'
C:/PROGRA~2/MICROS~1.0/VC/include\../../VC/include/unordered_set(67) :
error C4430: missing type specifier - int assumed. Note: C++
does not support default-int
C:/PROGRA~2/MICROS~1.0/VC/include\../../VC/include/unordered_set(67) :
error C2238: unexpected token(s) preceding ';'
C:/PROGRA~2/MICROS~1.0/VC/include\../../VC/include/unordered_set(69) :
error C2065: '_Mytraits' : undeclared identifier
C:/PROGRA~2/MICROS~1.0/VC/include\../../VC/include/unordered_set(69) :
error C3203: '_Uset_traits' : unspecialized class template
can't be used as a template argument for template parameter
'_Traits', expected a real type
C:/PROGRA~2/MICROS~1.0/VC/include\../../VC/include/unordered_set(69) :
error C2955: 'std::tr1::_Uset_traits' : use of class template
requires template argument list
C:/PROGRA~2/MICROS~1.0/VC/include\../../VC/include/unordered_set(20) :
see declaration of 'std::tr1::_Uset_traits'
C:/PROGRA~2/MICROS~1.0/VC/include\../../VC/include/unordered_set(73) :
error C2146: syntax error : missing ';' before identifier
'key_compare'
C:/PROGRA~2/MICROS~1.0/VC/include\../../VC/include/unordered_set(73) :
error C4430: missing type specifier - int assumed. Note: C++
does not support default-int
C:/PROGRA~2/MICROS~1.0/VC/include\../../VC/include/unordered_set(73) :
error C2208: '_Hash<_Traits>::_Traits::key_compare' : no
members defined using this type
C:/PROGRA~2/MICROS~1.0/VC/include\../../VC/include/unordered_set(202) :
error C2065: '_Hash_compare' : undeclared identifier
C:/PROGRA~2/MICROS~1.0/VC/include\../../VC/include/unordered_set(339)
: see reference to class template instantiation
'std::tr1::unordered_multiset<_Kty,_Hasher,_Keyeq,_Alloc>'
being compiled
C:/PROGRA~2/MICROS~1.0/VC/include\../../VC/include/unordered_set(202) :
error C2974: 'std::tr1::_Uset_traits' : invalid template
argument for '_Tr', type expected
C:/PROGRA~2/MICROS~1.0/VC/include\../../VC/include/unordered_set(20) :
see declaration of 'std::tr1::_Uset_traits'
C:/PROGRA~2/MICROS~1.0/VC/include\../../VC/include/unordered_set(202) :
error C2975: 'std::tr1::_Uset_traits' : invalid template
argument for '_Mfl', expected compile-time constant expression
C:/PROGRA~2/MICROS~1.0/VC/include\../../VC/include/unordered_set(20) :
see declaration of 'std::tr1::_Uset_traits'
C:/PROGRA~2/MICROS~1.0/VC/include\../../VC/include/unordered_set(202) :
error C2977: 'stdext::_Hash' : too many template arguments
C:/PROGRA~2/MICROS~1.0/VC/include\xhash(147) : see declaration of
'stdext::_Hash'
C:/PROGRA~2/MICROS~1.0
Open Office
Sehr geehrte Damen und Herren, Ich verwende noch immer “Star-Office 9” und möchte gerne auf “Open Office” umsteigen. Frage: werden nach der Installation meine vorhandenen Dokumente etc. von Star-Office auf Open-Office konvertiert? Vielen Dank für Ihre Hilfe Mit freundlichen Grüßen Werner Gruberbauer
Re: soltools need(s) to be rebuilt
On 08.12.2013 20:38, Απόστολος Συρόπουλος wrote: [...] This way I managed to build the missing libraries. I continued but building stopped at: build --all:binaryurp The following commands "helped" me to build the library: [...] Now it stops as follows: [...] Entering /extra/sources/OpenOffice/aoo4/main/eventattacher/source [...] : ERROR: ld.so.1: checkdll: fatal: relocation error: file ../unxsogi.pro/lib/check_libevtatt.so: symbol _ZTIN4cppu11OWeakObjectE: referenced symbol not found The demangled name of this symbol means typeinfo for cppu::OWeakObject AFAIK it should come from cppuhelper. Experts on cppuhelper or typeinfo visibility are invited to help us outhere... Speaking of symbol visibility on unxsogi platforms there is an interesting comment in main/solenv/inc/unxsogi.mk regarding that topic. In main/sal/inc/sal/types.h In that file there is some magic going on with that visibility and I'm quite sure that the Solaris+gcc specific checks need to be updated to work with newer versions of these tools. I guess I can use a similar trick to continue, but the question is: Is this the right way to build these libraries? The manual interventions are good to experiment with different solution approaches. When the experiments provided a clearer picture the solenv makefiles for the "unxsogi" platform should be updated so all that could work out of the box. We have so many libraries that it would be quite painful if one had to do many of them manually. Herbert - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Checked out revision 1547453 Build problem on Windows 7
Hello Vadim,
I'm replying on the mailing list, because this may be of interest to a
wider audience.
On 06.12.2013 18:58, Vadim Yedzinovich wrote:
Get preprocess output to debugbase.i file (you can see it in attached
file)...
Got it, thanks!
As I can see basic_string comes from namespace std templates definitions
like:
#line 13 "C:/PROGRA~2/MICROS~1.0/VC/include\\xstring"
namespace std {
[...]
The basic_strings being defined in the std namespace is fine. That's
where it belongs so this is good.
namespace _STL comes from allocator.hxx:
#line 32 "../../inc\\rtl/allocator.hxx"
namespace _STL
[...]
The _STL namespace is only mentioned at that one location, so I wonder
how basic_string is now expected in that namespace?
[...]
Sorry, but a the monemt I've no idea how to resolve this problem.
The few lines mentioning _STL in allocator.hxx should be obsolete
nowadays, anyway. Could you try out whether deleting them (the
"namespace _STL" from start to closing and all that it encloses) helps?
Herbert
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Using system boost 1.54 (was Re: EXTERNAL: Re: Building comphelper)
On 08.12.2013 19:26, Kay Schenk wrote: [...] short story -- I couldn't get things to work with 1.49, so I decided to try 1.54. Errors, but different. At first I WAS using 1.49. Ok. That 1.49 didn't work is an interesting data point. Is it OK to use this newer version because I'm getting errors [...] There should be no general problem, but boost 1.49 wasn't regularly used for building AOO, so the AOO may need some adaptions to work with boost 1.49. The 1.54 boost version you are using is much newer than the AOO internal version, which is version still at 1.48. We should upgrade our codebase to work with the newer version and update the internal boost then. This could solve many compile warnings that are spewed out for 1.48 and fix some hard problems like the one with the Solaris compilers. But as you saw such support for newer boost versions is more than just a recompile. Making AOO build with newer boost versions may be an interesting topic for a volunteer. One could leverage the experience of the very popular boost library to dive into many corners of the AOO codebase. I'm not sure what some of this statement really means... but definitely a worthwhile project for a volunteer! By the way I created an enhancement issue [1] for upgrading to the latest boost version. I also developed a patch that already works with my systems and attached it to that issue. [1] https://issues.apache.org/ooo/show_bug.cgi?id=123817 It would be interesting to know if that experimental patch to support the new boost version works better for e.g. our Solaris ports? Please test. Maybe upgrading to boost 1.55 is a good idea for the AOO 4.1 release. Herbert - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: a new feature for the extension mechanism
On 12/9/13 12:16 PM, Jörg Schmidt wrote: >> From: Andre Fischer [mailto:awf@gmail.com] > >> Two comments: >> >> - The office is not necessarily running when an extension is >> installed. >> In that case a post-installation job can not be run. > > you're absolutely right, but please think a little more general: > > an extension developer knows that beforehand and can take into account. > > When I ask about the possibility of a script after installation to run > automatically so that is quite flexible, a partial solution would start > already there where the license dialog would be really suitable display any > information. > > Yes, I can, instead of the license, display any text, but not formatted. Much > would be won if one could show there html texts (including links) the idea of having pre and post install hooks is not new and not a bad one. It's just that it have to implemented and it puts a further complexity in the already existing extension framework with too many specialties. I would first think about a redesign to remove the complexity (which is not necessary at all) and then add new features like this. But based on a well designed and defined workflow. > >> - Something similar to what you propose may already be >> possible. I am >> not sure about the details, but I think that you can specify >> jobs to be >> run on certain events (application start, document creation, >> etc). It >> may be possible to specify a job to be run exactly once. >> See >> https://wiki.openoffice.org/wiki/Documentation/DevGuide/Writin >> gUNO/Jobs/Jobs >> for details. > > yes, right, I know. > > However, I have not yet properly understood (OK, my mistake) and > unfortunately have to note that the uses hardly anyone what my suspicions > intensified, which is not particularly well used. > > OK, I'll only use your suggestion and concern myself with it again in more > detail. > > > quite openly: > it is a latent weakness of OpenOffice (and LO) is insufficient to address the > needs of macro programmers. > e.g. in MS Office VBA contributes to this success. "VBA" here is not the > language alone, but much more need what macro programmer, eg a good IDE and > much more. > it is a known issue and it is hard to provide a similar framework. It's always the same you need volunteers who are interested to work on this. Plug or use existing IDE's like Eclipse or NetBeans to do more enhanced macro programming and provide a much better tooling is of course an interesting challenge and possible. We had started to use for example NetBeans a long time ago for Java macro programming. But it was never finished or left the prototype status. It's easy to say what's missing comparing to MSO but more difficult to deliver something useful. Juergen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: a new feature for the extension mechanism
> From: Andre Fischer [mailto:awf@gmail.com] > Two comments: > > - The office is not necessarily running when an extension is > installed. > In that case a post-installation job can not be run. you're absolutely right, but please think a little more general: an extension developer knows that beforehand and can take into account. When I ask about the possibility of a script after installation to run automatically so that is quite flexible, a partial solution would start already there where the license dialog would be really suitable display any information. Yes, I can, instead of the license, display any text, but not formatted. Much would be won if one could show there html texts (including links) > - Something similar to what you propose may already be > possible. I am > not sure about the details, but I think that you can specify > jobs to be > run on certain events (application start, document creation, > etc). It > may be possible to specify a job to be run exactly once. > See > https://wiki.openoffice.org/wiki/Documentation/DevGuide/Writin > gUNO/Jobs/Jobs > for details. yes, right, I know. However, I have not yet properly understood (OK, my mistake) and unfortunately have to note that the uses hardly anyone what my suspicions intensified, which is not particularly well used. OK, I'll only use your suggestion and concern myself with it again in more detail. quite openly: it is a latent weakness of OpenOffice (and LO) is insufficient to address the needs of macro programmers. e.g. in MS Office VBA contributes to this success. "VBA" here is not the language alone, but much more need what macro programmer, eg a good IDE and much more. Greetings, Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: a new feature for the extension mechanism
On 08.12.2013 13:23, Jörg Schmidt wrote: Hello, A long time ago I proposed already in OOo following: There must be a way to create that, immediately after installing an extension, a script, macro (or similar), which was installed along with the extension, it is automatically started. This would be important in order to let the authors of extensions to give the opportunity custom initialization procedures for their extensions run. The setting of this could be done description.xml in the file, for example: Two comments: - The office is not necessarily running when an extension is installed. In that case a post-installation job can not be run. - Something similar to what you propose may already be possible. I am not sure about the details, but I think that you can specify jobs to be run on certain events (application start, document creation, etc). It may be possible to specify a job to be run exactly once. See https://wiki.openoffice.org/wiki/Documentation/DevGuide/WritingUNO/Jobs/Jobs for details. -Andre In my opinion the effort for the implementation would be low, and there would be a great benefit for Authors of Extensions. Is there a programmer could implement it? What do you think? Greetings, Jörg - 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: Patches on Windows (Update)
On 06.12.2013 22:58, Andrea Pescetti wrote:
On 04/12/2013 Andre Fischer wrote:
I have just checked in what basically is a reimplementation of the
defunct support for creating patches on and for Windows.
Thanks, another nice step forward.
0. Expected (disk) space and time requirements:
Disk space: Number of languages *
- Previous downloadable installation set (EXE) in ext_sources/
- The above unpacked in instsetoo_native/wntmsci12.pro
- The CAB file of the above (maybe 95% of the installation set) unpacked
- The installation set and downloadable installation set of the current
release
- A copy of the above, arranged so that msimsp.exe can process it.
- The MSP patch, about 10% of the downloadable installation set.
I did not measure it but I would estimate the total to be around 500 MB
So for (say) 40 languages we would be around 20 GBytes and 20 hours.
It seems that the above can be scripted and cached, but indeed this is
an extra burden for the release manager.
I could drop the requirement that whole installation sets of previous
versions are present in the 'build release=t' step.
But when the patches are created then the unpacked previous installation
sets have to present. The msimsp.exe tool requires that. I could
delete the EXE version, but if you run this step a second time, you
probably don't want to download and extract them again.
2. Store information about the new release for when we will be creating
patches when doing the next (future) release.
So basically the system is assuming that OpenOffice release numbers
always increase over time, right? I mean, if 4.1.0 is released (and
the patch created for 4.0.1->4.1.0) then no 4.0.2 will be released
after it (or anyway the patches won't support it, since this would
very quickly become absurdly complex). So basically patches assume
that we only have one development line active at any given moment, or
to be more precise: once 4.1.0 is released (and a patch 4.0.1->4.1.0
with it), it becomes the reference for new patches and further (if
any) 4.0.x releases are not supported by this mechanism.
No, at least in theory, the patch creation is a little more flexible.
It can create patches between any two versions. The only requirements
on the release numbers (that I know of) are:
- The build id (as defined by the PRODUCTBUILDID in the Property table
of an MSI, which in turn is set from the BUILD value in
solenv/inc/minor.mk) has to increase.
- The target version (the one the patch upgrades to) should not be a
major version, ie something like 4.5->5.0 is discouraged by the
Microsoft documentation. A major version should be a full installation set.
Therefore it should be possible for us to (should the need arise) to
create patches 4.0.1 -> 4.0.2 AND also patches 4.0.1->4.1.0.
Here is how the two version numbers are specified (I call them source
and target):
- The source version is specified via the
instsetoo_native/util/openoffice.lst file via
Apache_OpenOffice
{
Settings
{
variables
{
...
PREVIOUS_VERSION 4.0.1
...
}
}
}
If that is missing, then the Perl script tries to determine the previous
version based on the target version.
- The target version is always the currently built version. The Perl
scripts that create the patches can handle a different target version.
I just have not yet added a way to explicitly specify it.
I am open for ideas to make this more usable.
-Andre
Regards,
Andrea.
-
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
