From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Frank Laub <fried@franklaub.com>
Subject: [uml-devel] FAQ: problems with 2.4.22-4um and answers
Date: Sat, 20 Sep 2003 18:08:24 +0200 [thread overview]
Message-ID: <200309201808.24547.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <00af01c37d5f$65ac1f50$6059a043@clicktosecure.com>
There are two known frequent problems, already known, causing 2.4.22-4um(and
possibly patches based on it) to fail compilation:
- First, when you configure the uml, you must activate this option:
"Anonymous memory device"
or UML won't compile. So, activate it. By default it's off. Clear?
- if you instead see such messages:
/usr/src/uml-2.4.22-4um/arch/um/include/os.h:41: warning: no semicolon at
end of struct or union
it's for a known bug showing up on some systems(depends on changes in system
headers from glibc, showing up for instance on my Mdk9.1) which is already
being fixed. For now wait next patch or use 2.4.22-3um.
The problem that you, Frank Laub, had(I'm also answering to you) it's the
second one. By the way, what are your distro and glibc versions?
I'm posting this message because there are already enough people asking for
this problems.
--
cat <<EOSIGN
Paolo Giarrusso, aka Blaisorblade
Linux Kernel 2.4.21/2.6.0-test on an i686; Linux registered user n. 292729
EOSIGN
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2003-09-20 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-17 20:57 [uml-devel] Compiling 2.4.22-4um Frank Laub
2003-09-20 16:08 ` BlaisorBlade [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=200309201808.24547.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=fried@franklaub.com \
--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