Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Beagle Support and Installation help
View unanswered posts
View posts from last 24 hours

Goto page 1, 2, 3, 4  Next  
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
curtis119
Bodhisattva
Bodhisattva


Joined: 10 Mar 2003
Posts: 2160
Location: Phoenix, AZ USA, North America, Earth, SOL System, Milky Way, The Universe, The Cosmos, and Beyond.

PostPosted: Thu Feb 09, 2006 2:27 am    Post subject: Beagle Support and Installation help Reply with quote

This is a continuation of the Beagle HOWTO. All support questions concerning Beagle (the desktop search application) should go here.
_________________
Gentoo: it's like wiping your ass with silk.
Back to top
View user's profile Send private message
matttions
Guru
Guru


Joined: 19 Jul 2004
Posts: 338

PostPosted: Mon Feb 13, 2006 11:12 pm    Post subject: Reply with quote

I'm trying to install beagle from portage but I get this error
Code:
i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/lib/mozilla/include/gtkembedmoz -I/usr/lib/mozilla/include -I/usr/lib/mozilla/include/xpcom -I/usr/lib/mozilla/include/string -I/usr/lib/mozilla/include/nspr -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/atk-1.0 -I/usr/lib/mozilla/include/content -I/usr/lib/mozilla/include/dom -I/usr/lib/mozilla/include/find -I/usr/lib/mozilla/include/locale -I/usr/lib/mozilla/include/webbrwsr -I/usr/lib/mozilla/include/string -I/usr/lib/mozilla/include/pref -I/usr/lib/mozilla/include/gfx -I/usr/lib/mozilla/include/embedstring -I/usr/lib/mozilla/include/chrome -DALLOW_PRIVATE_API -DMOZILLA_HOME=\"/usr/lib/mozilla\" -include /usr/lib/mozilla/include/mozilla-config.h -I/usr/include/wv -I/usr/include/libgsf-1 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -O3 -march=pentium-m -pipe -fomit-frame-pointer -MT wv1-glue.lo -MD -MP -MF .deps/wv1-glue.Tpo -c wv1-glue.c -o wv1-glue.o >/dev/null 2>&1
/bin/sh ../libtool --tag=CC --mode=link i686-pc-linux-gnu-gcc  -O3 -march=pentium-m -pipe -fomit-frame-pointer  -Wl,-O1 -o libbeagleglue.la -rpath /usr/lib/beagle  beagled-utils.lo ioprio-glue.lo screensaver-glue.lo vmsize-glue.lo inotify-glue.lo wv1-glue.lo -lgdk-x11-2.0 -lgdk_pixbuf-2.0 -lm -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0   -lSM -lICE  -lX11 -lXss  -lwv -lwmf -lwmflite -lfreetype -lSM -lICE -lX11 -lexpat -ljpeg -lgsf-1 -lgobject-2.0 -lxml2 -lglib-2.0 -lpng -lz -lm
grep: /opt/fdo/lib/libX11.la: No such file or directory
/bin/sed: can't read /opt/fdo/lib/libX11.la: No such file or directory
libtool: link: `/opt/fdo/lib/libX11.la' is not a valid libtool archive
make[2]: *** [libbeagleglue.la] Error 1
make[2]: Leaving directory `/var/tmp/portage/beagle-0.1.2/work/beagle-0.1.2/glue'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/beagle-0.1.2/work/beagle-0.1.2'
make: *** [all] Error 2

!!! ERROR: app-misc/beagle-0.1.2 failed.
Call stack:
  ebuild.sh, line 1894:   Called dyn_compile
  ebuild.sh, line 941:   Called src_compile

!!! Make failed


But I have the last unstable Xorg installed and more over
Code:
emerge libX11 -pv

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild   R   ] x11-libs/libX11-1.0.0-r1  USE="ipv6 -debug" 0 kB


