All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Riley Williams" <Riley@Williams.Name>
To: Javier Sedano <javier.sedano@agora-2000.com>,
	elks <linux-8086@vger.kernel.org>
Subject: RE: Error compiling
Date: Thu, 17 Jul 2003 22:42:24 +0100	[thread overview]
Message-ID: <BKEGKPICNAKILKJKMHCAEEPCEOAA.Riley@Williams.Name> (raw)
In-Reply-To: <3F16E90B.1090407@agora-2000.com>

Hi Javier.

 * Nothing as pretty as a smile, nothing as ugly as a frown.

 > After a few months forgetting about elks, I'm trying to install
 > it again. I've got two questions:
 >
 > 1) The latest version available in the web page is 0.1.1, but
 >    this mailing list speaks of other newer versions... aren't
 >    they packtized?

Not yet, but 0.1.3-pre1 shortly will be. The releases on the ELKS
website can easily lag behind those being used since those with the
abilities to create releases are also the busiest of the developers.
The best way to obtain the current code is using CVS with commands
like the following...

    export CVS_RSH=`which ssh`
    CVSROOT=:pserver:anonymous@cvs.elks.sf.net:/cvsroot/elks
    cvs -d $CVSROOT get elks elkscmd elksnet elksutils

...which will download the current code base for all four packages,
and will drop it under the current directory.

 > 2) Version 0.1.1 gives me the next error:
 >
 > jsedano@taran:~/elks/elks-0.1.1> make Image
 >   Q> #define UTS_VERSION "#0.1.1?Thu Jul 17 20:14:02 CEST 2003"

=====8<===== CUT =====>8=====

 > bcc -0 -i -O -I/home/jsedano/elks/elks-0.1.1/include \
 >        -DELKS_VERSION_CODE=0x00010100 -DUTS_RELEASE=\"0.1.1\" \
 >        -D__KERNEL__ -ansi -c -o init/main.o init/main.c
 > make -C arch/i86 Image
 > make[1]: Entering directory `/home/jsedano/elks/elks-0.1.1/arch/i86'

=====8<===== CUT =====>8=====

 > gcc -E -traditional -I/home/jsedano/elks/elks-0.1.1/include \
 >        -DELKS_VERSION_CODE=0x00010100 -DUTS_RELEASE=\"0.1.1\" \
 >        -D__KERNEL__ -o boot/bootsect.s boot/bootsect.S
 > as86 -0  -o boot/bootsect.o boot/bootsect.s
 > ld86 -0  -s -o boot/bootsect -M boot/bootsect.o > Boot.map
 > gcc -E -traditional -I/home/jsedano/elks/elks-0.1.1/include \
 >        -DELKS_VERSION_CODE=0x00010100 -DUTS_RELEASE=\"0.1.1\" \
 >        -D__KERNEL__ -o boot/setup.s boot/setup.S
 > boot/setup.S:588: macro names must be identifiers
 > make[1]: *** [boot/setup.s] Error 1
 > make[1]: Leaving directory `/home/jsedano/elks/elks-0.1.1/arch/i86'
 > make: *** [Image] Error 2
 > jsedano@taran:~/elks/elks-0.1.1>

I'm not sure what that bug was, but it doesn't appear to be present
in the current CVS version which is 0.1.3-pre1 so has presumably been
fixed in the meantime.

Best wishes from Riley.
---
 * Nothing as pretty as a smile, nothing as ugly as a frown.

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.501 / Virus Database: 299 - Release Date: 14-Jul-2003


  reply	other threads:[~2003-07-17 21:42 UTC|newest]

Thread overview: 8+ 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 [this message]
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
2003-07-22 10:16         ` Johannes Lundberg
2003-10-09  9:24 error compiling Michal Semler (volny.cz)

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=BKEGKPICNAKILKJKMHCAEEPCEOAA.Riley@Williams.Name \
    --to=riley@williams.name \
    --cc=javier.sedano@agora-2000.com \
    --cc=linux-8086@vger.kernel.org \
    /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.