1.2 release candidate 4 now available.

1.2 release candidate 4 now available.

[Flanagan, Elizabeth]

[-- Attachment #1: Type: text/plain, Size: 571 bytes --]

All,

Release candidate 4 for 1.2 is now available for testing:

http://autobuilder.yoctoproject.org/pub/nightly/20120418-2/

This is based off of:

http://git.yoctoproject.org/cgit/cgit.cgi/poky/log/?h=denzil

We had two additional documentation patches past the tag
1.2_M4.rc4.0<http://git.yoctoproject.org/cgit/cgit.cgi/poky/tag/?h=denzil&id=1.2_M4.rc4.0>.
These were included in the release candidate.

The adt repository is currently being populated with the results of this
buildout.



-- 
Elizabeth Flanagan
Yocto Project
Build and Release

[-- Attachment #2: Type: text/html, Size: 809 bytes --]

Re: 1.2 release candidate 4 now available.

[Wolfgang Denk]

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


Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Overdrawn?  But I still have checks left!

Re: 1.2 release candidate 4 now available.

[Mark Hatle]

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
>