Re: [dev] In the Works: New OOo C++ Coding Standards
Hi Thorsten, >>A little bit of naming convention is certainly needed. Nobody wants to >>see a mixture of >> Foo aFoo(maFoo); >> CFoo foo(_foo); >> foo f_(f); >>even if it's in different modules. > > OK - so, what naming scheme would you propose? *gulp* No, please let's not start this. Chances for any result other than a religious war are pretty low. And as said, naming convensions isn't really what matters most. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Database http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] In the Works: New OOo C++ Coding Standards
Hi Niklas, you wrote: > Historically, modules also differ on a lot of other subjects. That's > why we need these guidelines in the first place. > Granted - but in my book, at least something like maName vs. m_aName needn't be standardized, just because we're standardizing on other stuff. > A little bit of naming convention is certainly needed. Nobody wants to > see a mixture of > Foo aFoo(maFoo); > CFoo foo(_foo); > foo f_(f); > even if it's in different modules. > OK - so, what naming scheme would you propose? Cheers, -- Thorsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: [dev] First release of the PengYou project
Hello Tom, On 12/14/06, Tom Schindl <[EMAIL PROTECTED]> wrote: Hi Jérémy, I testes the whole system and really looks promising (I'd like to include the whole in our SWT-Application). Might I suggest that you set up a mailing list to ask questions. I saw the webform at your the homepage but a mailing list or newsgroup would be a really great thing to ask questions (e.g. I'm having trouble to get the web-client working) and to give feedback. We already have a mailing list and a wiki Wiki : http://dev.pengyou-project.info/doku.php Mailing list : http://groups.google.com/group/pengyou-dev For now the mailing list is not accessible on the website but as a lot of people has been asking this information, it will soon figure on it. What is your SWT-Application? Is it open source? It could be great to have a SWT client for PengYou. Another great thing would be if the project could provide its SVN or CVS repository to access the sources and create patches for problems found in the projects. For now we don't have any public svn. We are currently working on migrating our private svn to google code svn here is the future url : http://code.google.com/p/pengyou/ We will send you an e-mail when it will be available. One more thing: The timestamp displayed in my openoffice-plugin always shows 1.1.1970 is this a known bug? Oh and a bugtracker would also be a great idea! Yes it's a known issue. You can already look at opened issues and open some issues at http://code.google.com/p/pengyou/ you need a google account for that, don't hesitate to ask us an invitation if needed. Tom Jérémy Bethmont schrieb: > I'm proud to announce the first version of the PengYou project: > > Web site: http://www.pengyou-project.info > Community web site: http://dev.pengyou-project.info > > PengYou is a Document Management System with innovative collaborative > functionalities which has an OpenOffice.org extension to edit the > documents. > > You can take a look to the demo video and if you want to give it a > try, go to the download page. > > Demo: http://www.pengyou-project.info/en/demo.php > Download: http://www.pengyou-project.info/en/download.php > > This project is released under the apache software License 2.0. The > team has spent a lot of time preparing this release, and I thank them > all for the energy and time they gave to this project. > > I'm the developer of the OpenOffice.org and I also want to thanks all > of the people of the list because you help me a lot! > > As an open source project, don't hesitate to give us your feedbaks, > report bugs and contact us if you want to join our team! > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Jérémy Bethmont - 李小杰 Dlili - Dalian Institute of Light Industry - China Epitech - European Institute of Technology - Paris PengYou Project - http://www.pengyou-project.info
Re: [dev] base
Glen Hinckley wrote: I was looking to work on base. I would like to do forms and reports. Not a lot to go on for the question... Perhaps this will get you started: http://www.pitonyak.org/database/AndrewBase.odt -- Andrew Pitonyak My Macro Document: http://www.pitonyak.org/AndrewMacro.odt My Book: http://www.hentzenwerke.com/catalog/oome.htm Info: http://www.pitonyak.org/oo.php See Also: http://documentation.openoffice.org/HOW_TO/index.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] In the Works: New OOo C++ Coding Standards
Thorsten Behrens wrote: You've hit the point exactly. There are some rules that require consistency and easy discernibility of local and member variables, and that's about all that needs to be said about that. Whether a member starts with m_ or with ma is largely irrelevant - as long as it is used consistently (module boundaries would be a natural border here). Historically, OOo modules differ on that, to some extent, and it would be IMO be a waste of time to enforce one single naming scheme. Historically, modules also differ on a lot of other subjects. That's why we need these guidelines in the first place. A little bit of naming convention is certainly needed. Nobody wants to see a mixture of Foo aFoo(maFoo); CFoo foo(_foo); foo f_(f); even if it's in different modules. Niklas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Bad PRJNAMEs
Stephan Bergmann schrieb: Attached are two quick and dirty scripts that worked for me (within Hamburg build environment on a Linux box) to find all the places where PRJNAME is probably set wrongly (see below). Feel free to fix those you feel responsible for. ./autodoc/source/parser/tokens/makefile.mk:PRJNAME=garden ./autodoc/source/parser_i/tokens/makefile.mk:PRJNAME=garden ./udm/source/unittest/makefile.mk:PRJNAME=cosv ... are my job, of course, Nikolai - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] In the Works: New OOo C++ Coding Standards
Kohei Yoshida schrieb: Also, variable naming scheme is not specified. Is that intended? I'm personally of the opinion that variable naming style is best left to the developers. So, if it's intentionally left out, I'd welcome it, Yes, it's intentionally left out. IMHO, if one tries to standardize things that are not really necessary, that would lessen the appreciation for the standards that are necessary. So we tried to leave out everything that does not really matter. As for naming schemes: Readability is important. How it is reached - there are many good ways. And as Thorsten wrote, consistency within module boundaries seems to be good enough. Nikolai - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] In the Works: New OOo C++ Coding Standards
On Thu, 2006-12-14 at 14:30 +0100, Eike Rathke wrote: > I think these configuration bits should go into and linked to the editor > articles instead, http://wiki.services.openoffice.org/wiki/Editor_Emacs Sounds highly sensible :-) I'll move them across. Regards, Michael. -- [EMAIL PROTECTED] <><, Pseudo Engineer, itinerant idiot - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] In the Works: New OOo C++ Coding Standards
Michael Meeks schrieb: On Tue, 2006-12-12 at 10:26 -0500, Kohei Yoshida wrote: The first thing that caught my eye is that, you guys are switching from using tab characters for indentation to using spaces. Me too; I added some "how to configure emacs" bits to the Details section, that makes it nice & easy to hack with emacs this way. Great - thanks! Nikolai - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] In the Works: New OOo C++ Coding Standards
Hi Michael, On Thursday, 2006-12-14 12:06:56 +, Michael Meeks wrote: > Me too; I added some "how to configure emacs" bits to the Details > section, that makes it nice & easy to hack with emacs this way. > How about a SlickEdit entry ? :-) I think these configuration bits should go into and linked to the editor articles instead, http://wiki.services.openoffice.org/wiki/Editor_Emacs and http://wiki.services.openoffice.org/wiki/Editor_Vim and http://wiki.services.openoffice.org/wiki/Editor_MSDev and then maybe SlickEdit, see also http://wiki.services.openoffice.org/wiki/Category:Developer_Tools Eike -- OOo/SO Calc core developer. Number formatter stricken i18n transpositionizer. OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't send personal mail to the [EMAIL PROTECTED] account, which I use for mailing lists only and don't read from outside Sun. Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] First release of the PengYou project
Hi Jérémy, I testes the whole system and really looks promising (I'd like to include the whole in our SWT-Application). Might I suggest that you set up a mailing list to ask questions. I saw the webform at your the homepage but a mailing list or newsgroup would be a really great thing to ask questions (e.g. I'm having trouble to get the web-client working) and to give feedback. Another great thing would be if the project could provide its SVN or CVS repository to access the sources and create patches for problems found in the projects. One more thing: The timestamp displayed in my openoffice-plugin always shows 1.1.1970 is this a known bug? Oh and a bugtracker would also be a great idea! Tom Jérémy Bethmont schrieb: > I'm proud to announce the first version of the PengYou project: > > Web site: http://www.pengyou-project.info > Community web site: http://dev.pengyou-project.info > > PengYou is a Document Management System with innovative collaborative > functionalities which has an OpenOffice.org extension to edit the > documents. > > You can take a look to the demo video and if you want to give it a > try, go to the download page. > > Demo: http://www.pengyou-project.info/en/demo.php > Download: http://www.pengyou-project.info/en/download.php > > This project is released under the apache software License 2.0. The > team has spent a lot of time preparing this release, and I thank them > all for the energy and time they gave to this project. > > I'm the developer of the OpenOffice.org and I also want to thanks all > of the people of the list because you help me a lot! > > As an open source project, don't hesitate to give us your feedbaks, > report bugs and contact us if you want to join our team! > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Build error in my build system with OOE680_m6
Hello Indraveni! Thank you for the detailed information. I will try your tipp ASAP, and I will send back infromation about solution. Best regards, KAMI Indraveni írta: HI, This is a common error. You can see the issue 64134. You can find it here http://www.openoffice.org/issues/show_bug.cgi?id=64134. In short, you can solve the problem by having a nas support. That is configure your source --with--system-nas (if you have nas installed). Also check whether libaudio-dev is installed. Then rebuild the OO. it may help you.. Good Luck Indraveni K KAMI <[EMAIL PROTECTED]> wrote: Hi! I wanted to build OOo 2.1 m6 on Linux (Sid) 4.0 base system. This is a newly set up of build system, so It can be a version or package error... I have got error message, the consol output is attached to this letter. Can someon help out the idea of possible problems? Thanks, KAMI - /ooo2/vcl/util dmake: Executing shell macro: $(PKGCONFIG) $(PKGCONFIG_PREFIX) --cflags $(PKGCONFIG_MODULES) dmake: Executing shell macro: $(PKGCONFIG) $(PKGCONFIG_PREFIX) --libs $(PKGCONFIG_MODULES) dmake: Executing shell macro: $(FIND) . -name "{$(subst,$($(WINVERSIONNAMES)_MAJOR),* $(subst,$(UPD)$(DLLPOSTFIX), $(SHL1TARGET)))}.xml" dmake: Executing shell macro: $(FIND) . -name "{$(subst,$($(WINVERSIONNAMES)_MAJOR),* $(subst,$(UPD)$(DLLPOSTFIX), $(SHL2TARGET)))}.xml" dmake: Executing shell macro: $(FIND) . -name "{$(subst,$($(WINVERSIONNAMES)_MAJOR),* $(subst,$(UPD)$(DLLPOSTFIX), $(SHL3TARGET)))}.xml" dmake: Executing shell macro: $(FIND) . -name "{$(subst,$($(WINVERSIONNAMES)_MAJOR),* $(subst,$(UPD)$(DLLPOSTFIX), $(SHL4TARGET)))}.xml" dmake: Executing shell macro: $(FIND) . -name "{$(subst,$($(WINVERSIONNAMES)_MAJOR),* $(subst,$(UPD)$(DLLPOSTFIX), $(SHL5TARGET)))}.xml" -- Making: ../unxlngi6.pro/lib/libvclplug_gen680li.so /usr/bin/ccache /usr/bin/g++ -Wl,-z,combreloc -Wl,-z,defs -Wl,-rpath,'$ORIGIN' -shared -L../unxlngi6.pro/lib -L../lib -L/ooo2/solenv/unxlngi6/lib -L/ooo2/solver/680/unxlngi6.pro/lib -L/ooo2/solenv/unxlngi6/lib -L/usr/local/jdk1.5.0-10/lib -L/usr/local/jdk1.5.0-10/jre/lib/i386 -L/usr/local/jdk1.5.0-10/jre/lib/i386/client -L/usr/local/jdk1.5.0-10/jre/lib/i386/native_threads -L/usr/lib ../unxlngi6.pro/slo/vclplug_gen_dflt_version.o ../unxlngi6.pro/slo/vclplug_gen_dflt_description.o -o ../unxlngi6.pro/lib/libvclplug_gen680li.so ../unxlngi6.pro/slo/FWS.o ../unxlngi6.pro/slo/salframe.o ../unxlngi6.pro/slo/salobj.o ../unxlngi6.pro/slo/salmenu.o ../unxlngi6.pro/slo/salgdi2.o ../unxlngi6.pro/slo/salbmp.o ../unxlngi6.pro/slo/salgdi.o ../unxlngi6.pro/slo/salvd.o ../unxlngi6.pro/slo/salogl.o ../unxlngi6.pro/slo/dtint.o ../unxlngi6.pro/slo/salcvt.o ../unxlngi6.pro/slo/xfont.o ../unxlngi6.pro/slo/xlfd_attr.o ../unxlngi6.pro/slo/xlfd_extd.o ../unxlngi6.pro/slo/xlfd_smpl.o ../unxlngi6.pro/slo/salgdi3.o ../unxlngi6.pro/slo/pspgraphics.o ../unxlngi6.pro/slo/salprnpsp.o ../unxlngi6.pro/slo/gcach_xpeer.o ../unxlngi6.pro/slo/i18n_cb.o ../unxlngi6.pro/slo/i18n_ic.o ../unxlngi6.pro/slo/i18n_im.o ../unxlngi6.pro/slo/i18n_xkb.o ../unxlngi6.pro/slo/i18n_wrp.o ../unxlngi6.pro/slo/i18n_status.o ../unxlngi6.pro/slo/i18n_keysym.o ../unxlngi6.pro/slo/saldata.o ../unxlngi6.pro/slo/saltimer.o ../unxlngi6.pro/slo/saldisp.o ../unxlngi6.pro/slo/salinst.o ../unxlngi6.pro/slo/salsys.o ../unxlngi6.pro/slo/soicon.o ../unxlngi6.pro/slo/sm.o ../unxlngi6.pro/slo/keysymnames.o ../unxlngi6.pro/slo/wmadaptor.o ../unxlngi6.pro/slo/salsound2.o ../unxlngi6.pro/slo/osssound.o ../unxlngi6.pro/slo/devaudiosound.o ../unxlngi6.pro/slo/audioconvert.o ../unxlngi6.pro/slo/rptpsound.o ../unxlngi6.pro/slo/nassound.o ../unxlngi6.pro/slo/pasfsound.o -lvcl680li -lpsp680li -lsot680li -lutl680li -ltl680li -lcomphelp4gcc3 -lucbhelper3gcc3 -luno_cppuhelpergcc3 -luno_cppu -lvos3gcc3 -luno_sal -Wl,-Bstatic -lXinerama -Wl,-Bdynamic -lsndfile -lportaudio -laudio -lXext -lSM -lICE -lX11 -ldl -ldl -lpthread -lm -Wl,-Bdynamic -lstlport_gcc /ooo2/solver/680/unxlngi6.pro/lib/libaudio.a(ConnSvr.o): In function `GetAuthorization': /ooo2/nas/unxlngi6.pro/misc/build/nas-1.6/lib/audio/ConnSvr.c:1981: undefined reference to `XauDisposeAuth' /ooo2/nas/unxlngi6.pro/misc/build/nas-1.6/lib/audio/ConnSvr.c:1832: undefined reference to `XauGetBestAuthByAddr' collect2: ld returned 1 exit status dmake: Error code 1, while making '../unxlngi6.pro/lib/libvclplug_gen680li.so' '---* tg_merge.mk *---' ERROR: Error 65280 occurred while making /ooo2/vcl/util dmake: Error code 1, while making 'build_instsetoo_native' '---* *---' - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Find out what India is talking about on - Yahoo! Answers India Send FREE SMS to your friend's mobile from Yahoo! Messenger Version 8. Get it NOW --
Re: [dev] Where to find pam.doc?
Hi Matthias, Hi Matthias, On 12/14/06 11:17, Matthias B. wrote: The file ooo_OOE680_m6_src/sw/source/core/crsr/pam.cxx contains the following comment /* 417 |* 418 |* SwPointAndMark 419 |* 420 |* BeschreibungPAM.DOC This looks as if there is a description of this class in a document pam.doc. Is this true? Where can I find this document? cvs tells me that this line has been written back in 1991. Maybe there once was a description for this file, but I'm quite sure that meanwhile it's lost in time and space. However, a SwPaM basically represents a pair of SwPosition, point and mark, which indicate a text range in the document, or a single position if point == mark. Hope this helps, Frank - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] Where to find pam.doc?
The file ooo_OOE680_m6_src/sw/source/core/crsr/pam.cxx contains the following comment /* 417 |* 418 |* SwPointAndMark 419 |* 420 |* BeschreibungPAM.DOC This looks as if there is a description of this class in a document pam.doc. Is this true? Where can I find this document? Matthias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Build error in my build system with OOE680_m6
HI, This is a common error. You can see the issue 64134. You can find it here http://www.openoffice.org/issues/show_bug.cgi?id=64134. In short, you can solve the problem by having a nas support. That is configure your source --with--system-nas (if you have nas installed). Also check whether libaudio-dev is installed. Then rebuild the OO. it may help you.. Good Luck Indraveni K KAMI <[EMAIL PROTECTED]> wrote: Hi! I wanted to build OOo 2.1 m6 on Linux (Sid) 4.0 base system. This is a newly set up of build system, so It can be a version or package error... I have got error message, the consol output is attached to this letter. Can someon help out the idea of possible problems? Thanks, KAMI - /ooo2/vcl/util dmake: Executing shell macro: $(PKGCONFIG) $(PKGCONFIG_PREFIX) --cflags $(PKGCONFIG_MODULES) dmake: Executing shell macro: $(PKGCONFIG) $(PKGCONFIG_PREFIX) --libs $(PKGCONFIG_MODULES) dmake: Executing shell macro: $(FIND) . -name "{$(subst,$($(WINVERSIONNAMES)_MAJOR),* $(subst,$(UPD)$(DLLPOSTFIX), $(SHL1TARGET)))}.xml" dmake: Executing shell macro: $(FIND) . -name "{$(subst,$($(WINVERSIONNAMES)_MAJOR),* $(subst,$(UPD)$(DLLPOSTFIX), $(SHL2TARGET)))}.xml" dmake: Executing shell macro: $(FIND) . -name "{$(subst,$($(WINVERSIONNAMES)_MAJOR),* $(subst,$(UPD)$(DLLPOSTFIX), $(SHL3TARGET)))}.xml" dmake: Executing shell macro: $(FIND) . -name "{$(subst,$($(WINVERSIONNAMES)_MAJOR),* $(subst,$(UPD)$(DLLPOSTFIX), $(SHL4TARGET)))}.xml" dmake: Executing shell macro: $(FIND) . -name "{$(subst,$($(WINVERSIONNAMES)_MAJOR),* $(subst,$(UPD)$(DLLPOSTFIX), $(SHL5TARGET)))}.xml" -- Making: ../unxlngi6.pro/lib/libvclplug_gen680li.so /usr/bin/ccache /usr/bin/g++ -Wl,-z,combreloc -Wl,-z,defs -Wl,-rpath,'$ORIGIN' -shared -L../unxlngi6.pro/lib -L../lib -L/ooo2/solenv/unxlngi6/lib -L/ooo2/solver/680/unxlngi6.pro/lib -L/ooo2/solenv/unxlngi6/lib -L/usr/local/jdk1.5.0-10/lib -L/usr/local/jdk1.5.0-10/jre/lib/i386 -L/usr/local/jdk1.5.0-10/jre/lib/i386/client -L/usr/local/jdk1.5.0-10/jre/lib/i386/native_threads -L/usr/lib ../unxlngi6.pro/slo/vclplug_gen_dflt_version.o ../unxlngi6.pro/slo/vclplug_gen_dflt_description.o -o ../unxlngi6.pro/lib/libvclplug_gen680li.so ../unxlngi6.pro/slo/FWS.o ../unxlngi6.pro/slo/salframe.o ../unxlngi6.pro/slo/salobj.o ../unxlngi6.pro/slo/salmenu.o ../unxlngi6.pro/slo/salgdi2.o ../unxlngi6.pro/slo/salbmp.o ../unxlngi6.pro/slo/salgdi.o ../unxlngi6.pro/slo/salvd.o ../unxlngi6.pro/slo/salogl.o ../unxlngi6.pro/slo/dtint.o ../unxlngi6.pro/slo/salcvt.o ../unxlngi6.pro/slo/xfont.o ../unxlngi6.pro/slo/xlfd_attr.o ../unxlngi6.pro/slo/xlfd_extd.o ../unxlngi6.pro/slo/xlfd_smpl.o ../unxlngi6.pro/slo/salgdi3.o ../unxlngi6.pro/slo/pspgraphics.o ../unxlngi6.pro/slo/salprnpsp.o ../unxlngi6.pro/slo/gcach_xpeer.o ../unxlngi6.pro/slo/i18n_cb.o ../unxlngi6.pro/slo/i18n_ic.o ../unxlngi6.pro/slo/i18n_im.o ../unxlngi6.pro/slo/i18n_xkb.o ../unxlngi6.pro/slo/i18n_wrp.o ../unxlngi6.pro/slo/i18n_status.o ../unxlngi6.pro/slo/i18n_keysym.o ../unxlngi6.pro/slo/saldata.o ../unxlngi6.pro/slo/saltimer.o ../unxlngi6.pro/slo/saldisp.o ../unxlngi6.pro/slo/salinst.o ../unxlngi6.pro/slo/salsys.o ../unxlngi6.pro/slo/soicon.o ../unxlngi6.pro/slo/sm.o ../unxlngi6.pro/slo/keysymnames.o ../unxlngi6.pro/slo/wmadaptor.o ../unxlngi6.pro/slo/salsound2.o ../unxlngi6.pro/slo/osssound.o ../unxlngi6.pro/slo/devaudiosound.o ../unxlngi6.pro/slo/audioconvert.o ../unxlngi6.pro/slo/rptpsound.o ../unxlngi6.pro/slo/nassound.o ../unxlngi6.pro/slo/pasfsound.o -lvcl680li -lpsp680li -lsot680li -lutl680li -ltl680li -lcomphelp4gcc3 -lucbhelper3gcc3 -luno_cppuhelpergcc3 -luno_cppu -lvos3gcc3 -luno_sal -Wl,-Bstatic -lXinerama -Wl,-Bdynamic -lsndfile -lportaudio -laudio -lXext -lSM -lICE -lX11 -ldl -ldl -lpthread -lm -Wl,-Bdynamic -lstlport_gcc /ooo2/solver/680/unxlngi6.pro/lib/libaudio.a(ConnSvr.o): In function `GetAuthorization': /ooo2/nas/unxlngi6.pro/misc/build/nas-1.6/lib/audio/ConnSvr.c:1981: undefined reference to `XauDisposeAuth' /ooo2/nas/unxlngi6.pro/misc/build/nas-1.6/lib/audio/ConnSvr.c:1832: undefined reference to `XauGetBestAuthByAddr' collect2: ld returned 1 exit status dmake: Error code 1, while making '../unxlngi6.pro/lib/libvclplug_gen680li.so' '---* tg_merge.mk *---' ERROR: Error 65280 occurred while making /ooo2/vcl/util dmake: Error code 1, while making 'build_instsetoo_native' '---* *---' - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Find out what India is talking about on - Yahoo! Answers India Send FREE SMS to your friend's mobile from Yahoo! Messenger Version 8. Get it NOW
Re: [dev] Build error in my build system with OOE680_m6
Hi, /ooo2/nas/unxlngi6.pro/misc/build/nas-1.6/lib/audio/ConnSvr.c:1981: undefined reference to `XauDisposeAuth' /ooo2/nas/unxlngi6.pro/misc/build/nas-1.6/lib/audio/ConnSvr.c:1832: undefined reference to `XauGetBestAuthByAddr' please enter on or the other string in quotes into IssueZilla search. -- Pavel Janík [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] Build error in my build system with OOE680_m6
Hi! I wanted to build OOo 2.1 m6 on Linux (Sid) 4.0 base system. This is a newly set up of build system, so It can be a version or package error... I have got error message, the consol output is attached to this letter. Can someon help out the idea of possible problems? Thanks, KAMI - /ooo2/vcl/util dmake: Executing shell macro: $(PKGCONFIG) $(PKGCONFIG_PREFIX) --cflags $(PKGCONFIG_MODULES) dmake: Executing shell macro: $(PKGCONFIG) $(PKGCONFIG_PREFIX) --libs $(PKGCONFIG_MODULES) dmake: Executing shell macro: $(FIND) . -name "{$(subst,$($(WINVERSIONNAMES)_MAJOR),* $(subst,$(UPD)$(DLLPOSTFIX), $(SHL1TARGET)))}.xml" dmake: Executing shell macro: $(FIND) . -name "{$(subst,$($(WINVERSIONNAMES)_MAJOR),* $(subst,$(UPD)$(DLLPOSTFIX), $(SHL2TARGET)))}.xml" dmake: Executing shell macro: $(FIND) . -name "{$(subst,$($(WINVERSIONNAMES)_MAJOR),* $(subst,$(UPD)$(DLLPOSTFIX), $(SHL3TARGET)))}.xml" dmake: Executing shell macro: $(FIND) . -name "{$(subst,$($(WINVERSIONNAMES)_MAJOR),* $(subst,$(UPD)$(DLLPOSTFIX), $(SHL4TARGET)))}.xml" dmake: Executing shell macro: $(FIND) . -name "{$(subst,$($(WINVERSIONNAMES)_MAJOR),* $(subst,$(UPD)$(DLLPOSTFIX), $(SHL5TARGET)))}.xml" -- Making: ../unxlngi6.pro/lib/libvclplug_gen680li.so /usr/bin/ccache /usr/bin/g++ -Wl,-z,combreloc -Wl,-z,defs -Wl,-rpath,'$ORIGIN' -shared -L../unxlngi6.pro/lib -L../lib -L/ooo2/solenv/unxlngi6/lib -L/ooo2/solver/680/unxlngi6.pro/lib -L/ooo2/solenv/unxlngi6/lib -L/usr/local/jdk1.5.0-10/lib -L/usr/local/jdk1.5.0-10/jre/lib/i386 -L/usr/local/jdk1.5.0-10/jre/lib/i386/client -L/usr/local/jdk1.5.0-10/jre/lib/i386/native_threads -L/usr/lib ../unxlngi6.pro/slo/vclplug_gen_dflt_version.o ../unxlngi6.pro/slo/vclplug_gen_dflt_description.o -o ../unxlngi6.pro/lib/libvclplug_gen680li.so ../unxlngi6.pro/slo/FWS.o ../unxlngi6.pro/slo/salframe.o ../unxlngi6.pro/slo/salobj.o ../unxlngi6.pro/slo/salmenu.o ../unxlngi6.pro/slo/salgdi2.o ../unxlngi6.pro/slo/salbmp.o ../unxlngi6.pro/slo/salgdi.o ../unxlngi6.pro/slo/salvd.o ../unxlngi6.pro/slo/salogl.o ../unxlngi6.pro/slo/dtint.o ../unxlngi6.pro/slo/salcvt.o ../unxlngi6.pro/slo/xfont.o ../unxlngi6.pro/slo/xlfd_attr.o ../unxlngi6.pro/slo/xlfd_extd.o ../unxlngi6.pro/slo/xlfd_smpl.o ../unxlngi6.pro/slo/salgdi3.o ../unxlngi6.pro/slo/pspgraphics.o ../unxlngi6.pro/slo/salprnpsp.o ../unxlngi6.pro/slo/gcach_xpeer.o ../unxlngi6.pro/slo/i18n_cb.o ../unxlngi6.pro/slo/i18n_ic.o ../unxlngi6.pro/slo/i18n_im.o ../unxlngi6.pro/slo/i18n_xkb.o ../unxlngi6.pro/slo/i18n_wrp.o ../unxlngi6.pro/slo/i18n_status.o ../unxlngi6.pro/slo/i18n_keysym.o ../unxlngi6.pro/slo/saldata.o ../unxlngi6.pro/slo/saltimer.o ../unxlngi6.pro/slo/saldisp.o ../unxlngi6.pro/slo/salinst.o ../unxlngi6.pro/slo/salsys.o ../unxlngi6.pro/slo/soicon.o ../unxlngi6.pro/slo/sm.o ../unxlngi6.pro/slo/keysymnames.o ../unxlngi6.pro/slo/wmadaptor.o ../unxlngi6.pro/slo/salsound2.o ../unxlngi6.pro/slo/osssound.o ../unxlngi6.pro/slo/devaudiosound.o ../unxlngi6.pro/slo/audioconvert.o ../unxlngi6.pro/slo/rptpsound.o ../unxlngi6.pro/slo/nassound.o ../unxlngi6.pro/slo/pasfsound.o -lvcl680li -lpsp680li -lsot680li -lutl680li -ltl680li -lcomphelp4gcc3 -lucbhelper3gcc3 -luno_cppuhelpergcc3 -luno_cppu -lvos3gcc3 -luno_sal -Wl,-Bstatic -lXinerama -Wl,-Bdynamic -lsndfile -lportaudio -laudio -lXext -lSM -lICE -lX11 -ldl -ldl -lpthread -lm -Wl,-Bdynamic -lstlport_gcc /ooo2/solver/680/unxlngi6.pro/lib/libaudio.a(ConnSvr.o): In function `GetAuthorization': /ooo2/nas/unxlngi6.pro/misc/build/nas-1.6/lib/audio/ConnSvr.c:1981: undefined reference to `XauDisposeAuth' /ooo2/nas/unxlngi6.pro/misc/build/nas-1.6/lib/audio/ConnSvr.c:1832: undefined reference to `XauGetBestAuthByAddr' collect2: ld returned 1 exit status dmake: Error code 1, while making '../unxlngi6.pro/lib/libvclplug_gen680li.so' '---* tg_merge.mk *---' ERROR: Error 65280 occurred while making /ooo2/vcl/util dmake: Error code 1, while making 'build_instsetoo_native' '---* *---' - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]