While googling, I found this link (http://mashandmish.wordpress.com/2011/04/20/crossbuilding-webkit-with-a-yocto-toolchain-part-i-glib/)
Here, the author is replacing the libtool generated by autoconf (./configure script) with the one form the sysroot. i.e. ./configure cp /opt/poky/1.0/sysroots/i686-pokysdk-linux/usr/bin/i686-pokysdk-libtool libtool I did the equivalent and amazingly got the same results. I am sure I am missing something. Just not sure what. On Mon, Jan 9, 2012 at 3:45 PM, autif khan <autif.ml...@gmail.com> wrote: > When I try to compile mono using the ADT (bitbake meta-ide-support, > source the environment file and configure, followed by make), I get > the same behavior. > > libtool: link: cannot find the library `=/usr/lib/libglib-2.0.la' or > unhandled argument `=/usr/lib/libglib-2.0.la' > > But then, even in this case, mono's autoconf (./configure) generated a > 'libtool' instead of using the one from yocto's development > environment. > > Please advise. > > Thanks > > Autif > > On Mon, Jan 9, 2012 at 3:12 PM, autif khan <autif.ml...@gmail.com> wrote: >> Here is a recipe that I using to generate a custom SDK image which I >> can use to natively compile mono on the target. >> >> require recipes-sato/images/core-image-sato-sdk.bb >> IMAGE_INSTALL += "bison libtool" >> PR="r0" >> >> bison is required and I added libtool because it was being generated >> by mono's autoconf (./configure) script and gave the following error: >> >> libtool: link: cannot find the library `=/usr/lib/libglib-2.0.la' or >> unhandled argument `=/usr/lib/libglib-2.0.la' >> >> If I understand correctly, yocto has a special libtool which >> understands how to handle '=/path/to/lib' >> >> The problem is that it looks like 'libtool' is not included in the >> image. I do have the libtool recipe in meta/recipes-devtools/libtool >> >> The libtool version generated by mono was 2.2.6b >> >> The libtoolize version in the image is 2.4 (automake 1.11.1, autoconf 2.68) >> >> Am I doing something wrong? If not, where is the 'libtool' in the image? >> >> Thanks >> >> Autif >> >> On Thu, Jan 5, 2012 at 4:59 PM, autif khan <autif.ml...@gmail.com> wrote: >>> I talked to a couple of mono developers (kangaroo and vargaz) - the >>> consensus is that "'auto' is hosed" >>> >>> I am not an expert in auto tools, I just know how to configure, make, >>> make install. >>> >>> I get by when I need to know my way around makefiles >>> >>> I am a capable C/C++ developer - please advise or point me to right >>> resources. >>> >>> Thanks >>> >>> Autif >>> >>> On Thu, Jan 5, 2012 at 4:52 PM, autif khan <autif.ml...@gmail.com> 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 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
