Le 3 nov. 2012 à 11:45, KP Kirchdoerfer a écrit :
> Hi;
>
> buildtool fails, when the ? statement tries to load the same
> file twice or more.
>
> Can't include file
> '/opt/buildtool-master/source/i486-unknown-linux-uclibc/ppp/common.cfg'
> from file
> '/opt/buildtool-master/source/i486-unknow
Hi;
buildtool fails, when the ? statement tries to load the same
file twice or more.
Can't include file
'/opt/buildtool-master/source/i486-unknown-linux-uclibc/ppp/common.cfg'
from file
'/opt/buildtool-master/source/i486-unknown-linux-uclibc/ppp/buildtool.cfg':
file has already been loaded. at /o
Le 17/10/2012 10:18, Erich Titl a écrit :
> Hi Folks
>
> This has driven me crazy for a long time and was the reason for a number
> of quirks in the makefiles.
>
> When calling 'build' the buildtool passes the parameters defined in
> buildtool.cfg to the environment and thus to the makefile.
>
> he
Hi Folks
This has driven me crazy for a long time and was the reason for a number
of quirks in the makefiles.
When calling 'build' the buildtool passes the parameters defined in
buildtool.cfg to the environment and thus to the makefile.
here...
buildtool::Make::Source::_makeEnvString:envstring=
Am Sonntag, 13. Februar 2011, um 11:47:45 schrieb davidMbrooke:
> On Sun, 2011-02-13 at 10:04 +, davidMbrooke wrote:
> > It is not well documented in the Wiki - at least not yet.
> > I feel a new Chapter coming on... :-)
>
> Now written, although rather brief:
> http://sourceforge.net/apps/med
On Sun, 2011-02-13 at 22:23 +1100, ads...@genis-x.com wrote:
> You might want to note that you have to run buildall.sh from within the
> buildtool directory not from the tools folder
That's why we always refer to it as "tools/buildall.sh" not
"./buildall.sh", and I claim the new Wiki page is *rel
, back in 2003 seems to ring a bell,
still going strong and still rolling them out.
Cheers
Adam
-Original Message-
From: KP Kirchdoerfer [mailto:kap...@users.sourceforge.net]
Sent: Sunday, 13 February 2011 8:57 PM
To: leaf-devel@lists.sourceforge.net
Subject: Re: [leaf-devel] Buildtool
On Sun, 2011-02-13 at 10:04 +, davidMbrooke wrote:
> It is not well documented in the Wiki - at least not yet.
> I feel a new Chapter coming on... :-)
Now written, although rather brief:
http://sourceforge.net/apps/mediawiki/leaf/index.php?title=Bering-uClibc_4.x_-_Developer_Guide_-_Building_a
On Sun, 2011-02-13 at 19:58 +1100, ads...@genis-x.com wrote:
> Awesome,
>
> ./buildtool.pl build buildenv
> works a treat
> ./buildtool.pl build did the job perfectly (iscsi package failed, but as
> sources.cfg says it's in progress ;o).
>
> So far so good, the one thing I'm a little confused on
Am Sonntag, 13. Februar 2011, um 09:58:40 schrieb ads...@genis-x.com:
> Awesome,
>
> ./buildtool.pl build buildenv
> works a treat
> ./buildtool.pl build did the job perfectly (iscsi package failed, but as
> sources.cfg says it's in progress ;o).
>
> So far so good, the one thing I'm a little con
o:ni...@seti.kr.ua]
Sent: Sunday, 13 February 2011 1:14 AM
To: leaf-devel@lists.sourceforge.net
Subject: Re: [leaf-devel] Buildtool issues
12.02.2011 13:20, davidMbrooke пишет:
> On Fri, 2011-02-11 at 13:07 +1100, ads...@genis-x.com wrote:
>> Hi Guys,
>>
>> Now that all the p
12.02.2011 13:20, davidMbrooke пишет:
> On Fri, 2011-02-11 at 13:07 +1100, ads...@genis-x.com wrote:
>> Hi Guys,
>>
>> Now that all the packages are in git I figured I would clone the latest from
>> there.
>>
>> Alas there are some issues..
>>
>>
>>
>> [leaf@leafbuilder buildtool]$ ./buildtool.pl b
On Fri, 2011-02-11 at 13:07 +1100, ads...@genis-x.com wrote:
> Hi Guys,
>
> Now that all the packages are in git I figured I would clone the latest from
> there.
>
> Alas there are some issues..
>
>
>
> [leaf@leafbuilder buildtool]$ ./buildtool.pl build buildenv
>
> make the list of required
Hi Guys,
Now that all the packages are in git I figured I would clone the latest from
there.
Alas there are some issues..
[leaf@leafbuilder buildtool]$ ./buildtool.pl build buildenv
make the list of required source packages: linux,buildenv [0.K.]
source/package: linux
---
the successful /
> failed environments that may highlight the issue, or perhaps you could
> compare the logs from 32-bit and 64-bit Ubuntu 10.
>
> dMb
>
> >
> > -Original Message-
> > From: davidMbrooke [mailto:dmb.leaf-de...@ntlworld.com]
> > Sen
uld
not be found
Cheers
Adam
-Original Message-
From: davidMbrooke [mailto:dmb.leaf-de...@ntlworld.com]
Sent: Thursday, 3 February 2011 11:52 PM
To: ads...@genis-x.com
Cc: leaf-devel@lists.sourceforge.net
Subject: RE: [leaf-devel] Buildtool with cvs down etc
On Thu, 2011-02-03 at 16:39
rsday, 3 February 2011 10:10 AM
> To: ads...@genis-x.com
> Cc: leaf-devel@lists.sourceforge.net
> Subject: RE: [leaf-devel] Buildtool with cvs down etc
>
> On Thu, 2011-02-03 at 08:37 +1100, ads...@genis-x.com wrote:
> > Hi,
> >
> > I was under the impression the new bering didn&
...@ntlworld.com]
Sent: Thursday, 3 February 2011 10:10 AM
To: ads...@genis-x.com
Cc: leaf-devel@lists.sourceforge.net
Subject: RE: [leaf-devel] Buildtool with cvs down etc
On Thu, 2011-02-03 at 08:37 +1100, ads...@genis-x.com wrote:
> Hi,
>
> I was under the impression the new bering didn&#
ew is much more of an expert on the buildenv than I am, so he may
have some other suggestions.
Does anybody else have a successful build on 64-bit Ubuntu 10?
dMb
>
> -Original Message-
> From: davidMbrooke [mailto:dmb.leaf-de...@ntlworld.com]
> Sent: Thursday, 3 February 2011 7
ginal Message-
From: davidMbrooke [mailto:dmb.leaf-de...@ntlworld.com]
Sent: Thursday, 3 February 2011 7:57 AM
To: leaf-devel
Subject: Re: [leaf-devel] Buildtool with cvs down etc
On Wed, 2011-02-02 at 20:13 +1100, ads...@genis-x.com wrote:
> I should have added,
> Base ma
t; Sent: Wednesday, 2 February 2011 5:16 PM
> To: leaf-devel@lists.sourceforge.net
> Subject: Re: [leaf-devel] Buildtool with cvs down etc
>
> Hey guys,
>
> I git clone'd the lastest buildtool and hit a snag.
>
>
> downloading: .config from serv
: [leaf-devel] Buildtool with cvs down etc
Hey guys,
I git clone'd the lastest buildtool and hit a snag.
downloading: .config from server leaf4-sourceforge type gitweb [0.K.]
downloading: 50_all_gcc44_no_ssp_tls_uclibc.patch from server
leaf4-sourceforge type gitweb [0.K.]
downloading: u
Hey guys,
I git clone'd the lastest buildtool and hit a snag.
downloading: .config from server leaf4-sourceforge type gitweb [0.K.]
downloading: 50_all_gcc44_no_ssp_tls_uclibc.patch from server
leaf4-sourceforge type gitweb [0.K.]
downloading: uClibc-0.9.30.3.tar.bz2 from server uclibc.org type
On Tue, 2011-02-01 at 10:49 -0600, Charles Steinkuehler wrote:
-snip-
> I'm not sure this is a great idea (I'd prefer SF to get CVS back
> on-line),
Everyone,
SF Staff expects to have CVS working later this week. I'll keep checking
status of the attack recovery on irc.
http://sourceforge.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/1/2011 6:26 AM, KP Kirchdoerfer wrote:
> Theoratically it should be possible to work with the tarball without access
> to
> cvs - but I doubt anyone has done this before.
If it helps, I have installed viewvc and made a backup of the SF CVS
arch
Am Dienstag, 1. Februar 2011, um 13:18:17 schrieb ads...@genis-x.com:
> Hey guys,
>
> I know your working on getting it all backup in GIT/SVN etc,
> but in the meantime I wanted to setup my buildenv to be able to play with
> pxe booting.
>
> Is it possible to setup buildtool with upacking the
> B
Hey guys,
I know your working on getting it all backup in GIT/SVN etc,
but in the meantime I wanted to setup my buildenv to be able to play with pxe
booting.
Is it possible to setup buildtool with upacking the
Bering-uClibc_4.0-beta2_src.tgz ?
The wiki docco mentions updating the sources.cfg b
Hi KP
at 03.01.2011 18:38, KP Kirchdoerfer wrote:
> Am Sonntag, 2. Januar 2011, 21:59:15 schrieb Erich Titl:
>> Hi Folks
>>
...
>
> We do have other packages like tools.lwp.
IMHO they should be in webconf.lrp anyway
They may be renamed to tools.lrp,
> but then a) it's not clear that it's a fi
Am Sonntag, 2. Januar 2011, 21:59:15 schrieb Erich Titl:
> Hi Folks
>
> Happy new year to all of you
>
> on 01.01.2011 23:46, KP Kirchdoerfer wrote:
> > Gents;
>
> ...
>
> > Note: To finalize the task the buildimage templates has to be changed to
> > add *.lwp files.
> >
> > So before I commit
Hi Folks
Happy new year to all of you
on 01.01.2011 23:46, KP Kirchdoerfer wrote:
> Gents;
>
...
>
> Note: To finalize the task the buildimage templates has to be changed to add
> *.lwp files.
>
> So before I commit, I'd like to ask, if you think I'm on the right track, or
> misleaded.
I s
On Sun, 2011-01-02 at 15:18 +0100, KP Kirchdoerfer wrote:
> Hi David;
>
> Am Sonntag, 2. Januar 2011, 15:01:20 schrieb davidMbrooke:
> > On Sat, 2011-01-01 at 23:46 +0100, KP Kirchdoerfer wrote:
> > > Gents;
> > >
> > > First a happy new year to all!
> > >
> > > I've created, but yet not committ
Hi David;
Am Sonntag, 2. Januar 2011, 15:01:20 schrieb davidMbrooke:
> On Sat, 2011-01-01 at 23:46 +0100, KP Kirchdoerfer wrote:
> > Gents;
> >
> > First a happy new year to all!
> >
> > I've created, but yet not committed, a buildtool setup for lwp files.
> >
> > It is based on the lwp's I had
On Sat, 2011-01-01 at 23:46 +0100, KP Kirchdoerfer wrote:
> Gents;
>
> First a happy new year to all!
>
> I've created, but yet not committed, a buildtool setup for lwp files.
>
> It is based on the lwp's I had on my Bering-uClibc 3.1 machine, therefor some
> files may be outdated - pls doublec
Gents;
First a happy new year to all!
I've created, but yet not committed, a buildtool setup for lwp files.
It is based on the lwp's I had on my Bering-uClibc 3.1 machine, therefor some
files may be outdated - pls doublecheck.
The setup just downloads and extracts a tarfile with all lwp's. Cau
On Sun, 2010-06-06 at 21:41 +0200, KP Kirchdoerfer wrote:
> Hi;
> it seems something went wrong with a cvs commit.
> I now have buildtool/tools/ and buildtool/tools/tools/ in my local cvs.
>
> In case it's a mistake we have to ask SF maintainers to remove the obsolet
> directory.
> Mike can you
Am Sonntag, 6. Juni 2010 21:49:47 schrieb Andrew:
> 06.06.2010 22:41, KP Kirchdoerfer пишет:
> > Hi;
> >
> > it seems something went wrong with a cvs commit.
> > I now have buildtool/tools/ and buildtool/tools/tools/ in my local cvs.
> >
> > In case it's a mistake we have to ask SF maintainers to r
06.06.2010 22:41, KP Kirchdoerfer пишет:
> Hi;
>
> it seems something went wrong with a cvs commit.
> I now have buildtool/tools/ and buildtool/tools/tools/ in my local cvs.
>
> In case it's a mistake we have to ask SF maintainers to remove the obsolet
> directory.
> Mike can you pls point us to th
Hi;
it seems something went wrong with a cvs commit.
I now have buildtool/tools/ and buildtool/tools/tools/ in my local cvs.
In case it's a mistake we have to ask SF maintainers to remove the obsolet
directory.
Mike can you pls point us to the right direction?
thx kp
On Tue, 2010-04-06 at 22:08 +0200, Martin Hejl wrote:
> Hi Mike,
>
> > What assistance will help with 'buildtool' conversion from cvs to git?
> >
> > http://leaf.cvs.sourceforge.net/viewvc/leaf/src/bering-uclibc/buildtool/
-snip-
> If we still want the packages to be stored in the SCM system,
Ma
On Tue, 2010-04-06 at 22:08 +0200, Martin Hejl wrote:
-snip-
> > This task is the main thing holding up a move to git.
>
> Just out of curiosity - what features of git make it the SCM of choice
> for leaf? Seriously, all I know about it is that it is used to store the
> sources of the linux kerne
Hi Mike,
> What assistance will help with 'buildtool' conversion from cvs to git?
>
> http://leaf.cvs.sourceforge.net/viewvc/leaf/src/bering-uclibc/buildtool/
For starters, somebody who knows something about git (if that person was
also a perl hacker, even better. But the code should be commente
Martin,
What assistance will help with 'buildtool' conversion from cvs to git?
http://leaf.cvs.sourceforge.net/viewvc/leaf/src/bering-uclibc/buildtool/
Everyone,
This task is the main thing holding up a move to git.
--
Mike Noyes
http://sourceforge.net/users/mhnoyes/
SF.net Projects: leaf, so
Hi Martin
Martin Hejl wrote:
> Hi Erich,
>
> Erich Titl wrote:
>> Hi Martin
>>
>> I have defined a number of links in my buildtool.cfg file, like
>>
>>
>> Filename= usr/lib/cups
>> Type= link
>> Target = data/cups/usr/lib/cups
Hi Erich,
Erich Titl wrote:
> Hi Martin
>
> I have defined a number of links in my buildtool.cfg file, like
>
>
> Filename= usr/lib/cups
> Type= link
> Target = data/cups/usr/lib/cups
>
>
> Which suggests that the target di
Hi Martin
I have defined a number of links in my buildtool.cfg file, like
Filename= usr/lib/cups
Type= link
Target = data/cups/usr/lib/cups
after running buildpacket I get now the following in the .lrp file
luna > ls -lR da
Martin Hejl wrote:
>> Is it used to build
>> the package hash, and if so wouldn't that necessitate all files to be of
>> type 'list'?
> Nope - all files in the package are automatically added to ".list" - the
> keyword in buildtool.cfg is to add things like directories, wildcards or
> things tha
Hi Erich,
>>From this document it is not completely clear to me which files have to
> have the type 'list', because I don't know, what the .list file is
> actually used for now that we have the new configdb.
I don't think it is used for anything anymore (I don't see a single
buildtool.cfg file i
Hi Martin
Erich Titl wrote:
> Hi Martin
>
> Martin Hejl wrote:
>> Hi Erich,
>>
> ..
>
>> See
>> http://leaf.sourceforge.net/doc/bucd-buildpacket.html (without the
>> colon, I should have put a space between the URL and the colon - sorry
>> about that)
>From this document it is not completely cl
Hi Erich,
The problem on the shorewall site is solved now, the www.shorewall.net
link works correct again.
Cheers,
Eric
Op Zo, 9 juli, 2006 11:40 am schreef Erich Titl:
> Hi Eric
>
>
> Eric Spakman wrote:
>
>> Hi Erich,
>>
>>
>> I think it's a temporary problem on shorewall's main site. I will
>
Hi Erich,
I think it's a temporary problem on shorewall's main site. I will
keep an eye on it and change to an other site if the problem persist.
Thanks for reporting.
Eric
>Eric
>
>Eric Spakman wrote:
>> Hi Erich,
>>
>>> I will download the current 2.4.2 tonight and see how it runs on my
>>
Hi Erich,
>I will download the current 2.4.2 tonight and see how it runs on my
>environment.
>
Thanks!
Eric
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integr
Hi Erich,
>
> Thank you, I will fetch them probably tonight and have them run.
>
>
> I believe though, that after these modifications it is in the best
> interest to tag these files as 2.4.3 and release them accordingly, as
> _they_were_modified_
>
>
> What do you think?
>
The changes in buildtool
Hi everybody,
>
> some of you may have seen my odyssey getting a buildenv for uClibc up and
> running. With lots of help and patience by Eric Spakman I finally got the
> CVS HEAD to compile without barfing on my SuSE 9.2 .
>
> Now the 2.4.2 tagged release is not as gentle, as it still contains som
Hello
following up to my compile problems with wlan-ng in 2.4.2 I believe I
found the culprit for this version in linux-wlan-Configure.patch.gz
+# Debian mod: Allow CC to be specified to set the compiler.
+if [ -z "$CC" ]; then
+CC=gcc
+fi
+
+
dump_str 'HOST_AS=$(HOST_COMPILE)as'linux
Hello Erich,
I tought about the same, but the strange thing is that HOST_COMPILE is
empty with the latest commit and $CC points to the crosscompiler (the
2.4.2 tag should be set to current HEAD). But I will take a look at it
this evening.
Erc
> Hello
>
>
> following up to my compile problems wit
Hi everybody
some of you may have seen my odyssey getting a buildenv for uClibc up
and running. With lots of help and patience by Eric Spakman I finally
got the CVS HEAD to compile without barfing on my SuSE 9.2 .
Now the 2.4.2 tagged release is not as gentle, as it still contains some
of the
Hi Erich,
I will take a look at it, although I can't remember seeing this in my test...
Eric
> Eric
>
>
> some more information. Although wlan-ng appears to compile correctly, not
> all is well in config.mk
>
> CROSS_COMPILE=/data/leaf/bering-uclibc/devel/latest/src/bering-uclibc/bui
> ldtool/st
Hi Erich,
I just checked-in a slightly different version of wlan-ng's buildtool.mk,
this is more in line with other sources. Can you check this one to see if
it solves your problem?
Eric
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-in
Hi Erich,
> The problem is in the linux-wlan-ng-0.2.3 directory, where CC is
> redefined in config.mk
>
> luna > grep /usr/bin/cc * config.mk:HOST_CC=$(HOST_COMPILE)/usr/bin/cc
> config.mk:CC=/data/leaf/bering-uclibc/devel/latest/src/bering-uclibc/build
> tool/staging/usr/bin//usr/bin/cc
> config
Op Di, 4 juli, 2006 3:31 pm schreef Erich Titl:
> Eric
>
>
> feels like a never ending story, herre the latest from the HEAD checkout
>
>
> -D__LINUX_WLAN__ ../shared/p80211types.c ../shared/p80211metamsg.c
> ../shared/p80211metamib.c ../shared/p80211meta.c mkmetadef.c
> ../shared/p80211types.c
Hi Erich,
Don't know where that (double path)
/staging/usr/bin//usr/bin/cc:
comes from, doesn't do that on my host
Eric
> Eric
>
>
> feels like a never ending story, herre the latest from the HEAD checkout
>
> build source/package: wlan-ng
> calling 'make build' for
Eric
feels like a never ending story, herre the latest from the HEAD checkout
build source/package: wlan-ng
calling 'make build' for wlan-ng make build failed for
/data/leaf/bering-uclibc/devel/latest/src/bering-uclibc/buildtool/source/wlan-ng/buildtool.mk
, please hav
Hi Erich,
>> This is very well possible, I seem to remember that I fixed something
>> like this some time ago. Maybe after the 2.4.2 tag
>
> :-)
>
In indeed did: source.cfg Revision 1.112 in CVS
>
> Boooh another one in building kernel
>
>
> I have 2 builds running at the same time, one
Hi Erich,
>> Not entirely, some sources are broken upstream for crosscompiling and
>> expect the loader to be in /lib (hardcoded).
>
> ooops... OK, may I suggest to add this to the docs :-)
>
It already is in the docs ;-)
http://leaf.sourceforge.net/doc/bk07ch02s02.html
last alinea, the process is
Eric
Eric Spakman wrote:
> Hi Erich,
>
>>> Buildtool checks the link to the right uClibc loader when you start it
>>> (either 0.9.20 or 0.9.28), it's not possible to do two simultanious
>>> builds for two different environments. So don't ;))
>> But these are unrelated processes, with unrelated bu
Hi Erich,
>> Buildtool checks the link to the right uClibc loader when you start it
>> (either 0.9.20 or 0.9.28), it's not possible to do two simultanious
>> builds for two different environments. So don't ;))
>
> But these are unrelated processes, with unrelated buildtool perl
> sources, librarie
Eric Spakman wrote:
> Hi Erich,
>
>>> This is very well possible, I seem to remember that I fixed something
>>> like this some time ago. Maybe after the 2.4.2 tag
>> :-)
>>
> In indeed did: source.cfg Revision 1.112 in CVS
Would you mind to tag that?
>
...
>>
>> Is is possible, that the
Hi Eric
Eric Spakman wrote:
> Hi Erich,
>
>>> The directory "setserial" seems to be missing in the path below:
>>> /home/mega/leaf/bering-uclibc/devel/2.4.2/src/bering-uclibc/contrib/buil
>>> dtool.cfg
>> sure, I did not want to update this before I was certain, but the problem
>> appears to be i
Hi Erich,
>> The directory "setserial" seems to be missing in the path below:
>> /home/mega/leaf/bering-uclibc/devel/2.4.2/src/bering-uclibc/contrib/buil
>> dtool.cfg
>
> sure, I did not want to update this before I was certain, but the problem
> appears to be in a corrupted sources.cfg, where the
Hi Eric
Eric Spakman wrote:
> Hi Erich,
>
> Did you checkout the "contrib" section in CVS also?
>
> The directory "setserial" seems to be missing in the path below:
> /home/mega/leaf/bering-uclibc/devel/2.4.2/src/bering-uclibc/contrib/buildtool.cfg
sure, I did not want to update this before I
Hi Erich,
Did you checkout the "contrib" section in CVS also?
The directory "setserial" seems to be missing in the path below:
/home/mega/leaf/bering-uclibc/devel/2.4.2/src/bering-uclibc/contrib/buildtool.cfg
The setserial setup is an user added setup, so I can't say a lot about it.
Although wit
Hi Folks
according to KP's suggestion I focused on 2.4.2
- checking out from CVS was a breeze
I modified sources.cfg according to the doc
- building buildenv was a breeze
now the next command I entered to build everything
./buildtool.pl build
resulted in the following error
source/package:
Am Montag, 3. Juli 2006 11:09 schrieb Erich Titl:
> Hi Eric
>
> Eric Spakman wrote:
> > Hi Erich,
> >
> > I don't know enough of CVS to see what goes wrong. You can try a
> > fresh checkout of buildtool in a different directory.
>
> OK, last resort, this worked for the head target. :-)
>
> Now havi
Hi Eric
Eric Spakman wrote:
> Hi Erich,
>
> I don't know enough of CVS to see what goes wrong. You can try a
> fresh checkout of buildtool in a different directory.
>
OK, last resort, this worked for the head target. :-)
Now having a problem with ntpd on 2.4.1 I tried a new checkout of this
Hi Erich,
>Hmmm... why would I have to rebuild the buildenv? AFAIK Andreas Steffen
>has just added some functionality to the *swan, just like openswan. I
>will have to look a bit deeper.
>
To be somewhat clearer, I rebuilt buildenv not for gcc/uClibc itself
but more to be sure all the headers are
Hi Erich,
>Hmmm... why would I have to rebuild the buildenv? AFAIK Andreas Steffen
>has just added some functionality to the *swan, just like openswan. I
>will have to look a bit deeper.
>
You may need the strongswan kernel headers to properly build
strongswan. It's a bit subtle, you could go ahe
Hello Erich,
>> The setup of "linux" and "kernel" is unlike other packages split in two
>> different setups because the linux source/headers are needed for buildenv
>> and buildenv is needed for building the kernel.
>
>That is probably the part I am missing. What are the linux kernel
>sources need
Hello Erich,
>How are the dependencies handled by buildtool? Is this done by flag files?
>
In sources.cfg. If some source depends on an other source, it's
listed in sources.cfg as a dependency.
Eric
___
leaf-devel mailing list
leaf-devel@lists.sourc
Hello Erich,
>> This is the latest patch known to me and has support for ppp-2.4.2+
>
>What about the patches at http://mppe-mppc.alphacron.de/
AFAIK the MPPE part is the same and the MPPC part could give legal
problems if we package it.
Eric
___
l
Hi Eric
Eric Spakman wrote:
..
>
> The setup of "linux" and "kernel" is unlike other packages split in two
> different setups because the linux source/headers are needed for buildenv
> and buildenv is needed for building the kernel.
That is probably the part I am missing. What are the linux kern
Hi Martin
Martin Hejl wrote:
> Hi Erich,
>
...
>
> The thing you're stumbling over is probably that you're expecting the
> build to be re-done, because the config changed - which is not how
> buildtool works -
Correct
if you've built something and wand to rebuild it, you
> need to undo the "b
Hi Eric
Eric Spakman wrote:
> Hello Erich,
>> A few questions before I dig deeper in the Bering uClibc stuff
>>
>>
>> - after a ./buildtool.pl build kernel, where does the upx compressed
>> kernel image go? Is it
>>
>> $BUILDROOT/buildtool/source/linux/linux/arch/i386/boot/bzlinux
>>
> It goes to
Eric
Eric Spakman wrote:
> Hi Erich,
>
...
>>
> Note that unlike openswan, strongswan doesn't have a seperate patchset. So
> you need to patch the kernel with the strongswan source tools itself,
> build the buildenv and after that build strongswan.
Hmmm... why would I have to rebuild the builde
Hi Erich,
>>> - replace openswan with strongswan and still track current kernel
>>> development/configuration..
>> don't know about that one - the whole *swan integration into the kernel
>> is a bit obscure (due to the fact that the buildenv needs the kernel
>> sources, but to build a kernel, you
Hello Erich,
>
> A few questions before I dig deeper in the Bering uClibc stuff
>
>
> - after a ./buildtool.pl build kernel, where does the upx compressed
> kernel image go? Is it
>
> $BUILDROOT/buildtool/source/linux/linux/arch/i386/boot/bzlinux
>
It goes to $BUILDROOT/buildtool/build/kernel/
>
>
Hi Erich,
> I am not sure I understand completely.
>
> Example:
>
> I want to make a small modification in the kernel configuration. What
> directory will these changes be made in, as it is neither in apps nor
> contrib. Basically the sources reside in
>
> $BUILDROOT/source/linux/
>
> the mods
Hello Erich,
>
> I want to make a small modification in the kernel configuration. What
> directory will these changes be made in, as it is neither in apps nor
> contrib. Basically the sources reside in
>
> $BUILDROOT/source/linux/
>
>
> the mods are done using menuconfig, which will make a modified
Hi Martin
Martin Hejl wrote:
> Hi Erich,
>
>>> If you change the config, the safest way (I'm going from memory here, I
>>> didn't double-check this) would be to do
>>>
>>> $ ./buildtool.pl srcclean busybox
>>> $ ./buildtool.pl build busybox
>>
>> I am afraid this will erase my modifications.
> No
Hi Erich,
>>If you change the config, the safest way (I'm going from memory here, I
>>didn't double-check this) would be to do
>>
>>$ ./buildtool.pl srcclean busybox
>>$ ./buildtool.pl build busybox
>
>
> I am afraid this will erase my modifications.
No, it won't, unless you're making the modifi
Martin
Thank you , I really appreciate the time you are taking
Martin Hejl wrote:
> Hi Erich,
>
> sorry - I'm not around the computer much these days, so don't expect
> speedy responses from me for the next few weeks.
Don't worry, I am pretty sure there are others in the team who must know
the
Hi Erich,
sorry - I'm not around the computer much these days, so don't expect
speedy responses from me for the next few weeks.
> I found that in the corresponding apps/busybox, there is no unpacked
> busybox source. Will buildtool use such a source when it exists or just
> unpack the tar archive
Hi Folks
A few questions before I dig deeper in the Bering uClibc stuff
- after a ./buildtool.pl build kernel, where does the upx compressed
kernel image go? Is it
$BUILDROOT/buildtool/source/linux/linux/arch/i386/boot/bzlinux
I looked into the kernel patches
- what are the various netfilter m
Hi Martin
Martin Hejl wrote:
> Hi Erich,
>
>> I know you want to avoid branches in CVS. What is the canonical way to,
>> let's say
>>
>> - replace openswan with strongswan and still track current kernel
>> development/configuration..
> don't know about that one - the whole *swan integration into
Hi Erich,
> I know you want to avoid branches in CVS. What is the canonical way to,
> let's say
>
> - replace openswan with strongswan and still track current kernel
> development/configuration..
don't know about that one - the whole *swan integration into the kernel
is a bit obscure (due to the
Hi KP
Thanks for the quick reply
KP Kirchdoerfer wrote:
...
>>
>> I see that the release tag enables me to get a certain release level for
>> apps and contrib. I believe that even the buildenv changes with
>> releases. What is the canonical way to handle this?
>
> The buildenv doesn't change tha
Hi Erich;
Am Samstag, 17. Juni 2006 09:56 schrieb Erich Titl:
> Hi folks
>
> this weekend the weather forecast is not too good, so time for another
> try at the buildenv stuff
>
> A few questions pop up .
>
> I see that the release tag enables me to get a certain release level for
> apps and c
Hi folks
this weekend the weather forecast is not too good, so time for another
try at the buildenv stuff
A few questions pop up .
I see that the release tag enables me to get a certain release level for
apps and contrib. I believe that even the buildenv changes with
releases. What is the ca
Hi
Thanks everybody, I will try to be patient.
Erich
Eric Spakman schrieb:
Hello Erich,
The warnings are normal (AFAIK) and sourceforge is having problems, I'm
also not able to check out sources now.
Eric
---
This SF.net email is
Hello Erich,
The warnings are normal (AFAIK) and sourceforge is having problems, I'm
also not able to check out sources now.
Eric
> Hi Folks
>
>
> I started a new attempt at buildtool, still no luck. Here is the log...
>
>
> buildtool::Download::download:file key: buildtool.cfg
> Warning: wildca
Hi Folks
I started a new attempt at buildtool, still no luck. Here is the log...
buildtool::Download::download:file key: buildtool.cfg
Warning: wildcards not supported in HTTP.
--09:12:19--
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/leaf/src/bering-uclibc/apps/linux/buildtool.cfg
1 - 100 of 118 matches
Mail list logo
