mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Adam J. Richter" <adam@yggdrasil.com>
To: kai@tp1.ruhr-uni-bochum.de, linux-kernel@vger.kernel.org
Subject: Various kbuild problems in 2.5.22
Date: Tue, 18 Jun 2002 05:18:29 -0700	[thread overview]
Message-ID: <200206181218.FAA08522@adam.yggdrasil.com> (raw)

	I would like to note the following problems with the
kernel build process in 2.5.22, after applying the patch that
Kai Germaschewski posted that enabled modversions to work again.
All but the first one are spurious dependencies.


	1. doing make modversions twice results in bad .ver files, with
lines like:

#define __ver_pcmcia_get_mem_page_Rsmp_3d2ded54 smp_ba03375b
#define pcmcia_get_mem_page_Rsmp_3d2ded54       _set_ver(pcmcia_get_mem_page_Rsmp_3d2ded54)

	...which should be:

#define __ver_pcmcia_get_mem_page smp_ba03375b
#define pcmcia_get_mem_page       _set_ver(pcmcia_get_mem_page)

	2. "make bzImage" does not build a bzImage if any module fails
to compile.  Really, it should not attempt to buidl modules or even
descend into directories that contain only modules.  To build a bzImage,
I have to edit the Makefile and comment out "BUILD_MODULES:=1".

	3. make include/linux/modversios.h aborts if any .c file has
a #error or #include's a .h that is not present (for example, because
the .h is built by the process, as is the case with one scsi driver).

	4. "make -k modules" will not build perfectly buildable modules
in a directory that has a subdirectory where a compile error occurs.

	All of this used to work a couple of kernel versions ago.

Adam J. Richter     __     ______________   575 Oroville Road
adam@yggdrasil.com     \ /                  Milpitas, California 95035
+1 408 309-6081         | g g d r a s i l   United States of America
                         "Free Software For The Rest Of Us."

             reply	other threads:[~2002-06-18 12:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-18 12:18 Adam J. Richter [this message]
2002-06-18 14:24 ` Kai Germaschewski
2002-06-18 15:00 Adam J. Richter
2002-06-18 16:14 ` Kai Germaschewski
2002-06-18 21:23   ` Gerd Knorr
2002-06-19  8:02   ` Martin Dalecki
2002-06-18 17:10 Adam J. Richter
2002-06-18 19:16 ` Sam Ravnborg
2002-06-18 19:28   ` Kai Germaschewski
2002-06-18 20:09     ` Sam Ravnborg
2002-06-19  2:50 Adam J. Richter
2002-06-19  2:56 ` Kai Germaschewski
2002-06-19  2:55 Adam J. Richter
2002-06-19  3:07 Adam J. Richter

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=200206181218.FAA08522@adam.yggdrasil.com \
    --to=adam@yggdrasil.com \
    --cc=kai@tp1.ruhr-uni-bochum.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®