From: Dale Amon <amon@vnl.com>
To: Stephen Smalley <sds@tislabs.com>
Cc: John Scroggins <dataefx@earthlink.net>, selinux@tycho.nsa.gov
Subject: Re: Undefined refs in compile attempt
Date: Fri, 14 Dec 2001 01:32:03 +0000 [thread overview]
Message-ID: <20011214013203.GB16720@vnl.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0112120840590.6865-100000@raven>
Okay, I'm making progress. I thought I'd report in just in case
our friend writing the book wants to follow what I do.
First, I took the newest version as Dr. Smalley suggested and
applied his two patches. I also applied the patch from Andrew
Morton on LKML to try to fix the problem that has shown up
because of the new, more restrictive binutils.
That failed. I believe the problem might be that there are
occurences of the problem that are in the lsm patch or the
selinux patches as it has to do with module exit code I
believe.
My second choice was to backoff to an older binutils and
do the ld using that.
533 tar zxf 2001121010-SELINUX/lsm-selinux-2001121010.tgz
537 cd selinux/
538 patch -p1 < ../2001121010-SELINUX/util-linux.patch
545 cd ../lsm
547 patch -p1 < ../2001121010-SELINUX/AndrewMorton-exit.patch
550 cd ../selinux/module/
552 make insert
554 cd ../../lsm
555 patch -p1 < ../2001121010-SELINUX/module.patch
558 cp -a ../20011213-collective.config .config
559 make oldconfig
560 make menuconfig
Downgrade to binutils_2.11.92.0.7-2_i386.deb
562 make dep
564 make bzImage
565 make modules
Now since I am not building for this machine, I move everything
to a target "root" which I'll later tar up and copy over
to the test machine:
571 cp -a System.map ../Selinux/boot/System.map-2.4.16-lsm
572 cp -a arch/i386/boot/bzImage ../Selinux/boot/vmlinuz-2.4.16-lsm
574 make INSTALL_MOD_PATH=/usr/src/Selinux/ modules_install
Since selinux doesn't have this feature, I edited the makefile and
added it. After I'm done I'd be happy to supply any patchfiles I
create in the process.
577 cd ../selinux/module
Patch Makefile to have ROOT variable
587 make ROOT=/usr/src/Selinux/usr/local install
At this point I'm not yet clear whether I can
continue on the kernel factory or have to complete the
commands in the README over on the target machine. I'm
hoping not as it would be terribly awkward if I have to
move the source tree across just to finish.
So, I'm on to the next RTFM and RTFC step.
--
------------------------------------------------------
Nuke bin Laden: Dale Amon, CEO/MD
improve the global Islandone Society
gene pool. www.islandone.org
------------------------------------------------------
--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
prev parent reply other threads:[~2001-12-14 1:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-12 1:43 Undefined refs in compile attempt Dale Amon
2001-12-12 1:50 ` James Morris
2001-12-12 13:54 ` Stephen Smalley
2001-12-12 17:45 ` Dale Amon
2001-12-12 18:33 ` Stephen Smalley
2001-12-12 22:37 ` Admin help, Please Shaun Savage
2001-12-13 13:35 ` Stephen Smalley
2001-12-14 1:32 ` Dale Amon [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=20011214013203.GB16720@vnl.com \
--to=amon@vnl.com \
--cc=dataefx@earthlink.net \
--cc=sds@tislabs.com \
--cc=selinux@tycho.nsa.gov \
/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.