search for: tcl8

...: creating java/native/Makefile config.status: creating java/org/Makefile config.status: creating java/org/xapian/Makefile config.status: creating java/org/xapian/errors/Makefile config.status: creating java/org/xapian/examples/Makefile config.status: creating guile/Makefile config.status: creating tcl8/Makefile config.status: creating xapian-bindings.spec config.status: creating config.h config.status: config.h is unchanged config.status: executing depfiles commands # make make all-recursive make[1]: Entering directory `/root/compile/xapian/xapian-bindings-0.8.3' Making all in tcl8 make[2]...

On Tue, May 11, 2004 at 06:11:36PM +0100, Richard Boulton wrote: > "xapian-config --cxxflags" assumes that it doesn't need to emit > -I/usr/include in this situation (presumably on the basis that > any sane C compiler will already have that on its path). Worse, passing -I/usr/include causes problems with some versions of GCC on some platforms as GCC generates

I've now uploaded Xapian 1.0.1, which you can download from the usual place: http://www.xapian.org/download.php This release mainly comprises bug fixes and performance improvements. The "simple" examples (for both C++ and the bindings) have also been overhauled and now use the QueryParser and TermGenerator classes, which makes for simpler examples and should better reflect

I've now uploaded Xapian 1.0.1, which you can download from the usual place: http://www.xapian.org/download.php This release mainly comprises bug fixes and performance improvements. The "simple" examples (for both C++ and the bindings) have also been overhauled and now use the QueryParser and TermGenerator classes, which makes for simpler examples and should better reflect

Hello :-) The instructions regards Tim Brody's packages are incomplete in that rpm-eprints-org-key is needed by rpm-eprints-org-xapian-5-1.noarch. The RPM for rpm-eprints-org-key is at http://rpm.eprints.org/rpm-eprints-org-key-1-1.noarch.rpm Best Charles

...the core until now, and it would be easier to remove them at the same time as removing the equivalent from the core. Finally, I'm not convinced that the replacement for Stem::stem_word() of using operator() will work for all the bindings - checking whether it can be accessed from PHP, Ruby, Tcl8, and CSharp would be useful (ideally, changing smoketest and the examples to demonstrate how). It works in Python, though. ;-) -- Richard

...Tikanga - added for OMSA install Any suggestions? Thanks! p.s. Here are the packages and version numbers I installed using YUM: Downloading Packages: (1/10): xapian-bindings-1.2.5-1.i386.rpm | 111 kB 00:00 (2/10): xapian-bindings-php-1.2.5-1.i386.rpm | 136 kB 00:00 (3/10): xapian-bindings-tcl8-1.2.5-1.i386.rpm | 166 kB 00:00 (4/10): xapian-bindings-ruby-1.2.5-1.i386.rpm | 201 kB 00:00 (5/10): ruby-1.8.5-29.el5_9.i386.rpm | 279 kB 00:00 (6/10): xapian-omega-1.2.5-1.i386.rpm | 333 kB 00:00 (7/10): xapian-bindings-perl-1.2.5-1.i386.rpm | 336 kB 00:00 (8/10): xapian-bindings-python-1.2....

In trying to install the pbatR package, I was greeted with the error Error: package 'tcltk' does not have a name space Execution halted Directly installing the package tcltk2 returned the following error: Loading required package: tcltk Error in firstlib(which.lib.loc, package) : Tcl/Tk support is not available on this system I have seen from previous posts that tcl/tk must be

Currently, the SWIG generated bindings catch exceptions raised by Xapian and rethrow them using the standard SWIG error types: for example, if any Xapian::DatabaseError exception is raised, SWIG will use its standard SWIG_IOError error type to report the error. In Python, this leads to code like the following: try: db.get_document(1) except RuntimeError, e: if

Currently, the SWIG generated bindings catch exceptions raised by Xapian and rethrow them using the standard SWIG error types: for example, if any Xapian::DatabaseError exception is raised, SWIG will use its standard SWIG_IOError error type to report the error. In Python, this leads to code like the following: try: db.get_document(1) except RuntimeError, e: if

