From: Javier Sedano <javier.sedano@agora-2000.com>
To: elks <linux-8086@vger.kernel.org>
Cc: Paul Nasrat <pauln@truemesh.com>, Riley Williams <Riley@Williams.Name>
Subject: Re: Error compiling
Date: Mon, 21 Jul 2003 17:19:07 +0200 [thread overview]
Message-ID: <3F1C046B.1030100@agora-2000.com> (raw)
In-Reply-To: 3F181870.3080002@agora-2000.com
Hi,
Javier Sedano wrote:
> Hi,
>
> I think the problem is related to the gcc version used in debian
> testing. The default gcc version is 3.3, but 2.95 is also installed.
> Forcing it to use 2.95 seems to compile (althoug it still does not boot)
>
Aha! So changing gcc to gcc-2.95 in Makefile-rules in the elks tree seems
to solve the compilation problem. It compiles... but does not run. I've
got what seems to be a dump of AX, BX, CX, DX registers, scrolling
quickly through the screen.
I am actually trying to run elks in vmware. The first step was to
download the Images.zip tarball and use it. It works... more or less ;-)
The comb image boots without problems, and I can even log in and play.
The boot/root image does not work; it causes the same error than my
home-compiled kernel.
So there seems to be any configuration option which makes elks not
runable under vmware. Does someone have a .config file for the boot
image and another one for the comb image, to look for the diference?
Any other idea?
Regards,
--
Javier Sedano Jarillo: javier.sedano@agora-2000.com
(http://www.it.uc3m.es/~jsedano)
Network&Systems Engineer
Agora Systems, S.A.
C/Aravaca 12
E-28040 Madrid (Spain)
Tel.: +34 91 533 58 57
Fax.: +34 91 534 84 77
--------
Any sufficiently advanced technology is indistinguishable from magic.
Arthur C. Clarke
next prev parent reply other threads:[~2003-07-21 15:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 18:20 Error compiling Javier Sedano
2003-07-17 21:42 ` Riley Williams
2003-07-18 12:04 ` Javier Sedano
2003-07-18 13:22 ` Paul Nasrat
2003-07-18 15:55 ` Javier Sedano
2003-07-21 15:19 ` Javier Sedano [this message]
2003-07-22 10:16 ` Johannes Lundberg
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=3F1C046B.1030100@agora-2000.com \
--to=javier.sedano@agora-2000.com \
--cc=Riley@Williams.Name \
--cc=linux-8086@vger.kernel.org \
--cc=pauln@truemesh.com \
/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