Re: [Angstrom-devel] Feed Server Mirror & Optical Experiments

[Philip Balister]

On 05/08/2015 04:48 PM, Marcel Ziswiler wrote:
> On Fri, 2015-04-24 at 08:50 +0200, Koen Kooi wrote:
>>> Op 22 apr. 2015, om 23:39 heeft Marcel Ziswiler 
>>>  het volgende geschreven:
>>> As you might know we at Toradex are using the Angstrom Distribution
>>> quite extensively basically since I started their Linux operation more
>>> than 4 years ago (;-p). The feed server outage of late has triggered
>>> quite some customer feedback and there is some internal discussion going
>>> on how such a condition could be avoided in the future. Given our IT's
>>> experience in running a globally distributed git server infrastructure
>>> we were wondering whether a globally mirrored feed server infrastructure
>>> would be of any value not only for our customers but also for the
>>> Angstrom community as a whole. What do you think about any of this? If
>>> this is anything you and the community consider worth pursuing we would
>>> need to know the storage and bandwidth requirements so we could further
>>> look into whether or not this is something Toradex could be hosting.
>>> Alternatively we could just run some optical experiments I guess (;-p).
>>
>> That sounds great, adding Tom King to CC: as well.
> 
> What's the status on this? It would be really sad if the current
> willingness of our global IT operation to provide the resources vanishes
> before we can make up our minds on how this actually needs to be done.

Is there a way to configure opkg to have two serers to chose from for
packages?

Philip

> 
> 
> ___
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel@linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
> 
> 

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] [RFC] repo based setup for angstrom

[Philip Balister]

On 10/22/2014 01:49 PM, Khem Raj wrote:
> Hi
> 
> I have been using repo based setup for angstrom distro for quite sometime now
> 
> https://github.com/kraj/angstrom-manifest
> 
> I would like to propose this to be included for mainline angstrom
> setup, therefore
> I am posting it here for comments and concerns

I haven;t used this one, but I use repo for oe-core based builds for
people doing gnuradio work and have had good results.

Philip

> 
> Looking for feedback
> 
> -Khem
> 
> ___
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel@linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
> 
> 

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Naming of the Angstrom derivative for resource limited systems

[Philip Balister]

On 10/03/2014 02:33 AM, Koen Kooi wrote:
> Hi,
> 
> I have a number of systems on my desk (Wifi accesspoints mainly) and a few I 
> want to buy (Arduino galileo, Intel edison) where the current angstrom config 
> just doesn't fit. My plan is to add a config to deal with those systems and 
> is binary incompatible with the regular angstrom. What I'm struggling with is 
> coming up with a catchy name for it. After discussing it with a few people in 
> person at Linaro Connect and virtually on IRC the following 2 options remain:
> 
> 1) The Angstrom of Things (AoT)
> 2) Internet of Things - Angstrom (iota)
> 
> What are your thoughts on all this?

Why doesn't the current config work?

Philip

> 
> thanks,
> 
> Koen
> ___
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel@linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
> 
> 

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Definition of Angstrom tasks

[Philip Balister]

On 05/05/2014 03:05 PM, Bob Feretich wrote:
> Is there a document that provides a detailed definition of what each
> these tasks do?
> Yocto, OE, and bitbake manuals tell us how to command a specific task to
> be run, but not what they do.

I'd send this to yo...@yoctoproject.org since it is a general interest
question.

Philip

> 
> The task name provides a good hint sometimes, but often that is not
> enough. Users shouldn't have to read the python code for this
> information. These descriptions should be a part of the yocto manual.
> 
> Sections 5.3.4 to 5.3.11 of the Yocto mega-manual provide a good
> overview of some of these tasks in the context of a workflow, but
> doesn't mention most of these tasks and doesn't go into enough detail on
> the tasks it discusses.
> 
> It wouldn't be appropriate to add more detail at that point in the
> manual, but it would be appropriate to include details regarding all of
> the tasks in an appendix.
> 
> Examples...
> The manual states that do_fetch fetches source, but doesn't state that
> when git is used whether it performs a pull, fetch, or clone. What are
> the common failure conditions of do_fetch? And what should the user do
> to fix the problem?
> 
> do_build is mentioned a few times, but there is no reference to it being
> the default task or what tasks are invoked by do_build and which are
> omitted.
> 
> do_rm_work and do_wm_work_all are not mentioned at all.
> 
> Result of listtasks:
> do_fetchall
> do_build
> do_devshell
> do_package_write_ipk
> do_cleansstate
> do_savedefconfig
> do_uboot_mkimage
> do_sizecheck
> do_strip
> do_packagedata_setscene
> do_configure
> do_clean
> do_deploy_setscene
> do_cleanall
> do_populate_lic
> do_populate_sysroot
> do_devicetree_image
> do_deploy
> do_menuconfig
> do_patch
> do_bundle_initramfs
> do_packagedata
> do_listtasks
> do_compile
> do_package_setscene
> do_populate_lic_setscene
> do_fetch
> do_checkuri
> do_compile_kernelmodules
> do_package_write_ipk_setscene
> do_package_write
> do_rm_work
> do_package
> do_unpack
> do_install
> do_checkuriall
> do_populate_sysroot_setscene
> do_rm_work_all
> 
> I don't have the knowledge to create such an appendix, but I volunteer
> to be a proofreader.
> 
> Regards,
> Bob
> 
> ___
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel@linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
> 
> 

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] U-Boot in meta-ti is broken

[Philip Balister]

On 01/17/2014 02:00 PM, Ulf Samuelsson wrote:
> It looks like the some of the u-boot recipes in meta-ti are broken.
> They do not include COMPATIBLE_MACHINE statements,
> so when building u-boot for non-ti machines, this  recipe is choosen
> instead.
> 
> This includes the u-boot 13.01 recipe

Should this email be o nthe meta-ti list?

Philip

> 
> BR
> 
> 
> ___
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel@linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
> 
> 

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Angstrom server down?

[Philip Balister]

On 11/22/2013 09:28 AM, Tim wrote:
> Hello,
> 
> I am trying to get started with an Angstrom toolchain for Beaglebone
> development, and I notice that this link seems to be
> broken.http://www.angstrom-distribution.org/simplified-development-setup
> 
> 
> 
> Do you know if there is a cached copy of that explanation of how to set
> up the toolchain?
> 
> Thanks for your time,

Try bitbake -c populate_sdk image-name if you have setup the build
environment.

Philip

> 
> Tim
> 
> 
> ___
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel@linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
> 
> 

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] v2013.06 and v2013.12 architecture change for ARMv7A machines

[Philip Balister]

On 10/27/2013 12:53 PM, Koen Kooi wrote:
> On Wed, 2013-10-23 at 18:30 +0200, Björn Krombholz wrote:
>> On 10/20/2013 09:04 PM, Koen Kooi wrote:
>>> Then I noticed that the 'genericarmv7a' machine in meta-linaro set
>>> the DEFAULTTUNE to armv7athf-neon. A MACHINE config shouldn't set
>>> that variable, but that's a different bug. It turns out that using
>>> that tune we can have a single feed again for all armv7a machines.
>>
>> Hi,
>>
>> just for clarification, I'm not sure where to set it if not in the 
>> MACHINE config without modifying meta-angstrom.
>>
>> I've seen you added MACHINE specific DEFAULTTUNEs based on the currently 
>> supported boards.
>> Basically the result should be (IMHO):
>> if MACHINE is a armv7a based and DISTRO is angstrom, then
>> DEFAULTTUNE = "armv7athf-neon"
>>
>> Would it be possible to add those definitions based on SOC_FAMILY:
>> DEFAULTTUNE_ti33x and DEFAULTTUNE_omap3?
> 
> I hope so, see below.
> 
>> As of now, when I add a new MACHINE=machfoo based on ti33x.inc from 
>> meta-ti, I end up with a DEFAULTTUNE=armv7a-neon instead of the new one, 
>> as the board is not known in meta-angstrom.
>>
>> I added
>> DEFAULTTUNE_machfoo = "${DEFAULTTUNE_genericarmv7a}"
>> to the machfoo.conf which is discouraged, if I understand you correctly.
>>
>> Maybe I'm just missing the obvious safe way?
> 
> There is no obvious safe way :( You are running into the same problems
> Khem and I ran into with the oe-core way of doing tune files.
> This is a big problem and needs to get fixed somehow.

Can we get a good description of the problem in the Yocto Project Bugzilla?

Philip

> 
> regards,
> 
> Koen
> 
> 
> 
> ___
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel@linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
> 

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Looking for an Angstrom and bitbake expert to consult / contract

[Philip Balister]

On 10/23/2013 11:42 PM, Edward Vidal wrote:
> Hello Chris,
> I have been working with Yocto for  beaglebone, beagleboard, pandaboard and
> now with the zedboard.  I have tried angstrom but found yocto to be a
> better approach for me.  For the zedboard I need to linux systems a

Angstrom is Yocto Project Compatible.

http://www.angstrom-distribution.org/yocto-project-compatible-status

Philip

> CentOSx6.4 x86_64 for the xilinx tools and a Fedora18x86_64 for yocto.  I
> build my system with a liveDVD and with cobbler over the network.
> Are you knowledgeable in git, Linux kernel, and general Linux?  What
> processor are  you looking to build for?  Is your application for a real
> time application or just embedded?
> With yocto you download the software and cross compile for you processor.
> You can call me at 915-595-1613 or 915-346-1476. I am located in El Paso
> Tex MST. My other e-mail is devel...@sbcglobal.net.
> If you want more information let me I can send my resume and cover letter.
> Regards
> 
> 
> On Wed, Oct 23, 2013 at 1:47 PM, Chris Morgan  wrote:
> 
>> Hello.
>>
>> We are looking at using Angstrom and bitbake. There are several areas
>> where we could use an expert that could both consult on questions and
>> approaches as well as help implement some of the customization that we
>> may need to ship product.
>>
>> This might start out as a several hour contract, phone or email
>> consultation, and extend to a handful of weeks.
>>
>> We are located in the Boston area but remote is fine.
>>
>> If you might be interested please send me a short email letting me
>> know what your rate would be, a little about your background and some
>> way to get in touch.
>>
>> Chris
>>
>> ___
>> Angstrom-distro-devel mailing list
>> Angstrom-distro-devel@linuxtogo.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
>>
>>
>>
>> ___
>> Angstrom-distro-devel mailing list
>> Angstrom-distro-devel@linuxtogo.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] v2013.06 and v2013.12 architecture change for ARMv7A machines

[Philip Balister]

On 10/20/2013 05:49 PM, Ulf Samuelsson wrote:
> 
> 
> 20 okt 2013 kl. 21:04 skrev Koen Kooi :
> 
>> Hi,
>>
>> A while ago we decided to switch armv7a machines for hardfloat because we 
>> were worn it with explaining that there's no real world difference between 
>> softfp (which does use hw fp despite its name) and hardfp and silicon 
>> vendors started moving their evil binary only stuff to that as well. So we 
>> looked into it and set the DEFAULTTUNE to cortexa8hf-neon. That gave us a 
>> hardfp build and it had no regressions so far, so good.
>>
> 
> So how are Cortex-A5 chips without neon going to be handled?
> They are also armv7a!

A5 or A15? We need an arm decoder ring!

Philip


> 
> Been struggling with this, during the weekend, since some recipes assume hat 
> if
> It is an arm7a, then Neon should be turned on.
> 
> Best Regards
> Ulf Samuelsson
> u...@emagii.com
> 
> 
> 
>> Two weeks ago I switched jobs and had to dust off my pandaboards for the new 
>> job and that's were things starting going south. 'cortexa8hf-neon' didn't 
>> work since the buildsystem knew it was an cortex-A9 CPU, so 
>> 'cortexa9hf-neon' needed to be used. Again that built and worked. But it 
>> required two seperate feeds that were  a single feed in v2012.12 and 
>> earlier. Then I started looking at cortex-A15 boards and realized this setup 
>> is wasting disk space and cpu time.
>>
>> Then I noticed that the 'genericarmv7a' machine in meta-linaro set the 
>> DEFAULTTUNE to armv7athf-neon. A MACHINE config shouldn't set that variable, 
>> but that's a different bug. It turns out that using that tune we can have a 
>> single feed again for all armv7a machines. Yay!
>>
>> If you have been using v2013.06 and your architecture for the feeds is 
>> cortexa*hf*, try doing the following:
>>
>>opkg update ; opkg install angstrom-feed-configs
>>opkg update ; opkg install opkg-config-base 
>>
>> That will update the feed configs to point to the new unified feed and drag 
>> in the /etc/opkg/arch.conf that lists the new armv7ahf-vfp-neon architecture 
>> as supported. It will throw a ton of warnings for the currently installed 
>> packages, but that's mostly harmless. Installing things from the feeds will 
>> work again, but it will try to reinstall a lot of things due to the 
>> architecture change.
>>
>> The v2013.12 feed will be cleaned up later, all the conferences will 
>> interfere with that.
>>
>> It looks like the complete angstrom cabal will be present at ELC-E in 
>> Edinburgh next week and at least 3 of us will also be attending Linaro 
>> Connect USA the week after that. If you're in the neighbourhood come say 
>> hello and please tell us about your pet peeve with angstrom or OE and we'll 
>> try to address it.
>>
>> thanks,
>>
>> Koen
>> ___
>> Angstrom-distro-devel mailing list
>> Angstrom-distro-devel@linuxtogo.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
> 
> ___
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel@linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
> 
> 

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Angstrom v2013.12 branched

[Philip Balister]

On 10/09/2013 11:29 AM, Khem Raj wrote:
> 
> On Oct 9, 2013, at 12:09 AM, Koen Kooi  wrote:
> 
>> All,
>>
>> The Angstrom v2013.12 release branch was opened today. This release will 
>> match the Yocto Project 1.5 release. Patches are very welcome, but keep in 
>> mind that it's not ready for consumption till the official release point in 
>> december.
>>
> 
> I would like to turn on gold as default linker, if people think its too late 
> then we can skip it for 2013.12

I'd like to stay as close to 1.5 as possible. I'm assuming 1.5 does not
use gold as a default?

Philip

> 
>> regards,
>>
>> Koen
>> ___
>> Angstrom-distro-devel mailing list
>> Angstrom-distro-devel@linuxtogo.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
> 
> 
> ___
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel@linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
> 
> 

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Narcissus update to v2012.12, please read

[Philip Balister]

On 03/22/2013 06:41 AM, Nicolas Aguirre wrote:
> 2013/3/22 Koen Kooi :
>>
>> Op 21 mrt. 2013, om 18:33 heeft Nicolas Aguirre  
>> het volgende geschreven:
>>
>>> Hi,
>>>
>>> I'm currently working on an home automation project (calaos), which
>>> uses angstrom and oe-core + my own recipes [1][2]. I "maitains" a set
>>> of machine for this project :
>>> n450
>>> cubieboard
>>> mele a1000/2000
>>> cubox
>>> olinuxino-a13
>>> rasberry-pi
>>>
>>> mele a1000/2000, cubieboard and olinuxino-a13 is based on meta-allwinner [3]
>>> cubox is based on meta-cubox [4]
>>>
>>> I'm using the danny branch for all my layers, so i guess i can help
>>> here. I attached the patch for the support of allwinner and cubox.
>>>
>>> I will run a build for mele/cubieboard/olinuxino and cubox during the
>>> night and tomorrow to check that everything build correctly with
>>> setup-scripts.
>>
>> Same comment I made a few months ago:
>>
>> DEFAULTTUNE="cortexa8hf-neon"
>>
>> Hardfloat/softfp t is a DISTRO decision, not a machine decision, so I can't 
>> add meta-allwinner and meta-cubox to Angstrom with that setting in the 
>> machine configs.
>>
>> regards,
>>
>> Koen
>> ___
>> Angstrom-distro-devel mailing list
>> Angstrom-distro-devel@linuxtogo.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
> 
> Ok, i was not aware about that, and it makes sense.
> So it's ok if i just remove this line in both machine configuration ?

