All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <yocto@yoctoproject.org>
Subject: Re: 1.2 release candidate 4 now available.
Date: Thu, 19 Apr 2012 09:36:02 -0500	[thread overview]
Message-ID: <4F9022D2.5030900@windriver.com> (raw)
In-Reply-To: <20120419102523.00657202B35@gemini.denx.de>

On 4/19/12 5:25 AM, Wolfgang Denk wrote:
> Dear Elizabeth,
>
> In message<CAPhnLPCs-57NxB5-O=YSiqbPzQk0xhigEEfDEhwrGB2_qtgJ3Q@mail.gmail.com>  you wrote:
>>
>> Release candidate 4 for 1.2 is now available for testing:
>
> Thanks.
>
>
> Sorry, here is a new Bug 2347 - libtool library files broken
>

I've commented on the bug report.  The libtool on the target being used to 
compile that item is broken in some way.  See the comments for a couple of 
possible solutions to the issue.

(For easy reference for people searching the email archives...)

The first question was, did you run libtoolize --copy --force before trying to 
compile?  If not, then the correct version of libtool is likely not being run 
from the build environment, but instead it's an older incompatible version 
included in the package being compiled.

Alternatively, if libtoolize was run, the target libtool itself is broken in 
some way related to the sysroots.  The libtool (.la) files themselves though 
appear to be correct based on the results of your grep.

--Mark

> Best regards,
>
> Wolfgang Denk
>



      reply	other threads:[~2012-04-19 14:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-19  0:21 1.2 release candidate 4 now available Flanagan, Elizabeth
2012-04-19 10:25 ` Wolfgang Denk
2012-04-19 14:36   ` Mark Hatle [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=4F9022D2.5030900@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.