[leaf-devel] LEAF Bering uClibc, OpenWRT, OpenEmbedded and the Uber Distribution

2005-01-19 Thread Hans Ulrich Niedermann
Hi!

I recently got myself a Linksys WRT54GS/OpenWRT box as a backup
solution for my PCEngines WRAP/Bering uClibc box (to maintain the
service while updating the box, or demoing it somewhere else).

When I was setting up OpenWRT (http://openwrt.org/), I noticed a few
things:

- Both OpenWRT and BU are built on a Linux kernel and uClibc.
- Both use the uClibc build root, and the .mk files look quite similar.
- Both a floppy-based BU on a PC with 4MB RAM and OpenWRT face serious
  space limitations.

- But 6wall is only in BU, and some other stuff only in OpenWRT.
- To package a certain piece of software, I have to build two packages.

I wonder whether it is possible and desirable to have a build system
which builds a base system image and packages for a Linux/uClibc based
OS running on completely different kinds of hardware:

  1. Standard PC booting from
 a) floppy
 b) harddisk
  2. Embedded PC board without keyboard, with special devices
 (HW watchdog)
  3. Broadcom/MIPS based routers like the Linksys WRT54G(S)
  4. Embedded boards running PPC, ARM, whatever...

It seems that I'm not the only one who ever thought of that. In the
OpenWRT developer forum (http://openwrt.org/forum/viewforum.php?f=2)
there is a thread (http://openwrt.org/forum/viewtopic.php?t=199) about
OpenEmbedded (http://openembedded.org/oe_wiki/index.php/OpenEmbedded)
which tries to do something quite similar...

Does anyone else from the LEAF devs think that this may be an
interesting idea to pursue?

GruÃ,

Uli


---
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

___
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel


[leaf-devel] What I don't like about Bering uClibc

2005-01-19 Thread Hans Ulrich Niedermann
Hi,

don't get me wrong - I love Bering uClibc. But while installing Bering
uClibc on a WRAP and building, installing and testing yate packages, I
got to hate some aspects of it :)

I'll make a list so you can give some input about it:

1. (buildtool)
   There is no "build-all-packages" to (re-)build all packages.

2. (buildtool?)
   There is no "build-hdd-image-for-my-board" which copies all the
   necessary lrp files, sets up leaf.cfg with all the lrp names,
   possibly installs grub on the image, and so on.

3. (lrcfg aka "config")
   Every time I have modified a config file of package XYZ in lrcfg, I
   have to
   a) run "/etc/init.d/XYZ restart" from another shell
   b) make the changes permanent doing this:
  - go up two levels in the menu
  - enter the "backup" menu
  - read through the list to find XYZ' number (different from XYZ'
number in the "Packages configuration" menu)
  - type b to back up
  - wait for some time
  - manually compare two numbers without given units, where one 
shows Bytes (new file size) and the other Kilobytes
(free space)
  - if enough space is available, I have to manually confirm
   I'd like to have to menu entries in the "package configuration":
   i)  "restart service"
   ii) "make changes permanent"
   This should check for the amount of free space by itself.

4. (lrcfg, buildtool, ???)
   Every time I have an updated package and install it, I have to
   manually save my config files and somehow merge them into the new
   package. Keeping the config, or having diff/edit, or even 3-way
   merge would be very nice.

GruÃ,

Uli


pgpXubfDGXX95.pgp
Description: PGP signature


[leaf-devel] Package for C++ libraries

2005-01-19 Thread Hans Ulrich Niedermann
Hi,

I have been building a BU package of

   YATE - Yet Another Telephony Engine http://yate.null.ro/>

which is written in C++ and thus requires libstdc++ and libgcc_s.

I have found neither libstdc++ nor libgcc_s in any standard
package. Is that correct?

If so, I provide the steps with which I have hacked together a working
"cxx.lrp" package to help with directly creating an official cxx.lrp:

1. Copied

-rwxr-xr-x root/root   2988706 2005-01-17 01:44:39 lib/libstdc++.so.5.0.5
lrwxrwxrwx root/root 0 2005-01-17 05:41:12 lib/libstdc++.so.5 -> 
libstdc++.so.5.0.5
-rw-r--r-- root/root863683 2005-01-17 01:46:06 lib/libgcc_s.so.0.9.9

   from my buildtool staging/ directory to the running BU, and added files

2) Created file var/lib/lrpkg/cxx.list with a content of

lib/libgcc_s.so.0.9.9
lib/libstdc++.so.*
var/lib/lrpkg/cxx.*

3) Created file var/lib/lrpkg/cxx.version with a content of

0.9.20

   (in the assumption that these files belong to uClibc/gcc)

4) Added proper entries in /var/lib/lrpkg/backdisk and
   /var/lib/lrpkg/packages.

5) Backed up "cxx" package in lrcfg.

GruÃ,

Uli


pgpUMyTS1ziDK.pgp
Description: PGP signature