public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Nasrat <pauln@truemesh.com>
To: Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: Uncompilable....
Date: Thu, 6 Jun 2002 11:56:31 +0100	[thread overview]
Message-ID: <20020606105631.GB5854@raq465.uk2net.com> (raw)
In-Reply-To: <1023363550.2443.35.camel@irongate.swansea.linux.org.uk>

On Thu, Jun 06, 2002 at 12:39:10PM +0100, Alan Cox wrote:
> On Thu, 2002-06-06 at 10:30, Harry Kalogirou wrote:
> > bcc -0  -i -O -I/home/harkal/cvs/elks/include
> > -DELKS_VERSION_CODE=0x00010002 -DUTS_RELEASE=\"0.1.1-pre2\" -D__KERNEL__
> > -ansi -c -o version.o version.c
> > version.c:10.48: error: string longer than dimension
> > make[2]: *** [version.o] Error 1
> > make[2]: Leaving directory `/home/harkal/cvs/elks/kernel'
> > make[1]: *** [kernel/kernel.a] Error 2
> > make[1]: Leaving directory `/home/harkal/cvs/elks'
> > make: *** [elks] Error 2
> 
> I compiled it about 5 minutes ago -and it built fine ?

Hmm broken in a different way here, I just slurped the cvs and did a
default .config

(cd ../.. ; ld86 -0 -i   \
	arch/i86/boot/crt0.o arch/i86/boot/crt1.o \
	init/main.o kernel/kernel.a fs/fs.a lib/lib.a net/net.a
fs/minix/minixfs.a arch/i86/kernel/akernel.a arch/i86/lib/lib86.a
arch/i86/mm/mm.a  arch/i86/drivers/char/chr_drv.a
arch/i86/drivers/block/blk_drv.a \
	-t -M -o arch/i86/boot/system > System.tmp ; \
	sort -k4 System.tmp > System.map ; rm -f System.tmp ) 
undefined symbol: _rs_ops

This seems to be defined in arch/i86/drivers/char/serial.c

but inside a:

#ifdef CONFIG_CONSOLE_SERIAL

but it's used in ntty.c within a

#ifdef CONFIG_CHAR_DEV_RS

Paul

  reply	other threads:[~2002-06-06 10:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-06  9:30 Uncompilable Harry Kalogirou
2002-06-06 11:39 ` Uncompilable Alan Cox
2002-06-06 10:56   ` Paul Nasrat [this message]
2002-06-06 18:13   ` Uncompilable Harry Kalogirou
2002-06-06 21:35     ` Uncompilable Riley Williams

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=20020606105631.GB5854@raq465.uk2net.com \
    --to=pauln@truemesh.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox