Well the 2.4.19pre7 won't compile past the ioctl32 section.  I'll just
wait until the sparc maintainers release a kernel that works properly.
The patch below won't patch either the binfmt_elf.c file with 2.4.18 or
2.4.19pre7 source.  Thanks for the information though, I was under the
impression that a relased kernel would at least compile on the platforms
contained in the source without modification from SuSE.

On Tue, 23 Apr
2002, Joshua Uziel wrote:

> Date: Tue, 23 Apr 2002 23:52:24 -0700
> From: Joshua Uziel <[EMAIL PROTECTED]>
> To: Thorsten Kukuk <[EMAIL PROTECTED]>
> Cc: Suse Mail List <[EMAIL PROTECTED]>
> Subject: Re: [suse-sparc] LVM problems with newer kernel...
>
> * Thorsten Kukuk <[EMAIL PROTECTED]> [020423 22:23]:
> > For 2.4.18, some patches are missing for SPARC. Try a 2.4.19preX, but
> > don't ask me which of them works.
>
> For 2.4.18 on sparc64, you pretty much want the patch at
>
> 
>http://linux.bkbits.net:[EMAIL PROTECTED]?nav=index.html|src/|src/fs|hist/fs/binfmt_elf.c
>
> --- 1.18/fs/binfmt_elf.c        Mon Feb 25 03:46:20 2002
> +++ 1.19/fs/binfmt_elf.c        Mon Feb 25 11:41:00 2002
> @@ -564,6 +564,9 @@
>                         // printk(KERN_WARNING "ELF: Ambiguous type,
>                         // using ELF\n");
>                         interpreter_type = INTERPRETER_ELF;
>                 }
> +       } else {
> +               /* Executables without an interpreter also need a personality  */
> +               SET_PERSONALITY(elf_ex, ibcs2_interpreter);
>         }
>
>         /* OK, we are done with that, now set up the arg stuff,
>
> (Pasted from my web browser, so it probably won't apply cleanly.)
>
> For sparc32, you want 2.4.19-pre7 (which is the latest) or later...
> 2.4.18 with the above patch and any 2.4.19-preX should be fine on
> sparc64...
>
>
> --
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>

Ah say, son, you're about as sharp as a bowlin' ball.


-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to