From: Eyal Lebedinsky <eyal@eyal.emu.id.au>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19pre8aa2
Date: Sun, 05 May 2002 17:40:56 +1000 [thread overview]
Message-ID: <3CD4E208.181AE989@eyal.emu.id.au> (raw)
In-Reply-To: <2661.1020567877@ocs3.intra.ocs.com.au>
Keith Owens wrote:
>
> On Sun, 05 May 2002 09:34:25 +1000,
> Eyal Lebedinsky <eyal@eyal.emu.id.au> wrote:
> >I agree with this. However, since this driver cannot be built, and
> >since the latest modutils will exit badly for unresolved, I strongly
> >believe that the comx driver should not be offered (disable it in
> >the Config.in) until it is fixed - 2.4 being a stable kernel.
> >
> >I had to wrap 'depmod' with a script to ignore failures in order
> >to get through a full build (which includes the kernel plus a few
> >extra modules like NVdriver, dc395, lm_sensors).
>
> You should not have to wrap depmod. Standard 2.4.* modutils returns 0
> for unresolved errors, for compatibility with previous behaviour. You
> have to do depmod -u to get a non-zero return code. The -u flag was
> added in modutils 2.4.7 and defaults to off. In modutils 2.5 it will
> default to on, that will break code that relies on the existing
> behaviour. I will not change modutils default behaviour in 2.4.
>
> So why is your version of depmod breaking? Either you are specifying
> -u or your distribution has hacked depmod to default -u to on. Check
> depmod.c for variable flag_unresolved_error, it should default to 0.
You are right, it is not the unresolved that caused it but the non
ELF objects in there (it used not to care before):
# /sbin/depmod-2.4.15 -ae ; echo $?
depmod: /lib/modules/2.4.19-pre8-aa2/ksyms is not an ELF file
depmod: /lib/modules/2.4.19-pre8-aa2/soundconf is not an ELF file
1
--
Eyal Lebedinsky (eyal@eyal.emu.id.au) <http://samba.org/eyal/>
next prev parent reply other threads:[~2002-05-05 7:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-04 14:54 2.4.19pre8aa2 Andrea Arcangeli
2002-05-04 15:02 ` 2.4.19pre8aa2 Christoph Hellwig
2002-05-04 23:34 ` 2.4.19pre8aa2 Eyal Lebedinsky
2002-05-05 3:04 ` 2.4.19pre8aa2 Keith Owens
2002-05-05 7:40 ` Eyal Lebedinsky [this message]
2002-05-05 8:04 ` 2.4.19pre8aa2 Keith Owens
2002-05-05 8:16 ` 2.4.19pre8aa2 Keith Owens
2002-05-05 13:38 ` 2.4.19pre8aa2 Eyal Lebedinsky
2002-05-05 0:25 ` 2.4.19pre8aa2 Andrea Arcangeli
2002-05-04 18:56 ` 2.4.19pre8aa2 Francois Romieu
2002-05-05 0:14 ` 2.4.19pre8aa2 Andrea Arcangeli
2002-05-08 2:27 ` 2.4.19pre8aa2 Pozsar Balazs
2002-05-08 9:34 ` 2.4.19pre8aa2 Andrea Arcangeli
2002-05-08 9:46 ` Problems with mm on Alpha Oliver Pitzeier
2002-05-08 10:54 ` Ivan Kokshaysky
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=3CD4E208.181AE989@eyal.emu.id.au \
--to=eyal@eyal.emu.id.au \
--cc=kaos@ocs.com.au \
--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®