Re: [leaf-devel] possible bug in linuxrc

Charles Steinkuehler <[EMAIL PROTECTED]> writes: > Erich Titl wrote: > > | There is a possible bug in linuxrc (at least with the busybox of Bering) > | when trying to create and mount the /tmp filesystem. > | > | Here is the output from /linuxrc.err > | > | mount -t tmpfs tmpfs /tmp -o size=20M >

Re: [leaf-devel] package libcxx: buildtool.cfg filenames

Martin Hejl <[EMAIL PROTECTED]> writes: >> But if someone wants to fix the current regexp based buildpacket.pl >> code, the proposed workaround should point to the bug quite directly. > correction - I found the issue you're seeing. It wasn't triggered when > I tried, because I didn't fully specify

Re: [leaf-devel] package libcxx: buildtool.cfg filenames

Hans Ulrich Niedermann <[EMAIL PROTECTED]> writes: > Oliver Ertl <[EMAIL PROTECTED]> writes: > >> in libcxx/buildtool.cfg you could change the Source line with the >> two questenmarks from: >> >> [...] >> Source = lib/libstdc??.so.5.0.5 >> [

Re: [leaf-devel] package libcxx: buildtool.cfg filenames

Oliver Ertl <[EMAIL PROTECTED]> writes: > in libcxx/buildtool.cfg you could change the Source line with the > two questenmarks from: > > [...] > Source = lib/libstdc??.so.5.0.5 > [...] > > to this > > [...] > Source = lib/libstdc\+\+.so.5.0.5 > [...] > > > Then you could specify the full filename

[leaf-devel] Integrating libstc++ and libpthread in BU root package

Hi, in current CVS, both the libstdc++ and libpthread .so libraries are created by ./buildtool build root but libcstc++ is not packaged at all, and libpthread is packaged in a separate empty package which builds nothing. That doesn't make sense, so here is my updated patch which removes the

[leaf-devel] grammar fix for buildtool.pl

Index: src/bering-uclibc/buildtool/buildtool.pl === RCS file: /cvsroot/leaf/src/bering-uclibc/buildtool/buildtool.pl,v retrieving revision 1.13 diff -u -3 -p -r1.13 buildtool.pl --- src/bering-uclibc/buildtool/buildtool.pl2 Mar 200

[leaf-devel] Re: [leaf-cvs-ci] src/bering-uclibc/buildtool buildpacket.pl,1.26,1.27

Martin Hejl <[EMAIL PROTECTED]> writes: > Update of /cvsroot/leaf/src/bering-uclibc/buildtool > In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv32764 > > Modified Files: > buildpacket.pl > Log Message: > Hopefully fixed problem with permissions of directories that are also used in >

Re: [leaf-devel] More errors with buildtool

Martin Hejl <[EMAIL PROTECTED]> writes: >> - lpthread -> wrong directory (lpthread) in sources.cfg > Fixed in CVS >From a buildtool outsider's point of view, I wonder why lpthread is a separate source package anyway. Isn't the content of lpthread.lrp generated when uclibc (i.e. the buildenv sou

Re: [leaf-devel] Package for C++ libraries

Hans Ulrich Niedermann <[EMAIL PROTECTED]> writes: > Hans Ulrich Niedermann <[EMAIL PROTECTED]> writes: > Therefore, I present the attached patch to the "root" package to fix > that. It creates a "libcxx.lrp" package containing libstdc++ and > libgcc

Re: [leaf-devel] Package for C++ libraries

Hans Ulrich Niedermann <[EMAIL PROTECTED]> writes: > I have found neither libstdc++ nor libgcc_s in any standard > package. Is that correct? It is correct, as I have just verified by building from CVS. Therefore, I present the attached patch to the "root" package to

Re: [leaf-devel] Canonical source for 6wall and lrcfg source code?

Eric de Thouars <[EMAIL PROTECTED]> writes: > Martin Hejl wrote: > >> Hans Ulrich Niedermann wrote: >> >>> where is the canonical place to get source code for 6wall and lrcfg >>> from? >> >> Not sure about 6wall - but I would guess th

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

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

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

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-)bui

[leaf-devel] Package for C++ libraries

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

[leaf-devel] Canonical source for 6wall and lrcfg source code?

Hi, where is the canonical place to get source code for 6wall and lrcfg from? The packages shipped with the latest Bering uClibc release? I'd like to see if I can improve lrcfg a little for BU, and I'd like to package 6wall for OpenWRT. GruÃ, Uli pgp7CcT9uegII.pgp Description: PGP signature

[leaf-devel] Creating Bering uClibc images

Hi, here are a few thoughts about how to create media images with Bering uClibc. They may serve as thought food and a foundation for a healthy discussion... 1. It is non-trivial to create images if you don't have a step by step HOWTO to follow. Currently we have these: http://leaf-project.

[leaf-devel] Another new developer

Hi developers! Mike Noyes was so kind and added me to the developers. I have been using LEAF Bering uClibc on an old 486 from floppy for several years, but recently built myself a cute little router box (see :) for which I had to build me a few packages.