SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Sorry to hear that. It compiles clean as a whistle here with the three apps mentioned and I hope that it's not an additional dependency I incidently met. I would check the configure output -- are there warnings, where are "no"s as result found ...
Only difference: I installed all four apps to /usr instead of /usr/local like you seem you did. Had to change the Makefile for antiword (changed line to "GLOBAL_INSTALL_DIR = /usr/bin" where /usr/local/bin was hardcoded) and configured the others with --prefix=/usr. But honestly I don't know if that makes a big difference.
EDIT: This program has by far the shortest configure output I've seen. If you want to compare ... aspell and xapian-config are the only ones that seem to be checked here:
Code:
configure: WARNING: you should use --build, --host, --target
checking for aspell... /usr/bin/aspell
withAspell = yes
configure: inotify monitoring disabled
checking for i486-slackware-linux-gcc... i486-slackware-linux-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether i486-slackware-linux-gcc accepts -g... yes
checking for i486-slackware-linux-gcc option to accept ANSI C... none needed
checking for iconv_open in -liconv... no
checking for iconv_open in -liconv... no
checking for iconv_open in -lc... yes
checking for xapian-config... /usr/bin/xapian-config
configure: rcl_cv_qt4 no
checking for qmake... /usr/lib/qt/bin/qmake
checking how to run the C preprocessor... i486-slackware-linux-gcc -E
checking for X... libraries /usr/X11/lib, headers
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
configure: creating ./config.status
config.status: creating mk/localdefs
config.status: creating recollinstall
config.status: creating Makefile
config.status: creating sampleconf/recoll.conf
config.status: creating qtgui/recoll.pro
config.status: creating common/autoconfig.h
Last edited by titopoquito; 05-18-2007 at 03:14 AM.
checking for aspell... /usr/bin/aspell
withAspell = yes
configure: inotify monitoring disabled
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for iconv_open in -liconv... yes
checking for xapian-config... /usr/local/bin/xapian-config
configure: rcl_cv_qt4 no
checking for qmake... /usr/lib/qt/bin/qmake
checking how to run the C preprocessor... gcc -E
checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
configure: creating ./config.status
config.status: creating mk/localdefs
config.status: creating recollinstall
config.status: creating Makefile
config.status: creating sampleconf/recoll.conf
config.status: creating qtgui/recoll.pro
config.status: creating common/autoconfig.h
config.status: common/autoconfig.h is unchanged
I don't see anything strange in it.
Quote:
Originally Posted by H_TeXMeX_H
Try changing line 80 from:
Code:
(char **)&rp,
to:
Code:
(const char **)&rp,
It might just work ... dunno if this will introduce a bug tho.
You mean of the makefile?
Don't see those lines there anywhere, except for lines 22-24:
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,644
Rep:
Quote:
Originally Posted by adriv
OK, so here's the output from ./configure:
Code:
checking for aspell... /usr/bin/aspell
withAspell = yes
configure: inotify monitoring disabled
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for iconv_open in -liconv... yes
checking for xapian-config... /usr/local/bin/xapian-config
configure: rcl_cv_qt4 no
checking for qmake... /usr/lib/qt/bin/qmake
checking how to run the C preprocessor... gcc -E
checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
configure: creating ./config.status
config.status: creating mk/localdefs
config.status: creating recollinstall
config.status: creating Makefile
config.status: creating sampleconf/recoll.conf
config.status: creating qtgui/recoll.pro
config.status: creating common/autoconfig.h
config.status: common/autoconfig.h is unchanged
I don't see anything strange in it.
I don't see anything too, looks basically the same
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,644
Rep:
It's not a real solution to the error you get, but I could send you my Slackbuild scripts I used or even the packages of all four via email. Don't know how to solve the error other way ...
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,644
Rep:
Generally a good (or very good) idea. The problem is I don't have the time now to clean them up from highly idiosyncratic stuff and get them tidy so that they would get accepted at linuxpackages.net or slackbuild.org. Maybe next week, but definitely not this weekend And I guess it would take some more time for them to be reviewed and accepted.
I am interested in recoll myself, so the review time at SlackBuilds.org would be fairly short :-) In fact I was already prepared to build the packages for my own repository (http://www.slackware.com/~alien/slackbuilds/) but to have your SlackBuilds on SBo is a good addition.
It's not a real solution to the error you get, but I could send you my Slackbuild scripts I used or even the packages of all four via email. Don't know how to solve the error other way ...
I also got the same error on compiling. would you please do me a favor to send the package and slackbuild to my email address? My Email: kitelau at gmail dot com
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,644
Rep:
Ok, I will try to prepare the scripts for submission on slackbuild.org, so that others could get them if they want. kite, I will send you the packages, then maybe in some days the build scripts will be available anyway ...
If it absolutely won't compile, you could try 'rpm2tgz' then 'installpkg' on an rpm build of it.
Why didn't I think of that?
But, a little later... no such luck.
I tried src2pkg as well and that didn't work either.
Quote:
Originally Posted by titopoquito
It's not a real solution to the error you get, but I could send you my Slackbuild scripts I used or even the packages of all four via email. Don't know how to solve the error other way ...
Thanks!
I'll wait for the script at SlackBuilds.org, there's no hurry. And I have just a hunch that it won't last very long before we see it there.
By the way: I tried Kat, but that's horrible. Eats up all your memory and Slack is sloooooooooooooooooooooow with Kat on the background (not to mention the two crashes of Kat).
So I got rid of it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.