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 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
24 matches
Mail list logo