And this is only an abi change, and does not prevent Angstrom from using
the floating point unit :)

The main change (in my understanding) with the hf abi is that a function
can return a value in one of the NEON registers.

Philip

PS: I know everyone already knows this, but it still comes up from time
to time.



> 
> --
> Nicolas Aguirre
> Mail: aguirre.nico...@gmail.com
> Web: http://enna.geexbox.org
> Blog: http://dev.enlightenment.fr/~captainigloo/
> 
> ___
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel@linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
> 

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Narcissus update to v2012.12, please read

[Philip Balister]

On 03/21/2013 11:33 AM, Nicolas Aguirre wrote:
> Hi,
> 
> I'm currently working on an home automation project (calaos), which
> uses angstrom and oe-core + my own recipes [1][2]. I "maitains" a set
> of machine for this project :
> n450
> cubieboard
> mele a1000/2000
> cubox
> olinuxino-a13
> rasberry-pi
> 
> mele a1000/2000, cubieboard and olinuxino-a13 is based on meta-allwinner [3]
> cubox is based on meta-cubox [4]
> 
> I'm using the danny branch for all my layers, so i guess i can help
> here. I attached the patch for the support of allwinner and cubox.
> 
> I will run a build for mele/cubieboard/olinuxino and cubox during the
> night and tomorrow to check that everything build correctly with
> setup-scripts.

Thanks!

Philip


> 
> Best regards,
> Nicolas
> 
> [1] https://github.com/enna-project/enna-os
> [2] https://github.com/naguirre/meta-enna
> [3] https://github.com/naguirre/meta-allwinner
> [4] https://github.com/naguirre/meta-cubox
> 
> 2013/3/21 Koen Kooi :
>> Hi,
>>
>> Work on narcissus has started again and I ran into a problem: packagenames 
>> have changed *again* between releases. So the plan was to dump OE-classic 
>> based releases and support v2012.05 and v2012.12. But between those two 
>> releases all 'task' packages have been renamed to 'packagegroup'. So in 
>> order to keep your favourite machine supported please do the following:
>>
>> 1) check if that machine has a BSP layer available that works against Yocto 
>> Project release 1.3 "Danny". If not, volunteer to maintain such a layer.
>> 2) check if that layer is already included in the angstrom setup-scripts for 
>> v2012.12. If not, send a patch/github pull request
>> 3) Ask for the layer to be added to the autobuilder.
>>
>> The current list of supported machines is sadly very short:
>>
>> beagleboard
>> beaglebone
>> fri2
>> minnow
>> qemuarm
>> qemumips
>> qemuppc
>> qemux86
>>
>> and possibly raspberry-pi
>>
>> thanks,
>>
>> Koen
>> ___
>> Angstrom-distro-devel mailing list
>> Angstrom-distro-devel@linuxtogo.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
> 
> 
> 
> 
> 
> ___
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel@linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
> 

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] systemd - udev conflicts

[Philip Balister]

Can you post the stuff at the start of the build log so we know what
layers/branches/versions are being built?

Philip

On 01/17/2013 02:33 PM, David Lambert wrote:
> I am not sure whether this is a Beaglebone or Angstrom issue, so I am
> posting it to both:
> 
> Over the past couple of weeks I have noticed that the build system
> appears to be unstable. Various errors relating to systemd and udev have
> appeared. Some workarounds have been suggested and seem to work for a
> while, but after ./oebb.sh update similar problems occur. Is this a
> known issue with Angstrom/Beaglebone? If so, is there a fix in the
> works? If not, could someone please guide me as to what I may be doing
> wrong.
> 
> Regards,
> 
> Dave.
> 
> 
> My work-flow is as follows:
> 
> cd ~/
> rm -rf ~/beaglebone
> mkdir -p ~/beaglebone
> cd ~/beaglebone
> git clone git://github.com/Angstrom-distribution/setup-scripts.git
> cd setup-scripts
> MACHINE=beaglebone ./oebb.sh config beaglebone
> MACHINE=beaglebone ./oebb.sh update
> . ~/.oe/environment-angstromv2012.05
> bitbake systemd-image
> 
> 
> <--snip-->
> 
> NOTE: Resolving any missing task queue dependencies
> NOTE: preferred version 189 of systemd not available (for item udev)
> NOTE: versions of systemd available: v189
> NOTE: preferred version 189 of systemd not available (for item systemd)
> NOTE: versions of systemd available: git v189
> NOTE: preferred version 189 of systemd not available (for item udev)
> NOTE: versions of systemd available: v189
> NOTE: preferred version 189 of systemd not available (for item
> udev-systemd)
> NOTE: versions of systemd available: v189
> NOTE: preferred version 189 of systemd not available (for item udev-utils)
> NOTE: versions of systemd available: v189
> NOTE: preferred version 189 of systemd not available (for item systemd-dev)
> NOTE: versions of systemd available: git v189
> NOTE: preferred version 189 of systemd not available (for item systemd)
> NOTE: versions of systemd available: git v189
> NOTE: Preparing runqueue
> ERROR: Multiple .bb files are due to be built which each provide systemd
> (/home/dlambert/beaglebone/setup-scripts/sources/meta-openembedded/meta-oe/recipes-core/systemd/systemd_v189.bb
> /home/dlambert/beaglebone/setup-scripts/sources/meta-openembedded/meta-oe/recipes-core/systemd/systemd_git.bb).
> 
>  This usually means one provides something the other doesn't and should.
> NOTE: Executing SetScene Tasks
> NOTE: Executing RunQueue Tasks
> NOTE: Running task 1553 of 3282 (ID: 1119,
> /home/dlambert/beaglebone/setup-scripts/sources/meta-ti/recipes-kernel/linux/linux-ti33x-psp_3.2.bb,
> do_package_write_ipk)
> 
> <--snip-->
> 
> | checking pkg-config is at least version 0.9.0... yes
> | checking for UDEV... no
> | configure: error: Package requirements ( libudev >= 172 ) were not met:
> |
> | No package 'libudev' found
> |
> | Consider adjusting the PKG_CONFIG_PATH environment variable if you
> | installed software in a non-standard prefix.
> |
> | Alternatively, you may set the environment variables UDEV_CFLAGS
> | and UDEV_LIBS to avoid the need to call pkg-config.
> | See the pkg-config man page for more details.
> | ERROR: oe_runconf failed
> NOTE: package systemd-git-r28: task do_configure: Failed
> ERROR: Task 165
> (/home/dlambert/beaglebone/setup-scripts/sources/meta-openembedded/meta-oe/recipes-core/systemd/systemd_git.bb,
> do_configure) failed with exit code '1'
> Waiting for 1 running tasks to finish:
> 0:
> linux-ti33x-psp-3.2.34-r18a+gitr720e07b4c1f687b61b147b31c698cb6816d72f01
> do_package_write_ipk (pid 22350)
> 
> 
> ___
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel@linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
> 

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] SDK for systemd-image error

[Philip Balister]

On 12/19/2012 02:06 AM, Bjørn Forsman wrote:
> On 19 December 2012 05:09, Peter Kurrasch  wrote:
>> Previously...
>>
 I only switched the branch of setup-scripts to
 angstrom-v2012.12-yocto1.3. Because in master "bitbake systemd-image
 -c populate_sdk" doesn't work at all (as the populate_sdk thingy came
 in yocto 1.2+).
>>
>> ...snip...
>>>
>>> I pull the setup-scripts from github and execute the following:
>>>
>>> $ git clone git://github.com/Angstrom-distribution/setup-scripts.git
>>> $ cd setup-scripts
>>> $ MACHINE=beaglebone ./oebb.sh config beaglebone
>>> $ MACHINE=beaglebone ./oebb.sh bitbake systemd-image
>>
>>
>> Point of information: the above procedure should give you
>> "angstrom-v2012.05-yocto1.2" whereas Bjorn is trying to use
>> "angstrom-v2012.12-yocto1.3".  I don't think this later version is formally
>> released yet?  (BTW--I found this in my sources/layers.txt file.)
>>
>> Regarding the 2012.12 release, I saw on one of the myriad sites/pages/wikis
>> I've reviewed recently that a "meta-beagleboard" will (or probably will) be
>> introduced.  The page mentioned this in conjunction with audio drivers and
>> there's something about it not being ready yet, blah blah blah.  The point
>> is that I wonder if the release is ready for prime time yet and if something
>> fancy like populate_sdk is sufficiently fleshed out?
> 
> Ok. But as far as the populate_sdk task goes, it seemed to work in the
> angstrom-v2012.12-yocto1.3 branch. Except for the openssh/dropbear
> conflict with the systemd-image, which is the reason for this thread.
> "bitbake core-image-minimal -c populate_sdk" works.

I am pretty sure populate_sdk is new to 1.3.

Philip

> 
>> As for dealing with SDK's, this is something I've been trying to wrap my
>> head around for a while.  I've come across the Arago project (also as
>> meta-arago) and the Sitara SDK--actually, any number of different TI SDKs.
>> I've been wondering how the meta-arago is supposed to tie-in with
>> meta-angstrom but haven't seen anyone who says it can be done.  I also don't
>> understand how the Sitara SDK is supposed to work here since it provides its
>> own toolchain and doesn't seem to have a particular association with a Linux
>> release/distribution.
> 
> Yeah, TI has their own SDK(s) and I have no idea how that maps into
> openembedded. I think TI often use the CodeSourcery (now Mentor)
> toolchain for their SDKs.
> 
>> I assume, Bjorn, that all you want to do is build new code using the same
>> headers, compilers, etc. as was used to build Angstrom...is that right?
>> This is what I'd like to do, myself, but so far I haven't quite figured that
>> out.  I did do a sample program using the Sitara SDK but haven't tried
>> anything too ambitious yet.
> 
> Yes, I'd like to get the toolchain, headers and libraries that was
> used to build the systemd-image.
> 
> I got "meta-toolchain" and "meta-toolchain-sdk" working. The first is
> (AFAIK) just the toolchain with libc (no extra libraries). And the
> latter is an alias for "meta-toolchain-gmae" which is a toolchain
> suitable for the "Gnome Mobile Application Environment". It has a
> bunch of additinal libraries and headers. But to use this SDK thing I
> need to be able to control what goes into it.
> 
> I'm now thinking about just using the toolchain and sysroot from the
> build dir...
> 
>> Just trying to make sense of all this stuff
> 
> Me too :-)
> 
> Best regards,
> Bjørn Forsman
> 
> ___
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel@linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
> 

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] How-to add boost headers for cross compile?

[Philip Balister]

On 12/11/2012 04:08 PM, Alan DuBoff wrote:

Is there an easy way to include the boost headers for cross compiling
within bitbake?


Boost should just work, as long as your recipe DEPENDS on it.

Philip



--

Regards,
Alan

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel




___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Removing x11 from DISTRO_FEATURES

[Philip Balister]

On 09/12/2012 03:06 PM, Daniel Lazzari wrote:

Hey everyone,

I have something of an odd request, but I can't figure out how to do this on my 
own. We are using Angstrom as our distro, but we have our own overlay layer and 
our own custom image recipes. We have recently been adding some new packages to 
our builds and it's been causing some trouble since they're pulling in x11 
packages. Looking at the recipes for the packages, just removing x11 from 
DISTRO_FEATURES would exclude all of the stuff we don't want, but I can't seem 
to figure out how to do that. It appears that the meta-angstrom distro.conf is 
parsed very late and overrides anything we put in our own layer.

Does anyone have a good way of doing this?

Sorry if this is the wrong list for this question.


From a philosophical point of view, Angstrom supports X11, so removing 
it from DISTRO_FEATURES means you are not really Angstrom. And your 
packages are incompatible with the packages in the feeds.


You should be able to only install the packages without the X11 bits if 
you are careful, bt I understand in practice that can be very tricky to 
get exactly correct.


Philip



Dan Lazzari Jr.
Firmware Engineer
dlazz...@leapfrog.com


___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel




___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] http://apc.io/

[Philip Balister]

On 09/05/2012 11:23 AM, i...@maki3000.net wrote:

hello

will there be an angstrom distribution for the http://apc.io/ once?


If someone writes a BSP layer for it.

Philip





___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel




___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Beaglebone Angstrom Build fails on gettext-native-0.18.1.1-r11

[Philip Balister]

On 08/30/2012 09:00 AM, Koen Kooi wrote:


Op 30 aug. 2012, om 01:27 heeft Wes Erhart  het volgende 
geschreven:


My local.conf. Note the comment in front of INHERIT += "rm_work" -- I won't


"won't" or "want"?


to keep the files around to use as a cross compile environment.  (If you
have any pointers to the "proper" way to do this, please point a way).



OpenEmbedded *is* a cross-compile environment and doesn't need those 
intermediate files, so I don't get what your are saying.


If you want a toolchain, try bitbake meta-toolchain. Also, even with 
rm-work, you can use the sysroots to get a cross compile environment for 
external development. I've used both methods successfully.


Philip


___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel




___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Multitasking using Angstrom

[Philip Balister]

On 08/26/2012 01:07 PM, anky mishra wrote:

Hi,

Im new to Angstrom. I have ported Angstrom to Beagle Board xM. Now i want
to create a program that will run automatically (without having to use the
GUI), the code will be Multitasking based..

However i cannot find any reference manual for Angstrom for creating tasks,
controlling resources etc.

Please Help me by providing a reference manual(if possible), or any other
way i can achieve the above said goal.


Developing a good understanding of Linux would be a god start to 
answering these questions.


Philip



Thanks

Ankit Mishra
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel




___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Narcissus update <- IMPORTANT

[Philip Balister]

On 05/03/2012 05:49 AM, Koen Kooi wrote:
> The process to add machines is fairly simple:
> 
> 1) Find the layer for the machine in 
> http://www.openembedded.org/wiki/LayerIndex
> 2) Check the setup scripts to see if it's already configured
> 3) Send patch for setupscripts
> 4) Send patch for narcissus

Does anyone know a good way to collect votes from users interested in
machines, but unable to commit to supporting them? This would be useful
feedback for people interested in adding machines back.

As we add machines back, I'd like to see two things:

1) No machine added unless someone is willing to handle questions on the
lists.

2) No machines added unless we know people want to use it.

I'd like to see more focus on getting Angstrom working well for a
"reasonable" set of machines, and less focus on supporting every
available combination of inits/libcs/machines.

Philip

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Setup-scripts branched for upcoming release

[Philip Balister]

On 04/18/2012 11:12 AM, Graeme Gregory wrote:
> On 18/04/12 16:08, Koen Kooi wrote:
>> What the default branch for the setup-scripts is after the release (master 
>> or release branch) is up for discussion on this list :)
>>
> Release!
> 
> Lets keep the beginners off the cutting edge!
> 
> Also still getting complaints about hidden sudo commands in
> setup-scripts, would be good to remove them before release! My opinion
> on these is we should print the instuctions and bail out at this point!

