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
| mount:
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 the
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.
I think we'd
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
[...]
to this
[...]
Source = lib/libstdc\+\+.so.5.0.5
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
a
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
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
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 source
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_s.
Apply in src/bering-uclibc.
Index: root
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 the latest lrp from CVS at
http://cvs.sourceforge.net/viewcvs.py/leaf/bin/bering
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 fix
that. It creates a libcxx.lrp
Hi,
I have been building a BU package of
YATE - Yet Another Telephony Engine URL: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
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
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
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:
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 http://n-dimensional.de/projects/router/ :) for which I had to
build me a few packages.
16 matches
Mail list logo
