all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Federico Beffa <beffa@ieee.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: gobject-introspection typelibs and shared libraries
Date: Tue, 13 Jan 2015 18:10:03 +0100	[thread overview]
Message-ID: <CAKrPhPM9RZV-T+6KZMbuDKu-tPynGEwnFf43iPEPnjqKwuHZNQ@mail.gmail.com> (raw)
In-Reply-To: <87h9wumz6f.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1814 bytes --]

On Wed, Dec 17, 2014 at 9:57 AM, Ludovic Courtès <ludo@gnu.org> wrote:
>> I've created a branch named wip-gobject-introspection with the patch
>> and version 1.42.0.  I've also pushed version updates for pango and
>> gdk-pixbuf compatible with the former.

[...]

> Mark H Weaver <mhw@netris.org> skribis:
>
>> I went down this road, and found that a great many things fail.  I don't
>> remember finding a single package that uses gobject-introspection that
>> worked without updating.
>>
>> I got stuck on eudev.  The newest version doesn't work, and I didn't see
>> anything in their git repo to fix it either.
>>
>> Before moving forward on this, can you find a way to build eudev with
>> gobject-introspection-1.42.0?

The attached patch fixes the build of eudev with the newer
gobject-introspection. It turns out that g-ir-scanner looks for the C
compiler as either 'cc' or as the environment variable 'CC'.  So, the
fix was easy in retrospective :-).

The question is: do we want to make a 'cc' symlink to 'gcc' in the
'gcc' package? This is something that many distributions do.  If we
don't, we may have to make a patch similar to the attached one for
several packages (or patch 'gobject-introspection' to look for 'gcc'
by default). Personally I would prefer the symlink approach.

>>
>> Also, I'm currently working on upgrading almost every package in
>> xorg.scm, as well as glib and dbus.  I'll push it as a branch in the
>> next day or two.  It probably makes the most sense to build your branch
>> on top of mine.

Now that your updates are in master, I've merged them into the branch
wip-gobject-introspection.
To help see what works and what not, it would be helpful to set up
hydra to build the wip-gobject-introspection branch.

WDYT?

Regards,
Fede

[-- Attachment #2: 0001-gnu-eudev-Add-pre-build-phase.patch --]
[-- Type: text/x-patch, Size: 1675 bytes --]

From 355bae94512391434bb6c7e14e8632451654380b Mon Sep 17 00:00:00 2001
From: Federico Beffa <beffa@fbengineering.ch>
Date: Tue, 13 Jan 2015 16:25:29 +0100
Subject: [PATCH] gnu: eudev: Add pre-build phase.

* gnu/packages/linux.scm (eudev): Add 'pre-build phase to fix compilation with
  'gobject-introspection' 1.42.0.
---
 gnu/packages/linux.scm | 18 +++++++++++++++---
 1 file changed, 15 insertions(+), 3 deletions(-)

diff --git a/gnu/packages/linux.scm b/gnu/packages/linux.scm
index 4599323..ad4e52c 100644
--- a/gnu/packages/linux.scm
+++ b/gnu/packages/linux.scm
@@ -1407,9 +1407,21 @@ time.")
                   (("linux/btrfs\\.h")
                    "")))))
     (arguments
-     (substitute-keyword-arguments (package-arguments udev)
-       ((#:configure-flags flags)
-        `(cons "--enable-libkmod" ,flags))))
+     `(,@(substitute-keyword-arguments (package-arguments udev)
+           ((#:configure-flags flags)
+            `(cons "--enable-libkmod" ,flags)))
+       #:phases 
+       (alist-cons-before
+        'build 'pre-build
+        ;; The program 'g-ir-scanner' (part of the package
+        ;; 'gobject-introspection'), to generate .gir files, makes some
+        ;; library pre-processing.  During that phase it looks for the C
+        ;; compiler as either 'cc' or as defined by the environment variable
+        ;; 'CC' (with code in 'giscanner/dumper.py').
+        (lambda* (#:key inputs #:allow-other-keys)
+          (let ((gcc (string-append (assoc-ref inputs "gcc") "/bin/gcc")))
+            (setenv "CC" gcc)))
+        %standard-phases)))
     (home-page "http://www.gentoo.org/proj/en/eudev/")))
 
 (define-public lvm2
-- 
1.8.4


  reply	other threads:[~2015-01-13 17:10 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-07 14:21 gobject-introspection typelibs and shared libraries Federico Beffa
2014-12-07 20:48 ` Ludovic Courtès
2014-12-07 22:11   ` Federico Beffa
2014-12-08  9:22     ` Ludovic Courtès
2014-12-08 12:21       ` Federico Beffa
2014-12-08 14:51         ` Federico Beffa
2014-12-08 20:37         ` Ludovic Courtès
2014-12-09 19:30           ` Federico Beffa
2014-12-09 20:27             ` Federico Beffa
2014-12-10  4:15               ` Mark H Weaver
2014-12-09 20:58             ` Ludovic Courtès
2014-12-10  4:39             ` Mark H Weaver
2014-12-10  4:54               ` Mark H Weaver
2014-12-10  8:48                 ` Ludovic Courtès
2014-12-10  8:57                   ` Federico Beffa
2014-12-10 12:56                     ` Ludovic Courtès
2014-12-16 19:45                       ` Federico Beffa
2014-12-17  7:20                         ` Mark H Weaver
2014-12-17  8:57                         ` Ludovic Courtès
2015-01-13 17:10                           ` Federico Beffa [this message]
2015-01-13 20:22                             ` Ludovic Courtès
2015-01-13 21:40                               ` Federico Beffa
2015-01-14 20:43                                 ` Ludovic Courtès
2015-01-15  8:27                                   ` Federico Beffa
2015-01-15 21:42                                     ` Ludovic Courtès
2015-01-16 17:07                                       ` Federico Beffa
2015-01-16 20:47                                       ` Andreas Enge
  -- strict thread matches above, loose matches on Subject: below --
2015-01-17  9:46 Federico Beffa
2015-01-17 10:15 ` 宋文武
2015-01-17 12:02 ` Andreas Enge
2015-01-18  9:39   ` Federico Beffa
2015-01-18 13:16     ` Andreas Enge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKrPhPM9RZV-T+6KZMbuDKu-tPynGEwnFf43iPEPnjqKwuHZNQ@mail.gmail.com \
    --to=beffa@ieee.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.