From: Steve French <smfrench@austin.rr.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] [Fwd: arch/um/sys-i386/bugs.c compile error]
Date: Sun, 16 Nov 2003 14:24:41 -0600 [thread overview]
Message-ID: <3FB7DD09.3050101@austin.rr.com> (raw)
This compile error shows up on my more recent SuSE systems due to
presumbably these sytems including the more current gcc (3.3.1). With
the deault UML config both 2.4 and 2.6 UML build fail on e.g. SuSE 9
Perhaps the compiler is stricter now - showing up a problem with the headers.
> I get the same arch/um/sys-i386/bugs.c compile error on 2.6.0-test9-1-um
> and 2.4.22-6-um. Anyone have an idea of what causes the error?
-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
_______________________________________________
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:[~2003-11-16 20:25 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=3FB7DD09.3050101@austin.rr.com \
--to=smfrench@austin.rr.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 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.