Hi folks
I am moving my build environment to a new hardware, what is the actual
uClibc version for the buildenv
Thanks
Erich
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest
Am Donnerstag, 23. Oktober 2008 20:09:44 schrieb Erich Titl:
Hi folks
I am moving my build environment to a new hardware, what is the actual
uClibc version for the buildenv
Hi Erich;
it's still 0.9.28
kp
-
This SF.Net
Am Donnerstag, 23. Oktober 2008 20:22:06 schrieb KP Kirchdoerfer:
Am Donnerstag, 23. Oktober 2008 20:09:44 schrieb Erich Titl:
Hi folks
I am moving my build environment to a new hardware, what is the actual
uClibc version for the buildenv
Hi Erich;
it's still 0.9.28
And if you change
Hi,
I need to rebuild a custom 2.4.2 old release using buildtool.
I have done:
cvs -d :pserver:[EMAIL PROTECTED]:/cvsroot/leaf login
cvs -z3 -d :pserver:[EMAIL PROTECTED]:/cvsroot/leaf \
co -r Release-2_4_2 src/bering-uclibc/buildtool
These command download the build environment related
Hi Sandro,
Check: http://leaf.sourceforge.net/doc/buc-buildtool.html
(Checking out an older version to build)
Eric
Hi,
I need to rebuild a custom 2.4.2 old release using buildtool.
I have done:
cvs -d :pserver:[EMAIL PROTECTED]:/cvsroot/leaf login
cvs -z3 -d :pserver:[EMAIL
Am Freitag, 1. Dezember 2006 12:52 schrieb Bob von Knobloch:
Dear Leafers,
the links on Bering uClibc, Buildtool.. that should point to
the LEAF Bering-uClibc Developer's Guide seem broken, giving:
An error has been encountered in accessing this page.
1. *Server:*
Bob von Knobloch wrote:
I have been trying to set up buildtool becuase I want to customise a
couple of things. I have done a CVS checkout, set up the configs,
installed the PERL package Config::General, as detailed in the LEAF
Bering-uClibc Developer's Guide.
Dear LEAF list,
I have been trying to set up buildtool becuase I want to customise a
couple of things. I have done a CVS checkout, set up the configs,
installed the PERL package Config::General, as detailed in the LEAF
Bering-uClibc Developer's Guide.
Am Samstag, 12. August 2006 16:40 schrieb Bob von Knobloch:
Dear LEAF list,
I have been trying to set up buildtool becuase I want to customise a
couple of things. I have done a CVS checkout, set up the configs,
installed the PERL package Config::General, as detailed in the LEAF
Bering-uClibc
Hello Cpu,
Thanks for testing.
I also did the same as you did and see the same behaviour, insmod
trying to load the module in the current directory.
This is a busybox bug, not much I can do about unfortuanatly. It's
probably in there since years. I will report it on the busybox list.
Luckely
Okay... I still think something is wrong. This is what
/etc/init.d/ipsec start is doing:
ipsec_setup: Starting Openswan IPsec 1.0.9...
insmod: not an ELF file
insmod: Could not load the module: Success
ipsec_setup: Using ipsec
ipsec_setup: Using /lib/modules/ipsec.o
_startklips has this line
Hello cpu,
This is a strange message:
insmod: not an ELF file
Can you run insmod from the command line?
errors out here because /lib/modules is not in my path
and it's trying to load the ipsec executable.
Should /lib/modules be in the path (presumably the start)?
Insmod looks at
Eric,
It looks like it's trying to load /lib/ipsec/ipsec (the shell script).
Does insmod default to the current directory? Perhaps the ipsec scripts
are being run from within /lib/ipsec.
Everywhere else it loads fine:
foobar# insmod ipsec
Using /lib/modules/ipsec.o
Here are some of the changes
Cpu,
Eric,
It looks like it's trying to load /lib/ipsec/ipsec (the shell
script).
Does insmod default to the current directory? Perhaps the ipsec
scripts
are being run from within /lib/ipsec.
No insmod shouldn't default to the current directory, just tested it
myself and ipsec is loaded by
Eric,
Thanks for the help. I followed your instructions in a previous post on
building the minimum packages after a kernel build: modules, initrd,
and root.lrp. ipsec was also built/packaged from the same kernel.
Today I tried beta 2.3:
1. Downloaded linux-2.4.29.upx (renamed to linux),
cpu memhd wrote:
Using buildtool to build openswan for bering-uclibc 2.3 beta (kernel
2.4.29). Copy ipsec.lrp to LEAF box... everything seems normal except
ipsec does not load ipsec_aes.o like it used to before.
IIRC this was never loaded by the original (FreeSWan) code. It is pretty
trivial
Using buildtool to build openswan for bering-uclibc 2.3 beta (kernel
2.4.29). Copy ipsec.lrp to LEAF box... everything seems normal except
ipsec does not load ipsec_aes.o like it used to before.
This becomes more of a problem when I want to:
svi ipsec stop (or restart) because it cannot unload
Kirchd,
Okay, no ticker problem with 2.4.29 (same squid problem though).
ls -al for /bin/sh has always been:
/bin/sh - ash
So it looks like 2.4.26 with newer build environment causes the ticker
problem. Not a big deal I guess. -cpu
K.-P. Kirchdörfer wrote:
Am Donnerstag, 24. März 2005 13:29
Hi;
Am Samstag, 26. März 2005 20:00 schrieben Sie:
Kirchd,
Okay, no ticker problem with 2.4.29 (same squid problem though).
Good to hear about ticker; squid is a damn problem (I installed an old
version, but fails also) - I'm currently out of ideas...
ls -al for /bin/sh has always been:
Kirchd,
I tried both 2.4.26 and 2.4.29. I ended up compiling the latest squid
stable9 on a mandrake box and using the libc225.lrp + a gcc library it
was complaining about. In other words, no uClibc. Works pretty good.
About the ticker problem. I guess it was pretty dumb of me to suggest
the
Am Donnerstag, 24. März 2005 13:29 schrieb cpu memhd:
I tried both 2.4.26 and 2.4.29. I ended up compiling the latest
squid stable9 on a mandrake box and using the libc225.lrp + a gcc
library it was complaining about. In other words, no uClibc. Works
pretty good.
Ok. Seems it's related to
...trying to get a USB keyboard to work on a USB only system. I don't
give up that easily...After having problems trying to build sysvinit
with an older Mandrake distro I switched to Suse Enterprise 9. Now with
buildtool, I am able to produce all of the above modules with new
kernel and USB
Hello,
Buildtool compiles the kernel with gcc-3.x instead of gcc-2.95
nowadays, that's why kgcc isn't necessary anymore.
Because of this you also have to use the kernel modules that are
compiled with buildtool. You can't mix gcc-2.95 and gcc-3.x kernel
modules, that's probably why you get a
Hi, thank you very much. That explains it. The question now is, what
core packages will I have to rebuild?
__
Do you Yahoo!?
All your favorites on one personal page Try My Yahoo!
http://my.yahoo.com
At least modules.lrp and if you are using a initrd with ide modules,
you have to rebuild initrd.lrp and root.lrp.
Eric Spakman
Hi, thank you very much. That explains it. The question now is, what
core packages will I have to rebuild?
__
Do you Yahoo!?
All
Thanks again. I was able to build package initrd, but not root or
modules:
- There is no modules package according to 'buildtool.pl describe'; how
do I build modules.lrp?
- I tried building root and it bombed out with an undefined reference
to crypt:
make[1]: Entering directory
How does one go about building a working kernel? I ran:
./buildtool.pl build kernel
I then tried booting both bzimage-2.4.26 and bzimage-2.4.26-upx and
both gave me oops/kernel panics after initializing the IDE controller
is seems.
./buildtool.pl describe says kgcc is required to build a
Mike Noyes wrote:
On Wed, 2005-01-12 at 20:21, cpu memhd wrote:
didn't work for me is pretty hard to debug for anyone but you.
What is this supposed to mean?
cpu,
I believe it means, it's nearly impossible to tell what went wrong on
your side without better information.
Yes, I agree. But
Okay, I see things more clearly now. A meaningful message is usually a
balance one: don't say too much, don't say too little.
I think we both said too little, and then jumped to conclusions because
of it.
My post was short honestly because I'm new not only to LEAF but to the
CVS and I did not
cpu memhd wrote:
I had the same problem.
From the CVS help page:
http://www.leaf-project.org/doc/guide/buc-buildtool.html
This line didn't work for me:
cvs -d :pserver:[EMAIL PROTECTED]:/cvsroot/leaf login
didn't work for me is pretty hard to debug for anyone but you.
But this one did:
cvs -z3
Hello,
Excuse me. I can't help but notice a negative tone in your reply. Maybe
I am mistaken. Please clarify:
Martin Hejl wrote:
cpu memhd wrote:
I had the same problem.
From the CVS help page:
http://www.leaf-project.org/doc/guide/buc-buildtool.html
This line didn't work for me:
cvs
On Wed, 2005-01-12 at 20:21, cpu memhd wrote:
didn't work for me is pretty hard to debug for anyone but you.
What is this supposed to mean?
cpu,
I believe it means, it's nearly impossible to tell what went wrong on
your side without better information.
I'll make a guess though. Have you
I'm trying to load the Buildtool to set up a build environment but I
cannot find the Buildtool files on Sourceforge. Referring to the Bering
uClibc Developers Guide, an anonymous download should work, but doesn't.
It seems that SF no longer allows anonymous logins ??
On Tue, 2005-01-11 at 07:30, Bob von Knobloch wrote:
I'm trying to load the Buildtool to set up a build environment but I
cannot find the Buildtool files on Sourceforge. Referring to the Bering
uClibc Developers Guide, an anonymous download should work, but doesn't.
It seems that SF no
I had the same problem.
From the CVS help page:
http://www.leaf-project.org/doc/guide/buc-buildtool.html
This line didn't work for me:
cvs -d :pserver:[EMAIL PROTECTED]:/cvsroot/leaf login
But this one did:
cvs -z3 -d :pserver:[EMAIL PROTECTED]:/cvsroot/leaf \
co src/bering-uclibc/buildtool
Dear all,
I'm trying to build bering-uClibc out of sources with buildtool/buildpacket.
Having done:
1) ./buildtool.pl build buildenv
2) ./buildtool.pl source root
3) ./buildtool.pl build root
that point needed following corrections:
3.1) 'mkdir staging/sbin' in order to get debianutils
bibl wrote:
Dear all,
I'm trying to build bering-uClibc out of sources with
buildtool/buildpacket.
Having done:
1) ./buildtool.pl build buildenv
2) ./buildtool.pl source root
3) ./buildtool.pl build root
that point needed following corrections:
3.1) 'mkdir staging/sbin' in order to get
Am Sunday 15 August 2004 14:22 schrieb Martin Hejl:
bibl wrote:
Dear all,
I'm trying to build bering-uClibc out of sources with
buildtool/buildpacket.
I hope that helps. Note that the buildtool setups are most likely going
to be changed a lot over the next few days, since I'm currently
Hi!!
With bering you use buildtool to construct it. The system buildtool is very
similar to GAR (http://lnx-bbc.org/faq-GAR.html), but this one is created in
bash.
For a long time there have been being been looking for a tool to construct a
toolchain from scratch. GAR was most similar than I
39 matches
Mail list logo
