On Tue, 2011-01-25 at 13:31 -0600, Mark Hatle wrote:
> On 1/25/11 12:36 PM, Lorenzati, Marcelo wrote:
> > Hi all,
> >
> > I wanted to know if it’s feasible to build Yocto with ulibc
> > instead of glibc and if someone have tried.
> >
> > In a really constrained system could be the
On Tue, 2011-01-25 at 20:41 +0100, Koen Kooi wrote:
> Op 25 jan 2011, om 20:18 heeft Koen Kooi het volgende geschreven:
> > Switchting from usrp-e1xx (armv7a) to beagleboard (also armv7a) and
> > building console-image again:
> >
> > NOTE: package perl-5.12.2-r0: task do_package: Started
> > ERRO
Op 25 jan 2011, om 20:18 heeft Koen Kooi het volgende geschreven:
>
> Op 25 jan 2011, om 19:34 heeft Koen Kooi het volgende geschreven:
>
>>
>> Op 25 jan 2011, om 14:57 heeft Richard Purdie het volgende geschreven:
>>
>>> As has been mentioned in other emails we're working on some major
>>> e
On 1/25/11 12:36 PM, Lorenzati, Marcelo wrote:
> Hi all,
>
> I wanted to know if it’s feasible to build Yocto with ulibc
> instead of glibc and if someone have tried.
>
> In a really constrained system could be the difference between selecting RT
> Linux or another real time OS.
>
Op 25 jan 2011, om 19:34 heeft Koen Kooi het volgende geschreven:
>
> Op 25 jan 2011, om 14:57 heeft Richard Purdie het volgende geschreven:
>
>> As has been mentioned in other emails we're working on some major
>> enhancements for the next release. Several components of these are now
>> ready
On Tue, Jan 25, 2011 at 12:20 PM, Saul Wold wrote:
> On 01/25/2011 07:59 AM, Bruce Ashfield wrote:
>>
>> We already had this fix in the 2.6.37 kernel (and it is staged
>> temporarily there) so this is the same change for the -stable
>> kernel to fix the perf build error reported by Gary this morni
Hi all,
I wanted to know if it's feasible to build Yocto with ulibc
instead of glibc and if someone have tried.
In a really constrained system could be the difference between selecting RT
Linux or another real time OS.
Regards
[cid:image001.gif@01CBBCA4.CBC86F00]
Marcelo Lorenz
Op 25 jan 2011, om 14:57 heeft Richard Purdie het volgende geschreven:
> As has been mentioned in other emails we're working on some major
> enhancements for the next release. Several components of these are now
> ready for merging to the master branch. These include:
>
> * Rework of the compile
On 01/25/2011 07:59 AM, Bruce Ashfield wrote:
We already had this fix in the 2.6.37 kernel (and it is staged
temporarily there) so this is the same change for the -stable
kernel to fix the perf build error reported by Gary this morning.
I went ahead and merged this to the kernel tree directly, s
Updating SRCREVs to reflect:
perf: hard-code NO_LIBPERL/NO_LIBPYTHON
ExtUtils::Embed ccopts is getting the host's -I/usr/local/include and
using it to compile perf, which results in a compilation error that
started appearing just recently.
This turns the code that makes use o
We already had this fix in the 2.6.37 kernel (and it is staged
temporarily there) so this is the same change for the -stable
kernel to fix the perf build error reported by Gary this morning.
I went ahead and merged this to the kernel tree directly, since
we may not loop back and do another fix for
Op 25 jan 2011, om 14:57 heeft Richard Purdie het volgende geschreven:
> As has been mentioned in other emails we're working on some major
> enhancements for the next release. Several components of these are now
> ready for merging to the master branch. These include:
>
> * Rework of the compile
As has been mentioned in other emails we're working on some major
enhancements for the next release. Several components of these are now
ready for merging to the master branch. These include:
* Rework of the compiler bootstrap process
If you've ever tried to run "bitbake eglibc -c clean;bitbake e
13 matches
Mail list logo