Hello from Gregg C Levine First off all, thank you for the BK advice. That was what I was missing. I actually didn't think that the clone command applied to everything that BK is used for, just for themselves. (Don't ask why!)
However, the next question is which version of the library are you using? I chose the most recent, and before that: I chose version 0.198 as well, but it is failing with the included headers from the Linux kernel, I'll post a copy of the script blurb here: strip --strip-all -R .comment -R .note shared/ipconfig ar cru libipconfig.a main.o netdev.o packet.o bootp_proto.o dhcp_proto.o make[1]: Leaving directory `/usr/src/klibc-0.198/ipconfig' make[1]: Entering directory `/usr/src/klibc-0.198/nfsmount' gcc -Wp,-MD,./.main.o.d -mregparm=3 -DREGPARM=3 -march=i386 -Os -g -falign-functions=0 -falign-jumps=0 -falign-loops=0 -nostdinc -iwithprefix include -D__KLIBC__ -DBITSIZE=32 -I../include/arch/i386 -I../include/bits32 -I../include -I../linux/include -I../linux/include2 -I../linux/include -Wstrict-prototypes -Wall -I. -c -o main.o main.c In file included from main.c:16: ../linux/include/linux/nfs_mount.h:26: error: field `old_root' has incomplete type ../linux/include/linux/nfs_mount.h:40: error: field `root' has incomplete type make[1]: *** [main.o] Error 1 make[1]: Leaving directory `/usr/src/klibc-0.198/nfsmount' make: *** [all] Error 2
Ironically the release before that one, 0.190 gets through everything, but crashes to a halt inside the ash directory. And 0.181 builds the library, but complains about some trivial data, or a trivial error.
Whereas the currently stable release 1.0 gets all of the way through building stuff until it reaches this point: cp -f shared/ipconfig shared.g strip --strip-all -R .comment -R .note shared/ipconfig ar cru libipconfig.a main.o netdev.o packet.o bootp_proto.o dhcp_proto.o make[1]: Leaving directory `/usr/src/klibc-1.0/ipconfig' make[1]: Entering directory `/usr/src/klibc-1.0/nfsmount' gcc -Wp,-MD,./.main.o.d -march=i386 -Os -g -fomit-frame-pointer -falign-functions=0 -falign-jumps=0 -falign-loops=0 -m32 -nostdinc -iwithprefix include -D__KLIBC__ -I../include/arch/i386 -I../include/bits32 -I../include -I../linux/include -I../linux/include2 -I../linux/include -mregparm=3 -D_REGPARM=3 -Wstrict-prototypes -Wall -I. -c -o main.o main.c In file included from main.c:16: ../linux/include/linux/nfs_mount.h:26: error: field `old_root' has incomplete type ../linux/include/linux/nfs_mount.h:40: error: field `root' has incomplete type make[1]: *** [main.o] Error 1 make[1]: Leaving directory `/usr/src/klibc-1.0/nfsmount' make: *** [all] Error 2
----- All of this is being built using the tools with Slackware-10.1, binary utilities are at 2..19 and the gcc release version 3.3.4. Also the kernel is at 2.4.29.
If you would like to know why I chose the Slackware distribution, it's because I have found that one to be relatively easy to use for setting up new systems, including work stations, and servers.
What is strange is why the two versions have the exactly the same errors. Do you think I should send those two complaints to the list which covers the activities of the library? ------------------- Gregg C Levine hansolofalcon@worldnet.att.net ------------------------------------------------------------ "The Force will be with you...Always." Obi-Wan Kenobi "Use the Force, Luke." Obi-Wan Kenobi
-----Original Message----- From: Jon Smirl [mailto:jonsmirl@gmail.com] Sent: Saturday, March 26, 2005 8:16 PM To: Gregg C Levine Cc: linuxbios@openbios.org Subject: Re: [LinuxBIOS] New version of ROM posting app
On Sat, 26 Mar 2005 20:03:40 -0500, Gregg C Levine hansolofalcon@worldnet.att.net wrote:
Hello from Gregg C Levine While I appreciate the offer of the application, as I am eager to
test
nearly everything new for the primary Linux BIOS project, I have
one
or two questions.
Question One, Is this the same emu86, that is a project on
BerliOS?
It's at http://emu86.berlios.de Also where is this vm86 available?
It is the emu86 that is contained in the linusbios project. linuxbios/src/devices/emulator
There are about 100 variations on emu86 floating around.
Question Two, I have bitkeeper installed, and it can reach itself, that is the company's site. But how can I retrieve the code stored
at
bk://mesa3d.bkbits.net/rom? I try feeding the string to bk
command,
and I get an odd command back.
bk clone bk://mesa3d.bkbits.net/rom target_dir
Has anyone on the list used bitkeeper before, other then yourself?
I
am afraid I am more use to CVS, then BK.
The Linux kernel is developed using bitkeeper. Instead of copying kernel images from kernel.org you can use this to keep up to date
with
the latest changes.
bk clone bk://linux.bkbits.net/linux-2.5 target_dir
After you have the initial tree down, to get updates cd target_dir bk pull
You can get bitkeeper here: http://www.bitkeeper.com/Products.BK_Pro.Downloads.html It is a free download.
-- Jon Smirl jonsmirl@gmail.com