I also agree, hidden sudo must go. They annoy the brighter users, and
they are the people we want to attract.

Philip

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Ruby for Angstrom?

[Philip Balister]

On 03/27/2012 07:57 AM, Graeme Gregory wrote:
> On 27/03/2012 12:55, Philip Balister wrote:
>> On 03/27/2012 04:14 AM, Paul Eggleton wrote:
>>> Koen Kooi wrote:
>>>> Op 26 mrt. 2012, om 22:02 heeft Jacek Radzikowski het volgende geschreven:
>>>>> That turned to be easier than I thought. How can I commit the recipe
>>>>> to the main angstrom repository?
>>>> It should probably live in the meta-openembedded repository in the meta-oe
>>>> layer, follow the readme to see where to git send-email the patch to.
>>> Let's have them in their own separate layer (meta-ruby), since it's not
>>> unlikely the number of ruby recipes will increase over time.
>> Aren't we getting a little layer happy?
>>
>> How many recipes would really be in such a layer?
>>
>>
> As ruby has its own equivalent of CPAN, then thousands if some actual
> ruby programmer starts using it.
> 
> Graeme
> 
> 
> ___
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel@linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
> 

OK, I am wrong :) It does sound like a good candidate for a layer.

Philip

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Ruby for Angstrom?

[Philip Balister]

On 03/27/2012 04:14 AM, Paul Eggleton wrote:
> Koen Kooi wrote:
>> Op 26 mrt. 2012, om 22:02 heeft Jacek Radzikowski het volgende geschreven:
>>> That turned to be easier than I thought. How can I commit the recipe
>>> to the main angstrom repository?
>>
>> It should probably live in the meta-openembedded repository in the meta-oe
>> layer, follow the readme to see where to git send-email the patch to.
> 
> Let's have them in their own separate layer (meta-ruby), since it's not
> unlikely the number of ruby recipes will increase over time.

Aren't we getting a little layer happy?

How many recipes would really be in such a layer?

Philip

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] python-numpy build failure for cloud9-image?

[Philip Balister]

Remove it from the image you are building.

Philip

On 03/10/2012 11:36 PM, Russell Senior wrote:
> what is the easiest way to turn off the numpy build?
> On Mar 10, 2012 2:34 PM, "Philip Balister"  wrote:
> 
>> On 03/10/2012 07:41 PM, Russell Senior wrote:
>>>>>>>> "Koen" == Koen Kooi  writes:
>>>
>>> Koen> Op 9 mrt. 2012, om 23:28 heeft Russell Senior het volgende
>>> Koen> geschreven:
>>>
>>>>>  This appears to be a missing cross-compiling gfortran?
>>>
>>> Koen> Actually no, it will fail to build if you have blas-dev and
>>> Koen> lapack-dev installed on your host. Numpy is basically unfixable,
>>> Koen> so the recommended course of action is to uninstall those
>>> Koen> development packages from your host...
>>>
>>> Those development packages are in use.
>>
>> Basically, do not do oe builds that need numpy on machines where you
>> need the atlas and blas development packages.
>>
>> Yes it is a pain and I learned this the hard way.
>>
>> Philip
>>
>> ___
>> Angstrom-distro-devel mailing list
>> Angstrom-distro-devel@linuxtogo.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
>>
> ___
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel@linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
> 

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] python-numpy build failure for cloud9-image?

[Philip Balister]

On 03/10/2012 07:41 PM, Russell Senior wrote:
>> "Koen" == Koen Kooi  writes:
> 
> Koen> Op 9 mrt. 2012, om 23:28 heeft Russell Senior het volgende
> Koen> geschreven:
> 
>>>  This appears to be a missing cross-compiling gfortran?
> 
> Koen> Actually no, it will fail to build if you have blas-dev and
> Koen> lapack-dev installed on your host. Numpy is basically unfixable,
> Koen> so the recommended course of action is to uninstall those
> Koen> development packages from your host...
> 
> Those development packages are in use.  

Basically, do not do oe builds that need numpy on machines where you
need the atlas and blas development packages.

Yes it is a pain and I learned this the hard way.

Philip

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] No more minimal-image

[Philip Balister]

On 02/20/2012 04:31 AM, Christophe Aeschlimann wrote:
> On 17.02.2012 19:08, Philip Balister wrote:
> 
>> On 02/17/2012 04:06 AM, Christophe Aeschlimann wrote:
>>> On 17.02.2012 12:13, Samuel Stirtzel wrote:
>>>
>>>> 2012/2/17 Christophe Aeschlimann :
>>>
>>> Hi and thank you for your suggestion.
>>>
>>> I had a look at this oe-core recipe and it would definitely fit my
>>> rootfs size requirement but it looks like it really hasn't much included
>>> and it doesn't include any Angstrom configuration. Maybe it's a starting
>>> point but to be honest I would prefer to remove what I don't need than
>>> to spend a lot of time figuring out what I'm missing :)
>>
>> RP and I (and some others) have been talking about this at ELC this week.
>>
>> He swears the correct answer is run hob to create the image. The hob
>> should save the image spec as a bb file that you could edit "normally"
>> later :)
>>
>> He claims this will work with OE-Core + Angstrom and will address bugs
>> in this config. I am going to try this when I get home.
>>
>> I do not think hob supports systemd (yet) but we should go ahead and
>> test. Please send feedback to the oe-core list.
>>
>> Philip 
> 
> 
> Is it because of the systemd incompatibility that I don't see any of the
> Angstrom images in the "base image" drop down list ? Because I see all
> the oe-core images plus the extra image I created by inheriting
> core-image-minimal.bb but not the Angstrom one. Or maybe the tool only
> lists the images inheriting core-image ?
> 
> The Angstrom layer is listed in the available layers in the layer
> configuration dialog and is enabled. (and I can see the angstrom tasks
> and extra packages).

You are getting further than me :) I ssh'ed into my build machine and X
forwarding is not on, so I got an obscure python error.

I'm still unpacking and will try again later.

Philip

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] No more minimal-image

[Philip Balister]

On 02/17/2012 04:06 AM, Christophe Aeschlimann wrote:
> On 17.02.2012 12:13, Samuel Stirtzel wrote:
> 
>> 2012/2/17 Christophe Aeschlimann :
> 
> Hi and thank you for your suggestion.
> 
> I had a look at this oe-core recipe and it would definitely fit my
> rootfs size requirement but it looks like it really hasn't much included
> and it doesn't include any Angstrom configuration. Maybe it's a starting
> point but to be honest I would prefer to remove what I don't need than
> to spend a lot of time figuring out what I'm missing :)

RP and I (and some others) have been talking about this at ELC this week.

He swears the correct answer is run hob to create the image. The hob
should save the image spec as a bb file that you could edit "normally"
later :)

He claims this will work with OE-Core + Angstrom and will address bugs
in this config. I am going to try this when I get home.

I do not think hob supports systemd (yet) but we should go ahead and
test. Please send feedback to the oe-core list.

Philip

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

[Angstrom-devel] Future directions of Angstrom

[Philip Balister]

As we enter the OE-Core universe, I think it is a good time to think
about where the Angstrom Distribution needs to focus its efforts.

Currently, the most user visible feature of Angstrom is the availability
of binary feeds so end users can add packages via the internet easily.

Some ideas:

1) Continue providing package feeds.
2) Improve web services (Narcissus)

One of the issues I have with Angstrom is the config files are hard to
follow, there are files pinning package and toolchain versions. Most of
these exist to control the flow of data from upstream OE, although that
may not be as large a problem with the new pull model for OE-core and
meta-oe.

The other issue is toolchain management. Angstrom uses various gcc
versions for different archs. The idea is we can select toolchains that
work well for each arch, but my concern is this is hard to evaluate
across the range of architectures supported. I'd like to see the
toolchian selection clearly documented somewhere, including detailed
reasons so we can pass this info upstream and try and get the current
toolchains usable by all archs.

Finally, there is the issue of older hardware that is poorly supported.
Narcissus has selections for older hardware, but it does not produce
working images. The problem here is that most people using it post they
have a problem and we have no way to find and fix the problem. Working
and non-working, or supported and un-supported machines should be
clearly documented to avoid false expectations by users.

Philip

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] git server down?

[Philip Balister]

On 01/11/2012 05:06 PM, Andreas Müller wrote:
> Hi
> 
> feels like angstrom git server is down:
> 
> | git pull
> | fatal: Unable to look up git.angstrom-distribution.org (port 9418) (Name or 
> service not known)
> 
> Also opening
> http://git.angstrom-distribution.org/

This worked for me just now.

Philip

> 
> fails. Is it only me facing this?
> 
> Andreas
> 
> ___
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel@linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
> 

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Build Confusion

[Philip Balister]

Try asking on the beagle list. There are more Beagle people there.

Philip

On 12/24/2011 01:40 PM, David Thomas wrote:
> After struggling with a Compulab CM3530 board to no avail I purchased
> a Beagleboard-xM. Out of the box the demo image included came right
> up. I managed to get uvcvideo working, installed gstreamer, everything
> seemed OK except cmemk.ko will not install overlapping the kernel.
> 
> The uEnv.txt options are ignored, I have tried every possible
> combination and gave up assuming the kernel is ignoring my
> mem=99M@0x8000 mem=384M@0x8800 arguments (yes I have tried
> countless permutations and yes loadmodules.sh is inside this gap). So
> then I built a Narcissus image with Gnome, etc, all included. It boots
> only to:
> 
>  usb0: link up, 100Mbps, full-duplex, lpa 0x45E1 on the serial console
> and the DVI is the Angstrom image and hangs there. Pinging it gives a
> kernel error in sync with the ping. I have no way to find out where or
> why it hangs...
> 
> I have built two times and to no avail. I then had Narcissus build a
> console image. It does allow me to create a 16M window but uvcvideo
> refuses to work despite every attempt.
> 
> modprobe uvcvideo gives no found, insmod seems to work but camera is
> not detected.
> 
> I am now trying the setup-scripts but there is no documents telling me
> how to get gnome built into this. So, is it actually possible to get a
> working image for the BB-xM? I have spent days hacking on this and all
> I want to do is stream video and audio over the network.
> 
> Where in this mountain of stuff can I specify the exact options for my
> build? Under the setup-scripts Meta-Ti there are 6 or 8 kernel
> version, it is endless..
> 
> Is this documented anywhere?
> 
> ALso, am I missing something on the sd scripts? It failes to build the
> rootfs partition on every attempt I end up having to fiddle with
> that as well.
> 
> I really had hoped Narcissus would work but apparently it is a bust as
> well. I am at the point of finding a new platform or OS for this
> design
> 
> 
> Sorry to be cynical but does any of this actually work as advertised?
> Any help would be appreciated...
> 
> 

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

[Angstrom-devel] [PATCH] angstrom-2010-preferred-versions.inc : Stop pinning python-cairo.

[Philip Balister]

Signed-off-by: Philip Balister 
---
 .../include/angstrom-2010-preferred-versions.inc   |1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/conf/distro/include/angstrom-2010-preferred-versions.inc 
b/conf/distro/include/angstrom-2010-preferred-versions.inc
index 60c9b70..d1fd3b9 100644
--- a/conf/distro/include/angstrom-2010-preferred-versions.inc
+++ b/conf/distro/include/angstrom-2010-preferred-versions.inc
@@ -44,7 +44,6 @@ PREFERRED_VERSION_pango-native = "1.29.4"
 PREFERRED_VERSION_pkgconfig= "0.25"
 PREFERRED_VERSION_pkgconfig-native = "0.25"
 PREFERRED_VERSION_pulseaudio   = "0.9.23"
-PREFERRED_VERSION_python-pycairo = "1.8.0"
 PREFERRED_VERSION_qt4-native = "${ANGSTROM_QT_VERSION}"
 PREFERRED_VERSION_qt4-tools-native = "${ANGSTROM_QT_VERSION}"
 PREFERRED_VERSION_qt4-tools-nativesdk = "${ANGSTROM_QT_VERSION}"
-- 
1.7.3.4


___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] [meta-ettus] console-gnuradio-image: angstrom systemd-image has moved to recipes-images/angstrom

[Philip Balister]

Thanks, applied.

Philip

On 10/15/2011 10:23 AM, Andreas Müller wrote:
> 
> Signed-off-by: Andreas Müller 
> ---
>  recipes/images/console-gnuradio-image.bb |2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/recipes/images/console-gnuradio-image.bb 
> b/recipes/images/console-gnuradio-image.bb
> index 68ba57d..2c8a828 100644
> --- a/recipes/images/console-gnuradio-image.bb
> +++ b/recipes/images/console-gnuradio-image.bb
> @@ -1,4 +1,4 @@
> -require recipes-angstrom/images/systemd-image.bb
> +require recipes-images/angstrom/systemd-image.bb
>  
>  IMAGE_INSTALL += " \
>task-base-extended \

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] openssh vs dropbear

[Philip Balister]

On 10/08/2011 11:13 PM, Cliff Brake wrote:
> What are the tradeoffs between using openssh and dropbear?  I'm using
> Angstrom/systemd images, and would prefer dropbear as its likely
> smaller, but want to make sure I understand the other tradeoffs.

In my case, the customer asked for openssh over dropbear, largely
because they are familiar with openssh and we have space.

Philip

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Making angstrom-core the default in the setup scripts

[Philip Balister]

On 07/27/2011 01:31 PM, Koen Kooi wrote:


Op 27 jul. 2011, om 19:24 heeft Philip Balister het volgende geschreven:


On 07/26/2011 12:35 PM, Paul Eggleton wrote:

Paul Menzel wrote:


I am still having some concerns I raised in reply to Khem?s message [2]
but I am pasting them here again.


Will reply to your original message on OE-dev.


If someone can point me at a coherent set of instructions for building Angstrom 
with OE core, I can start to put in some spare cycles.


As mentioned before: 
http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-angstrom/tree/README


OK for now  ...

But how about a wikipedia article? I hear that is your new favorite 
source for information.


(I am poking fun at Koen)

Philip

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Making angstrom-core the default in the setup scripts

[Philip Balister]

On 07/26/2011 12:35 PM, Paul Eggleton wrote:

Paul Menzel wrote:


I am still having some concerns I raised in reply to Khem?s message [2]
but I am pasting them here again.


Will reply to your original message on OE-dev.


If someone can point me at a coherent set of instructions for building 
Angstrom with OE core, I can start to put in some spare cycles.


Philip

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] ti-cgt6x-1_6_1_17 fetch error

[Philip Balister]

On 07/26/2011 10:51 AM, Maksym Parkachov wrote:

Hi developers,

Building my image from scratch, I would like to report fetch error on
the package ti-cgt6x-1_6_1_17. I thought licensing issues were
resolved and it could be distributed by angstrom ?


I'm pretty sure you need to log in to the TI website and download the 
proper version and manually put it in the sources directory still.


Philip




command:

bitbake -f -c fetch ti-cgt6x

here is configuration:

BB_VERSION= "1.12.0"
METADATA_BRANCH   = "2011.03-maintenance"
METADATA_REVISION = "a1f31c7"
TARGET_ARCH   = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE   = "beagleboard"
DISTRO= "angstrom"
DISTRO_VERSION= "2011.03"
TARGET_FPU= "hard"

here is the log:

NOTE: package ti-cgt6x-1_6_1_17-r4: task do_fetch: Started
--2011-07-26 16:46:09--
http://install.source.dir.local/ti_cgt_c6000_6.1.17_setup_linux_x86.bin
  Resolving install.source.dir.local... failed: Name or service not known.
  wget: unable to resolve host address `install.source.dir.local'
  --2011-07-26 16:46:19--
http://mirrors.openembedded.org/ti_cgt_c6000_6.1.17_setup_linux_x86.bin
  Resolving mirrors.openembedded.org... 82.197.159.157
  Connecting to mirrors.openembedded.org|82.197.159.157|:80... failed:
No route to host.
  --2011-07-26 16:46:22--
http://sources.openembedded.org/ti_cgt_c6000_6.1.17_setup_linux_x86.bin
  Resolving sources.openembedded.org... 140.211.169.165
  Connecting to sources.openembedded.org|140.211.169.165|:80... connected.
  HTTP request sent, awaiting response... 404 Not Found
  2011-07-26 16:46:23 ERROR 404: Not Found.

  --2011-07-26 16:46:23--
http://www.angstrom-distribution.org/unstable/sources/ti_cgt_c6000_6.1.17_setup_linux_x86.bin
  Resolving www.angstrom-distribution.org... 188.40.83.200
  Connecting to www.angstrom-distribution.org|188.40.83.200|:80... connected.
  HTTP request sent, awaiting response... 404 Not Found
  2011-07-26 16:46:23 ERROR 404: Not Found.

NOTE: package ti-cgt6x-1_6_1_17-r4: task Fetch failed: Unable to fetch
URL 
http://install.source.dir.local/ti_cgt_c6000_6.1.17_setup_linux_x86.bin;name=cgt6xbin
from any source.: Failed
ERROR: Function 'Fetch failed: Unable to fetch URL
http://install.source.dir.local/ti_cgt_c6000_6.1.17_setup_linux_x86.bin;name=cgt6xbin
from any source.' failed
ERROR: Task 0 
(/home/angstrom/setup-scripts/sources/openembedded/recipes/ti/ti-cgt6x_6.1.17.bb,
do_fetch) failed with exit code '1'
ERROR: 
'/home/angstrom/setup-scripts/sources/openembedded/recipes/ti/ti-cgt6x_6.1.17.bb'
failed

If someone could look at the issue it would be great.

Thanks in advance,
Maksym.

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel



___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Making angstrom-core the default in the setup scripts

[Philip Balister]

On 07/15/2011 12:21 PM, Koen Kooi wrote:

Hi,

What do you think of making the oe-core branch[1] the default in the setup 
scripts? The basic needs are there and I'm using it for for all the new work 
I'm doing. It is missing a lot of recipes, but if people can name the ones that 
are missing we can port them over to meta-oe and/or meta-angstrom.


We should wait on making it the default, but we should start making sure 
people now how to try oe-core.


I'm not sure we are ready for a bunch of new people building oe-core yet.

Philip

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Broken ncurses mirrors or something else?

[Philip Balister]

On 04/13/2011 12:09 AM, Graeme Gregory wrote:

Hmm, permisions on disk look ok, Ill have to bug koen when he is back from
travelling to look at the apache setup.


I'll kick him in person.

Philip



Graeme

On Wed, Apr 13, 2011 at 09:50:39AM +0400, Maxim Podbereznyy wrote:

Hi!

I tried to build a kernel for Beagleboard today and got the following issue,
which confirms the previous message:

--2011-04-12 22:47:55--
ftp://invisible-island.net/ncurses/5.7/ncurses-5.7-20110108-patch.sh.bz2
 =>
`/media/hdd/OE.new/sources/downloads/ncurses-5.7-20110108-patch.sh.bz2'
  Resolving invisible-island.net... 216.194.248.64
  Connecting to invisible-island.net|216.194.248.64|:21... connected.
  Logging in as anonymous ... Logged in!
  ==>  SYST ... done.==>  PWD ... done.
  ==>  TYPE I ... done.  ==>  CWD (1) /ncurses/5.7 ...
  No such directory `ncurses/5.7'.

  --2011-04-12 22:47:57--
http://mirrors.openembedded.org/ncurses-5.7-20110108-patch.sh.bz2
  Resolving mirrors.openembedded.org... 82.197.159.157
  Connecting to mirrors.openembedded.org|82.197.159.157|:80... failed:
Connection refused.
  --2011-04-12 22:47:58--
http://sources.openembedded.org/ncurses-5.7-20110108-patch.sh.bz2
  Resolving sources.openembedded.org... 140.211.169.165
  Connecting to sources.openembedded.org|140.211.169.165|:80... connected.
  HTTP request sent, awaiting response... 404 Not Found
  2011-04-12 22:47:58 ERROR 404: Not Found.

  --2011-04-12 22:47:59--
http://www.angstrom-distribution.org/unstable/sources/ncurses-5.7-20110108-patch.sh.bz2
  Resolving www.angstrom-distribution.org... 188.40.83.200
  Connecting to www.angstrom-distribution.org|188.40.83.200|:80... connected.
  HTTP request sent, awaiting response... 403 Forbidden
  2011-04-12 22:48:03 ERROR 403: Forbidden.

NOTE: package ncurses-native-5.7+20110115-r16: task Fetch failed: Unable to
fetch URL
ftp://invisible-island.net/ncurses/5.7/ncurses-5.7-20110108-patch.sh.bz2;apply=yes;name=p20110108shfrom
any source.: Failed
ERROR: Function 'Fetch failed: Unable to fetch URL
ftp://invisible-island.net/ncurses/5.7/ncurses-5.7-20110108-patch.sh.bz2;apply=yes;name=p20110108shfrom
any source.' failed
ERROR: Task 317
(virtual:native:/media/hdd/OE.new/sources/openembedded/recipes/ncurses/
ncurses_5.7.bb, do_fetch) failed with exit code '1'
Waiting for 1 active tasks to finish:
0: perl-native-5.10.1-r10 do_compile (pid 16795)
NOTE: package perl-native-5.10.1-r10: task do_compile: Succeeded
ERROR:
'virtual:native:/media/hdd/OE.new/sources/openembedded/recipes/ncurses/
ncurses_5.7.bb' failed


2011/4/6 Wayne Tams


Hi,

I am relatively new to angstrom and I have found the instructions at the
Angstrom site invaluable for getting set up and quickly and runnning
Angstrom on the Beagleboard.

I am having to trouble building packages, bitbake is failing when tryin gto
apply the patch ncurses-5.7-20110108-patch.sh.bz2, would the below message
indicate a broken mirror or am I looking at a local problem?

--2011-04-06 12:32:57--
http://mirrors.openembedded.org/ncurses-5.7-20110108-patch.sh.bz2
  Resolving mirrors.openembedded.org... 82.197.159.157
  Connecting to mirrors.openembedded.org|82.197.159.157|:80... failed:
Connection refused.
  --2011-04-06 12:33:02--
http://sources.openembedded.org/ncurses-5.7-20110108-patch.sh.bz2
  Resolving sources.openembedded.org... 140.211.169.165
  Connecting to sources.openembedded.org|140.211.169.165|:80... connected.
  HTTP request sent, awaiting response... 404 Not Found
  2011-04-06 12:33:07 ERROR 404: Not Found.

  --2011-04-06 12:33:07--
http://www.angstrom-distribution.org/unstable/sources/ncurses-5.7-20110108-patch.sh.bz2
  Resolving www.angstrom-distribution.org... 188.40.83.200
  Connecting to www.angstrom-distribution.org|188.40.83.200|:80...
connected.
  HTTP request sent, awaiting response... 403 Forbidden
  2011-04-06 12:33:12 ERROR 403: Forbidden.

NOTE: package ncurses-native-5.7+20110115-r16: task Fetch failed: Unable to
fetch URL
ftp://invisible-island.net/ncurses/5.7/ncurses-5.7-20110108-patch.sh.bz2;apply=yes;name=p20110108shfrom
 any source.: Failed
ERROR: Function 'Fetch failed: Unable to fetch URL
ftp://invisible-island.net/ncurses/5.7/ncurses-5.7-20110108-patch.sh.bz2;apply=yes;name=p20110108shfrom
 any source.' failed
ERROR: Task 8
(virtual:native:/home/Adam/oe/setup-scripts/sources/openembedded/recipes/ncurses/
ncurses_5.7.bb, do_fetch) failed with exit code '1'
ERROR:
'virtual:native:/home/Adam/oe/setup-scripts/sources/openembedded/recipes/ncurses/
ncurses_5.7.bb' failed


Regards


Wayne Tams
Regenersis Plc
t:  +44 (0)1592 774704   f:  +44 (0)1592 779654
1 James Watt Avenue, Westwood Park, Glenrothes, Fife KY7 4UA

Confidentiality Notice
This e-mail's content is confidential to the intended recipient and should
not be copied, used or disclosed to or by anyone else, nor may other parties
rely on it.  If received in error, please notify the sender and delete the
e-mail immediately.
Computer Repair Centre Limited is a 

Re: [Angstrom-devel] Bootable x86 Angstrom image

[Philip Balister]

On 04/06/2011 06:48 AM, Michael Burghart wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

Am 06.04.2011 12:57, schrieb Michael Burghart:

Hi,

is it possible to directly create a bootable Angstrom image for x86
(using grub)? Similar to an Voyage Linux img file?
If so please tell me where to find the according  docu for doing so. Thanks.


nobody can answer my questions?
Pity-
How can I integrate initrdscripts into my image?!


I do not think there are many x86 developers using Angstrom.

Philip



___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel



- --
- --
cheers
- -micha-
- --
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNnG9DAAoJEEMkp/gkis19llAH/i68udVLQ3yNvlM2ITVxTIu6
HZB6DtgHwobaQW8FgC8OOvqmAVousZT6tNXHhgsSgbu1p+5AcE4rTmB+U4Y7CzIT
6c6fb2BA+g+3hQCidhqeKBR665z6lS0TY0obWdD+ZpHugBSD79z8yq0gzaC5QGuQ
tE8r1wsndq7GGtAHC/fbHERWUmIb+A02ULasd0if0JXwAB4dsH9D2LRyLWBlSZtI
g+9iLsv0mtl5eVgjO9ptuSAhkUmhOKYDeslUp4HjzWK+GHOXACvnnLVZ7Kgwr3QX
WNqVbn4pd9GfdePiFg5+rUKiT6VrGpjCnWCGNFL3WoCdFl1Wq/8JvjSB2yGJ0Ak=
=ZbQH
-END PGP SIGNATURE-

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel



___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Can't build Angstrom

[Philip Balister]

On 04/05/2011 09:33 AM, Gary Thomas wrote:

Build Configuration:
BB_VERSION = "1.11.0"
METADATA_BRANCH = "org.openembedded.dev"
METADATA_REVISION = "5568192"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "beagleboard"
DISTRO = "angstrom"
DISTRO_VERSION = "v20110405"
TARGET_FPU = "hard"

| install: cannot stat
`/local/Angstrom_BeagleBoard/tmp/work/beagleboard-angstrom-linux-gnueabi/angstrom-version-1_v20110405-r6/lsb_release':
No such file or directory
NOTE: package angstrom-version-1_v20110405-r6: task do_install: Failed



Some form of heisenbug. Try restarting, cleaning, and updating bitbake :)

Philip

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Problem building numpy

[Philip Balister]

On 03/18/2011 09:12 PM, Connor Abbott wrote:

Thanks! I use blas-dev and lapack-dev for other projects. Is it possible to
get Angstrom lapack/blas and these packages to coexist?


Probably, but I couldn't solve the problem and need to get other stuff 
done :)


Philip



On Fri, Mar 18, 2011 at 2:05 PM, Philip Balisterwrote:


On 03/18/2011 11:29 AM, Connor Abbott wrote:


Hi,

It seems I'm having a problem building python-numpy. I'm using the setup
script and building for the beagleboard, and I've tried DISTRO=2008.1 and
DISTRO=2010.x. I can build task-gpe-base, but anything that pulls in
Python,
such as angstrom-gpe-image and opencv, fails to build. I found a mention
of
this in the irc logs, but I haven't found a fix yet.



Make sure you do not have any of the lapack-dev, blas-dev and similar
packages installed on the build machine.

Philip



Here's the relevant log.do_compile:

+ do_compile
+ BUILD_SYS=x86_64-linux
+ HOST_SYS=arm-angstrom-linux-gnueabi
+

/home/connor/angstrom/build/tmp-angstrom_2010_x/sysroots/x86_64-linux/usr/bin/python
setup.py build
Running from numpy source directory.
non-existing path in 'numpy/distutils': 'site.cfg'
F2PY Version 2
blas_opt_info:
blas_mkl_info:
   libraries mkl,vml,guide not found in

/home/connor/angstrom/build/tmp-angstrom_2010_x/sysroots/x86_64-linux/usr/lib
   libraries mkl,vml,guide not found in /usr/local/lib
   libraries mkl,vml,guide not found in /usr/lib64
   libraries mkl,vml,guide not found in /usr/lib
   NOT AVAILABLE

atlas_blas_threads_info:
Setting PTATLAS=ATLAS
   libraries ptf77blas,ptcblas,atlas not found in

/home/connor/angstrom/build/tmp-angstrom_2010_x/sysroots/x86_64-linux/usr/lib
   libraries ptf77blas,ptcblas,atlas not found in /usr/local/lib
   libraries ptf77blas,ptcblas,atlas not found in /usr/lib64/atlas
   libraries ptf77blas,ptcblas,atlas not found in /usr/lib64
   libraries ptf77blas,ptcblas,atlas not found in /usr/lib/atlas
   libraries ptf77blas,ptcblas,atlas not found in /usr/lib
   NOT AVAILABLE

atlas_blas_info:
   libraries f77blas,cblas,atlas not found in

/home/connor/angstrom/build/tmp-angstrom_2010_x/sysroots/x86_64-linux/usr/lib
   libraries f77blas,cblas,atlas not found in /usr/local/lib
   libraries f77blas,cblas,atlas not found in /usr/lib64/atlas
   FOUND:
 libraries = ['f77blas', 'cblas', 'atlas']
 library_dirs = ['/usr/lib64']
 language = c
 include_dirs = ['/usr/include']


/home/connor/angstrom/build/tmp-angstrom_2010_x/work/armv7a-angstrom-linux-gnueabi/python-numpy-1.4.1-ml0/numpy-1.4.1/numpy/distutils/command/config.py:394:
DeprecationWarning:
+
Usage of get_output is deprecated: please do not
use it anymore, and avoid configuration checks
involving running executable on the target machine.
+

   DeprecationWarning)
customize GnuFCompiler
Could not locate executable arm-angstrom-linux-gnueabi-g77 -march=armv7-a
-mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -mthumb-interwork
-mno-thumb

--sysroot=/home/connor/angstrom/build/tmp-angstrom_2010_x/sysroots/armv7a-angstrom-linux-gnueabi
Could not locate executable g77
Could not locate executable f77
customize IntelFCompiler
Could not locate executable ifort
Could not locate executable ifc
customize LaheyFCompiler
Could not locate executable lf95
customize PGroupFCompiler
Could not locate executable pgf90
customize AbsoftFCompiler
Could not locate executable f90
customize NAGFCompiler
Could not locate executable f95
customize VastFCompiler
customize GnuFCompiler
customize CompaqFCompiler
Could not locate executable fort
customize IntelItaniumFCompiler
Could not locate executable efort
Could not locate executable efc
customize IntelEM64TFCompiler
customize Gnu95FCompiler
Could not locate executable gfortran
customize G95FCompiler
Could not locate executable g95
don't know how to compile Fortran code on platform 'posix'
compiling '_configtest.c':

