public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Orr <markorr@intersurf.com>
To: Steven Cole <elenstev@mesatop.com>
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.0-ac9 (shmem.c errors)
Date: Sat, 13 Jan 2001 20:33:19 -0600 (CST)	[thread overview]
Message-ID: <XFMail.20010113203319.markorr@intersurf.com> (raw)
In-Reply-To: <01011318404000.18233@localhost.localdomain>


On 14-Jan-2001 Steven Cole wrote:
> I got the following error while building 2.4.0-ac9:
> 
> shmem.c:971: `shmem_readlink' undeclared here (not in a function)
> shmem.c:971: initializer element is not constant
> shmem.c:971: (near initialization for 
> `shmem_symlink_inode_operations.readlink')
> shmem.c:972: `shmem_follow_link' undeclared here (not in a function)
> shmem.c:972: initializer element is not constant
> shmem.c:972: (near initialization for 
> `shmem_symlink_inode_operations.follow_link')
> shmem.c:973: initializer element is not constant
> shmem.c:973: (near initialization for `shmem_symlink_inode_operations')
> shmem.c:973: initializer element is not constant
> shmem.c:973: (near initialization for `shmem_symlink_inode_operations')
> make[2]: *** [shmem.o] Error 1
> 
> It looks like changes were recently made to linux/mm/shmem.c.

I'm getting the same errors here.  Christoph Rohland submitted
a series of shm patches to the list -- I tried --dry-run reapplying
them and at least a couple of them partially applied.  Looks like
it didnt all get integrated.

--
Mark Orr
markorr@intersurf.com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-14  2:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-14  1:40 Linux 2.4.0-ac9 Steven Cole
2001-01-14  2:33 ` Mark Orr [this message]
2001-01-14  3:05 ` Karsten Hopp
2001-01-14  3:47   ` Steven Cole
2001-01-14  9:56     ` Christoph Rohland

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=XFMail.20010113203319.markorr@intersurf.com \
    --to=markorr@intersurf.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=elenstev@mesatop.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox