All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Luc Coulon <jean-luc.coulon@wanadoo.fr>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.30 does not build cleanly
Date: Fri, 02 Aug 2002 12:36:00 +0200	[thread overview]
Message-ID: <3D4A6090.AA67CB08@wanadoo.fr> (raw)
In-Reply-To: 20020802090831.GB1055@suse.de

Hi Jens,

TU for the tip but I still have one unresolved symbol :

make[3]: Leaving directory `/usr/src/kernel-source-2.5.30/arch/i386/pci'
if [ -r System.map ]; then /sbin/depmod -ae -F System.map -b
/usr/src/linux/debian/tmp-image -r 2.5.30; fi
depmod: *** Unresolved symbols in
/usr/src/linux/debian/tmp-image/lib/modules/2.5.30/kernel/arch/i386/kernel/apm.o
depmod: 	cpu_gdt_table
make[2]: *** [_modinst_post] Erreur 1
make[2]: Leaving directory `/usr/src/kernel-source-2.5.30'
make[1]: *** [real_stamp_image] Erreur 2

-----
regards
	Jean-Luc

Jens Axboe wrote:
> 
> On Fri, Aug 02 2002, Jean-Luc Coulon wrote:
> > Hi,
> >
> > I get the following messages :
> >
> > make[3]: Leaving directory `/usr/src/kernel-source-2.5.30/arch/i386/pci'
> > if [ -r System.map ]; then /sbin/depmod -ae -F System.map -b
> > /usr/src/linux/debian/tmp-image -r 2.5.30; fi
> > depmod: *** Unresolved symbols in
> > /usr/src/linux/debian/tmp-image/lib/modules/2.5.30/kernel/arch/i386/kernel/apm.o
> > depmod:       cpu_gdt_table
> > depmod: *** Unresolved symbols in
> > /usr/src/linux/debian/tmp-image/lib/modules/2.5.30/kernel/drivers/block/floppy.o
> > depmod:       elv_queue_empty
> > depmod: *** Unresolved symbols in
> > /usr/src/linux/debian/tmp-image/lib/modules/2.5.30/kernel/drivers/block/nbd.o
> > depmod:       elv_queue_empty
> > depmod: *** Unresolved symbols in
> > /usr/src/linux/debian/tmp-image/lib/modules/2.5.30/kernel/drivers/scsi/scsi_mod.o
> > depmod:       elv_queue_empty
> > make[2]: *** [_modinst_post] Erreur 1
> > make[2]: Leaving directory `/usr/src/kernel-source-2.5.30'
> > make[1]: *** [real_stamp_image] Erreur 2
> 
> fixes the elv_queue_empty one
> 
> --- linux/drivers/block/elevator.c~     2002-08-02 11:07:33.000000000 +0200
> +++ linux/drivers/block/elevator.c      2002-08-02 11:07:49.000000000 +0200
> @@ -482,5 +482,6 @@
>  EXPORT_SYMBOL(__elv_add_request);
>  EXPORT_SYMBOL(elv_next_request);
>  EXPORT_SYMBOL(elv_remove_request);
> +EXPORT_SYMBOL(elv_queue_empty);
>  EXPORT_SYMBOL(elevator_exit);
>  EXPORT_SYMBOL(elevator_init);
> 
> --
> Jens Axboe

      reply	other threads:[~2002-08-02 10:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-02  8:20 2.5.30 does not build cleanly Jean-Luc Coulon
2002-08-02  9:08 ` Jens Axboe
2002-08-02 10:36   ` Jean-Luc Coulon [this message]

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=3D4A6090.AA67CB08@wanadoo.fr \
    --to=jean-luc.coulon@wanadoo.fr \
    --cc=axboe@suse.de \
    --cc=linux-kernel@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.