Hi Erich, Eric, and all Bering-users,
most Bering-users would not like to spend time on
the following "bug/deviation report".
I removed the previous message to lessen the burden
and will here comment on 'buildtoollog' and otherwise
on my preparations, so that my fault or any other
shortcoming may benefit others.
The only thing remotely related to C-compiling that
happened on my laptop between this morning and the
experiments with the funcional buildtool.pl last
week, was that I built dietlibc and tucked it away
in a remote spot. This should mean no harm.
After the failure with buildtool before noon, I
removed the old directory src/ in order to erase
every trace of the environment. I even removed
the symbolic link /lib/ld-uClibc.so.0 to certify
that no disturbance should take place.
There followed an anonymous checkout of buildtool
from the cvs-tree, and I added the logout that is
not mentioned in the Bering-uClibc documentation.
My only deviation from the documentation recipe
was neglect to issue "export CVS_RSH=ssh", which
ought to be harmless for anonymous access.
When firing of
buildtool.pl build buildenv
there was the expected prayer to kindly be allowed
to create the symbolic link /lib/ld-uClibc.so.0
and which I gladly accepted.
I have tracked the messages in buildtoollog:
a) a number of fairly standard warnings concering
mixed variable typing, bad choice of 'mktemp'
and so on,
b) after patching uClibc, make complains almost
immediately that staging/bin/i386-linux-gcc
does not exist four times,
c) a substantial while later calamity arise:
make has entered buildenv/gcc-3.3.3-final/gcc
after leaving .../libiberty. The host gcc has
succeeded in compiling gengenrtl.o, but then
fails in building executable gengenrtl and says
gcc -g -O2 -DIN_GCC -W -Wall -Wwrite-strings
-Wstrict-prototypes -Wmissing-prototypes
-Wtraditional -pedantic -Wno-long-long
-DHAVE_CONFIG_H -DGENERATOR_FILE -o gengenrtl
gengenrtl.o ../libiberty/libiberty.a
./gengenrtl -h > tmp-genrtl.h
/bin/sh: line 1: ./gengenrtl: No such file or
directory
make[2]: *** [s-genrtl] Error 127
There buildtool.pl inhibits further actions
after a clean bailout.
d) The next try proceeded equally far but ended
with
./gengenrtl: can't load library 'libc.so.0'
make[2]: *** [s-genrtl] Error 16
e) Then I added a softlink
ln -s <longpath>/staging/libuClibc-0.9.28.so
/lib/libc.so.0
The building of buildenv proceeded well
including
the contruction of genattrtab, but came then to
a halt with
./genattrtab <longpath>/gcc-3.3.3/gcc/config/\
i386/i386.md > tmp-attrtab.c
./genattrtab: can't load library 'libm.so.0'
make[2]: *** [s-attrtab] Error 16
f) As my next action a made a soft link
ln -s <longpath>/staging/libm-0.9.28.so
/lib/libm.so.0
Then the build of buildenv went well and
the following build of the kernel and ralink
seems to have put every file where it belongs.
The log file is large, but source and
destination directories do make sense.
At present I cannot make much more sense of the
build log file, but tell me what to search for
and I will try to find it.
Regards
Mats E A
_________________________________________________________
Flyger tiden iväg? Fånga dagen med Yahoo! Mails inbyggda
kalender. Dessutom 250 MB gratis, virusscanning och antispam. Få den på:
http://se.mail.yahoo.com
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/
