From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Warnings during build
Date: Wed, 26 Mar 2014 20:15:27 +0100 [thread overview]
Message-ID: <20140326191527.GH3709@jama> (raw)
In-Reply-To: <CAFeBWL69O+4K4sP6jX1uFhPJ+K78Lh1DQLjwZrixRKK-wrYVRQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2293 bytes --]
On Wed, Mar 26, 2014 at 11:41:43AM -0700, Adam Lee wrote:
> I see! I trust bitbake to link against the right one (newer one that is).
bitbake doesn't know which one is right, that's why there is the warning
so
bitbake gtk something-which-links-with-im-ipa.so
and
bitbake gtk3 something-which-links-with-im-ipa.so
will give you different packages (well the same package but with
different runtime dependency).
> Thanks for ur response JaMa.
>
> Adam
>
>
> On Wed, Mar 26, 2014 at 11:28 AM, Martin Jansa <martin.jansa@gmail.com>wrote:
>
> > On Wed, Mar 26, 2014 at 11:12:28AM -0700, Adam Lee wrote:
> > > Hope I am not spamming the list with pesky questions.
> > > I am getting build warnings similar to below:
> > >
> > > WARNING: gtk-immodule-ipa-2.24.22 was registered as shlib provider for
> > > im-ipa.so, changing it to gtk3-immodule-ipa-3.10.7 because it was built
> > > later
> > >
> > >
> > > The full list of warnings can be found at - http://pastebin.com/quqwCPEq
> > .
> > >
> > > I am not sure what these warnings are. They are definitely new in 1.6. I
> > am
> > > trying to figure out if there is something I can do, or if this will be
> > > sorted out as we get closer to the 1.6 release date.
> >
> > See
> > http://comments.gmane.org/gmane.comp.handhelds.openembedded/62213
> >
> > as long as nothing tries to link against im-ipa.so it's safe and you
> > should just list them in PRIVATE_LIBS.
> >
> > The warning means that if something links with im-ipa.so then it's not
> > known if it will get runtime dependency on gtk-immodule-ipa-2.24.22 or
> > gtk3-immodule-ipa-3.10.7 (it will always be the one built later in the
> > same sysroot).
> >
> > --
> > Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
> >
> > --
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
> >
> >
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2014-03-26 19:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 18:12 Warnings during build Adam Lee
2014-03-26 18:28 ` Martin Jansa
2014-03-26 18:41 ` Adam Lee
2014-03-26 19:15 ` Martin Jansa [this message]
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=20140326191527.GH3709@jama \
--to=martin.jansa@gmail.com \
--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.