Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 453] New: libglib2 autoreconfigure
Date: Mon, 13 Jul 2009 19:01:11 +0000 (UTC)	[thread overview]
Message-ID: <bug-453-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=453

              Host: x86-64
            Target: SH4
           Summary: libglib2 autoreconfigure
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: lionel.landwerlin at openwide.fr
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Hi,

currently it's not possible to reconfigure libglib2.

The main problem is gtk-doc. You can find a patch to fix the problem. Cairo has
a similar patch.

Regards,

Lionel


-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2009-07-13 19:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-13 19:01 bugzilla at busybox.net [this message]
2009-07-13 19:02 ` [Buildroot] [Bug 453] libglib2 autoreconfigure bugzilla at busybox.net
2009-07-13 19:50 ` [Buildroot] [Bug 453] libglib2 autoreconf bugzilla at busybox.net
2009-07-17  8:57 ` bugzilla at busybox.net
2009-07-17 10:13 ` bugzilla at busybox.net
2009-07-17 11:25 ` bugzilla at busybox.net
2009-07-17 12:51 ` bugzilla at busybox.net
2009-07-17 13:22 ` bugzilla at busybox.net
2009-07-17 14:50 ` bugzilla at busybox.net
2009-07-18 14:08 ` bugzilla at busybox.net
2009-08-07 22:06 ` bugzilla at busybox.net
2010-02-21 18:07 ` bugzilla at busybox.net

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=bug-453-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox