Re: Failed compilation on RedHat 7.0

2000-10-31 Thread Adam Huffman
On Tue, 31 Oct 2000, OKUJI Yoshinori wrote: From: Adam Huffman [EMAIL PROTECTED] Subject: Failed compilation on RedHat 7.0 Date: Sun, 29 Oct 2000 13:49:42 + This is with RedHat's gcc-2.96-54 and glibc 2.1.94-3 First of all, don't use gcc-2.96. GCC 2.96 is never released. See the

New FS driver (and support for a new OS).

2000-10-31 Thread Kurt Skauen
Hi, all. I have ported GRUB to the AtheOS operating system http://www.atheos.cx/ (or was it the other way around? I'm not sure :) and written a GRUB filesystem driver for the native AtheOS filesystem. I also modified the kernel to make it MultiBoot compliant and everything works nicely. I can

Re: Failed compilation on RedHat 7.0

2000-10-31 Thread andrew.markebo
This seems to be due to that the configure script thinks that no ncurses are installed, I got it to work by editing the config.cache-file and replacing the 'no' a 'yes' on the lines regarding ncurses. I don't know why configure doesn't think I have ncurses, checking the config.log file the tests

Re: Failed compilation on RedHat 7.0

2000-10-31 Thread OKUJI Yoshinori
Don't paraphrase the result. Send config.log instead of interpretting it yourself. Okuji ___ Bug-grub mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-grub

Re: EZ-BIOS support

2000-10-31 Thread OKUJI Yoshinori
From: "Jochen Hoenicke" [EMAIL PROTECTED] Subject: Re: EZ-BIOS support Date: Tue, 31 Oct 2000 11:38:10 +0100 (MET) Is it enough if grub just refuses to access a disk where it can see the ez-bios partition in the MBR (which means that ez-bios wasn't loaded) or should grub do the mapping itself

Re: New FS driver (and support for a new OS).

2000-10-31 Thread OKUJI Yoshinori
From: Kurt Skauen [EMAIL PROTECTED] Subject: New FS driver (and support for a new OS). Date: 31 Oct 2000 10:48:30 +0100 Hi, all. I have ported GRUB to the AtheOS operating system http://www.atheos.cx/ (or was it the other way around? I'm not sure :) and written a GRUB filesystem driver for

Internal ZIP bug, more command, dynamic memory

2000-10-31 Thread Volker Augustin
Am Tue, 31 Oct 2000 schrieb OKUJI Yoshinori: About asm.diff: Your code doesn't work correctly, because prot_to_real and real_to_prot destroy the value of %ebp (see the comments!). So your code just trys to read data from a bogus drive. About cat.diff: I don't like such an ad hoc way. Why

Re: Internal ZIP bug, more command, dynamic memory

2000-10-31 Thread OKUJI Yoshinori
From: Volker Augustin [EMAIL PROTECTED] Subject: Internal ZIP bug, "more" command, dynamic memory Date: Tue, 31 Oct 2000 13:03:33 +0100 Internal ZIP bug: Yes, I figured that deficiency in the code in asm.diff myself. Do you have any other ideas how to get an internal zip drive to work?

Re: New FS driver (and support for a new OS).

2000-10-31 Thread Kurt Skauen
Johan Rydberg [EMAIL PROTECTED] writes: Kurt Skauen wrote: I'm also wondering if the filesystem driver must follow the GNU coding style? It should. So I have to rewrite it? Anybody who know about a portable code-obfuscator? :) Well, Why not use Emacs c-mode and

Re: New FS driver (and support for a new OS).

2000-10-31 Thread Jochen Hoenicke
On Oct 31, Kurt Skauen wrote: The only solution I found to this (other than hacking the linker-scripts) was to strip away the offending sections with the "-R" option to objcopy. The resulting makfile rule: %: %.exec $(OBJCOPY) -O binary -R .hash -R .dynsym -R .dynstr -R .rel.text

Re: Failed compilation on RedHat 7.0

2000-10-31 Thread Mathieu ChouquetStringer
I got the same result few weeks ago (remember ??). The problem is gcc 2.96 : it reports errors when it compiles the test file for the curses. One solution : export CC=kgcc ./configure On Tue, Oct 31, 2000 at 08:08:21PM +0900, OKUJI Yoshinori wrote: Don't paraphrase the result. Send

Redhat configuration.

2000-10-31 Thread Andrew Markebo
Now when me and my linux machine is closer, here comes the config.log from a redhat 7 system and grub 0.5.96.1. The problem is that configure doesn't think that ncurses exist on my machine. doing gcc -c test.c works fine, with test.c is: #include ncurses/curses.h works fine, no errs. /Andy

Re: Redhat configuration.

2000-10-31 Thread Mathieu ChouquetStringer
On Tue, Oct 31, 2000 at 06:20:30PM +0100, Andrew Markebo wrote: doing gcc -c test.c works fine, with test.c is: #include ncurses/curses.h works fine, no errs. Compiles, runs but gives you warnings... configure:2355: checking for curses.h configure:2366: gcc -E -Wall -Wmissing-prototypes

Re: New FS driver (and support for a new OS).

2000-10-31 Thread Gordon Matzigkeit
Kurt Skauen writes: The FSF needs to hold the copyright for their projects. This ensures that the FSF has the legal right to distribute the package, and the right to defend its free status in court if necessary. KS Ok. I will wait for Gordon to come with the description then. Here I

Kernel section info.

2000-10-31 Thread Kurt Skauen
How do I get information about the kernel image after the kernel is booted? I tried to read the symbol information in the boot info structure passed to the kernel, but the MB_INFO_ELF_SHDR flag is never set, and as far as I can see the section info is never initialized in GRUB. How am I supposed

Re: Antw: HELP! GRUB wiped out my first hard drive's partition table!

2000-10-31 Thread Harmon S. Nine
Just one more thing ... Is it at all possible to use a stage1_5 along with EZ-bios? TIA -- Harmon ___ Bug-grub mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-grub

Re: Redhat configuration.

2000-10-31 Thread OKUJI Yoshinori
From: "Andrew Markebo" [EMAIL PROTECTED] Subject: Redhat configuration. Date: Tue, 31 Oct 2000 18:20:30 +0100 Now when me and my linux machine is closer, here comes the config.log from a redhat 7 system and grub 0.5.96.1. The problem is that configure doesn't think that ncurses exist on my

Re: Kernel section info.

2000-10-31 Thread OKUJI Yoshinori
From: Kurt Skauen [EMAIL PROTECTED] Subject: Kernel section info. Date: 31 Oct 2000 19:50:57 +0100 How do I get information about the kernel image after the kernel is booted? I tried to read the symbol information in the boot info structure passed to the kernel, but the MB_INFO_ELF_SHDR flag