Why beagle is still searching thing in
Code:
/opt/fdo/lib/*

_________________
gentoo ... l'unico pinguino da corsa
Back to top
View user's profile Send private message
evan-
n00b
n00b


Joined: 13 Aug 2003
Posts: 63
Location: Italy

PostPosted: Tue Feb 14, 2006 12:28 am    Post subject: Reply with quote

i have this problem emerging beagle

Code:

(cd .libs && rm -f libbeagleglue.la && ln -s ../libbeagleglue.la libbeagleglue.la)
if /bin/sh ../libtool --tag=CXX --mode=compile i686-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/lib/mozilla-firefox/include/gtkembedmoz -I/usr/lib/mozilla-firefox/include -I/usr/lib/mozilla-firefox/include/xpcom -I/usr/lib/mozilla-firefox/include/string -I/usr/include/nspr   -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/atk-1.0  -I/usr/lib/mozilla-firefox/include/content -I/usr/lib/mozilla-firefox/include/dom -I/usr/lib/mozilla-firefox/include/find -I/usr/lib/mozilla-firefox/include/locale -I/usr/lib/mozilla-firefox/include/webbrwsr -I/usr/lib/mozilla-firefox/include/string -I/usr/lib/mozilla-firefox/include/pref -I/usr/lib/mozilla-firefox/include/gfx -I/usr/lib/mozilla-firefox/include/embedstring -I/usr/lib/mozilla-firefox/include/chrome -DALLOW_PRIVATE_API -DMOZILLA_HOME=\""/usr/lib/mozilla-firefox\"" -include /usr/lib/mozilla-firefox/include/mozilla-config.h     -O2 -march=pentium3 -pipe -fomit-frame-pointer -mmmx -msse -msse2 -mfpmath=sse -fshort-wchar -I/usr/lib/mozilla-firefox/include -I/usr/lib/mozilla-firefox/include/embedstring -I/usr/lib/mozilla-firefox/include/content -I/usr/lib/mozilla-firefox/include/necko -I/usr/lib/mozilla-firefox/include -I/usr/lib/mozilla-firefox/include/xpcom -I/usr/lib/mozilla-firefox/include/string -I/usr/include/nspr   -MT gecko-utils.lo -MD -MP -MF ".deps/gecko-utils.Tpo" -c -o gecko-utils.lo gecko-utils.cpp; \
then mv -f ".deps/gecko-utils.Tpo" ".deps/gecko-utils.Plo"; else rm -f ".deps/gecko-utils.Tpo"; exit 1; fi
 i686-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/lib/mozilla-firefox/include/gtkembedmoz -I/usr/lib/mozilla-firefox/include -I/usr/lib/mozilla-firefox/include/xpcom -I/usr/lib/mozilla-firefox/include/string -I/usr/include/nspr -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/atk-1.0 -I/usr/lib/mozilla-firefox/include/content -I/usr/lib/mozilla-firefox/include/dom -I/usr/lib/mozilla-firefox/include/find -I/usr/lib/mozilla-firefox/include/locale -I/usr/lib/mozilla-firefox/include/webbrwsr -I/usr/lib/mozilla-firefox/include/string -I/usr/lib/mozilla-firefox/include/pref -I/usr/lib/mozilla-firefox/include/gfx -I/usr/lib/mozilla-firefox/include/embedstring -I/usr/lib/mozilla-firefox/include/chrome -DALLOW_PRIVATE_API -DMOZILLA_HOME=\"/usr/lib/mozilla-firefox\" -include /usr/lib/mozilla-firefox/include/mozilla-config.h -O2 -march=pentium3 -pipe -fomit-frame-pointer -mmmx -msse -msse2 -mfpmath=sse -fshort-wchar -I/usr/lib/mozilla-firefox/include -I/usr/lib/mozilla-firefox/include/embedstring -I/usr/lib/mozilla-firefox/include/content -I/usr/lib/mozilla-firefox/include/necko -I/usr/lib/mozilla-firefox/include -I/usr/lib/mozilla-firefox/include/xpcom -I/usr/lib/mozilla-firefox/include/string -I/usr/include/nspr -MT gecko-utils.lo -MD -MP -MF .deps/gecko-utils.Tpo -c gecko-utils.cpp  -fPIC -DPIC -o .libs/gecko-utils.o
gecko-utils.cpp: In function `gboolean gecko_prefs_set_string(const gchar*, const gchar*)':
gecko-utils.cpp:76: error: `nsCOMPtr' was not declared in this scope
gecko-utils.cpp:76: error: expected primary-expression before '>' token
gecko-utils.cpp:76: error: `prefService' was not declared in this scope
gecko-utils.cpp:77: error: `do_GetService' was not declared in this scope
gecko-utils.cpp:78: error: expected primary-expression before '>' token
gecko-utils.cpp:78: error: `pref' was not declared in this scope
gecko-utils.cpp:79: error: `getter_AddRefs' was not declared in this scope
gecko-utils.cpp: In function `gboolean gecko_prefs_set_int(const gchar*, gint)':
gecko-utils.cpp:93: error: `nsCOMPtr' was not declared in this scope
gecko-utils.cpp:93: error: expected primary-expression before '>' token
gecko-utils.cpp:93: error: `prefService' was not declared in this scope
gecko-utils.cpp:94: error: `do_GetService' was not declared in this scope
gecko-utils.cpp:95: error: expected primary-expression before '>' token
gecko-utils.cpp:95: error: `pref' was not declared in this scope
gecko-utils.cpp:96: error: `getter_AddRefs' was not declared in this scope
gecko-utils.cpp: In function `nsresult getUILang(nsAString&)':
gecko-utils.cpp:141: error: `nsCOMPtr' was not declared in this scope
gecko-utils.cpp:141: error: expected primary-expression before '>' token
gecko-utils.cpp:141: error: `localeService' was not declared in this scope
gecko-utils.cpp:141: error: `do_GetService' was not declared in this scope
make[2]: *** [gecko-utils.lo] Error 1
make[2]: Leaving directory `/var/tmp/portage/beagle-0.1.2/work/beagle-0.1.2/glue'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/beagle-0.1.2/work/beagle-0.1.2'
make: *** [all] Error 2

!!! ERROR: app-misc/beagle-0.1.2 failed.
Call stack:
  ebuild.sh, line 1894:   Called dyn_compile
  ebuild.sh, line 941:   Called src_compile

!!! Make failed
!!! If you need support, post the topmost build error, and the call stack if relevant.


do i miss any dependencies?
Back to top
View user's profile Send private message
matttions
Guru
Guru


Joined: 19 Jul 2004
Posts: 338

PostPosted: Sat Feb 18, 2006 5:43 pm    Post subject: Reply with quote

Well finnally I get beagle installed and compiled... but

I got this error
Code:
gmime-CRITICAL **: internet_address_get_addr: assertion `ia->type != INTERNET_AD DRESS_GROUP' failed


And the beagle abort.. any ideas ?
_________________
gentoo ... l'unico pinguino da corsa
Back to top
View user's profile Send private message
kwyjibo
n00b
n00b


Joined: 21 Feb 2005
Posts: 14
Location: Switzerland

PostPosted: Tue Feb 21, 2006 10:24 pm    Post subject: Reply with quote

followed this guide to install beagle, but i ran into the following error:

Code:
./Lucene.Net/QueryParser/Precedence/PrecedenceQueryParserTokenManager.cs(1263,1): warning CS0162: Unreachable code detected
./Lucene.Net/QueryParser/Precedence/PrecedenceQueryParserTokenManager.cs(1173,17): warning CS0219: The variable `kind' is assigned but its value is never used
./Lucene.Net/QueryParser/Precedence/PrecedenceQueryParserTokenManager.cs(1174,19): warning CS0219: The variable `specialToken' is assigned but its value is never used
./Lucene.Net/QueryParser/Precedence/PrecedenceQueryParser.cs(698,13): warning CS0162: Unreachable code detected
./Lucene.Net/QueryParser/Precedence/PrecedenceQueryParser.cs(746,13): warning CS0162: Unreachable code detected
./Lucene.Net/QueryParser/Precedence/PrecedenceQueryParser.cs(804,1): warning CS0162: Unreachable code detected
./Lucene.Net/QueryParser/Precedence/PrecedenceQueryParser.cs(849,1): warning CS0162: Unreachable code detected
./Lucene.Net/QueryParser/Precedence/PrecedenceQueryParser.cs(935,13): warning CS0162: Unreachable code detected
./Lucene.Net/QueryParser/Precedence/PrecedenceQueryParser.cs(1296,13): warning CS0162: Unreachable code detected
./Lucene.Net/QueryParser/QueryParser.cs(804,13): warning CS0162: Unreachable code detected
./Lucene.Net/QueryParser/QueryParser.cs(852,13): warning CS0162: Unreachable code detected
./Lucene.Net/QueryParser/QueryParser.cs(897,1): warning CS0162: Unreachable code detected
./Lucene.Net/QueryParser/QueryParser.cs(983,13): warning CS0162: Unreachable code detected
./Lucene.Net/QueryParser/QueryParser.cs(1348,13): warning CS0162: Unreachable code detected
./Lucene.Net/QueryParser/QueryParser.cs(992,18): warning CS0219: The variable `rangein' is assigned but its value is never used
./Lucene.Net/QueryParser/QueryParserTokenManager.cs(151,17): warning CS0219: The variable `j' is assigned but its value is never used
./Lucene.Net/QueryParser/QueryParserTokenManager.cs(146,19): warning CS0219: The variable `nextStates' is assigned but its value is never used
./Lucene.Net/QueryParser/QueryParserTokenManager.cs(628,8): warning CS0219: The variable `j' is assigned but its value is never used
./Lucene.Net/QueryParser/QueryParserTokenManager.cs(623,10): warning CS0219: The variable `nextStates' is assigned but its value is never used
./Lucene.Net/QueryParser/QueryParserTokenManager.cs(821,12): warning CS0219: The variable `l' is assigned but its value is never used
./Lucene.Net/QueryParser/QueryParserTokenManager.cs(840,12): warning CS0219: The variable `l2' is assigned but its value is never used
./Lucene.Net/QueryParser/QueryParserTokenManager.cs(839,10): warning CS0219: The variable `i2' is assigned but its value is never used
./Lucene.Net/QueryParser/QueryParserTokenManager.cs(838,12): warning CS0219: The variable `l1' is assigned but its value is never used
./Lucene.Net/QueryParser/QueryParserTokenManager.cs(837,10): warning CS0219: The variable `i1' is assigned but its value is never used
./Lucene.Net/QueryParser/QueryParserTokenManager.cs(778,8): warning CS0219: The variable `j' is assigned but its value is never used
./Lucene.Net/QueryParser/QueryParserTokenManager.cs(773,10): warning CS0219: The variable `nextStates' is assigned but its value is never used
./Lucene.Net/QueryParser/QueryParserTokenManager.cs(956,8): warning CS0219: The variable `j' is assigned but its value is never used
./Lucene.Net/QueryParser/QueryParserTokenManager.cs(951,10): warning CS0219: The variable `nextStates' is assigned but its value is never used
./Lucene.Net/QueryParser/QueryParserTokenManager.cs(1268,1): warning CS0162: Unreachable code detected
./Lucene.Net/QueryParser/QueryParserTokenManager.cs(1178,8): warning CS0219: The variable `kind' is assigned but its value is never used
./Lucene.Net/QueryParser/QueryParserTokenManager.cs(1179,10): warning CS0219: The variable `specialToken' is assigned but its value is never used
./EvolutionMailDriver/EvolutionMailIndexableGenerator.cs(367,4): error CS1502: The best overloaded method match for `GMime.Object.WriteToStream(GMime.Stream)' has some invalid arguments
./EvolutionMailDriver/EvolutionMailIndexableGenerator.cs(367,4): error CS1503: Argument 1: Cannot convert from `System.IO.MemoryStream' to `GMime.Stream'
Compilation failed: 2 error(s), 63 warnings
make[2]: *** [BeagleDaemonLib.dll] Error 1
make[2]: Leaving directory `/var/tmp/portage/beagle-0.1.2/work/beagle-0.1.2/beagled'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/beagle-0.1.2/work/beagle-0.1.2'
make: *** [all] Error 2

!!! ERROR: app-misc/beagle-0.1.2 failed.
!!! Function src_compile, Line 87, Exitcode 2
!!! Make failed
!!! If you need support, post the topmost build error, NOT this status message.
Back to top
View user's profile Send private message
certocivitas
Apprentice
Apprentice


Joined: 29 Dec 2004
Posts: 194

PostPosted: Wed Feb 22, 2006 1:17 am    Post subject: Reply with quote

I have Beagle installed and working but it will only index my home directory. Whenever I use beagle-settings or beagle-config to add indexes I get this error:

Quote:
ERROR: Could not load configuration from indexing.xml: Exception has been thrown by the target of an invocation.


Any idea what is wrong?
Back to top
View user's profile Send private message
Naib
Watchman
Watchman


Joined: 21 May 2004
Posts: 5490
Location: Removed by Neddy

PostPosted: Wed Feb 22, 2006 2:11 am    Post subject: Reply with quote

Woot it is in portage!!!
What happened to that bug innit that would hose a Ext3 partition? I stopped using it after that
_________________
The best argument against democracy is a five-minute conversation with the average voter
Great Britain is a republic, with a hereditary president, while the United States is a monarchy with an elective king
Back to top
View user's profile Send private message
kwyjibo
n00b
n00b


Joined: 21 Feb 2005
Posts: 14
Location: Switzerland

PostPosted: Wed Feb 22, 2006 11:31 pm    Post subject: Reply with quote

kwyjibo wrote:
followed this guide to install beagle, but i ran into the following error:

Code:
[...]
./EvolutionMailDriver/EvolutionMailIndexableGenerator.cs(367,4): error CS1503: Argument 1: Cannot convert from `System.IO.MemoryStream' to `GMime.Stream'
Compilation failed: 2 error(s), 63 warnings
make[2]: *** [BeagleDaemonLib.dll] Error 1
make[2]: Leaving directory `/var/tmp/portage/beagle-0.1.2/work/beagle-0.1.2/beagled'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/beagle-0.1.2/work/beagle-0.1.2'
make: *** [all] Error 2

!!! ERROR: app-misc/beagle-0.1.2 failed.
!!! Function src_compile, Line 87, Exitcode 2
!!! Make failed
!!! If you need support, post the topmost build error, NOT this status message.



fixed it with:
Code:
 emerge -av =dev-libs/gmime-2.1.16


and then:
Code:
emerge -av app-misc/beagle



w00t!
Back to top
View user's profile Send private message
kdvgent
Guru
Guru


Joined: 29 Sep 2004
Posts: 328
Location: Belgium

PostPosted: Fri Feb 24, 2006 8:44 am    Post subject: problem emerging beagle on ~amd64 Reply with quote

Trying to install beagle, I get the following error:

Quote:

>>> cfg-update-1.8.0-r3 : No new packages have been emerged, checksum index OK...
Calculating dependencies ...done!
>>> emerge (1 of 1) app-misc/beagle-0.2.1 to /
>>> checksums files ;-) beagle-0.1.1.ebuild
>>> checksums files ;-) beagle-0.2.1.ebuild
>>> checksums files ;-) beagle-0.1.2.ebuild
>>> checksums files ;-) files/digest-beagle-0.1.1
>>> checksums files ;-) files/digest-beagle-0.2.1
>>> checksums files ;-) files/beagle-0.2.1-multilib.patch
>>> checksums files ;-) files/digest-beagle-0.1.2
>>> checksums files ;-) files/beagle-0.1.1-null-task-source.patch
>>> checksums files ;-) files/beagle-0.1.1-uri-serialization.patch
>>> checksums src_uri ;-) beagle-0.2.1.tar.bz2
* Mono support enabled in dev-libs/gmime, I will continue...
>>> Unpacking source...
>>> Unpacking beagle-0.2.1.tar.bz2 to /var/tmp/portage/beagle-0.2.1/work
* Applying beagle-0.2.1-multilib.patch ... [ ok ] * Running eautoreconf in '/var/tmp/portage/beagle-0.2.1/work/beagle-0.2.1' ...
* Running aclocal ... [ ok ] * Running libtoolize --copy --force --automake ... [ ok ] * Running aclocal ... [ ok ] * Running autoconf ... [ ok ] * Running autoheader ... [ ok ] * Running automake --add-missing --copy ... [ ok ] * Running elibtoolize in: beagle-0.2.1
* Applying max_cmd_len-1.5.0.patch ...
* Applying sed-1.5.6.patch ...
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/beagle-0.2.1/work/beagle-0.2.1 ...
* econf: updating beagle-0.2.1/config.sub with /usr/share/gnuconfig/config.sub
* econf: updating beagle-0.2.1/config.guess with /usr/share/gnuconfig/config.guess
./configure --prefix=/usr --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-evolution --enable-gui --enable-python --enable-libbeagle --libdir=/usr/lib64 --build=x86_64-pc-linux-gnu
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for a BSD-compatible install... /bin/install -c
checking for style of include used by make... GNU
checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-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 x86_64-pc-linux-gnu-gcc accepts -g... yes
checking for x86_64-pc-linux-gnu-gcc option to accept ANSI C... none needed
checking dependency style of x86_64-pc-linux-gnu-gcc... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by x86_64-pc-linux-gnu-gcc... /usr/x86_64-pc-linux-gnu/bin/ld
checking if the linker (/usr/x86_64-pc-linux-gnu/bin/ld) is GNU ld... yes
checking for /usr/x86_64-pc-linux-gnu/bin/ld option to reload object files... -rchecking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... x86_64-pc-linux-gnu-gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for x86_64-pc-linux-gnu-g++... x86_64-pc-linux-gnu-g++
checking whether we are using the GNU C++ compiler... yes
checking whether x86_64-pc-linux-gnu-g++ accepts -g... yes
checking dependency style of x86_64-pc-linux-gnu-g++... gcc3
checking how to run the C++ preprocessor... x86_64-pc-linux-gnu-g++ -E
checking for x86_64-pc-linux-gnu-g77... x86_64-pc-linux-gnu-g77
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether x86_64-pc-linux-gnu-g77 accepts -g... yes
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from x86_64-pc-linux-gnu-gcc object... ok
checking for objdir... .libs
checking for x86_64-pc-linux-gnu-ar... x86_64-pc-linux-gnu-ar
checking for x86_64-pc-linux-gnu-ranlib... x86_64-pc-linux-gnu-ranlib
checking for x86_64-pc-linux-gnu-strip... x86_64-pc-linux-gnu-strip
checking for correct ltmain.sh version... yes
checking if x86_64-pc-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no
checking for x86_64-pc-linux-gnu-gcc option to produce PIC... -fPIC
checking if x86_64-pc-linux-gnu-gcc PIC flag -fPIC works... yes
checking if x86_64-pc-linux-gnu-gcc static flag -static works... yes
checking if x86_64-pc-linux-gnu-gcc supports -c -o file.o... yes
checking whether the x86_64-pc-linux-gnu-gcc linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by x86_64-pc-linux-gnu-g++... /usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64
checking if the linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the x86_64-pc-linux-gnu-g++ linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for x86_64-pc-linux-gnu-g++ option to produce PIC... -fPIC
checking if x86_64-pc-linux-gnu-g++ PIC flag -fPIC works... yes
checking if x86_64-pc-linux-gnu-g++ static flag -static works... yes
checking if x86_64-pc-linux-gnu-g++ supports -c -o file.o... yes
checking whether the x86_64-pc-linux-gnu-g++ linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for x86_64-pc-linux-gnu-g77 option to produce PIC... -fPIC
checking if x86_64-pc-linux-gnu-g77 PIC flag -fPIC works... yes
checking if x86_64-pc-linux-gnu-g77 static flag -static works... yes
checking if x86_64-pc-linux-gnu-g77 supports -c -o file.o... yes
checking whether the x86_64-pc-linux-gnu-g77 linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for x86_64-pc-linux-gnu-g++... (cached) x86_64-pc-linux-gnu-g++
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether x86_64-pc-linux-gnu-g++ accepts -g... (cached) yes
checking dependency style of x86_64-pc-linux-gnu-g++... (cached) gcc3
checking for pkg-config... /usr/bin/pkg-config
checking for bash... /bin/sh
checking for zip... /usr/bin/zip
checking for mono... /usr/bin/mono
checking for mcs... /usr/bin/mcs
checking for mono.pc... found
checking for x86_64-pc-linux-gnu-pkg-config... (cached) /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for MONO... yes
checking for Mono.Data.SqliteClient.dll... found
checking for Mono.Posix.dll... found
checking for System.Runtime.Remoting.dll... found
checking for System.Web.dll... found
checking for System.Web.Services.dll... found
checking for desktop-launch... no
checking for wsdl... /usr/bin/wsdl
checking for intltool >= 0.23... 0.34.1 found
checking for perl... /usr/bin/perl
checking for XML::Parser... ok
checking for iconv... /usr/bin/iconv
checking for msgfmt... /usr/bin/msgfmt
checking for msgmerge... /usr/bin/msgmerge
checking for xgettext... /usr/bin/xgettext
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking for LC_MESSAGES... yes
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
checking for ngettext in libc... yes
checking for dgettext in libc... yes
checking for bind_textdomain_codeset... yes
checking for msgfmt... /usr/bin/msgfmt
checking for dcgettext... yes
checking for gmsgfmt... /usr/bin/gmsgfmt
checking for xgettext... /usr/bin/xgettext
checking for catalogs to be installed... bg ca cs da de el en_CA en_GB es fi fr he hu ja lt mk nb nl no pl pt_BR sv tr uk vi zh_CN zh_HK zh_TW
checking for SQLITE... checking for SQLITE3... configure: error: You need to install sqlite 2.x or >= 3.3.1

!!! Please attach the following file when filing a report to bugs.gentoo.org:
!!! /var/tmp/portage/beagle-0.2.1/work/beagle-0.2.1/config.log

!!! ERROR: app-misc/beagle-0.2.1 failed.
Call stack:
ebuild.sh, line 1894: Called dyn_compile
ebuild.sh, line 941: Called src_compile
beagle-0.2.1.ebuild, line 97: Called econf 'compile' '--disable-evolution' '--enable-gui' '--enable-python'

!!! econf failed
!!! If you need support, post the topmost build error, and the call stack if relevant.


But I have sqlite 3.3.4 installed !!!

Quote:
>>> cfg-update-1.8.0-r3 : No new packages have been emerged, checksum index OK...

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild R ] dev-db/sqlite-3.3.4 USE="-debug -doc -nothreadsafe -tcltk" 0 kB

Total size of downloads: 0 kB


Any suggestions? In the logfile, there is no other warning than the one about sqlite.

Many thanks in advance for helping
Back to top
View user's profile Send private message
RegisG
n00b
n00b


Joined: 12 Jan 2004
Posts: 34

PostPosted: Fri Feb 24, 2006 1:53 pm    Post subject: Reply with quote

I've got the same problem !!
Any Idea ?
Back to top
View user's profile Send private message
kdvgent
Guru
Guru


Joined: 29 Sep 2004
Posts: 328
Location: Belgium

PostPosted: Fri Feb 24, 2006 5:10 pm    Post subject: ~amd64 no longer in new ebuild Reply with quote

No idea. Today there was a new ebuild, without the ~amd64 keyword. No explanation in change-log.
Back to top
View user's profile Send private message
MADcow
l33t
l33t


Joined: 23 Jan 2003
Posts: 742
Location: RIT (Henrietta, New York, United States)

PostPosted: Sun Feb 26, 2006 9:07 am    Post subject: Reply with quote

i was wondering how i can change beagle's actions - ex: opening a website. since i don't use gnome, it doesn't work very well with the programs i want to use.
i figure i need to edit beagle's mime actions, but it doesn't seem to be using the normal mime stuff from /usr/share/mime
any suggestions?
Back to top
View user's profile Send private message
matttions
Guru
Guru


Joined: 19 Jul 2004
Posts: 338

PostPosted: Sun Feb 26, 2006 11:45 am    Post subject: Reply with quote

Try gconf ... to change the browser ..
this are the info at the end of the evolution ebuild
Code:
 einfo "To change the default browser if you are not using GNOME, do:"
        einfo "gconftool-2 --set /desktop/gnome/url-handlers/http/command -t string 'mozilla %s'"
        einfo "gconftool-2 --set /desktop/gnome/url-handlers/https/command -t string 'mozilla %s'"
        einfo ""
        einfo "Replace 'mozilla %s' with which ever browser you use."


Maybe it will do the trick :)
_________________
gentoo ... l'unico pinguino da corsa
Back to top
View user's profile Send private message
fuchsmi
Tux's lil' helper
Tux's lil' helper


Joined: 11 Jun 2003
Posts: 118

PostPosted: Sun Feb 26, 2006 8:47 pm    Post subject: Reply with quote

where can I find the ebuild for beage 2.1?
Back to top
View user's profile Send private message
MADcow
l33t
l33t


Joined: 23 Jan 2003
Posts: 742
Location: RIT (Henrietta, New York, United States)

PostPosted: Sun Feb 26, 2006 9:30 pm    Post subject: Reply with quote

matttions: thanks. i'm not a gnome guy so i haven't used that before. and i don't have evolution, so i've never seen that einfo.
thanks a ton! :)

fuchsmi: beagle 0.2.1 (newest release) is in portage. check for app-misc/beagle. it's masked ~x86.
i'd suggest you follow the guide at http://gentoo-wiki.com/HOWTO_Beagle
it's a little old, but most of the information is still relevant.

EDIT: i can't seem to find any keys that beagle actually listens to.
Back to top
View user's profile Send private message
golding
Apprentice
Apprentice


Joined: 07 Jun 2005
Posts: 230
Location: Adelaide / South Australia

PostPosted: Mon Feb 27, 2006 3:34 am    Post subject: Reply with quote

Any reason to keep the FF extention, or should I use the beagle-index-url script?

More to the point, what does the beagle-index-url script actually do?
_________________
Regards, Robert

..... Some people can tell what time it is by looking at the sun, but I have never been able to make out the numbers.
Back to top
View user's profile Send private message
MADcow
l33t
l33t


Joined: 23 Jan 2003
Posts: 742
Location: RIT (Henrietta, New York, United States)

PostPosted: Mon Feb 27, 2006 4:44 am    Post subject: Reply with quote

if i read the --help output correctly, it indexes one page or a list of pages.
meaning that it exists so that you can manually add pages to the index
or it's a backend for beagle's own purposes.
if either are accurate, you should keep using the firefox extension.
Back to top
View user's profile Send private message
golding
Apprentice
Apprentice


Joined: 07 Jun 2005
Posts: 230
Location: Adelaide / South Australia

PostPosted: Mon Feb 27, 2006 7:26 am    Post subject: Reply with quote

Just went looking for detailed documentation regarding beagle and could find nothing really.

The readme lists shorthand differences to the last version and nothing more, let alone going to the beagle site (any of them) for info. You were right, the --help from each command is far more cryptic than helpful, unfortunately the writers seem to have a view of assumed knowledge that we don't have.

However, I did find an XPI build for FF v1.0 to v1.5 and also extensions for Evolution, IM's and Epiphany hidden within the tar.gz.

So, no extra information, but, plenty of extra stuff, even if they chose not to tell :-)
_________________
Regards, Robert

..... Some people can tell what time it is by looking at the sun, but I have never been able to make out the numbers.
Back to top
View user's profile Send private message
MADcow
l33t
l33t


Joined: 23 Jan 2003
Posts: 742
Location: RIT (Henrietta, New York, United States)

PostPosted: Mon Feb 27, 2006 7:52 am    Post subject: Reply with quote

yes, beagle has horrible documentation. this seems to be a common problem with new/small FOSS projects.
beagle, though, is neither. it has been around for years (since early 2004?) and is part of GNOME and has a corporate sponsor or two (NOVELL)

so, there's no excuse. a quick scan of CIA's CVS stats shows that they don't have many developers, though. they might be too busy making featurey-goodness and squashing bugs to make docs.
well, drat. and i want my customized actions!
Back to top
View user's profile Send private message
lefou
Apprentice
Apprentice


Joined: 18 Feb 2004
Posts: 197
Location: Germany, Leipzig

PostPosted: Mon Feb 27, 2006 8:56 am    Post subject: kde-misc/kerry-0.07.ebuild Reply with quote

For those of you, who want using beagle with KDE, there is a KDE client now available in bugs.gentoo.org. It is called kerry and in version 0.07. It's very well integrated into KDE, at least it opens the right apps. :)

See Bug #124173

Please post problems with the ebuild, so that I can correct it, e.g. dependencies.

lefou
_________________
lefous portage overlay
Back to top
View user's profile Send private message
sog
Guru
Guru


Joined: 04 Apr 2004
Posts: 356

PostPosted: Mon Feb 27, 2006 9:55 pm    Post subject: Reply with quote

anybody else having a problem wherein beagle runs in debug mode by default?

when i run this:

Code:
sog@mymachine /home/sog $ beagled


i get this:

Code:
sog       6682 11.5  2.9  53052 26368 pts/1    S    14:45   0:00 mono-beagled --debug /usr/lib/beagle/BeagleDaemon.exe --bg
sog       6684  0.0  2.9  53052 26368 pts/1    S    14:45   0:00 mono-beagled --debug /usr/lib/beagle/BeagleDaemon.exe --bg
sog       6685  0.0  2.9  53052 26368 pts/1    S    14:45   0:00 mono-beagled --debug /usr/lib/beagle/BeagleDaemon.exe --bg
sog       6686  0.0  2.9  53052 26368 pts/1    S    14:45   0:00 mono-beagled --debug /usr/lib/beagle/BeagleDaemon.exe --bg
sog       6688  9.0  2.9  53052 26368 pts/1    S    14:45   0:00 mono-beagled --debug /usr/lib/beagle/BeagleDaemon.exe --bg
sog       6689  0.0  2.9  53052 26368 pts/1    S    14:45   0:00 mono-beagled --debug /usr/lib/beagle/BeagleDaemon.exe --bg
sog       6690  0.0  2.9  53052 26368 pts/1    S    14:45   0:00 mono-beagled --debug /usr/lib/beagle/BeagleDaemon.exe --bg
sog       6691  0.0  2.9  53052 26368 pts/1    S    14:45   0:00 mono-beagled --debug /usr/lib/beagle/BeagleDaemon.exe --bg


more to the point, the machine runs slow and worse, ends up creating huge logfiles. i've disabled it at startup until i can get this sorted. anyone else seeing it? is this a Gentoo ebuild problem or something upstream?

i've had the problem for the past few versions of beagle, all the way up 'till 0.2.1 which i'm running now. it also does not appear to be specific to my mono version (currently 1.1.8.3).
_________________
------------------------------------------------
(blog) http://www.redmonk.com/sogrady/
Back to top
View user's profile Send private message
MADcow
l33t
l33t


Joined: 23 Jan 2003
Posts: 742
Location: RIT (Henrietta, New York, United States)

PostPosted: Tue Feb 28, 2006 3:18 am    Post subject: Reply with quote

sog: does emerge app-misc/beagle -vp show that you've compiled it with the debug useflag?
Back to top
View user's profile Send private message
sog
Guru
Guru


Joined: 04 Apr 2004
Posts: 356

PostPosted: Tue Feb 28, 2006 3:37 am    Post subject: Reply with quote

don't think so, MADcow - this is what i've got:

Code:
[ebuild   R   ] app-misc/beagle-0.2.1  -debug -evo +gtk -ole -pdf +python 0 kB

_________________
------------------------------------------------
(blog) http://www.redmonk.com/sogrady/
Back to top
View user's profile Send private message
MADcow
l33t
l33t


Joined: 23 Jan 2003
Posts: 742
Location: RIT (Henrietta, New York, United States)

PostPosted: Tue Feb 28, 2006 4:15 am    Post subject: Reply with quote

no star next to debug, so i guess you're not using a different USE setting for at than when you compiled it. sorry.
Back to top
View user's profile Send private message
MetalGod
Bodhisattva
Bodhisattva


Joined: 10 Mar 2003
Posts: 816
Location: Portugal

PostPosted: Wed Mar 01, 2006 3:34 am    Post subject: Re: ~amd64 no longer in new ebuild Reply with quote

kdvgent wrote:
No idea. Today there was a new ebuild, without the ~amd64 keyword. No explanation in change-log.


The keywords had been removed to avoid problems with the dependencies that causes lots of trouble to users because mono use flag is currently masked for amd64.
We will keyword it asap (maybe in a few days/weeks after mono use flag unmask).
_________________
ex: Gentoo Linux Developer: amd64 media-optical sound gnome
ex: Portuguese Moderator
------------------------------------------------------------------------------
God Doesn't Play Dice
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Goto page 1, 2, 3, 4  Next
Page 1 of 4

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum