OpenEmbedded: compile Puppy from source

[technosaurus]

For developers on the Arm platform there is a Kickstarter project
https://liliputing.com/2016/12/firefly- ... r-139.html

_____________________________________________________

Don't bother. The octa-core odroid XU4 has better support for half the price (2 usb3 ports for 8Tb+ and emmc for fast root filesystem and swap)

[BarryK]

My "meta-quirky" layer for OpenEmbedded is now on github.

Blog announcement:

http://barryk.org/news/?viewDetailed=00576

And github, with a nice readme:

https://github.com/bkauler/oe-qky-src

[scsijon]

Since you told me too, i'm playing with oe (your version), but..

After a bit of reading, and a lot of playing, i'm a little confused still, can I ask for guidance please.

1- How do I find out what packages are already in the list, whether enabled or not, is there an equivalent (think of T2's config file) and where would it be?

2- And where do I add files I want included, that don't seem to be already there?

I'm using xerus 8.3 and there are a few name changes and extras not as dependancies, from xerus8.1.6 for the extra packages. Do you want a 8.3 list?

Oh, yes, using a frugal build seems to fail as we are using all the ram up before a build is completed. I'm going to reinstall a full xerus 8.3 as the partition was origonally just for testing and has nothing keepable on it.

thanks
-------
ps barryk.org brings up a contact support message." Webmaster please contact hostgater.com" and the associated links are being redirected to what I call JUNK pages.
ie, unrelated to puppy. Do you need to change your domain account?

[BarryK]

Since you told me too, i'm playing with oe (your version), but..

After a bit of reading, and a lot of playing, i'm a little confused still, can I ask for guidance please.

1- How do I find out what packages are already in the list, whether enabled or not, is there an equivalent (think of T2's config file) and where would it be?

2- And where do I add files I want included, that don't seem to be already there?

I'm using xerus 8.3 and there are a few name changes and extras not as dependancies, from xerus8.1.6 for the extra packages. Do you want a 8.3 list?

Oh, yes, using a frugal build seems to fail as we are using all the ram up before a build is completed. I'm going to reinstall a full xerus 8.3 as the partition was origonally just for testing and has nothing keepable on it.

thanks

You need to build in a partition with heaps of space, maybe 200GB - 500GB.

Instructions:

https://github.com/bkauler/oe-qky-src/b ... /readme.md

...it explains that "# bitbake -g core-image-quirky" will create a package-list.

To add or remove packages, edit buildPC/conf/local.conf

[s243a]

Barry, I can recommend the Synology DS216J 2-Bay NAS. This is a reliable, fast and quiet NAS.

The DiskStation OS is topnotch, with lots of configuration settings. It even has its own 'app' store!

I use this NAS (in 'RAID 1' aka mirroring) for storage and streaming media. My older DS212j 2-bay unit I bought years ago now serves as an archive.

http://www.austin.net.au/synology-ds216j-2-bay-nas.html

Just in case anyone else decides to do this research, I looked into the most economical method of getting a 1Gbit SATA file server and found the banana pi m1 (in headless mode) to be the most bang for the buck (<$40)... plus you get an extra dual core arm system with a mali GPU for distributed builds. Note that later versions of the banana pi use an inferior usb2->sata controller that severely limits speed. Although the product page states that the m1's drive size is limited to 2Tb, various forums report success with 4Tb.

Edit: for usb3 the lemon pi is a similar price point, but it appears to be poorly documented, which in my experience usually means some of the driver work is still incomplete/experimental.

Here are two boards with USB 3.0:
Banana Pi R2

ROC-RK3328-CC (Renegade)

[scsijon]

...., using a frugal build seems to fail as we are using all the ram up before a build is completed. I'm going to reinstall a full xerus 8.3 as the partition was origonally just for testing and has nothing keepable on it.

thanks

You need to build in a partition with heaps of space, maybe 200GB - 500GB.

Instructions:

https://github.com/bkauler/oe-qky-src/b ... /readme.md

...it explains that "# bitbake -g core-image-quirky" will create a package-list.

To add or remove packages, edit buildPC/conf/local.conf

The partition space wasn't the problem as I gave it 512gig to play around in, it was that I was trying to build from 8.3 frugal which seems to want to run everything in ram. Changed over to a 8.3 full install and it built ok. I was trying an initial test run with -minimal rather than -quirky. Now I know it's right I will start a test run with -quirky next and see how that goes.

However, in the last couple of weeks, i've been pointed at sourcemage, the spinoff from when sorcerer initially vanished from the linux world. I have been starting to play with it and it's interesting. However using the wayback machine i've found git and iso copysets from sourcerer itself which in turn a couple of days ago lead me to a git dated dec2017, so someone is still working on sourcerer. I want to see which packages it contains and how up to date it's packages are, and if it can deal with updates, so that goes first for this month. It'd be nice to add apps dynamically by building them and their dependencies on the fly and that's what the sourcerer and sourcemage linux's are proposed to do.
Maybe I'll start a puppy sourcery http://puppylinux.org/wikka/PuppySourceryinstead of fighting my way through with T2 again. Look like a basic Puppy, but allow users to build those extra packages they themselves want dynamically. I won't bet on it yet as I suspect there are a few getchas in the pipe to work through.

[scsijon]

And a full build is underway.......

Two minor changes with your latest set of oe-qky-source-master.zip build package.

Bacon has updated to 3.7, if we/you need to use 3.5.4 it's now in the museum directory rather than stable, i'll try first with 3.7 after working how to use recipetool and adding your code from 3.5.4 to the new bacon-3.7.dd. I've left the 3.5.4.dd there by adding a .org on the end and the builder seems to have ignored it;
EDIT1: no failed on compile so will go back to 3.5.4 for now and see what happens there.

Vcdimager's .dd file has wrong source paths pointing to kernel.org rather than gnu.org, copied the origonal one to a .dd.org and modified the .dd and it now finds the source ok.

EDIT2+ for now below

Schroedinger's home and download pages have changed to https://launchpad.net/schroedinger. The sourceforge url takes you to a website that hasn't been populated yet.

Sane has it's own site http://www.sane-project.org/source.html but uses debian (usa) for storage of versions https://alioth.debian.org/frs/?group_id=30186. The origonal link takes you to a site with the latest version 1.0.27, not 1.0.25.

Anything happens tomorrow will just halt it as i'll be elsewhere for most part.

[BarryK]

And a full build is underway.......

Two minor changes with your latest set of oe-qky-source-master.zip build package.

Bacon has updated to 3.7, if we/you need to use 3.5.4 it's now in the museum directory rather than stable, i'll try first with 3.7 after working how to use recipetool and adding your code from 3.5.4 to the new bacon-3.7.dd. I've left the 3.5.4.dd there by adding a .org on the end and the builder seems to have ignored it;
EDIT1: no failed on compile so will go back to 3.5.4 for now and see what happens there.

Vcdimager's .dd file has wrong source paths pointing to kernel.org rather than gnu.org, copied the origonal one to a .dd.org and modified the .dd and it now finds the source ok.

I think mcewanw already tried to bump up the version of bacon, but it failed.

There is another problem with bacon. Although the 'popup' utility compiles, it is partly broken.

Compiled with a much old version of bacon, it works properly.

So, in Easy, I have created z_popup PET package, with popup compiled in a running easy, with bacon 3.0.2.

...that's only a temporary workaround.