/* This file is generated from numpy/distutils/system_info.py */
void ATL_buildinfo(void);
int main(void) {
   ATL_buildinfo();
   return 0;
}
C compiler: arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8
-mfpu=neon -mfloat-abi=softfp -mthumb-interwork -mno-thumb

--sysroot=/home/connor/angstrom/build/tmp-angstrom_2010_x/sysroots/armv7a-angstrom-linux-gnueabi
-DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fexpensive-optimizations
-fomit-frame-pointer -frename-registers -O2 -ggdb2 -fPIC

compile options: '-c'
arm-angstrom-linux-gnueabi-gcc: _configtest.c
arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon
-mfloat-abi=softfp -mthumb-interwork -mno-thumb

--sysroot=/home/connor/angstrom/build/tmp-angstrom_2010_x/sysroots/armv7a-angstrom-linux-gnueabi
_configtest.o -L/usr/lib64 -lf77blas -lcblas -latlas -o _configtest
/usr/lib64/libf77blas.so: file not recognized: File format not recognized
collect2: ld returned 1 exit status
/usr/lib64/libf77blas.so: file not recognized: File format no

Re: [Angstrom-devel] Problem building numpy

[Philip Balister]

On 03/18/2011 11:29 AM, Connor Abbott wrote:

Hi,

It seems I'm having a problem building python-numpy. I'm using the setup
script and building for the beagleboard, and I've tried DISTRO=2008.1 and
DISTRO=2010.x. I can build task-gpe-base, but anything that pulls in Python,
such as angstrom-gpe-image and opencv, fails to build. I found a mention of
this in the irc logs, but I haven't found a fix yet.


Make sure you do not have any of the lapack-dev, blas-dev and similar 
packages installed on the build machine.


Philip



Here's the relevant log.do_compile:

+ do_compile
+ BUILD_SYS=x86_64-linux
+ HOST_SYS=arm-angstrom-linux-gnueabi
+
/home/connor/angstrom/build/tmp-angstrom_2010_x/sysroots/x86_64-linux/usr/bin/python
setup.py build
Running from numpy source directory.
non-existing path in 'numpy/distutils': 'site.cfg'
F2PY Version 2
blas_opt_info:
blas_mkl_info:
   libraries mkl,vml,guide not found in
/home/connor/angstrom/build/tmp-angstrom_2010_x/sysroots/x86_64-linux/usr/lib
   libraries mkl,vml,guide not found in /usr/local/lib
   libraries mkl,vml,guide not found in /usr/lib64
   libraries mkl,vml,guide not found in /usr/lib
   NOT AVAILABLE

atlas_blas_threads_info:
Setting PTATLAS=ATLAS
   libraries ptf77blas,ptcblas,atlas not found in
/home/connor/angstrom/build/tmp-angstrom_2010_x/sysroots/x86_64-linux/usr/lib
   libraries ptf77blas,ptcblas,atlas not found in /usr/local/lib
   libraries ptf77blas,ptcblas,atlas not found in /usr/lib64/atlas
   libraries ptf77blas,ptcblas,atlas not found in /usr/lib64
   libraries ptf77blas,ptcblas,atlas not found in /usr/lib/atlas
   libraries ptf77blas,ptcblas,atlas not found in /usr/lib
   NOT AVAILABLE

atlas_blas_info:
   libraries f77blas,cblas,atlas not found in
/home/connor/angstrom/build/tmp-angstrom_2010_x/sysroots/x86_64-linux/usr/lib
   libraries f77blas,cblas,atlas not found in /usr/local/lib
   libraries f77blas,cblas,atlas not found in /usr/lib64/atlas
   FOUND:
 libraries = ['f77blas', 'cblas', 'atlas']
 library_dirs = ['/usr/lib64']
 language = c
 include_dirs = ['/usr/include']

/home/connor/angstrom/build/tmp-angstrom_2010_x/work/armv7a-angstrom-linux-gnueabi/python-numpy-1.4.1-ml0/numpy-1.4.1/numpy/distutils/command/config.py:394:
DeprecationWarning:
+
Usage of get_output is deprecated: please do not
use it anymore, and avoid configuration checks
involving running executable on the target machine.
+

   DeprecationWarning)
customize GnuFCompiler
Could not locate executable arm-angstrom-linux-gnueabi-g77 -march=armv7-a
-mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -mthumb-interwork -mno-thumb
--sysroot=/home/connor/angstrom/build/tmp-angstrom_2010_x/sysroots/armv7a-angstrom-linux-gnueabi
Could not locate executable g77
Could not locate executable f77
customize IntelFCompiler
Could not locate executable ifort
Could not locate executable ifc
customize LaheyFCompiler
Could not locate executable lf95
customize PGroupFCompiler
Could not locate executable pgf90
customize AbsoftFCompiler
Could not locate executable f90
customize NAGFCompiler
Could not locate executable f95
customize VastFCompiler
customize GnuFCompiler
customize CompaqFCompiler
Could not locate executable fort
customize IntelItaniumFCompiler
Could not locate executable efort
Could not locate executable efc
customize IntelEM64TFCompiler
customize Gnu95FCompiler
Could not locate executable gfortran
customize G95FCompiler
Could not locate executable g95
don't know how to compile Fortran code on platform 'posix'
compiling '_configtest.c':

/* This file is generated from numpy/distutils/system_info.py */
void ATL_buildinfo(void);
int main(void) {
   ATL_buildinfo();
   return 0;
}
C compiler: arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8
-mfpu=neon -mfloat-abi=softfp -mthumb-interwork -mno-thumb
--sysroot=/home/connor/angstrom/build/tmp-angstrom_2010_x/sysroots/armv7a-angstrom-linux-gnueabi
-DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fexpensive-optimizations
-fomit-frame-pointer -frename-registers -O2 -ggdb2 -fPIC

compile options: '-c'
arm-angstrom-linux-gnueabi-gcc: _configtest.c
arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon
-mfloat-abi=softfp -mthumb-interwork -mno-thumb
--sysroot=/home/connor/angstrom/build/tmp-angstrom_2010_x/sysroots/armv7a-angstrom-linux-gnueabi
_configtest.o -L/usr/lib64 -lf77blas -lcblas -latlas -o _configtest
/usr/lib64/libf77blas.so: file not recognized: File format not recognized
collect2: ld returned 1 exit status
/usr/lib64/libf77blas.so: file not recognized: File format not recognized
collect2: ld returned 1 exit status
failure.
removing: _configtest.c _configtest.o
Status: 255
Output:
   FOUND:
 libraries = ['f77blas', 'cblas', 'atlas']
 library_dirs = ['/usr/lib64']
 language = c
 define_macros = [('NO_ATLAS_INFO', 2)]
 include_dirs = ['/usr/include']

lapack_opt_info:
lapack_mkl_i

Re: [Angstrom-devel] Strategic Ångström goals

[Philip Balister]

On 03/03/2011 06:05 AM, Steffen Sledz wrote:

Hi Ångström maintainers,

it would be nice, if you can have a look 
at 
 and make a statement on the strategic goals for the Ångström distro.

This would be really helpful for all the users forced to use older kernels.


This is a real quick answer, but does it help if do maintenance 
(especially for older releases) in branches so we can avoid upgrading 
recipes like this?


Philip

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

[Angstrom-devel] Narcissus image builder

[Philip Balister]

The online image builder is moving to another machine atm. It will be 
offline for 3-4 hours.


Go celebrate the holiday season of your choice!

Philip

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] What version of the OE metadata are the feeds built from?

[Philip Balister]

On 12/07/2010 11:12 AM, Koen Kooi wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 07-12-10 16:39, Gary Thomas wrote:

On 12/07/2010 08:32 AM, Koen Kooi wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 07-12-10 15:37, Philip Balister wrote:

I'm looking for a way to point people at a relatively sane checkout of
the OE dev for people using a product based on Angstrom 2010.


short version:

cat /etc/angstrom-version


Does this tell you the OE branch&  revision?  Those are the
most important data, not just a generic 'angstrom-2010'


Why don't you just try and find out?


The problem with the short version is you need a working and up to date 
installation ...


Philip

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

[Angstrom-devel] What version of the OE metadata are the feeds built from?

[Philip Balister]

I'm looking for a way to point people at a relatively sane checkout of 
the OE dev for people using a product based on Angstrom 2010.


What I would to see is a branch called something like 
"angstrom-2010-feeds" that follows dev, but is only used to build feeds 
and available for people to pull from if they want a known reasonable 
starting point for doing their own OE builds. By following the feed 
builds, this should receive reasonable build testing. Ideally, we 
process to make a decision when to update the branch from dev.


By creating and documenting how the feeds are built, we also increase 
the "bus factor" of the feeds since we can have people fill in if Koen 
is not available for some reason :)


Thoughts?

Philip

PS: Similar thoughts apply to 2008, but my major interest now is 2010.

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Angstrom server slow

[Philip Balister]

On 10/18/2010 05:31 PM, Koen Kooi wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

We broke the 1TB per month barrier and now the ISP is throttling us to
10Mbit/s. The admins are working on solving this, but it might be a case
of "wait for the month to end".

Stay tuned...


Thanks for the update!

Philip




regards,

Koen
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMvLyXMkyGM64RGpERAnHaAJ9zLkoy+7DZ+h9UifX3ACsgOhOuvQCeLBNO
DT4Zj0HyuvT5nkw1KFUydBw=
=JFLT
-END PGP SIGNATURE-


___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel



___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Modifying audio register value in Angstrom

[Philip Balister]

On 09/20/2010 05:00 PM, Almohanad Fayez wrote:


Hi,  I'm running the Angstrom on the Beagleboard and I'm trying to find a way to modify the audio rate 
register values to force sampling rates other than 44.1 kHz and 48 kHz.  Basically when I run 
"cat /sys/devices/platform/soc-audio/codec_reg" register 0x1 reads 0x91 which from the 
datasheet means the sampling rate = 44.1kHz.  I'm trying to set register 0x1 to 0x81 to force it to 
run at 32 kHz.  but the "echo 1 81>  codec_reg" command is apparently not supported and 
from the angstrom the register is read-only I even tried chmod +w the register but that didn't work.

I tried using debugfs to modify the register value unfortunately  the 
functionality isn't available through that.  I found a few listings online of 
ALSA patches that expose the register during debugfs, after copying and pasting 
them I still couldn't access the register.  When I tried modifying the 
twl4030.c driver in the openembedded directory 
linux-omap-2.6.28/git/audio/soc/twl4030.c  by basically hardcoding the reigster 
value to 0x81 it still didn't work.


I'm running the 2.6.28.  can anyone share some advice ???


You might try the Beagleboard list also.

Philip





al fayez
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel



___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Native compilation and library linking on beagleboard using angstrom

[Philip Balister]

Oh crap.

All the  easy answers are exhausted 

Drop me a personal email and lets figure this out.

Philip

On 07/16/2010 07:04 PM, alfa...@aol.com wrote:

yep they're all there





  al



-Original Message-
From: Philip Balister
To: Discussion of the angstrom distribution 
development
Sent: Fri, Jul 16, 2010 4:10 pm
Subject: Re: [Angstrom-devel] Native compilation and library linking on 
beagleboard using angstrom


On 07/16/2010 03:59 PM, alfa...@aol.com wrote:

I already installed the dev packages "fftw3"&   "fftw3-dev"&   "libfftw"


Are the header files in the include directory?

Philip






   al



-Original Message-
From: Philip Balister
To: Discussion of the angstrom distribution 
development
Sent: Fri, Jul 16, 2010 3:13 pm
Subject: Re: [Angstrom-devel] Native compilation and library linking on 
beagleboard using angstrom


ffOn 07/16/2010 02:54 PM, alfa...@aol.com wrote:

Hi, I'm running into some issues linking against libraries.  I'm running a 
"console-image" Angstrom on the Beagleboad and I've been adding packages as 
necessary to support compiling code directly on the board.

To support building packages on the BB, I bitbaked "package-native-sdk" and 
"pkg-config" and installed those packages with all the other dependencies as indicated by 
opkg: gcc, libgcc, automake, perl,  etc.

Now I'm trying to compile a program natively that links against fftw3 library so I 
bitbaked and installed the fftw3 library: the libfftw3, fftw3, and fftw3-dev.  Now to 
link to fftw3 I added the "-L /usr/lib -lfftw3" flags for link but i would get 
the error message

cannot find -lfftw3
collect2: ld returned 1 exit status

I also tried using "pkg-config --libs fftw3" in my Makefile and I still get the 
same error message.  I don't know why GCC can't seem to find the library especially that 
pkg-config and ldconfig have links to the library.  The following are outputs from 
pkg-config and ldconfig

ldconfig -v | grep fftw
   libfftw3.so.3 ->libfftw3.so.3.2.2
   libfftw3f.so.3 ->libfftw3f.so.3.2.2

pkg-config --list-all
fftw3f FFTW - fast Fourier transform library
fftwFFTW - fast Fourier transform library
fftw3  FFTW - fast Fourier transform library


it seems to me that everything is in order but i'm probably missing something 
... any help would be greatly appreciated.  thanks


I bet you need the dev packages.

fftwf-dev and/or fftw-dev

Philip




al
=
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel



___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel


___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel



___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel


___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel



___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Native compilation and library linking on beagleboard using angstrom

[Philip Balister]

On 07/16/2010 03:59 PM, alfa...@aol.com wrote:

I already installed the dev packages "fftw3"&  "fftw3-dev"&  "libfftw"


Are the header files in the include directory?

Philip






  al



-----Original Message-
From: Philip Balister
To: Discussion of the angstrom distribution 
development
Sent: Fri, Jul 16, 2010 3:13 pm
Subject: Re: [Angstrom-devel] Native compilation and library linking on 
beagleboard using angstrom


ffOn 07/16/2010 02:54 PM, alfa...@aol.com wrote:

Hi, I'm running into some issues linking against libraries.  I'm running a 
"console-image" Angstrom on the Beagleboad and I've been adding packages as 
necessary to support compiling code directly on the board.

To support building packages on the BB, I bitbaked "package-native-sdk" and 
"pkg-config" and installed those packages with all the other dependencies as indicated by 
opkg: gcc, libgcc, automake, perl,  etc.

Now I'm trying to compile a program natively that links against fftw3 library so I 
bitbaked and installed the fftw3 library: the libfftw3, fftw3, and fftw3-dev.  Now to 
link to fftw3 I added the "-L /usr/lib -lfftw3" flags for link but i would get 
the error message

cannot find -lfftw3
collect2: ld returned 1 exit status

I also tried using "pkg-config --libs fftw3" in my Makefile and I still get the 
same error message.  I don't know why GCC can't seem to find the library especially that 
pkg-config and ldconfig have links to the library.  The following are outputs from 
pkg-config and ldconfig

ldconfig -v | grep fftw
  libfftw3.so.3 ->   libfftw3.so.3.2.2
  libfftw3f.so.3 ->   libfftw3f.so.3.2.2

pkg-config --list-all
fftw3f FFTW - fast Fourier transform library
fftwFFTW - fast Fourier transform library
fftw3  FFTW - fast Fourier transform library


