From: Franz Sirl <Franz.Sirl@munich.netsurf.de>
To: Tom Vier <thomassr@erols.com>
Cc: Tom Vier <thomassr@erols.com>,
mklinux-development-system@public.lists.apple.com,
mklinux-setup@public.lists.apple.com,
linuxppc-dev@lists.linuxppc.org
Subject: Re: egcs-1.1.1-1c bug (was Re: major ksyms problem)
Date: Tue, 23 Feb 1999 16:00:01 +0100 [thread overview]
Message-ID: <4.1.19990223155132.049de8f0@mail.lauterbach.com> (raw)
In-Reply-To: <Pine.LNX.4.05.9902220928100.405-100000@localhost.erols.com >
At 15:36 22.02.99 , Tom Vier wrote:
>
>it's an egcs bug. i think it's not aligning instructions properly, cuz
>i believe the 601 is more strict about alignment. is anyone having
>problems using bsd_comp.o, ppp_deflate.o, and hfs.o on a non-601
>machine built under pre-R5 (egcs-1.1.1-1c)?
What makes you think that it is an egcs bug? I have no problems on 601
(7200/75) with any of the modules you listed. Are you sure you have the
latest modutils (2.1.121 or later) installed?
>i rebuilt bsd_comp.o and ppp_deflate.o w/ egcs-1.0-2e from dr3 and
>they worked perfectly.
>
>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.
>
>is this a know problem?
>
>> > 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.
Franz.
[[ 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 ]]
next prev parent reply other threads:[~1999-02-23 15:00 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 [this message]
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
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=4.1.19990223155132.049de8f0@mail.lauterbach.com \
--to=franz.sirl@munich.netsurf.de \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mklinux-development-system@public.lists.apple.com \
--cc=mklinux-setup@public.lists.apple.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).