From: Lionel Landwerlin <llandwerlin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] libglib2 build failure
Date: Wed, 10 Feb 2010 10:56:06 +0100 [thread overview]
Message-ID: <4d28d4b51002100156r181bd836mf9c9f367c8578d53@mail.gmail.com> (raw)
In-Reply-To: <20100210082659.63d38b8c@surf>
On Wed, Feb 10, 2010 at 8:26 AM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:
> On Wed, 10 Feb 2010 07:26:06 +0100
> Lionel Landwerlin <llandwerlin@gmail.com> wrote:
>
> > I recompiled libglib2 2.22.4 recently with an external toolchain and
> > having libglib2-dev installed on my host, and I don't see the
> > problem...
>
> Ah, ah, interesting. Just for curiosity, which version of libtool is
> installed on your host ? On mine, it's libtool 1.5.26.
>
2.2.6b here
>
> > What if you set AUTORECONF=YES and LIBTOOL_PATCH=YES ?
>
> Well, I think LIBTOOL_PATCH=YES cannot work, since the
> buildroot-libtool.patch only applies properly to packages containing
> libtool 1.x, and libglib2 contains libtool 2.x.
>
AUTORECONF shouldn't run libtoolize ?
>
> Cheers,
>
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers, real-time and embedded Linux
> development, consulting, training and support.
> http://free-electrons.com
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100210/5c46827a/attachment.htm>
next prev parent reply other threads:[~2010-02-10 9:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 23:48 [Buildroot] libglib2 build failure Thomas Petazzoni
2010-02-10 6:26 ` Lionel Landwerlin
2010-02-10 7:26 ` Thomas Petazzoni
2010-02-10 7:51 ` Thomas Petazzoni
2010-02-10 10:06 ` Lionel Landwerlin
2010-02-11 7:44 ` Thomas Petazzoni
2010-02-10 9:56 ` Lionel Landwerlin [this message]
2010-02-12 7:49 ` Thomas Petazzoni
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=4d28d4b51002100156r181bd836mf9c9f367c8578d53@mail.gmail.com \
--to=llandwerlin@gmail.com \
--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 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.