it seems to me that everything is in order but i'm probably missing something 
... any help would be greatly appreciated.  thanks


I bet you need the dev packages.

fftwf-dev and/or fftw-dev

Philip




al
=
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel



___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel


___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel



___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Native compilation and library linking on beagleboard using angstrom

[Philip Balister]

ffOn 07/16/2010 02:54 PM, alfa...@aol.com wrote:

Hi, I'm running into some issues linking against libraries.  I'm running a 
"console-image" Angstrom on the Beagleboad and I've been adding packages as 
necessary to support compiling code directly on the board.

To support building packages on the BB, I bitbaked "package-native-sdk" and 
"pkg-config" and installed those packages with all the other dependencies as indicated by 
opkg: gcc, libgcc, automake, perl,  etc.

Now I'm trying to compile a program natively that links against fftw3 library so I 
bitbaked and installed the fftw3 library: the libfftw3, fftw3, and fftw3-dev.  Now to 
link to fftw3 I added the "-L /usr/lib -lfftw3" flags for link but i would get 
the error message

cannot find -lfftw3
collect2: ld returned 1 exit status

I also tried using "pkg-config --libs fftw3" in my Makefile and I still get the 
same error message.  I don't know why GCC can't seem to find the library especially that 
pkg-config and ldconfig have links to the library.  The following are outputs from 
pkg-config and ldconfig

ldconfig -v | grep fftw
 libfftw3.so.3 ->  libfftw3.so.3.2.2
 libfftw3f.so.3 ->  libfftw3f.so.3.2.2

pkg-config --list-all
fftw3f FFTW - fast Fourier transform library
fftwFFTW - fast Fourier transform library
fftw3  FFTW - fast Fourier transform library


it seems to me that everything is in order but i'm probably missing something 
... any help would be greatly appreciated.  thanks


I bet you need the dev packages.

fftwf-dev and/or fftw-dev

Philip




al
=
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel



___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] [PATCH] Extra explanation re: md5 file in the ti-cgt6x.inc file

[Philip Balister]

On 06/02/2010 01:14 PM, Koen Kooi wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 02-06-10 15:45, Robert P. J. Day wrote:


Make it clear in that include file that the user must manually create
the MD5 checksum file.


NAK. As I said before, those go into the README


How about a patch that adds a reference to the README to the recipes and 
adding the md5sum stuff to the README?


Philip






Signed-off-by: Robert P. J. Day

---

   the comment is, of course, innocuous. the only other part is
tightening up the variable assignments.


diff --git a/recipes/ti/ti-cgt6x.inc b/recipes/ti/ti-cgt6x.inc
index 8ae25da..1fd8ea6 100644
--- a/recipes/ti/ti-cgt6x.inc
+++ b/recipes/ti/ti-cgt6x.inc
@@ -11,9 +11,19 @@ PR = "r4"

  S = "${WORKDIR}/cgt6x_${PV}"

-SRC_URI = 
"http://install.source.dir.local/ti_cgt_c6000_${PVwithdots}_setup_linux_x86.bin;name=cgt6xbin";
+# steps involved in setting this up
+#
+# 1. Log into the TI page, and download the appropriate binfile into
+#your download directory.
+#
+# 2. In that same directory, create the appropriate MD5 checksum file with
+#the properly-versioned form of the command:
+#
+#$ md5sum ti_cgt_c6000_6.1.9_setup_linux_x86.bin>  
ti_cgt_c6000_6.1.9_setup_linux_x86.bin.md5

  BINFILE="ti_cgt_c6000_${PVwithdots}_setup_linux_x86.bin"
+SRC_URI = "http://install.source.dir.local/${BINFILE};name=cgt6xbin";
+
  TI_BIN_UNPK_CMDS="Y:qY:workdir: : "
  TI_BIN_UNPK_WDEXT="/cgt6x_${PV}"




-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMBpF0MkyGM64RGpERAlu3AJ949lKv1UsMhPVj0tJWNtqW5v7AwgCfXhbY
TFpO3ekxewXxmtUqGwV2u54=
=5vY1
-END PGP SIGNATURE-


___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel



___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] [oe] Is Angstrom dead?

[Philip Balister]

On 06/01/2010 10:47 AM, Merciadri Luca wrote:

Gary Thomas wrote:

On 06/01/2010 08:24 AM, Robert P. J. Day wrote:

On Tue, 1 Jun 2010, Gary Thomas wrote:


I tried again today, updating to org.openembedded.dev branch,
commit a2834c64fb3ed535fca51c25547754fa907e4ca5  Sadly, new
problems (and probably still the old ones) remain:

| checking for CHEESE... configure: error: Package requirements (
glib-2.0>=
2.16.0   gobject-2.0>= 2.12.0   gio-2.0>= 2.16.0   gtk+-2.0>= 2.19.1
gdk-2.0>= 2.14.0 gnome-desktop-2.0>= 2.26.0   gconf-2.0>= 2.16.0
gstreamer-0.10>= 0.10.23   gstreamer-plugins-base-0.10>= 0.10.23
cairo>=
1.4.0   dbus-1>= 1.0   dbus-glib-1>= 0.7 pangocairo>= 1.18.0
librsvg-2.0

= 2.18.0

|   libcanberra-gtk gudev-1.0) were not met:
|
| No package 'gstreamer-plugins-base-0.10' found
|
| Consider adjusting the PKG_CONFIG_PATH environment variable if you
| installed software in a non-standard prefix.
|
| Alternatively, you may set the environment variables CHEESE_CFLAGS
| and CHEESE_LIBS to avoid the need to call pkg-config.
| See the pkg-config man page for more details.
|
NOTE: package cheese-2.30.1-r0: task do_configure: Failed


now i'm slightly confused since neither ubuntu or fedora appear to
have any pkgconfig info for the cheese package, so why would there be
a test for it that you would need to override?  or is this not
pkgconfig-related?


I've no idea - all I was pointing out is that as of this morning,
there's a new failure...


It is not dead. The problem is that there is a small linux community,
and an even smaller Angström community, and, in this community, only a
slight part is composed of gurus. At least, that's my POV.



And as I noted on the OE list, the gurus are picking up paid work that 
cuts into our time. This is good for Angstrom in the long term, but does 
cut into our response times. Please feel free to step up and start 
working through the problems, everyone starts on the path to becoming a 
guru slowly.


Philip

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] DM6446 USB driver support

[Philip Balister]

On 12/15/2009 11:01 PM, alfa...@aol.com wrote:


Hi, I was wondering about the extent of USB support for the Davinci DM6446 
board.  I'm currently trying to mount a USB stick formatted to FAT 16 but the 
board would not recognize it.  I even changed the jumper for it to work in host 
mode.  I'm using an Angstrom image that I built from the stable branch about 2 
months ago.

On a "probably" related note,  while inspecting the Angstrom bootup on my board I see the 
following message "root: mount: mount point /proc/bus/usb does not exist", does this mean 
that the USB driver isn't installed?

When I search for USB in my filesystem on the board I get the following result 
back

/sys/devices/platform/musb_hdrc
/sys/bus/platform/devices/musb_hdrc

I'm fairly confused and would appreciate any help ... thanks guys.


You need to see if the kernel builds the host drivers. Beyond that, not 
you need to find someone who uses the DM6446B to help you with the usb 
stuff.


Anyone know of any good resources for this sort of question?

Philip




al fayez
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel



___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Novice problems: trouble building angstrom for the at91sam9263ek dev board

[Philip Balister]

On 11/30/2009 08:31 AM, Séverin MARCOMBES wrote:

Hello,

 I'm a really new user of openembedded and angstrom.

I need a JFFS2 image of an Angstrom filesystem compiled for the Atmel
AT91SAM9263-EK board.
I would like an image as little as possible, with support of SSH, Blue-Z and
QT, so that to execute a project involving a custom QT interface interacting
with Bluetooth.

However, I have trouble building this image.
The online builder fails building a JFFS2 image for the AT91SAM9263-EK
board. I tried to use the tar.bz2 image that it produces and convert it into
JFFS2, but somehow I never could make this solution working.

I thus installed the OpenEmbedded build tools, with the objective to build a
"console-image" of angstrom.
After having followed the instructions of the "Getting
started"
  webpage of OpenEmbedded, I assumed that all I had to do was to configure my
local.conf file, and execute:
bitbake console-image

After some hours of compilation, the process seems successful, but I cannot
encounter the image produced anywhere...


Look in tmp/deploy/.../.../... ...

Philip



I'm a bit lost. Could someone guide me on the steps to build an
interface-less Angstrom image supporting Bluetooth for the AT91SAM9263-EK
board?

I would be really grateful if you could.
Thank you,

--
Séverin MARCOMBES
ECE / Aalborg Universitet
http://severin-marcombes.fr
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel


___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] any fix for xterm_207 build?

[Philip Balister]

On 10/29/2009 05:28 AM, Robert P. J. Day wrote:


   log file contents for xterm_207 build failure:

NOTE: make 
DESTDIR=/home/rpjday/oe/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/xterm-207-r0/image
 install
/bin/sh 
/home/rpjday/oe/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/xterm-207-r0/xterm-207/mkdirs.sh
 
/home/rpjday/oe/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/xterm-207-r0/image/usr/bin
mkdir 
/home/rpjday/oe/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/xterm-207-r0/image/usr
mkdir 
/home/rpjday/oe/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/xterm-207-r0/image/usr/bin
/bin/sh 
/home/rpjday/oe/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/xterm-207-r0/xterm-207/sinstall.sh
  "/home/rpjday/oe/angstrom-dev/staging/x86_64-linux/usr/bin/install -c" xterm  
/usr/bin/xterm 
/home/rpjday/oe/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/xterm-207-r0/image/usr/bin/`echo
 xterm|  sed 's/$//'|sed 's,x,x,'|sed 's/$//'`
