Attachment 7873 Details for Bug 9132 – Patch that fixes the problem for me

[patch] Patch that fixes the problem for me

parse.c.patch (text/plain), 1.48 KB, created by J. Scott Berg on 2006-11-22 22:09:54 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: J. Scott Berg

Created: 2006-11-22 22:09:54 UTC

Size: 1.48 KB

patch

obsolete

>--- parse.c.orig	2006-08-16 14:45:45.000000000 -0400
>+++ parse.c	2006-11-23 01:06:13.000000000 -0500
>@@ -558,8 +558,6 @@
>     }
> 
>   g_slist_free (parsed);
>-  
>-  pkg->requires = g_slist_reverse (pkg->requires);
> }
> 
> static void
>@@ -607,8 +605,6 @@
>     }
> 
>   g_slist_free (parsed);
>-  
>-  pkg->requires_private = g_slist_reverse (pkg->requires_private);
> }
> 
> static void
>@@ -719,10 +715,6 @@
>       ++i;
>     }
> 
>-  pkg->l_libs = g_slist_reverse (pkg->l_libs);
>-  pkg->L_libs = g_slist_reverse (pkg->L_libs);
>-  pkg->other_libs = g_slist_reverse (pkg->other_libs);
>-  
> }
> 
> 
>@@ -883,9 +875,6 @@
> 
>   g_free (argv);
>   g_free (trimmed);
>-
>-  pkg->I_cflags = g_slist_reverse (pkg->I_cflags);
>-  pkg->other_cflags = g_slist_reverse (pkg->other_cflags);
> }
> 
> static void
>@@ -1105,9 +1094,20 @@
>   fclose(f);
> 
>   /* make ->requires_private include a copy of the public requires too */
>-  pkg->requires_private = g_slist_concat(pkg->requires_private,
>-					 g_slist_copy (pkg->requires));
>+  pkg->requires_private = g_slist_concat(g_slist_copy (pkg->requires),
>+					 pkg->requires_private);
>+  
>+  pkg->requires = g_slist_reverse (pkg->requires);
>+  
>+  pkg->requires_private = g_slist_reverse (pkg->requires_private);
> 
>+  pkg->I_cflags = g_slist_reverse (pkg->I_cflags);
>+  pkg->other_cflags = g_slist_reverse (pkg->other_cflags);
>+
>+  pkg->l_libs = g_slist_reverse (pkg->l_libs);
>+  pkg->L_libs = g_slist_reverse (pkg->L_libs);
>+  pkg->other_libs = g_slist_reverse (pkg->other_libs);
>+  
>   return pkg;
> }
>

Actions: View | Splinter Review

Attachments on bug 9132: 7872 | 7873

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.