public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Richard Moser <nigelenki@comcast.net>
To: linux-kernel@vger.kernel.org
Subject: undefined references
Date: Mon, 24 Jan 2005 19:04:53 -0500	[thread overview]
Message-ID: <41F58D25.1000203@comcast.net> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

icebox linux-2.6.10-grs # make
  CHK     include/linux/version.h
make[1]: `arch/x86_64/kernel/asm-offsets.s' is up to date.
  CHK     include/linux/compile.h
  CHK     usr/initramfs_list
  GEN     .version
  CHK     include/linux/compile.h
  UPD     include/linux/compile.h
  CC      init/version.o
  LD      init/built-in.o
  LD      .tmp_vmlinux1
fs/built-in.o(.text+0xe413): In function `link_path_walk':
: undefined reference to `gr_inode_follow_link'
fs/built-in.o(.text+0xe933): In function `link_path_walk':
: undefined reference to `gr_inode_follow_link'
fs/built-in.o(.text+0x10c28): In function `sys_link':
: undefined reference to `gr_inode_hardlink'
fs/built-in.o(.text+0x10c52): In function `sys_link':
: undefined reference to `gr_inode_handle_create'
make: *** [.tmp_vmlinux1] Error 1

What would cause this kind of error?

I'm messing with reimplementing LSM from scratch and have a patch for
what I'm doing if anyone wants to communicate on this; it's pretty much
an academic endeavor (learn to code in the kernel, learn how lsm was
created, learn how GrSecurity's codebase works).
- --
All content of all messages exchanged herein are left in the
Public Domain, unless otherwise explicitly stated.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB9Y0lhDd4aOud5P8RAmGxAJ9XZESD1nHO7mEIA7Bw0YCC/ns3KACfSgLF
4XRkAjHoayXprZR1Ma/0doI=
=LqFc
-----END PGP SIGNATURE-----

             reply	other threads:[~2005-01-25  0:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-25  0:04 John Richard Moser [this message]
2005-01-25  2:04 ` undefined references Valdis.Kletnieks
2005-01-25  4:15   ` John Richard Moser

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=41F58D25.1000203@comcast.net \
    --to=nigelenki@comcast.net \
    --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