From: Allen Chan <alydar@users.sourceforge.net>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Latest 2.6.7 incremental patches
Date: Fri, 13 Aug 2004 12:13:16 -0400 [thread overview]
Message-ID: <200408131213.16558.alydar@users.sourceforge.net> (raw)
There is a slight problem with the patch named
dont-need-no-steenking-linker-script. The original
arch/um/kernel/vmlinux.lds.S file is only 11 lines long with all the
substance coming from an include statement. The patch is assuming a
much larger file without the include statement.
If I zero out the arch/um/kernel/vmlinux.lds.S file manually, the
compile goes fine and the resulting kernel appears to be working fine
(so far).
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
reply other threads:[~2004-08-13 16:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200408131213.16558.alydar@users.sourceforge.net \
--to=alydar@users.sourceforge.net \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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