From: Michel Lanners <mlan@cpu.lu>
To: thomassr@erols.com
Cc: nester@erols.com, Franz.Sirl@munich.netsurf.de,
mklinux-development-system@public.lists.apple.com,
linuxppc-dev@lists.linuxppc.org
Subject: Re: egcs-1.1.1-1c bug (was Re: major ksyms problem)
Date: Wed, 24 Feb 1999 08:14:18 +0100 (CET) [thread overview]
Message-ID: <199902240714.IAA00361@piglet.cpu.lu> (raw)
In-Reply-To: <Pine.LNX.4.05.9902231559510.6465-100000@localhost.erols.com>
On 23 Feb, this message from Tom Vier echoed through cyberspace:
[snip]
>> >egcs-1.1.1-1c failed using -O0, -O2, and -O3 with all combinations of
>> >-mcpu=601, -mcpu=604, and -fno-schedule-insns. -fpic did work, however
>> >it addes an offset table symbol that makes insmod complain.
>> >> > Feb 21 09:36:18 zero insmod: /lib/modules/2.0.37-osfmach3/net/bsd_comp.o:
>> >> > Unhandled relocation of type 26 for .L343
>>
>> Is "Unhandled relocation of type 26" the behaviour for standard compilation
>> or for -fpic? You can't compile a kernel/modules with -fpic and expect
>> modutils still to work, modutils only handles the minimum necessary
>> relocation types.
Just to make sure we all talk about the same things, there was an issue
with relocation of kernel modules some time ago when we moved to a
newer version of egcs, which needed a newer version of modutils to be
able to handle that new relocation.
The modutils version to use is 2.1.121. If nowhere else, you can find a
binary on my site (see below).
Now, I may be completely off track, and this problem now is something
completely different ;-)
Michel
-------------------------------------------------------------------------
Michel Lanners | " Read Philosophy. Study Art.
23, Rue Paul Henkes | Ask Questions. Make Mistakes.
L-1710 Luxembourg |
email mlan@cpu.lu |
http://www.cpu.lu/~mlan | Learn Always. "
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
prev parent reply other threads:[~1999-02-24 7:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.05.9902220432430.2138-100000@localhost.erols.com>
1999-02-22 14:36 ` egcs-1.1.1-1c bug (was Re: major ksyms problem) Tom Vier
1999-02-23 7:22 ` Gary Thomas
1999-02-23 12:24 ` Tom Vier
1999-02-23 20:53 ` Tom Vier
[not found] ` <Pine.LNX.4.05.9902220928100.405-100000@localhost.erols.com >
1999-02-23 15:00 ` Franz Sirl
1999-02-23 21:06 ` Tom Vier
1999-02-23 21:15 ` Franz Sirl
1999-02-24 9:53 ` Gary Thomas
1999-02-24 16:06 ` Franz Sirl
1999-02-25 2:20 ` Tom Vier
1999-02-24 18:40 ` Tom Vier
1999-02-24 7:14 ` Michel Lanners [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=199902240714.IAA00361@piglet.cpu.lu \
--to=mlan@cpu.lu \
--cc=Franz.Sirl@munich.netsurf.de \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mklinux-development-system@public.lists.apple.com \
--cc=nester@erols.com \
--cc=thomassr@erols.com \
/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.