All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierluigi Passaro <pierluigi.passaro@phoenixsoftware.it>
To: openembedded-devel@lists.openembedded.org
Subject: Re: external-toolchain-csl and libtool 2.4
Date: Fri, 22 Oct 2010 23:31:08 +0200	[thread overview]
Message-ID: <4CC2029C.5070106@phoenixsoftware.it> (raw)
In-Reply-To: <AANLkTi=ir567dGvzgOTgwvba3M0k1wyWmAJiwG4HNeJG@mail.gmail.com>

Khem Raj wrote:
> On Thu, Oct 21, 2010 at 4:02 PM, Pierluigi Passaro
> <pierluigi.passaro@phoenixsoftware.it> wrote:
>   
>> Hi all,
>> LIBTOOL_HAS_SYSROOT feature has been recently enabled on Angstom 2010.x
>> distro.
>>
>> However, using CodeSourcery toolchain, this feature lead to use CSL sysroot
>> as search path, that is generally different from
>> ${STAGING_DIR_TARGET}${libdir} folder used for packages.
>>     
>
> hmmm yes I see the problem. Right now its left upto the compile to provide
> the sysroot which works well with internal toolchain but will not work with
> external toolchains or the compilers which dont support --print-sysroot option
>
> I will come up with a patch so specify the sysroot for libtool so that it
> does not rely upon the compiler to compute it.
>
>   
I'm not expert of libtool mechanisms but please let me know I can 
provide any support.
>> At present I worked around the problem with the attached patch, but I was
>> wondering if this could be a misconfiguration or a bug.
>>
>> Any suggestion will be appreciated.
>>
>>     
>
> With libtool 2.4 I dont see a reason to disable sysroot. The variable is only
> provided to keep libtool 2.2.6 functional as same time. So when using 2.4 please
> do not disable the sysroot feature.
>
>   
I agree with you, I will just keep the patch for personal use, until 
libtool will not rely on CSL compiler to compute sysroot.
>> Regards
>> Gigi
>>
>> --
>> Ing. Pierluigi Passaro
>> Viale Don Luigi Sturzo 34
>> 30174 Venezia Mestre
>> Cel: +39 348 355 4119
>> Tel: +39 041 862 3373
>> Fax: +39 041 862 3173
>> Web: www.phoenixsoftware.it
>> P.IVA 03884060272
>>
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>     
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>   



  reply	other threads:[~2010-10-22 23:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-21 23:02 external-toolchain-csl and libtool 2.4 Pierluigi Passaro
2010-10-22 20:49 ` Khem Raj
2010-10-22 21:31   ` Pierluigi Passaro [this message]
2010-10-23  5:04     ` Khem Raj
2010-10-29  9:29       ` Pierluigi Passaro

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=4CC2029C.5070106@phoenixsoftware.it \
    --to=pierluigi.passaro@phoenixsoftware.it \
    --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.