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
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 with a
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 was
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 setserial
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 in a corrupted
Hello Paul,
I fully agree, but unfortuanatly I can't do anything about it.
I hope Mike can give the status of PDF (and/or HTML) generation.
Eric
-- Eric Spakman [EMAIL PROTECTED] wrote:
Hello Paul,
AFAIK pdf generation is still not ready... But you can checkout the XML
document
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 link to the
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, libraries and
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 buildtool perl
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
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
snip
I have 2 builds running at the same time, one 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
On Tue, 4 Jul 2006 11:24:37 +0200 (CEST) Eric Spakman
[EMAIL PROTECTED] writes:
I fully agree, but unfortuanatly I can't do anything about it.
XML Parsing Error: not well-formed
Location:
file:///home/paul/dl/Computing/SW/Linux/Bering-uClibc/book.xml
Line Number 53, Column 148:div
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
snip
-D__LINUX_WLAN__ ../shared/p80211types.c ../shared/p80211metamsg.c
../shared/p80211metamib.c ../shared/p80211meta.c mkmetadef.c
../shared/p80211types.c
On Tue, 2006-07-04 at 08:17, Paul G Rogers wrote:
On Tue, 4 Jul 2006 11:24:37 +0200 (CEST) Eric Spakman
[EMAIL PROTECTED] writes:
I fully agree, but unfortuanatly I can't do anything about it.
XML Parsing Error: not well-formed
Location:
On Tue, 2006-07-04 at 02:24, Eric Spakman wrote:
I fully agree, but unfortuanatly I can't do anything about it.
Eric,
You're free to use FOP, and place the result in our FRS on SF.
I hope Mike can give the status of PDF (and/or HTML) generation.
PDF generation is on my to-do list.
Hi Erich,
snip
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
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
18 matches
Mail list logo
