From: Joaquim Duran <joaquinduran@adtelecom.es>
To: openembedded-devel@lists.openembedded.org
Subject: Re: gnome-vfs-2.20.0 needs glib-2.0-2.14.x
Date: Fri, 14 Mar 2008 09:35:43 +0100 [thread overview]
Message-ID: <47DA38DF.6020307@adtelecom.es> (raw)
In-Reply-To: <19c1b8a90803132350x14a3496en8e921fae09cf9aff@mail.gmail.com>
En/na Khem Raj ha escrit:
> Hi
>
> I stumbled upon this while compiling x11-image using
> angstrom-2008-1.conf that gnome-vfs does not build because it needs
> headers from glibc-2.0-2.14.x but in
> ngstrom-2008-preferred-versions.inc we override this
> PREFERRED_VERSION_glib-2.0 = "2.15.6"
>
> Should be still stick to 2.14.4 ?
>
> Thanks
>
> -Khem
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
>
Hello,
glib 2.15.x are development series. I think that 2.16.x series are out.
The last one is 2.16.1.
Joaquim Duran
next prev parent reply other threads:[~2008-03-14 7:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 6:50 gnome-vfs-2.20.0 needs glib-2.0-2.14.x Khem Raj
2008-03-14 8:35 ` Joaquim Duran [this message]
2008-03-15 17:21 ` Khem Raj
2008-03-16 7:57 ` Marcin Juszkiewicz
2008-03-16 8:09 ` Junqian Gordon Xu
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=47DA38DF.6020307@adtelecom.es \
--to=joaquinduran@adtelecom.es \
--cc=openembedded-devel@lists.openembedded.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.
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.