mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans-Joachim Baader <hjb@pro-linux.de>
To: linux-kernel@vger.kernel.org
Subject: 2.4.19-rc3 build problem
Date: Sun, 21 Jul 2002 23:41:52 +0200	[thread overview]
Message-ID: <20020721214151.GD27075@mandel.hjbaader.home> (raw)

[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]

Hi!

Please disregard my previous mail. I forgot to run "make oldconfig".
Sorry.

I wanted to report a different problem anyway but I cannot reproduce
it. The error was:

make[2]: Entering directory `/mnt/linux-2.4.19-rc3/drivers/scsi'
mkdir -p /lib/modules/2.4.19-rc3/kernel/drivers/scsi/
cp aha1542.o g_NCR5380.o ppa.o sg.o sr_mod.o st.o /lib/modules/2.4.19-rc3/kernel/drivers/scsi/
cp: aha1542.o: No such file or directory
make[2]: *** [_modinst__] Error 1
make[2]: Leaving directory `/mnt/linux-2.4.19-rc3/drivers/scsi'
make[1]: *** [_modinst_scsi] Error 2
make[1]: Leaving directory `/mnt/linux-2.4.19-rc3/drivers'
make: *** [_modinst_drivers] Error 2

during "make modules_install". In this configuration, aha1542 was disabled
and I did a "make oldconfig" and "make menuconfig", "make dep", and
"make clean" before the build.

Could there be a problem when the previous kernel configuration has
CONFIG_SCSI_AHA1542=m and then a new configuration with CONFIG_SCSI_AHA1542
off is created?

Regards,
hjb
-- 
Pro-Linux - Germany's largest volunteer Linux support site
http://www.pro-linux.de/          Public Key ID 0x3DDBDDEA

[-- Attachment #2: Type: application/pgp-signature, Size: 200 bytes --]

             reply	other threads:[~2002-07-21 21:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-21 21:41 Hans-Joachim Baader [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-21 21:05 Hans-Joachim Baader

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=20020721214151.GD27075@mandel.hjbaader.home \
    --to=hjb@pro-linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®