checking for presumed installation-mode
... if "/usr/bin/xterm" is null, try the ls -g option
... if "/usr/bin/xterm" is null, we do not look for group
... if we have date in proper columns (Mar 2 2009), "" is null
... derived user "root", group "root" of previously-installed xterm
... see if mode "-rwxr-xr-x." has s-bit set
... installing xterm as user "rpjday", group "rpjday"
/home/rpjday/oe/angstrom-dev/staging/x86_64-linux/usr/bin/install -c -m 755.   
xterm 
/home/rpjday/oe/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/xterm-207-r0/image/usr/bin/xterm
/home/rpjday/oe/angstrom-dev/staging/x86_64-linux/usr/bin/install: invalid mode 
`755.'
make: *** [install] Error 1
FATAL: oe_runmake failed


   i tried to track that down myself but i don't know OE well enough,
sorry.


In the good news for you, bad news for me, I have duplicated the 
problem. I guess I need to poke around and figure out what is going on.


Philip




rday
--


Robert P. J. Day   Waterloo, Ontario, CANADA

 Linux Consulting, Training and Kernel Pedantry.

Web page:  http://crashcourse.ca
Twitter:   http://twitter.com/rpjday


___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel



___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] angstrom website

[Philip Balister]

Hans-J. Ullrich wrote:

Dear webmasters!

Thanks for reactivating the website! 

You asked for information, if something is missing. Yes, there is something 
missing. It is the link to the wiki (better say: the wiki-site), which is 
still not accessible.


The LTG people are working on the problem. We had pretty short notice of 
the move, and people are busy with paying work :(


Philip




Best wishes

Hans-J. Ullrich

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel



smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] angstrom website

[Philip Balister]

Hans-J. Ullrich wrote:

Dear webmasters!

Thanks for reactivating the website! 

You asked for information, if something is missing. Yes, there is something 
missing. It is the link to the wiki (better say: the wiki-site), which is 
still not accessible.


Thanks, I am checking on it now.

Philip




Best wishes

Hans-J. Ullrich

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel



smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

[Angstrom-devel] Website outage

[Philip Balister]

It looks like the Angstrom website is back. Sorry for the outage, we had 
a server move with short notice, and I have been on vacation. Let us 
know if there is anything else not working.


Thanks,

Philip


smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Making a new kernel

[Philip Balister]

Koen Kooi wrote:

On 22-06-09 18:18, Maxim Podbereznyi wrote:

Dear Koen,

I always ask myself a question why we have the online builder for 
rootfs but
never have a toolchain available online. Is it really necessary for 
all to
pass all that way to compile all the OE distribution to get a 
toolchain? I
understand that it is somehow possible to compile a toolchain apart 
from a

compilation of the whole OE


It's because everytime we distributed a toolchain for people that "just 
need a toolchain" it turns out that they don't "just need a toolchain" 
but more, at which point we'd point to OE. So to get around this, we 
start by pointing to OE. If you only want to toolchain, do 'bitbake 
gcc-cross' and 20 minutes later you have an up-to-date toolchain that 
matches your target environment perfectly.


Still we need to find a way to create and deliver toolchains usable by 
application developers. I realize there are issues supporting the 
diverse community of application developers with the appropriate 
libraries and header files.


But this is an area where they would be tremendous benefits for people 
developing for machines built from OE.


Philip


smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Hello world fails on AT91SAM9261-EK

[Philip Balister]

Lundqvist Anders wrote:

The instructions (and files) are explicitly stating the directory to /OE

But perhaps I am taking things too seriously...?


The instructions on the Angstrom page do not mention the need to chown 
/OE to be owned by you, but they should :)


You could also use $(HOME)/OE and change the OETREE var accordingly.

Philip



Best regards

Anders

-Original Message-
From: angstrom-distro-devel-boun...@linuxtogo.org on behalf of Philip Balister
Sent: Wed 4/22/2009 2:11 PM
To: Discussion of the angstrom distribution development
Subject: Re: [Angstrom-devel] Hello world fails on AT91SAM9261-EK
 
chown /OE to be owned by you.


Any particular reason the instructions do not have you install in in the 
users home directory?


Philip

Lundqvist Anders wrote:

Reinstalled the entire Ubuntu from scratch!

As a user:

alund...@alundqvi-ubuntu:/OE/openembedded$ bitbake meta-toolchain
Traceback (most recent call last):
  File "/OE/openembedded/bitbake/bin/bitbake", line 143, in 
main()
  File "/OE/openembedded/bitbake/bin/bitbake", line 123, in main
cooker.parseConfiguration()
  File "/OE/openembedded/bitbake/lib/bb/cooker.py", line 69, in 
parseConfiguration
self.parseConfigurationFile( os.path.join( "conf", "bitbake.conf" ) )
  File "/OE/openembedded/bitbake/lib/bb/cooker.py", line 403, in 
parseConfigurationFile
bb.fetch.fetcher_init(self.configuration.data)
  File "/OE/openembedded/bitbake/lib/bb/fetch/__init__.py", line 93, in 
fetcher_init
pd = persist_data.PersistData(d)
  File "/OE/openembedded/bitbake/lib/bb/persist_data.py", line 52, in __init__
bb.mkdirhier(self.cachedir)
  File "/OE/openembedded/bitbake/lib/bb/__init__.py", line 138, in mkdirhier
if e.errno != 17: raise e
OSError: [Errno 13] Permission denied: '/OE/angstrom-dev'

As root you get

r...@alundqvi-ubuntu:/OE/openembedded# bitbake meta-toolchain
ERROR:  Openembedded's config sanity checker detected a potential 
misconfiguration.
Either fix the cause of this error or at your own risk disable the 
checker (see sanity.conf).
Following is the list of potential problems / advisories:

Do not use Bitbake as root.

So either I have to extend user rights or disable sanity checker! Or do I still 
have a broken installation?

Best regards

Anders 


-Original Message-
From: angstrom-distro-devel-boun...@linuxtogo.org on behalf of Marcin 
Juszkiewicz
Sent: Wed 4/22/2009 12:20 PM
To: angstrom-distro-devel@linuxtogo.org
Subject: Re: [Angstrom-devel] Hello world fails on AT91SAM9261-EK
 
Dnia sroda, 22 kwietnia 2009 o 11:38:13 Lundqvist Anders napisal(a):

bitbake can only be run as user, but running git as user does not
work. I assume that I have missed something important somewhere, but
right now I cannot see it!
How do I proceed?
I suggest fixing your operating system. Exchange it with Debian or 
Ubuntu for example.



Basically all I want to have is a toolchain for building a very
simple GTK+ app! Hello world is fine with me, as long as it has a
window and perhaps a button...
'bitbake meta-toolchain' probably would be a way to it. But as your 
system behave like totally broken one...


Regards, 





___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel


___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel





___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel


smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Hello world fails on AT91SAM9261-EK

[Philip Balister]

chown /OE to be owned by you.

Any particular reason the instructions do not have you install in in the 
users home directory?


Philip

Lundqvist Anders wrote:

Reinstalled the entire Ubuntu from scratch!

As a user:

alund...@alundqvi-ubuntu:/OE/openembedded$ bitbake meta-toolchain
Traceback (most recent call last):
  File "/OE/openembedded/bitbake/bin/bitbake", line 143, in 
main()
  File "/OE/openembedded/bitbake/bin/bitbake", line 123, in main
cooker.parseConfiguration()
  File "/OE/openembedded/bitbake/lib/bb/cooker.py", line 69, in 
parseConfiguration
self.parseConfigurationFile( os.path.join( "conf", "bitbake.conf" ) )
  File "/OE/openembedded/bitbake/lib/bb/cooker.py", line 403, in 
parseConfigurationFile
bb.fetch.fetcher_init(self.configuration.data)
  File "/OE/openembedded/bitbake/lib/bb/fetch/__init__.py", line 93, in 
fetcher_init
pd = persist_data.PersistData(d)
  File "/OE/openembedded/bitbake/lib/bb/persist_data.py", line 52, in __init__
bb.mkdirhier(self.cachedir)
  File "/OE/openembedded/bitbake/lib/bb/__init__.py", line 138, in mkdirhier
if e.errno != 17: raise e
OSError: [Errno 13] Permission denied: '/OE/angstrom-dev'

As root you get

r...@alundqvi-ubuntu:/OE/openembedded# bitbake meta-toolchain
ERROR:  Openembedded's config sanity checker detected a potential 
misconfiguration.
Either fix the cause of this error or at your own risk disable the 
checker (see sanity.conf).
Following is the list of potential problems / advisories:

Do not use Bitbake as root.

So either I have to extend user rights or disable sanity checker! Or do I still 
have a broken installation?

Best regards

Anders 


-Original Message-
From: angstrom-distro-devel-boun...@linuxtogo.org on behalf of Marcin 
Juszkiewicz
Sent: Wed 4/22/2009 12:20 PM
To: angstrom-distro-devel@linuxtogo.org
Subject: Re: [Angstrom-devel] Hello world fails on AT91SAM9261-EK
 
Dnia sroda, 22 kwietnia 2009 o 11:38:13 Lundqvist Anders napisal(a):

bitbake can only be run as user, but running git as user does not
work. I assume that I have missed something important somewhere, but
right now I cannot see it!



How do I proceed?


I suggest fixing your operating system. Exchange it with Debian or 
Ubuntu for example.



Basically all I want to have is a toolchain for building a very
simple GTK+ app! Hello world is fine with me, as long as it has a
window and perhaps a button...


'bitbake meta-toolchain' probably would be a way to it. But as your 
system behave like totally broken one...


Regards, 





___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel


___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] at91sam9263-ek: change udev to static dev

[Philip Balister]

Maxim Podbereznyi wrote:

Dear Koen,

CCACHE did not help.

I think I've found the problem. I'm using Fedora Core 7 as a main build host
and gcc version is 4.1.2 there. So I decided to try to build Angstrom in
Ubuntu 8.10 where gcc-4.3.2 was installed. I don't know if it succeeds till
the end, but it definitely builds.

Are there any restrictions on the compiler version for successful build?


Fedora 7 works for me. I don't know of any compiler version restrictions.

Philip




regards,
Max

2009/4/7 Koen Kooi 


On 06-04-09 22:14, Maxim Podbereznyi wrote:


I've installed git version 1.6.2.2 and the steps from
http://www.angstrom-distribution.org/building-ångström
began
to work.

But shasum does not build..


Try doing:

CCACHE = ""

in your local.conf, there are known problems with some versions of ccache.

regards,

Koen




NOTE: Handling BitBake files: \ (6632/6632) [100 %]
NOTE: Parsing finished. 0 cached, 6340 parsed, 292 skipped, 0 masked.
NOTE: build 200904070010: started

OE Build Configuration:
BB_VERSION= "1.8.12"
METADATA_BRANCH   = "stable/2009"
METADATA_REVISION = "fe6822f3e85d5b14586d747c72b4e0395d981ea9"
TARGET_ARCH   = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE   = "at91sam9263ek"
DISTRO= "angstrom"
DISTRO_VERSION= "2009.X-test-20090406"
TARGET_FPU= "soft"

NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
ERROR: Multiple .bb files are due to be built which each provide
virtual/psplash (/stuff/OE/openembedded/recipes/psplash/
psplash-angstrom_svn.bb /stuff/OE/openembedded/recipes/psplash/
psplash_svn.bb).
 This usually means one provides something the other doesn't and should.
NOTE: Executing runqueue
NOTE: Running task 1 of 2926 (ID: 20,
/stuff/OE/openembedded/recipes/shasum/
shasum-native.bb, do_setscene)
NOTE: Running task 2 of 2926 (ID: 960,
/stuff/OE/openembedded/recipes/stage-manager/stagemanager-native_0.0.1.bb
,
do_setscene)
NOTE: package shasum-native-1.0-r1: task do_setscene: started
NOTE: package shasum-native-1.0-r1: task do_setscene: completed
NOTE: package stagemanager-native-0.0.1-r11: task do_setscene: started
NOTE: Running task 3 of 2926 (ID: 1,
/stuff/OE/openembedded/recipes/images/
base-image.bb, do_setscene)
NOTE: package base-image-1.0-r0: task do_setscene: started
NOTE: package stagemanager-native-0.0.1-r11: task do_setscene: completed
NOTE: package base-image-1.0-r0: task do_setscene: completed
NOTE: Running task 4 of 2926 (ID: 21,
/stuff/OE/openembedded/recipes/shasum/
shasum-native.bb, do_fetch)
NOTE: package shasum-native-1.0-r1: task do_fetch: started
NOTE: package shasum-native-1.0-r1: task do_fetch: completed
NOTE: Running task 5 of 2926 (ID: 23,
/stuff/OE/openembedded/recipes/shasum/
shasum-native.bb, do_unpack)
NOTE: Running task 6 of 2926 (ID: 33,
/stuff/OE/openembedded/recipes/shasum/
shasum-native.bb, do_distribute_sources)
NOTE: package shasum-native-1.0-r1: task do_unpack: started
NOTE: Unpacking /stuff/OE/openembedded/recipes/shasum/files/main.c to
/stuff/OE/build/tmp/work/i686-linux/shasum-native-1.0-r1/
NOTE: Unpacking /stuff/OE/openembedded/recipes/shasum/files/mhash_sha256.h
to /stuff/OE/build/tmp/work/i686-linux/shasum-native-1.0-r1/
NOTE: package shasum-native-1.0-r1: task do_distribute_sources: started
NOTE: Unpacking /stuff/OE/openembedded/recipes/shasum/files/sha256.c to
/stuff/OE/build/tmp/work/i686-linux/shasum-native-1.0-r1/
NOTE: package shasum-native-1.0-r1: task do_unpack: completed
NOTE: package shasum-native-1.0-r1: task do_distribute_sources: completed
NOTE: Running task 7 of 2926 (ID: 24,
/stuff/OE/openembedded/recipes/shasum/
shasum-native.bb, do_patch)
NOTE: package shasum-native-1.0-r1: task do_patch: started
NOTE: package shasum-native-1.0-r1: task do_patch: completed
NOTE: Running task 8 of 2926 (ID: 25,
/stuff/OE/openembedded/recipes/shasum/
shasum-native.bb, do_configure)
NOTE: package shasum-native-1.0-r1: task do_configure: started
NOTE: package shasum-native-1.0-r1: task do_configure: completed
NOTE: Running task 9 of 2926 (ID: 26,
/stuff/OE/openembedded/recipes/shasum/
shasum-native.bb, do_qa_configure)
NOTE: package shasum-native-1.0-r1: task do_qa_configure: started
NOTE: Checking sanity of the config.log file
NOTE: package shasum-native-1.0-r1: task do_qa_configure: completed
NOTE: Running task 10 of 2926 (ID: 27,
/stuff/OE/openembedded/recipes/shasum/shasum-native.bb, do_compile)
NOTE: package shasum-native-1.0-r1: task do_compile: started
ERROR: function do_compile failed
ERROR: see log in

/stuff/OE/build/tmp/work/i686-linux/shasum-native-1.0-r1/temp/log.do_compile.10600
NOTE: Task failed:

/stuff/OE/build/tmp/work/i686-linux/shasum-native-1.0-r1/temp/log.do_compile.10600
NOTE: package shasum-native-1.0-r1: task do_compile: failed
ERROR: TaskFailed event exception, aborting
ERROR: Build of
/stuff/OE/openembedd

Re: [Angstrom-devel] Avahi recipe

[Philip Balister]

Stanislav Brabec wrote:

Ben Gamari wrote:

Furthermore, I just attempted to remove the dependency on avahi
altogether by adding the following to task-base.bb,

BAD_RECOMMENDATIONS = "avahi-daemon avahi-autoipd"

Despite this, it pulled in both packages. This I am truly baffled by. Ideas?


I am not sure whether it will not break Zeroconf support in full builds
of the same distro.

Another possible solutions:

- Branch a new minimal avahi-less distribution.


Do you really mean to create a new distro.conf file, when you could 
create an avahi-less image?


There seems to be a lot of confusion about what a distro.conf file does 
lately.


Philip


smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Can't create functional images for h1910

[Philip Balister]

Capn_Fish Zaurus wrote:

Can somebody at least let me know what OS works for building
functional images? Ubuntu 8.04 isn't working for me, nor is Gentoo
~x86. Is either Fedora 10 or Ubuntu 8.10 known to work?


Do you have specific issues? OE works for me on all Fedora up to 9.

Philip



Thanks in advance.

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel



smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] [RFC] Using narcissus as preferred way to build images for release

[Philip Balister]

Koen Kooi wrote:

On 10-02-09 15:59, Bernhard Guillon wrote:

Koen Kooi wrote:

Hi,

In an effort to reduce the skillset needed to get involved into
angstrom I'd like to propose this:

Narcissus[1] is the preferred way to build an image to be put in the
download are for users.

The workflow would be:

1) go to http://amethyst.openembedded.net/~koen/narcissus/
2) select machine, packages and click 'build me'
3) downloading resulting image
4) test it
5) Convert it to the proper format (e.g. ubifs, jffs2, tar.bz2, ext2,
installkit)
6) upload it to angstrom-distribution.org
7) Announce it

Note that step 5 can be scripted, but due to php/fakeroot limitations
we can't do it all with narcissus. An option would be that narcissus
spits out the scripts needed.

As the narcissus page points out, patches are welcome. If you are
missing packages, send me a patch :)

So, what do you think about this proposal?


I like narcissius much but we should keep alternatives such as
autobuilder or build images from the mentors.


Why? Noone is interested in doing that judging from the *complete* lack 
of activity, so let's make narcissus default till mentors start being 
active again and indicate they want to provide OE built images *next to* 
narcissus images.


Agreed. I want to be able to create some simple images for machines I 
can test so there are known good images. But I do not want to test a 
large number of images, especially since Narcissus seems to be working 
well for the Beagle community.


Philip


smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Why is Angstroms documentation spread over wiki and the webpage?

[Philip Balister]

Koen Kooi wrote:

Bob Igo wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Koen Kooi wrote:

Ah, that error is one of that random libtool ones we fixed in .dev:
'bitbake -c clean libtool-cross ; bitbake -c clean fontconfig'


Thanks for helping me work around that.  How does this fix get
propagated to the stable branch so that others don't run into that same
problem?


The fix would be hundreds of commits large, since it's tied it to the 
toolchain overhaul, sysroot changes and libtool 2.x changes. So that's 
sadly not feasible to do.
The good news however is that a new stable branch based on current .dev 
is being prepared, which should land in a few weeks if things work out ok.
The current stable branch will still be supported for 3 months after the 
new stable branch has been started.


I think we should "support" the current stable branch for as long as we 
can manage. Hopefully, people will still use devices based on it for 
longer than three months.


Philip


smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Why is Angstroms documentation spread over wiki and the webpage?

[Philip Balister]

Bob Igo wrote:


Frankly, I think that Rolf's apt-gettable build process should be the
official way, and the current generic build process should be a fallback
in case the official process fails or won't run on a user's distro of
choice.  I mean, look at it - it's 5 shell commands, and then you're up
and running.


What about the non-apt universe? I have problem pointing people to 
Rolf's apt-get stuff (except that it isn't immediately obvious from the 
blog post what to do for Angstrom) for people that can use it.


I'd be much happier if people having trouble with the generic install 
emailed or asked on irc. We can't figure out every problem in a 
reasonable amount of time, but it does help to have some record of where 
problems are so we can try and reproduce the problem and fix it.


Philip


smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Successful fix the Angstrom Release 2007.12r13 WPA problem: could not allocate crypto API arc4 FIXED

[Philip Balister]

See article near the top of http://www.openembedded.org

Thanks,

Philip

Matthew Swabey wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Bug is http://bugs.openembedded.net/show_bug.cgi?id=4180.

I can confirm that compiling in the modules shown works, as described on
my c860 (c7x0).

Kernel size differences: Modularised: 1264180 bytes
With the suggested modules built in: 1269336 bytes.

Got to be worth it, and hope the problem doesn't reoccur in 2.6.25 when
we get around to using it.

Can someone remind me what email address to use to suggest inclusion in
angstrom stable?

Dr M Swabey
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkgzbT0ACgkQsoSsB2Ynk1CpeQCgqAkb9wFwaZqHgwf0dxYP5Jak
1x0An3uSC0qoXGXREvrnccm3meWDW4Gl
=/COu
-END PGP SIGNATURE-

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel



smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

[Angstrom-devel] [Fwd: Re: [oe] Change ANGSTROM_EXTRA_INSTALL to IMAGE_EXTRA_INSTALL]

[Philip Balister]

Any thoughts?

Philip

 Original Message 
Subject: Re: [oe] Change ANGSTROM_EXTRA_INSTALL to IMAGE_EXTRA_INSTALL
Date: Fri, 9 May 2008 17:23:22 +0200
From: Leon Woestenberg <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
References: <[EMAIL PROTECTED]>

Hello Philip,

On Fri, May 9, 2008 at 5:14 PM, Philip Balister <[EMAIL PROTECTED]> wrote:

I'd like to change the variable used for the user to add packages to a
standard image from ANGSTROM_EXTRA_INSTALL to IMAGE_EXTRA_INSTALL. This is
an image property, and not Angstrom specific.

Is there anything wrong with this idea?


No, except I guess you ask the Angstrom guys'n'gals as well?

Regards,
--
Leon

___
Openembedded-devel mailing list
[EMAIL PROTECTED]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel



smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] [Announce] org.openembedded.angstrom-2007.12-stable renamed to org.openembedded.stable

[Philip Balister]

SDG Systems wrote:

The 2007.12 naming made sense to me. 2007.12 was the time period when
you branched from .dev, essentially. So the next time you branch from
.dev to stabilize will it be org.openembedded.new-stable? I would
think that at some point you will do a stable branch from .dev again
and the current 2007.12 branch is no longer maintained (or an end of
life is established). Correct?


I would name the next stable branch .stable-2008.12 (assuming a December 
release).


Philip


smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] [RFC] Changing stable branch commit policy

[Philip Balister]

Koen Kooi wrote:
If we drop the bookkeeping part, getting things into the stable tree  
will be much easier:


* send explanation and diff to angstrom-distro-devel
* 2 developers sign off on it
* apply diff
* copy-paste explanation into NEWS or Changelog

This makes a faster turnaround possible, since a roundtrip to .dev  
isn't needed anymore. And we can create tarball releases of the tree  
every $period where people can read the NEWS or Changelog file to see  
the difference and decided wether updating it worth it or not.


I hope with this changes people (especially machine mentors) have more  
time to fix bugs. Especially rare machines like Poodle, Simpad or Tosa  
would benefit from this.


objections, additions?


+1

At some point in time, a stable and development branch will diverge. We 
should focus Angstrom stable on being usable and not tracking .dev.


I do hope people take the time to look at what goes into the stable 
branch and also send it to .dev when it is appropriate.


Philip


smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] [review] org.oe.dev angstrom.inc: Make Angstrom bitbake caches to be per libc mode.

[Philip Balister]

Funny date from a couple of emails?

Philip

Koen Kooi wrote:


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Paul Sokolovsky schreef:
| Hello,
|
|
|
| Up.

*Rubberstamp OK*

|
|
| On Sat, 23 Feb 2008 20:35:58 +0200
| Paul Sokolovsky <[EMAIL PROTECTED]> wrote:
|
|>
|> Begin forwarded message:
|>
|> Date: Thu, 21 Feb 2008 18:06:33 +0100
|> From: "pfalcon commit"

|> To:
openembedded-commits-ZwoEplunGu3dfDuKDZ/[EMAIL PROTECTED]
|> Subject: [oe-commits] org.oe.dev angstrom.inc: Make Angstrom bitbake
|> caches to be per libc mode.
|>
|>
|> angstrom.inc: Make Angstrom bitbake caches to be per libc mode.
|> * This is allows easy switching between glibc and uclibc builds,
|> without waiting for long reparses on every switch.
|> * Note that it applies to dependent distros, like OpenMoko, too.
|>
|> Author: [EMAIL PROTECTED]
|> Branch: org.openembedded.dev
|> Revision: 3859c4593b2a4ff696a5e81383ed8bc6dd957598
|> ViewMTN:
|>
http://monotone.openembedded.org/revision/info/3859c4593b2a4ff696a5e81383ed8bc6dd957598
|> Files: 1
|> conf/distro/include/angstrom.inc
|> Diffs:
|>
|> #
|> # mt diff -r6c2d621bdfd446c13552a5e4b126ef9c5dd20106
|> -r3859c4593b2a4ff696a5e81383ed8bc6dd957598 #
|> #
|> #
|> # patch "conf/distro/include/angstrom.inc"
|> #  from [b86b952c90304d1fd39f1415f6af7f71d02e00df]
|> #to [2519c1b72831f6c678dec86bda400fdbdd069054]
|> #
|> 
|> --- conf/distro/include/angstrom.inc
|> b86b952c90304d1fd39f1415f6af7f71d02e00df +++
|> conf/distro/include/angstrom.inc
|> 2519c1b72831f6c678dec86bda400fdbdd069054 @@ -12,6 +12,7 @@
|> ANGSTROM_MODE ?= "glibc" # Can be "glibc", "eglibc" or "uclibc"
|> ANGSTROM_MODE ?= "glibc"
|> +CACHE = "${TMPDIR}/cache/${ANGSTROM_MODE}/${MACHINE}"
|>  DEPLOY_DIR = "${TMPDIR}/deploy/${ANGSTROM_MODE}"
|>  require conf/distro/include/angstrom-${ANGSTROM_MODE}.inc
|>
|>
|>
|>
|> ___
|> Openembedded-commits mailing list
|> Openembedded-commits-ZwoEplunGu3dfDuKDZ/[EMAIL PROTECTED]
|> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-commits
|
|
|

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHxx0SMkyGM64RGpERAtR0AJ0QHO04hP3KZONyxI85DF5IRp4u9gCgqr4n
IHKZKfpmqj87Gguh7LjjuGg=
=ThTe
-END PGP SIGNATURE-


___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel


smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Google summer of code: 1 day left, who will submit the angstrom project?

[Philip Balister]

Koen Kooi wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

As the subject says:

Google summer of code: 1 day left, who will submit the angstrom project?


I was going to, but I missed the deadline. I read the deadline as May 
12, which I took to be midnight GMT or California time. Turns out it was 
1900 UTC (noon in California), which is when I sat down to start working 
on it.


So, the lesson for this year is, read the GSoC timeline and note the 
deadlines very carefully.


I'm really sorry about this, I will look for related projects when the 
post the list of accepted organizations and do what little I can to find 
projects for people interested in OE and Angstrom.


Philip


smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Google summer of code: 1 day left, who will submit the angstrom project?

[Philip Balister]

The application is here. I plan to fill it out tomorrow. I need google 
addresses from mentors. I could also use a backup admin. Mickey, I know 
you are interested in one of the ideas, it would be good to have one or 
two more mentors for the other ideas.


If anyone has any suggestions for content let me know :)  I'll probably 
pitch this as a joint OE/Angstrom effort since the ideas serve both 
communities.


Philip

Koen Kooi wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Philip Balister schreef:
| I am going to work on this today/tomorrow.

Great! Many thanks to all the people putting effort into this!

regards,

Koen
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFH1rueMkyGM64RGpERAstNAKCM4DxEcKpx3XYaz1B4Hr+U9dVwrACfTmO/
OP2eYRdHQo/oBZB4gz8tz/w=
=QryQ
-END PGP SIGNATURE-


___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel



smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Google summer of code: 1 day left, who will submit the angstrom project?

[Philip Balister]

I'm not having any luck finding the page. Can you be more specific?

Philip

Jacob Thebault-Spieker wrote:
Wiki page is up, check the main page of the Angstrom wiki. It's just a 
concatenated version of what I saw on the mailing list.


--
Jacob Thebault-Spieker
Cell: (207) 717-5114


Philip Balister wrote:
I am going to work on this today/tomorrow. Dis we get a wiki page 
together for ideas?


Philip

Koen Kooi wrote:
Hi,

As the subject says:

Google summer of code: 1 day left, who will submit the angstrom project?

regards,

Koen




___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel









___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel





___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel


smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Google summer of code: 1 day left, who will submit the angstrom project?

[Philip Balister]

I am going to work on this today/tomorrow. Dis we get a wiki page 
together for ideas?


Philip

Koen Kooi wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

As the subject says:

Google summer of code: 1 day left, who will submit the angstrom project?

regards,

Koen
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFH1ll9MkyGM64RGpERAlyKAJ0aIcL7P0twRC7M+7Eq28vxPx3B8ACgswtg
U2ZEW67Vgef1qTJnNaVNjlI=
=aLEH
-END PGP SIGNATURE-


___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel



smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Boost not found

[Philip Balister]

Look at the boost bb file. You may need to depend on something like 
boost-dev.


Philip

Capn_Fish Zaurus wrote:

I'm trying to make a BB file for the latest Wesnoth, which needs Boost. I
added Boost to the deps list in the BB file, and it (Boost) built OK, but
Wesnoth doesn't find the headers, and spits out this error:

checking for Boost headers version >= 1.33... no
configure: error: Could not find Boost headers version >= 1.33
FATAL: oe_runconf failed


How do I fix this?
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel



smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] GSoc 2008 status

[Philip Balister]

I've poked around the SoC web pages and there are projects that only 
list one or two ideas. Also some organizations list partner 
organizations, so we could list the mentoring organization as 
OpenEmbedded and Angstrom"


I'd be glad to list myself as the contact. This will make dealing with 
money easier since I already have a US tax ID :)


Philip

Michael 'Mickey' Lauer wrote:
Hi, just thought I ping you because mentoring application deadline is in two 
days and it would be sad to miss it for Ängstrom. Where's the wiki page for 
the list of ideas, btw.?


:M:

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel





smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Google Summer of Code ideas for Angstrom

[Philip Balister]

Michael 'Mickey' Lauer wrote:



I'm willing to mentor one project, but I'm not available as general organizer.



I'd be willing to do the general organization (submit the app etc). I'm 
not sure who to apply as, but we have plenty of projects we could apply 
this to. (OE, Angstrom). What we need is a pool of good ideas that 
involve writing actual code.


Philip


smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] [RFC] Switch angstrom 2008 to opkg

[Philip Balister]

Koen Kooi wrote:


What do you think?


Does this mean people will stop complaining about ipkg?

Philip


smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

[Angstrom-devel] OMAP5912OSK images

[Philip Balister]

I finally had a chance to look the Angstrom-2007 images for the OSK. 
I've made console-image and the kernel available to the general public.


Philip


smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Maintenance of unstable feed

[Philip Balister]

Koen Kooi wrote:

| and invite people to upload more builds.

No, if it hasn't been built by a autobuilder, it shouldn't be available
for download (that includes images!).


We should encourage people to request the addition of new images and 
packages to the autobuilder? How does the autobuilder decide what 
packages get built?


Philip


smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] [PATCH, CRITICAL] ipaq-sleep fix

[Philip Balister]

Paul Sokolovsky wrote:

Hello,

  Please approve this critical fix. And I would like to RFC
coreteam members to be able to commit without pre-review for critical
bug and security fixes.


We should at least give people 24 hours to object to something before it 
goes into the stable branch. Generally, only people knowledgeable about 
a change would approve, we need a way to auto-approve a change where the 
pool of knowledgeable people is very small though.


Philip


smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] [Review] Patches for the 2007 branch

[Philip Balister]

Koen Kooi wrote:


  2008 release is going to be tough, as we will need to ensure
ipkg-upgradability from 2007,


We're upgrading both libc6 and libgcc1, so I'm not sure if we can
achieve upgradability, but it is a good goal to keep in mind.


I am not concerned about upgrading from one major release to another. 
Rather we should focus our efforts on solving problems in the release 
branch until users stop reporting problems :)


I work mainly in the class of machines where the end-user would not 
upgrade the software on package basis, so maintaining upgradability 
across releases is not important. (Just to document my personal bias)


Philip


smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] RC3 on OMAP starter kit

[Philip Balister]

Koen Kooi wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Rod Whitby schreef:

Koen Kooi wrote:

Philip Balister schreef:

Console image runs fine on the OSK (omap5912osk), but base image is
hanging during boot. I have created bug
http://bugs.openembedded.org/show_bug.cgi?id=3571 for this.

I suspect this is because base-image doesn't use util-linux-mount, and
the busybox one is broken. Angstrom adds it to DISTRO_EXTRA_RDEPENDS for
a reason :)

Sounds like it's a MACHINE_ESSENTIAL_RDEPENDS if it's required to boot
...  or do we really need a DISTRO_ESSENTIAL_RDEPENDS ?


I'm not sure, since it's a busybox bug, which is more image teritory
than distro territory. We could make it DISTRO_ESSENTIAL in 2007.12 and
see if busybox 1.7.x (or 1.8.x) still have the same bug in 2008.6


The fstab used on the OSK uses the same options as the Efika fstab. Does 
base image work on the Efika?


Should we examine the options used in the fstab to work with both 
mounts? I'm assuming the mount options are the problem.


I remember we switched minimal image to util-linux-mount for this reason.

Philip


smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

[Angstrom-devel] RC3 on OMAP starter kit

[Philip Balister]

Console image runs fine on the OSK (omap5912osk), but base image is 
hanging during boot. I have created bug 
http://bugs.openembedded.org/show_bug.cgi?id=3571 for this.


Any ideas on the hang? Same kernel for both images. kernel and images 
came from the autobuilder.


Philip


smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Device release status

[Philip Balister]

Koen Kooi wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

AFAIK the status breaks down like this:



* omap5912osk   UNTESTED


I'll try to test the OSK in the next couple of days.

For the gumstix verdex, there are still a number of unresolved issues, 
some have been fixed already in the gumstix treee, and some (the 
touchscreen) are still problems.


Philip


smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] RFC: replace minimal-image with base-image in autobuilder for all machines. (was :Re: RC1 on saturday?)

[Philip Balister]

Paul Sokolovsky wrote:

Hello Philip,

Monday, December 17, 2007, 4:22:23 PM, you wrote:


Koen Kooi wrote:



Which brings me to the RFC:

 * replace minimal-image with base-image in autobuilder for all machines



Why not build both? One for people who want a very basic image to start
from and the other for people who want to start with package management?



Mind you, I'm having a hard time figuring out what I would actually use
minimal image for, over base image at this point.


  As was pointed out during OE list discussion of this matter,
minimal-image is an abstract example of really minimal firmware-type
image, a starting point for vendors who'd like to create a
non-runtime-customizable firmware. Its usefulness for the general-purpose
open-source distro is doubtful, so +1 for the RFC.


I agree, no sense for the autobuilder to produce both. Let's have the 
autobuilder produce images useful to the end user. Developers can 
produce minimal image as needed.


+1

Philip


smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] RFC: replace minimal-image with base-image in autobuilder for all machines. (was :Re: RC1 on saturday?)

[Philip Balister]

Koen Kooi wrote:


Which brings me to the RFC:

 * replace minimal-image with base-image in autobuilder for all machines


Why not build both? One for people who want a very basic image to start 
from and the other for people who want to start with package management?


Mind you, I'm having a hard time figuring out what I would actually use 
minimal image for, over base image at this point.


Philip


smime.p7s
Description: S/MIME Cryptographic Signature
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Preparing for the release

[Philip Balister]

I have an OSK (and a mistral display for it).

I can test the console images, I'm having trouble flashing the X11 
images due to some size issues.

Philip


Michael 'Mickey' Lauer wrote:
> Thanks for getting this started.
> 
>> 1) make a list of machines we can support *now*[1]
> 
> I'm in posession of
> 
> * SL-5500
> * SL-5600
> * SL-C750
> * SL-C3200
> 
> I will reserve as much of one full day as necessary for testing images
> on these models (probably Friday or Saturday though).
> 
> I have no opinion whether to include or exclude Opie, I'll agree with
> the majority here.
> 
> Regards,
> 
> :M:

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

[Angstrom-devel] Sound and Efika

[Philip Balister]

Has anyone tried sound with a recent Efika? I can't find the sound 
modules on the image.

Philip

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel