linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Martin Costabel <costabel@wanadoo.fr>
To: satadru pramanik <satadru@umich.edu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: compilation failure of 2.2 series cvs kernel sources
Date: Wed, 02 Jun 1999 21:58:00 +0200	[thread overview]
Message-ID: <37558CC8.A5025227@wanadoo.fr> (raw)
In-Reply-To: Pine.LNX.4.10.9906021228590.15449-100000@beer.pub.umich.edu


satadru pramanik wrote:
> 
> yes. I did upgrade glibc recently. ;-)
> 
> However, the symlink is still the same.   Do I need to change it?  And
> wouldn't doing a cvs update change the scsi.h file "back"?  Or is that the
> problem?

I don't really know what happens in this case, but it shouldn't be hard
to find out what version of include/scsi/scsi.h (and sg.h, which sits in
the same boat) you have: "cvs status include/scsi/scsi.h".
BTW, cvs log tells me that TYPE_ENCLOSURE came into scsi.h on February
9, version 1.10.

--
Martin

[[ 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. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

      reply	other threads:[~1999-06-02 19:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-02  4:17 compilation failure of 2.2 series cvs kernel sources Satadru Pramanik
1999-06-02  6:54 ` Martin Costabel
1999-06-02 16:30   ` satadru pramanik
1999-06-02 19:58     ` Martin Costabel [this message]

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=37558CC8.A5025227@wanadoo.fr \
    --to=costabel@wanadoo.fr \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=satadru@umich.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).