All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michel Lanners <mlan@cpu.lu>
To: costabel@wanadoo.fr
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.2.2 compilation errors
Date: Sun, 28 Feb 1999 21:49:19 +0100 (CET)	[thread overview]
Message-ID: <199902282049.VAA06261@piglet.cpu.lu> (raw)
In-Reply-To: <36D685FD.1E07A1DE@wanadoo.fr>


Hi there,

On  26 Feb, this message from Martin Costabel echoed through cyberspace:
[concerning compile poblems with 2.2.2 re semaphores]
> 1) Downgrade. Take the 2 files kernel/ksyms.c and kernel/sched.c from a
> previous version. For your convenience, I have put them on my site
> http://www.maths.univ-rennes1.fr/~costabel/linux/boot/
> 
> 2) Upgrade. Take the 2 files include/asm-ppc/semaphore.h and
> include/asm-ppc/semaphore-helper.h from the cvs tree at samba.anu.edu.au
> (or take the whole tree; it contains many other bug fixes). On my Web
> site, I have a file kernel222-samba.diff that patches these 2 files. It
> is only 5kB, so this is the simplest way to go.

Hmmm... for me, this is not enough.

I get errors in drivers/scsi/scsi_error.c like this:

scsi_error.c: In function `scsi_error_handler':
scsi_error.c:1975: structure has no member named `owner'

The structure it complains about is struct semaphore, as defined in
include/asm/semaphore.h

Now, for PPC, we have a different (simpler) definition of struct
semaphore, lacking some of the members that i386 has. Obviously, these
members are referenced in drivers/scsi/scsi_error.c.

Any hints?

A quick look at your patch file will show it contains the same simpler
definition of struct semaphore.

Thanks

Michel

-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "


[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

  parent reply	other threads:[~1999-02-28 20:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-26  4:04 2.2.2-ac4 compilation errors satadru pramanik
1999-02-26  6:57 ` Hollis R Blanchard
1999-02-26 11:31 ` 2.2.2 " Martin Costabel
1999-02-26 15:18   ` satadru pramanik
1999-02-27  9:39     ` Martin Costabel
1999-02-27 17:39       ` satadru pramanik
1999-02-26 17:33   ` Gary Thomas
1999-02-26 18:18     ` Martin Costabel
1999-02-28 23:18       ` Paul Mackerras
1999-02-28 20:49   ` Michel Lanners [this message]
1999-02-28 21:45     ` Martin Costabel
1999-02-28 22:57     ` Paul Mackerras
1999-03-01 17:18     ` PowerCenterPro + L2 cache frank.pierce

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199902282049.VAA06261@piglet.cpu.lu \
    --to=mlan@cpu.lu \
    --cc=costabel@wanadoo.fr \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.