All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andrew Linfoot" <andy@derfel99.freeserve.co.uk>
To: "linux" <linux@cthulhu.engr.sgi.com>
Subject: Kernel Build Problem
Date: Fri, 11 Jun 1999 11:44:40 +0100	[thread overview]
Message-ID: <000901beb3f7$6be730c0$0a02030a@snafu> (raw)

Hi,

I'm trying to build the 2.2.1 kernel with sound support enabled and i get
the following warnings:

sound_firmware.c: In function `do_mod_firmware_load':
sound_firmware.c:23: warning: implicit declaration of function `lseek'
sound_firmware.c:38: warning: implicit declaration of function `read'

and then during the final link:

drivers/sound/sound.a(sound_firmware.o): In function `do_mod_firmware_load':
sound_firmware.c(.text+0x84): undefined reference to `lseek'
sound_firmware.c(.text+0x84): relocation truncated to fit: R_MIPS_26 lseek
sound_firmware.c(.text+0xc4): undefined reference to `lseek'
sound_firmware.c(.text+0xc4): relocation truncated to fit: R_MIPS_26 lseek
sound_firmware.c(.text+0xfc): undefined reference to `read'
sound_firmware.c(.text+0xfc): relocation truncated to fit: R_MIPS_26 read
make: *** [vmlinux] Error 1

I can compile OK with/without modules and sound disabled.

Is this fixed in the 2.2.9 kernel and if so will an archive of 2.2.9 be made
available on linus? (I don't have CVS access from my development box at the
moment).

Any help would be appreciated.

Thanks
Andy

Andrew Linfoot
Tel: +44 (0)114 265 0251
Mobile: +44 (0)7974 299 545

             reply	other threads:[~1999-06-11 10:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-11 10:44 Andrew Linfoot [this message]
     [not found] <2A9AA9C52024F94A96634E39B9858FF166B969@empwilex1.empirix.com>
2004-09-01 16:23 ` Kernel build problem Vladimir G. Ivanovic
2004-09-01 18:45   ` Erik Mouw
2004-09-01 18:50   ` Bryan Henderson
  -- strict thread matches above, loose matches on Subject: below --
1998-12-22 23:26 kernel " Alex deVries
1998-12-23  4:44 ` ralf
1998-12-24 15:31   ` Alex deVries
1998-12-25 17:14     ` ralf
1998-12-26  4:08       ` Alex deVries

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='000901beb3f7$6be730c0$0a02030a@snafu' \
    --to=andy@derfel99.freeserve.co.uk \
    --cc=linux@cthulhu.engr.sgi.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 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.