From: Mark Hatle <mark.hatle@windriver.com>
To: <yocto@yoctoproject.org>
Subject: Re: Trying to compile mono on target for machine crownbay
Date: Thu, 5 Jan 2012 16:17:27 -0600 [thread overview]
Message-ID: <4F062177.3010706@windriver.com> (raw)
In-Reply-To: <CADzUK1KR-tyiabskATGp1pH_yUN_AgiBA+EUv9mtsjuXfnB5uw@mail.gmail.com>
On 1/5/12 3:52 PM, autif khan wrote:
> I bitbaked core-image-sato-sdk, copied it to the target disk and tried
> to build mono natively on the target machine and I got the following
> error:
>
> libtool: link: cannot find the library `=/usr/lib/libglib-2.0.la' or
> unhandled argument `=/usr/lib/libglib-2.0.la'
The version of libtool you are currently using is damaged in some way. I
suspect the program is falling back and trying to use either a local version or
the host-system version.
The libtool located within the OE/Poky environment understands that when a "="
is predicating a path, it means locate the item within the sysroot at the
following path. Since the error indicates it doesn't understand that concept,
it appears that that version of libtool is broken.
Normally the autotools class will deal with this situation for you. Simply
inheriting autotools class usually does it.
--Mark
> the filesystem does have a /usr/lib/libglib-2.0.la and it seems to be valid
>
> I am not sure why there is a leading '=' in the path. Needless to say
> - mono builds fine on ubuntu, so it is unlikely (not impossible) to be
> a mono build issue.
>
> Has anyone seen anything like this with mono or some other piece of software?
>
> Thanks
>
> Autif
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
next prev parent reply other threads:[~2012-01-05 22:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 21:52 Trying to compile mono on target for machine crownbay autif khan
2012-01-05 21:59 ` autif khan
2012-01-09 20:12 ` autif khan
2012-01-09 20:45 ` autif khan
2012-01-09 21:39 ` autif khan
2012-01-05 22:17 ` Mark Hatle [this message]
2012-01-05 22:36 ` autif khan
2012-01-21 23:57 ` Khem Raj
2013-02-20 16:30 ` Evgheni Antropov
2013-02-27 15:26 ` Autif Khan
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=4F062177.3010706@windriver.com \
--to=mark.hatle@windriver.com \
--cc=yocto@yoctoproject.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.