There were two problems here:
1) The package details were being stored in a CMakeCache.txt file that
wasn't getting cleared by ./configure. Therefore, the cflags weren't
being regenerated with the new package information. I deleted the cache
file and ./configured again, to discover....
2) I had manually installed libsecret 0.10; geary wants 0.11. So I
installed the new versions from quantal-updates.
With this, I can compile geary. Unfortunately, when I run it, I get the
same seg fault as before. Worried that there could be an issue with the
.gir file coming from a different source, I recompiled webkit with
--enable-introspection to get a new .gir file. This doesn't help. The
full backtrace is below.
Any thoughts?
Robert
#0 0x00007ffff42aa350 in g_type_check_instance_cast ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#1 0x00007ffff5e6013d in WebKit::core(_WebKitDOMDOMTokenList*) ()
from /home/rschroll/webkit/lib/libwebkitgtk-3.0.so.0
#2 0x00007ffff5e60784 in webkit_dom_dom_token_list_add ()
from /home/rschroll/webkit/lib/libwebkitgtk-3.0.so.0
#3 0x00000000004b3f29 in conversation_viewer_add_message (self=0xaaa140,
email=0x7fff885265a0)
at /home/rschroll/geary/src/client/views/conversation-viewer.vala:223
#4 0x0000000000457158 in geary_controller_do_show_message_co (
_data_=0x1008040)
at /home/rschroll/geary/src/client/geary-controller.vala:654
#5 0x00007ffff4534f97 in g_simple_async_result_complete ()
from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#6 0x000000000054ebdc in
geary_imap_engine_generic_folder_real_fetch_email_async_co (_data_=0xb50800)
at
/home/rschroll/geary/src/engine/imap-engine/imap-engine-generic-folder.vala:978
#7 0x00007ffff4534f97 in g_simple_async_result_complete ()
from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#8 0x0000000000553baf in
geary_imap_engine_replay_operation_wait_for_ready_async_co (_data_=0xf7ba60)
at
/home/rschroll/geary/src/engine/imap-engine/imap-engine-replay-operation.vala:120
#9 geary_imap_engine_replay_operation_wait_for_ready_async_co (
_data_=0xf7ba60) at imap-engine-replay-operation.c:491
#10 0x00007ffff4534f97 in g_simple_async_result_complete ()
from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#11 0x000000000056aeb4 in
geary_nonblocking_abstract_semaphore_real_wait_async_co (_data_=0xf004f0)
at
/home/rschroll/geary/src/engine/nonblocking/nonblocking-abstract-semaphore.vala:135
#12 0x000000000058d3c3 in geary_scheduler_scheduled_instance_on_callback (
self=0x7fff884896d0)
at /home/rschroll/geary/src/engine/util/util-scheduler.vala:66
#13 _geary_scheduler_scheduled_instance_on_callback_gsource_func (
self=0x7fff884896d0)
at /home/rschroll/geary/build/src/engine/util/util-scheduler.c:192
#14 0x00007ffff3fc8f63 in g_main_context_dispatch ()
from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x00007ffff3fc92b0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007ffff3fc96aa in g_main_loop_run ()
from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007ffff554742d in gtk_main ()
from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#18 0x0000000000590380 in yorba_application_run (self=0x891010,
args=0x7fffffffe1a8, args_length1=1)
at /home/rschroll/geary/src/common/common-yorba-application.vala:143
#19 0x000000000046070f in _vala_main (args=0x7fffffffe1a8, args_length1=1)
at /home/rschroll/geary/src/client/main.vala:10
#20 0x00007ffff34c876d in __libc_start_main ()
from /lib/x86_64-linux-gnu/libc.so.6
#21 0x0000000000450229 in _start ()
On 04/19/2013 10:00 PM, Eric Gregory wrote:
Great to hear this is coming along!
On Fri, Apr 19, 2013 at 4:50 PM, Robert Schroll <[email protected]
<mailto:[email protected]>> wrote:
Unfortunately, I can't complete the compilation; now I'm getting
errors about libsecret:
[ 74%] Building C object
src/CMakeFiles/geary.dir/__client/secret-mediator.c.o
/home/rschroll/geary/src/__client/secret-mediator.c:17:__30: fatal
error: libsecret/secret.h: No such file or directory
I'm not sure why it can't find the header file, since it is installed.
$ locate secret.h
/usr/include/libsecret-1/__libsecret/secret.h
Can someone with more CMake knowledge point me in the right direction?
This could be a few things:
* Is pkg-config aware of libsecret? This *should* happen
automatically. The easy way to check is:
pkg-config --list-all | grep libsecret
* Did you re-./configure after installing libsecret?
- Eric
_______________________________________________
Geary mailing list
[email protected]
http://lists.yorba.org/cgi-bin/mailman/listinfo/geary
