i may have answered my own question, at least partially. it appears
that commenting out those two references to g_type_init allow the
libraries to at least build.
--- openvas_file.c.orig 2013-05-16 12:10:43.813633319 -0400
+++ openvas_file.c 2013-05-16 12:11:32.111310102 -0400
@@ -164,7 +164,7 @@
GFile *sfile, *dfile;
GError *error;
- g_type_init ();
+ /*g_type_init ();*/
sfile = g_file_new_for_path (source_file);
dfile = g_file_new_for_path (dest_file);
error = NULL;
@@ -200,7 +200,7 @@
GFile *sfile, *dfile;
GError *error;
- g_type_init ();
+ /*g_type_init ();*/
sfile = g_file_new_for_path (source_file);
dfile = g_file_new_for_path (dest_file);
error = NULL;
however, i'm not experienced enough to know preemptively what the
implications may ultimately be.
-ben
No implications for you. You are just using a new version of glib which
has deprecated the g_type_init() call. Added version check as revision
16369.
Cheers,
Hani.
_______________________________________________
Openvas-devel mailing list
Openvas-devel@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-devel
