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 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 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 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,
> 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 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,
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
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,
>>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
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
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 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,
>
> 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,
>>> - 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
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 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
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:
..
>
> 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
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
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,
>> 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
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
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
23 matches
Mail list logo
