CC'd to BLFS-Dev, follow-ups should be made there, as this is now a -dev issue
On 1/17/2013 2:55 PM, Armin K. wrote: > Try: > > glib-compile-schemas-2.0 /usr/share/glib-2.0/schemas > > and re-run make check Thanks for the quick reply. I ran the command 'glib-compile-schemas /usr/share/glib-2.0/schemas' (note that there is no "-2.0") and it created /usr/share/glib-2.0/schemas/gschemas.compiled I had already went ahead and installed glib-networking and after running the command above the make check works up to a point. I think the fix is running the command, and that command probably needs to be on the gsettings-desktop-schemas instructions. However, 'make check' still does not run to completion. The error was discovered on 11/17 last year and somebody emailed to BLFS-Support but it went unanswered. Here is that mail. > I,m having trouble running make check on glib-networking-2.34.2 > I recieve an error > > T: connection... (pid=18853) > /tls/connection/basic: OK > /tls/connection/verified: OK > /tls/connection/client-auth: OK > /tls/connection/client-auth-rehandshake: OK > /tls/connection/no-database: OK > /tls/connection/failed: OK > /tls/connection/socket-client: OK > /tls/connection/socket-client-failed: OK > /tls/connection/simultaneous-async: OK > /tls/connection/simultaneous-sync: OK > /tls/connection/simultaneous-async-rehandshake: ** > GLib-Net:ERROR:connection.c:300:run_echo_server: assertion failed (error > == NULL): Error performing TLS handshake: An unexpected TLS packet was > received. (g-tls-error-quark, 1) > FAIL > GTester: last random seed: R02S7be3a64a8d3d987836f32404cc10adc9 > /bin/sh: line 1: 18849 Terminated gtester --verbose > certificate file-database connection pkcs11-util pkcs11-array pkcs11-pin > pkcs11-slot > make[2]: *** [test-nonrecursive] Error 143 > make[2]: Leaving directory > `/home/spiky/Downloads/glib-networking-2.34.2/tls/tests' > make[1]: *** [check-am] Error 2 > make[1]: Leaving directory > `/home/spiky/Downloads/glib-networking-2.34.2/tls/tests' > make: *** [check-recursive] Error 1 > > I would like to get to the bottom of this, any advice on errors pls I get the same exact error. I am not sure if this is worth reporting upstream; however, we should probably mention it in the book. -- Randy -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
