From: Michal Jaegermann <michal@harddata.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.19-pre5
Date: Sat, 30 Mar 2002 18:41:01 -0700 [thread overview]
Message-ID: <20020330184101.A16046@mail.harddata.com> (raw)
In-Reply-To: <20020330134017.A14523@mail.harddata.com> <11078.1017531282@ocs3.intra.ocs.com.au>
On Sun, Mar 31, 2002 at 09:34:42AM +1000, Keith Owens wrote:
> On Sat, 30 Mar 2002 13:40:17 -0700,
> Michal Jaegermann <michal@harddata.com> wrote:
> >
> >On Fri, Mar 29, 2002 at 06:47:39PM -0300, Marcelo Tosatti wrote:
> >>
> >> Here goes pre5.
> >
> >Tried to recompile that on Alpha and I run into module symbol
> >troubles of that sort:
> >
> >depmod: /lib/modules/2.4.19-pre5/kernel/drivers/sound/trident.o: Bad symbol index: 20414130 >= 000000d6
> >depmod: /lib/modules/2.4.19-pre5/kernel/drivers/sound/trident.o: Bad symbol index: 74202a2f >= 000000d6
> >depmod: /lib/modules/2.4.19-pre5/kernel/drivers/sound/trident.o: Bad symbol index: 0a2f2a20 >= 000000d6
> >depmod: Bad symbol index: 20414130 >= 000000d6
> >depmod: Bad symbol index: 74202a2f >= 000000d6
> >depmod: Bad symbol index: 0a2f2a20 >= 000000d6
>
> That is almost always caused by bad output from binutils.
Thanks to the helpful comment from Keith the matter is resolved. The
box in which this happened still has "issues" and apparently decided
that it is time for one of its surprises. That trident.o module
recreated from scratch looks ok.
Thanks,
Michal
next prev parent reply other threads:[~2002-03-31 1:41 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-29 21:47 Linux 2.4.19-pre5 Marcelo Tosatti
2002-03-30 0:11 ` Linux 2.4.19-pre5: bad config Eyal Lebedinsky
2002-03-30 9:06 ` Russell King
2002-03-30 10:19 ` Russell King
2002-03-30 17:46 ` Alan Cox
2002-03-30 19:13 ` Russell King
2002-03-30 0:23 ` Linux 2.4.19-pre5: neofb.c compile failure Eyal Lebedinsky
2002-03-30 20:40 ` Linux 2.4.19-pre5 Michal Jaegermann
2002-03-30 23:34 ` Keith Owens
2002-03-31 1:41 ` Michal Jaegermann [this message]
2002-03-31 0:39 ` Linux 2.4.19-pre5: hotplug config Eyal Lebedinsky
2002-03-31 14:02 ` Alan Cox
2002-03-31 17:53 ` Greg KH
2002-04-01 0:11 ` Alan Cox
2002-04-04 19:50 ` Linux 2.4.19-pre5 Adrian Bunk
2002-04-04 21:41 ` Marcelo Tosatti
2002-04-09 2:42 ` Reworked CONFIG_IDE_TASKFILE_IO help text Thomas Zimmerman
2002-04-09 6:01 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2002-03-30 18:53 Linux 2.4.19-pre5 rwhron
2002-03-30 19:49 ` Andrew Morton
2002-03-30 21:33 ` Randy Hron
2002-03-30 21:42 ` Ed Sweetman
2002-03-30 22:25 ` Randy Hron
2002-03-30 23:48 ` Ed Sweetman
2002-03-31 12:42 ` Randy Hron
2002-03-31 20:05 ` Ed Sweetman
2002-03-31 23:11 ` Randy Hron
2002-03-31 6:52 ` Andrew Morton
2002-04-01 0:36 ` Andrea Arcangeli
2002-04-01 1:24 ` Andrea Arcangeli
2002-04-04 9:08 Tom Holroyd
2002-04-04 19:28 ` Marcelo Tosatti
2002-04-05 4:13 ` Tom Holroyd
2002-04-16 14:49 ` Andrea Arcangeli
2002-04-17 1:22 ` Tom Holroyd
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=20020330184101.A16046@mail.harddata.com \
--to=michal@harddata.com \
--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