On 08/25/2013 05:02 PM, Olly Betts wrote: > So the simple fix is > probably just to install the perl-Search-Xapian RPM instead. Thanks, the Centos 6 repos don't have that rpm and the http://xapian.org/download page seems to only cover the XS bindings, if I am reading this correctly: But I was able to remove the rpm packages and compile and install the core and swig from source.

I discovered, while trying to set up Tcl bindings for Notmuch (https://notmuchmail.org/), which uses Xapian, that flintlock was not being locked (I had lost updates). I then found that opening a Xapian database for writing directly via the Xapian Tcl bindings also silently fails to lock flintlock. I have taken a copy of flint_lock.cc to play with, and I find that it locks the file when called

...http://mail.gnu.org/archive/html/autoconf/2002-12/msg00098.html With your fix to use $PYTHON instead of python, test -x isn't actually needed AFAICS - the case statement will just get empty stdout and so the bindings will be disabled. I tested "./configure TCLSH=/no/such/path" and tcl8 doesn't get put in SUBDIRS in Makefile. Are you OK with reverting this? Cheers, Olly

...i All, I've built RPM packages for Xapian 1.2.7 for RHEL 6. Instructions: su rpm -ivh http://rpm.eprints.org/rpm-eprints-org-key-1-1.noarch.rpm rpm -ivh http://rpm.eprints.org/xapian/6/noarch/rpm-eprints-org-xapian-6-1.noarch.rpm yum update yum install xapian-omega xapian-bindings-{php,python,tcl8,perl,ruby} perl-Search-Xapian is available for those not using the SWIG bindings. I had to add to the omega .spec %files section: %{_libdir}/%{name}/bin/outlookmsg2html So I could build xapian-omega. Even though Olly promised to fix that two versions ago :-) NB Xapian 1.0.20 is available from E...

...o that the C++ object doesn't either, and the changes don't get committed. I would try calling close() on the WritableDatabase object before your script exits. There's some discussion of this in the Tcl bindings docs (section "Destructors"): https://xapian.org/docs/bindings/tcl8/ Cheers, Olly

Non of these errors occured in earliers versions of R. > library(tcltk) /usr/lib/dld.sl: Unresolved symbol: Tcl_GetVar2Ex (code) from /opt_local/opt/R/lib/R/library/tcltk/libs/tcltk.sl /usr/lib/dld.sl: Unresolved symbol: Tcl_GetString (code) from /opt_local/opt/R/lib/R/library/tcltk/libs/tcltk.sl /usr/lib/dld.sl: Unresolved symbol: Tcl_SetVar2Ex (code) from

.../www.tcl.tk and to install them (the -dev packages also), but the error hold over. 2. To install the previous releases (version: 8.4) for these packages. The error hold over. 3. To set the environment variables 'TCL_LIBRARY' and 'TK_LIBRARY', in this mode: TCL_LIBRARY=/usr/local/lib/tcl8.5 * (or 8.4)* TK_LIBRARY=/usr/lib/tk8.5 *(or 8.4)* but the error hold over. 4.Therefore, after this modifications, i uninstalled R and I installed again it. I try to do this both without setting environment variables and setting it. The error hold over. I look for a solution. Thank you...

Hi, I compiled R-1.1.1 in 2 machines -- one running SuSE 6.3 and the other 6.4. If I do: > plot(jj) the graphics window pops up in 6.3, but not in 6.4 Also, doing x11() is of no help, it merely replicates the behavior above. I should add that being root (xhost + and su) in 6.4 does not help. Postscript works just fine. Additional details: XFree3.3.6, KDE1.1.2 (or KDE2.0 Beta 4), updated

Hi, I compiled R-1.1.1 in 2 machines -- one running SuSE 6.3 and the other 6.4. If I do: > plot(jj) the graphics window pops up in 6.3, but not in 6.4 Also, doing x11() is of no help, it merely replicates the behavior above. I should add that being root (xhost + and su) in 6.4 does not help. Postscript works just fine. Additional details: XFree3.3.6, KDE1.1.2 (or KDE2.0 Beta 4), updated

A short note: this message comes as a public reply to a discussion about xapian-bindings, that is why it can look a little bit incomplete... however the problem for now was to modify the xapian-core distribution so that there are symbols #defined (or maybe #undefined) to reflect what backends were available in the library. As I said to Olly, I'm a complete newbie at Autotools (and SWIG), so