Page 7 of 9

Posted: Sat 18 Aug 2012, 13:34
by Iguleder
You configuration is invalid; you have supplied an invalid architecture: it should be either i686 or x86_64 for Arch.

EDIT: see the configuration here if you need an example.

EDIT 2: it seems mplayer2 is screwed up. Since it depends on Python 3, it cannot be built using Slackware's Python. Also, syslinux fails to build for some reason - I'm still investigating this.

Posted: Sat 18 Aug 2012, 13:39
by aragon
smokey,

the arch is missing in your url e.g. i686 ...

EDIT: ah iguleder you been faster (and you know more about that ...)

aragon

Posted: Sat 18 Aug 2012, 13:59
by Iguleder
Forgot to mention - make sure you work against the latest version (here).

Currently, there is a development branch called "raspberry-pi", which has many improvements. I'm going to merge it back to the master branch soon.

Posted: Sat 18 Aug 2012, 15:28
by smokey01
I progressed a lot further this time but encountered a lot of command not found errors.

Never got to build an image.

See attached output from Terminal window.

Regards

Posted: Sat 18 Aug 2012, 15:37
by Iguleder
Well, that makes lots of sense - take a look at the package list you used - it's pretty much empty. You don't even have a C library or a kernel. :evil:

But yes, you used roar-ng right - kudos for that. Now, get a real package list (as the one here) and run 1download, 2createpackages and 3builddistro again.

Posted: Sat 18 Aug 2012, 15:40
by smokey01
Yes, already doing that now.

It's not so clear to us old chaps.

Thanks

Posted: Sat 18 Aug 2012, 15:42
by Iguleder
That's why you have this.

Posted: Sat 18 Aug 2012, 15:48
by smokey01
Iguleder wrote:That's why you have this.
I read the readme.

What would be easier to understand is if you had a fully configured conf directory so following the ./1 ./2 ./3 & ./4 would have produced something.

You are much cleverer than the average bear.

Posted: Sat 18 Aug 2012, 16:20
by Iguleder
Great news! I got both Syslinux and mplayer2 to build.

The former had an issue with LDFLAGS - for some reason, it reads it from the environment but fails to build with my custom flags.

The latter required Python 3, so I got Python 3.1 from Debian to work (extremely hacky!).

I'm currently uploading all packages - you'll have to run 0setup, 1download and 2createpackages again. Make sure you clean processed-packages from remains of the previous .rxz packages.

EDIT: smokey01 - I improved the README and added details documentation of the configuration. Packages are still uploading, shouldn't take very long.

Posted: Sat 18 Aug 2012, 16:48
by smokey01
Iguleder wrote:
EDIT: smokey01 - I improved the README and added details documentation of the configuration. Packages are still uploading, shouldn't take very long.
Thanks mate.

It's generating a lot of "command not found errors" during the ./2createpackages stage. Is this normal?

Anyway, after 02:00 better go to bed.

Thanks for your help and advice.

Posted: Sat 18 Aug 2012, 16:53
by Iguleder
Yes, it's normal. That happens because you don't have AdvanceCOMP or OptiPNG installed.

The result is a larger, less optimized distro.

Posted: Sun 19 Aug 2012, 00:19
by smokey01
Iguleder wrote:Yes, it's normal. That happens because you don't have AdvanceCOMP or OptiPNG installed.

The result is a larger, less optimized distro.
With AdvanceCOMP and/or OptiPNG installed, is it larger?
Is it better with or without?

It's slowly starting to make sense but just when I think it's safe to go back in the water, another bugger bites me.

During the ./2createpackages:
squashfs-tools (subito)
Error: squashfs-tools-4.2.rxz does not exist under packages.

It appears squashfs-tools-4.2.rxz has not been downloaded. I guess it's pretty important as it's required to build the iso.

I re-ran ./1download but it still did not find the package. Is it missing or is something wrong with the script?

I guess you wouldn't notice as it would already be in your packages directory from previous ./1downloads.

Should I comment all lines out in the conf/package_list or are these files required when building slackware?

###################################
# Subito GNU/Linux-specific stuff #
###################################
subito|subito-desktop|subito-desktop|exe,dev,doc,nls
subito|locale-gen|locale-gen|exe,dev,doc,nls
subito|advancecomp|advancecomp|exe>dev,dev,doc,nls
in the conf/package_list or are these files required when building slackware?
.
.
.


I don't fully understand what packages are required. It would be nice to have a default list of bare minimum for each distro, or is this list it?

I also read in the manual: ./3builddistro
"It is recommended to edit the script before its execution, in order to tweak various parameters, such as the default desktop background."

In sandbox/rootfs there doesn't appear to be a backgrounds directory where I would expect it /usr/share/backgrounds. Do I need to manually create this directory and populate it with backgrounds?

Thanks

Posted: Sun 19 Aug 2012, 17:16
by Iguleder
It's better with AdvanceCOMP and OptiPNG - they're used to shrink the ISO. Get them installed on your distro.

And no, you can't build "slackware", but you can build a distro which contains packages taken from Slackware. If you don't have any other AdvanceCOMP package, use the one in the example I gave you.

By the way - the manual was removed from recent versions of roar-ng. It's totally irrelevant - if you still have it, get a newer version.

missing Sublito V1 ISO

Posted: Mon 20 Aug 2012, 18:22
by gcmartin
Iguleder wrote:Uploading the 1.0.0 stable release to this directory. It's 248 MB, since the ISO contains the devx.

Here's the list of the ISO contents: ...
Hi @Iguleder.

I saw this post to this thread, but, I cannot find the ISO you present. Has it been moved or placed somewhere else?

Thanks in advance. ... Also see PM

Posted: Tue 21 Aug 2012, 12:59
by nooby
I guess you need what is referred to as "git"

I know nothing about it but I failed to download
due to me have no "git"

Here is a link to the ReadMe of latest version 2013?
https://github.com/iguleder/roar-ng-ii/ ... ter/README

Posted: Thu 17 Jan 2013, 10:51
by nooby
So what lies in the future for this then? Any prediction?
I find it interesting but I am not on the level needed to get any of it.

https://github.com/iguleder/roar-ng-ii/ ... ter/README

Posted: Thu 17 Jan 2013, 11:24
by anikin
The future's so bright, you gotta wear shades. ©

roar-ng-ii

Posted: Fri 18 Jan 2013, 13:24
by Embla
Maybe it's too early to ask questions about roar-ng-ii:

After successfully running:
# sh roar-ng setup

I'm now stuck at:
# sh roar-ng download
busybox (subito 3 x86_64)
Error: failed to locate the package "busybox".
Error: failed to locate busybox.

Posted: Fri 18 Jan 2013, 17:15
by Iguleder
Yep, I'm aware of this problem. I'm currently trying to solve it - it's a problem with my domain, which prevents download tools from downloading package lists.

EDIT: I think it works now.

EDIT 2: I'm currently working on a new distro using roar-ng-ii. It's a console-only, live distro similar to Puppy, with heaps of console applications. I also have a Raspberry Pi (btw, the reason why you had issues with roar-ng-ii is the fact I moved all my stuff from hosting in the US to my Raspberry Pi, at home :)) and I want to port this distro to ARM later.

Posted: Fri 18 Jan 2013, 18:57
by Embla
Thanks, Iguleder, downloading now! Just a minor problem:
Error: failed to download terminus-font-4.36-1.rxz.

And I'm really, REALLY looking forward to your ARM port! But take all the time you need.
*currently building a retro-Acorn BBC Microcomputer round my Pi*